Earlier quoted context omitted.
I don't know whether you are some miserable provocateur or just an idiot. Either way, that was a very bad analogy. And I don't say 'bad' with a moral connotation. It was just stupid, really. I see that you maybe were alluding to the fact that blind people can't SEE the page, but you ignore that they can READ it with assistance of software/hardware in a variety of ways. The article goes in detail about that.
While I completely agree with you, your comment isn't very constructive. It attacks the user, informs him his argument is weak, and provides no argument or counterpoint to the discussion.
How to design websites for blind and partially sighted people
11–20 of 21 posts
Re: How to design websites for blind and partially sighted people
#12Accessibility (a11y) is an interesting and exciting topic, but it's exhausting to see yet another SEO guy to add his two cents about it. From a technical point of view, web a11y is almost exclusively about semantics or machine readability. There are two kinds of machines: web crawlers and screen readers for visually impaired humans. For whom would you like to work? You are not magically improving a11y by doing good S…
I've had a couple US clients specifically request "ADA compliance".
Re: How to design websites for blind and partially sighted people
#13Accessibility (a11y) is an interesting and exciting topic, but it's exhausting to see yet another SEO guy to add his two cents about it. From a technical point of view, web a11y is almost exclusively about semantics or machine readability. There are two kinds of machines: web crawlers and screen readers for visually impaired humans. For whom would you like to work? You are not magically improving a11y by doing good S…
The US government also put out a set of accessibility guidelines: https://www.ada.gov/pcatoolkit/chap5toolkit.htm I've had a couple US clients specifically request "ADA compliance".
Re: How to design websites for blind and partially sighted people
#14Grey text is all the rage these days, as are gray backgrounds. Dark grey text on a light grey background is difficult for many fully-sighted people to read, yet it persists on many websites (including HN — the visited link at the top of the page is #828282 and it's presented on a background of #F6F6F0. This yields a contrast ratio of 3.54:1, well shy of the recommended 4.5:1.)
The contrast problem also manifests on websites that have scrolling background images, which move underneath text and can create tricky contrast issues. Ironically, I've even seen these problems on accessibility-focused websites.
To be honest, I'm not sure how to fully solve this problem. I think as long as scrolling background images are popular, this will continue to be an issue. The only "fix" I can think of is to only use images that are mostly light or mostly dark, so that a single color of text can comfortably be read on top of them. But most images that people like to use in this scrolling are bright and dynamic, with light regions and dark regions. This doesn't bode well for text contrast or accessibility.
Re: How to design websites for blind and partially sighted people
#15Re: How to design websites for blind and partially sighted people
#16Accessibility (a11y) is an interesting and exciting topic, but it's exhausting to see yet another SEO guy to add his two cents about it. From a technical point of view, web a11y is almost exclusively about semantics or machine readability. There are two kinds of machines: web crawlers and screen readers for visually impaired humans. For whom would you like to work? You are not magically improving a11y by doing good S…
The US government also put out a set of accessibility guidelines: https://www.ada.gov/pcatoolkit/chap5toolkit.htm I've had a couple US clients specifically request "ADA compliance".
Re: How to design websites for blind and partially sighted people
#17Earlier quoted context omitted.
The US government also put out a set of accessibility guidelines: https://www.ada.gov/pcatoolkit/chap5toolkit.htm I've had a couple US clients specifically request "ADA compliance".
Is there a verifier/validator that will flag misuses/non compliance? Even if it's an incomplete set of misuses, it would still be useful.
Its a CLI tool that inspects HTML pages and determines if it meets a limited number of WCAG checks.
https://github.com/data61/wcag-zoo
Here is an ASCIInema that shows how it works (which I should embed in the readme)
https://asciinema.org/a/104903
It was mostly build so I could add it to my CI builds to check WCAG compliance and stop deploys that didn't meet it.
Re: How to design websites for blind and partially sighted people
#18Making websites for the blind sounds a lot like 'making music for the deaf'. It can be done and people are doing it, but it just seems like the most inefficient thing to do.
Re: How to design websites for blind and partially sighted people
#19I actually made a chrome ext that uses im2txt to help blind/partially sighted individuals get scene descriptions for images. Perhaps that can make up for the fact that a lot of devs don't take the time to write alt tags for their images. http://abhinavsuri.com/aat
Re: How to design websites for blind and partially sighted people
#20Earlier quoted context omitted.
Is there a verifier/validator that will flag misuses/non compliance? Even if it's an incomplete set of misuses, it would still be useful.
I built a tool that does just this. Its a CLI tool that inspects HTML pages and determines if it meets a limited number of WCAG checks. https://github.com/data61/wcag-zoo Here is an ASCIInema that shows how it works (which I should embed in the readme) https://asciinema.org/a/104903 It was mostly build so I could add it to my CI builds to check WCAG compliance and stop deploys that didn't meet it.
My $.02 from an uneducated view on this topic is that it would be nice to be able to have a mode to "test the whole zoo" or "the whole zoo, excluding: '...' ". The zoo metaphor is a little odd btw.