HNHacker News
TopNewBestAskShowJobs

zichy

841 karma · joined August 14, 2014

submissionscomments
zichy··on W3.css – A minimal alternative to Bootstrap
>All css frameworks really should prefix their classes so you can mix them.

I don't believe that would work out.

zichy··on MVP.css – Minimalist stylesheet for HTML elements
I'm not sure why you are so insistent. Of course it is important for accessibility. I have also worked for government sites, conducted a11y tests myself, and worked with independent auditors from Canada and Germany. Semantic HTML is a very basic but critical part. See https://www.w3.org/WAI/WCAG21/Understanding/info-and-relatio....
zichy··on MVP.css – Minimalist stylesheet for HTML elements
Hey, thanks for commenting!

* I think everything regarding the `aside` elements has already been said in the GitHub issue: It's context specific and you can't determine in advance if a certain (card) element is part of the main content or not. Therefore, `aside` should only be used if needed. (The top three cards on the MVP.css homepage definitely are part of the main content for example.)

* Your `a i` and `a strong` solutions are pretty unusual and they show the limit of what is possible using a classless CSS. I would have preferred staying even more minimalist and simply pass on button-like links.

* You could think about adding the underlining for links in continuous text. See https://www.w3.org/TR/WCAG20-TECHS/F73.html.

I'm not trying to be a dick about it since it's your personal project and I am not forced to use it – but I am not sure why the framework had to be classless and usable for a MVP all at once. I absolutely love classless CSS for simple/personal websites, but I associate MVPs (products) and rapid prototyping with more extensive and interactive interfaces than the typical text-based onepager.

zichy··on MVP.css – Minimalist stylesheet for HTML elements
I was referring to the global page header/footer you were talking about, should've made that more clear. Obviously you are allowed to use multiple `<header>` and `<footer>` elements on the same page.

While it is true that HTML semantics aren't as stringent as often assumed, there certainly are more or less universally accepted best practices. They depend on the complexity of the site itself. (It may also be unclear what a "page header" actually is. It could contain your logo and navigation, but the `<h1>` should rather be in the `<main>` element.)

So this is what my most basic structure inside the `<body>` would look like:

  <header></header>
  <main></main>
  <footer></footer>
If you're doing this with the global page header/footer, there would be no reason to use `<main>` at all:

  <main>
    <header></header>
    <footer></footer>
  </main>

Also, I can't really reproduce your initial issue regarding the flexibility of page spacing. You are pretty limited when using classless CSS, but where's the problem using the body selector for that?
zichy··on MVP.css – Minimalist stylesheet for HTML elements
It is not true that they do have hardly any impact on accessibility. But if you want to go that way: MVP.css uses `<label>` instead of `<fieldset>`/`<legend>`. See https://www.w3.org/TR/WCAG20-TECHS/H71.html.
zichy··on MVP.css – Minimalist stylesheet for HTML elements
The problem of using semantic elements incorrectly remains. The front page states "just semantic HTML and you're done" which is wrong.

I know that it is called "MVP", but firstly the term viability can mean different things and secondly there's no indication that the markup is implemented incorrectly. I love to check out example/demo pages from CSS frameworks and it's not uncommon to see glaring semantic errors in the HTML. People just copy everything that is presented to them and you should make sure to give them a good introduction.

zichy··on MVP.css – Minimalist stylesheet for HTML elements
But putting the `<header>` and `<footer>` inside the `<main>` element is not semantically correct. If it would be, you wouldn't need `<main>`. That's exactly why there's a very basic limit to classless CSS frameworks.
zichy··on MVP.css – Minimalist stylesheet for HTML elements
That's a nice way to say "I don't care about accessibility".
zichy··on I'm Publishing My Next Book on Substack
Using this as an opening sentence without any irony is the worst thing I ever read.
zichy··on Google Maps launches Street View in India
Speaking of Geoguessr, I can definitely recommend Geotastic[1] – a free and donor-funded alternative.

[1]: https://geotastic.net

zichy··on Ask HN: Why are privacy coins like Monero not seeing wide adoption?
Having the supposed foresight, I can tell that cryptocurrencies are definitely part of the dystopia.
zichy··on Where's the fun in accessibility?
>get rid of the buzzwords such as 'SEO' and 'accessibility' to just think of putting the customer first

>a customer first ethos and not treat them as 'disabled'

That's a weird way of phrasing it. It sounds to me like you try to play accessibility and customer focus against each other. I'd argue that speaking about "customers" instead of "humans" is counterproductive and only some kind of commercial websites like online shops could be compared to a retail businesses. Also, "accessibility" is not a buzzword.

Maybe you could get comfortable with the term universal/inclusive design?

https://sayyeah.com/digital-insights/universal-design-access...

>Text might be below the size Google deems 'accessible'

Which Google guidelines you are referring to?

>Making that text big and chunky might upset designers who want the customer to be browsing by pictures not words.

Do you assume good design and accessibility can't go together? Developing an accessible product generally means that ideally everyone involved has some basic knowledge about a11y. I totally agree that using "SEO" to justify certain decisions is (almost always) a bad idea. Referring to detailed guidelines like the WCAG may be helpful in order to get everyone on board. Obviously designers will get frustrated when told without explanation or context that their design needs to be changed in favor of a11y.

zichy··on Writing my PhD using groff
This together with some padding could help:

  <meta name="viewport" content="width=device-width, initial-scale=1">
