5 ms·
Definitely agree accessibility is important going into 2019. Different users are going to be viewing a site with more screen readers, dark theme, and other alte
by droobles 8y ago
Definitely agree accessibility is important going into 2019. Different users are going to be viewing a site with more screen readers, dark theme, and other alternative viewing options, very much like we saw with mobilegeddon and the advent of responsive design. I've seen the argument that this hurts the "intended web experience", but this can be solved by keeping up with modern CSS practices and crafting the experience with screen readers in mind.
Good stuff, thank you for sharing.
- deleted 8y ago[deleted]
- nickbee 8y agoHow does HN stack up in terms of accessibility? Anyone using a screen reader with HN? What do you wish was different?
- Pfhreak 8y agoI struggle with how low contrast it is. I skip 'Ask HN' style posts because they are too hard to read.
- krapp 8y ago> I skip 'Ask HN' style posts because they are too hard to read. That's done on purpose to discourage people from posting (or reading) them too often. PG was afraid letting people write text posts would lead to "blogging."
- joshstrange 8y agoCan we get a source on this? Not disputing but I had never heard that before and it's interesting.
- krapp 8y agohttps://news.ycombinator.com/item?id=468471 https://news.ycombinator.com/item?id=468471
- alistairSH 8y agoWow, that's a ridiculously user-hostile approach to the problem.
- nickbee 8y agoHN was designed for a small audience, and it intentionally did things to discourage growth. The goal was to preserve the community for longer.
- alistairSH 8y agoI understand the reason. That doesn't make it any less hostile to users with poor eye-sight.
- krapp 8y agoIf Hacker News wanted to discourage growth, they should have made the forum private and invite only. There was never any real chance of this forum going mainstream, not because it was too ugly and awkward but because it didn't have any mainstream appeal. Negative reinforcements like making the text purposely difficult to read mostly just punish existing users.
- Pfhreak 8y agoInteresting. I mean, it works, I don't read those posts at all...
- Noumenon72 8y agoI suggest highlighting the text to read in reverse video.
- jolmg 8y agoI wish the nesting of replies were visible in elinks. I just see one post after another in a linear fashion. I can't tell which post is a reply to which. That nesting is visible on w3m, though, so that's neat. Still, I can't seem to be able to collapse thread branches because it requires javascript. That's a shame. I wonder if w3m would recognize something like: .collapse:checked + .content-and-replies-container { display: none; }
- jameslk 8y agoI agree we need to give accessibility more priority and we likely will once the discrimination lawsuits start rolling in. But this isn't an accessibility issue. Nowhere in WCAG 2 will you find anything that explicitly outlines both color and background color need to defined in stylesheets. This is for users who prefer dark themes who are overriding styles of websites incorrectly. It is a failing of the user's browser/OS for not explicitly overriding both background and color at the same time or neither. If every developer had to add in a color for the edge case that someone is overriding styles globally, then we'd be bloating stylesheets with extra unnecessary bytes.
- luuio 8y agoYou got it backward. The custom CSS of the website is overriding the system styles in this case. Let's take font-family for example. Just because you're setting the font for your input[text] tags doesn't mean the browser will also automatically set the font for other elements to match the style. If you want the website to have uniform look, then you'll need to set the font-family for other elements, too.
- jameslk 8y agoThis is really just the old debate of whether to use a reset css in disguise. It has nothing to do with accessibility.
- alistairSH 8y agoNowhere in WCAG 2 will you find anything that explicitly outlines both color and background color need to defined in stylesheets. WCAG doesn't specify implementation, but WCAG 1.4.3 does require a minimum contrast ratio[0]. If the site allows black text on a black background, it will fail that requirement. 0 - https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-cont...