zichy··on Ask HN: How did you increase your UX skills?
Question yourself every step of the way if you are creating barriers for anyone.

To get your started, I recommend this short summary about universal design, inclusive design, and accessibility:

https://sayyeah.com/digital-insights/universal-design-access...

zichy··on Rowan Atkinson: Visual Comedy (1992) [video]
Trying to be edgy is truly terrible as well.
zichy··on Show HN: Logto beta – build universal sign-in, auth, and identity with ease
Please keep accessibility in mind when creating forms. I just checked out the demo app and you are using `placeholder` instead of `label`.
zichy··on Show HN: I built a tiny platform where you can say anything you want
Finally, a platform where you can say anything you want created by "a bunch of bored incels". And I can already see holocaust denial and transphobia.
zichy··on Show HN: I made a site that shows jobs where you can work pseudonymously
The fact that there are many bullshit companies out there does not change the fact that all web3/blockchain companies are bullshit.
zichy··on Show HN: I made a site that shows jobs where you can work pseudonymously
Every single job posting is from a weird crypto bullshit company. Great.
zichy··on Shinobi – A Text-Based RSS Blogging System
https://news.ycombinator.com/item?id=31372373
zichy··on This site is now a “shinobi website”
I totally get the minimalist approach to websites, but using plain text instead of semantic HTML elements means giving up accessibility. People who rely on screen readers will not be able to read your content in a pleasant way.
zichy··on Show HN: Recipe search engine, built in vanilla PHP
Nice work! I have two suggestions usability-wise:

* Make sure your navigation is consistent. The left filter links and the about/contact links are missing on many pages. A breadcrumb would help as well.

* The horizontal tabs on the recipe pages aren't really useful, I'd display all content at once. No need to force the users to click several times. Even on smaller viewports it's easier to just scroll.

zichy··on Show HN: HTML/CSS Photo Sheet
Really nice showcase. While I like non-JS solutions, some kind of JavaScript is almost always needed when creating interactive elements to ensure accessibility.
zichy··on Show HN: Aeon – a lightweight date picker built with web components
Good job so far, it feels very lightweight and simple. It works well with different input devices, but the accessibility for screen readers could be improved:

* The first day immediately gets focused when opening the datepicker. It might be a bit confusing to just hear a number.

* There's enough space to spell the months in full.

* Use semantic abbrevations for weekdays, e.g. `<abbr title="Monday">Mo</abbr>`.

* Use `label`s which refer to the corresponding `select`.

* Use `table` instead of `div`s for the calendar view.

* Use (hidden) text instead of the `title` attribute in buttons.

Furthermore:

* Try using more unique classes for your elements, e.g. '.aeon-datepicker__select' instead of '.select'.

* `cursor: pointer` for buttons would be helpful to see how large the click area is.

zichy··on Is Prison Necessary?
>I don’t think anyone outside academia values the lives of murderers very much

What.

zichy··on Free web kits for fast web design and development – Uix Kit 3.5 Released
Jesus, there is just so much going on. The drop-down menu is huge and too tall for my browser window. I clicked through some of the components, you should learn some basics about accessibility.

(Also, this is your third time promoting this "kit". Maybe read up on the Show HN guidelines[1].)

[1]: https://news.ycombinator.com/showhn.html

zichy··on Luda: A lightweight and responsive UI framework for modern web development
1. I get that short and simple code snippets are important in order to understand the fundamentals of a framework, but people with little experience will just copy the code in your documentation 1:1. I believe that semantic and accessible code snippets are very important. The way you constructed some elements[1] also suggests that there are no labels necessary.

2. & 3. There seems to be a general misunderstanding with a lot of frameworks about what needs to be customized. Native browser elements are always to be preferred - they are known by the users, accessible, and just work. Custom elements often are a lot more about design than usability and not wanting to "break" the designer's creation. A server-sided validation is of course necessary in both cases nevertheless. Custom client-sided validation can be useful in complex forms though.

3. You’re right, there are examples of both custom and native select elements.

4. Cool, thanks!

[1] e.g. https://oatw.github.io/luda/0.1.x/elements/form#select-field

zichy··on Luda: A lightweight and responsive UI framework for modern web development
Thanks! Besides, please consider to make headlines bold again. That would help a lot with content hierarchy.
zichy··on Luda: A lightweight and responsive UI framework for modern web development
Whenever I stumble upon yet another UI/CSS framework, I always check the form elements first. Here we go.[1]

* _Every_ input needs a <label>.

* Use the `for` attribute to connect labels and inputs.

* Placeholders are not a replacement for labels. You don’t need placeholders just for the sake of it.[2]

* Do not build custom form elements if it can be done without them. There is no need for the dropdown, just use <select>.

* Do use <fieldset> and <legend> to group multiple checkbox/radio inputs.

* Error texts should be connected to the particular input via `aria-describedby`.

* Do use the `required` attribute if form fields are mandatory.

[1]: https://oatw.github.io/luda/0.1.x/elements/form, https://oatw.github.io/luda/0.1.x/patterns/form-group

[2]: https://www.w3.org/WAI/tutorials/forms/instructions/#placeho...

zichy··on Luda: A lightweight and responsive UI framework for modern web development
Raleway is such a poor typeface choice. They even forgot to import the italic styles from Google.
← PreviousPage 2 of 5Next →