accessibilty for hearing impaired (vom 16. Januar, abgerufen am 17. Januar 2019)
Dieser Artikel stößt bei mir auf offene Ohren. Nachdem ich das Buch der Autorin gelesen (und mir ein Exemplar gekauft) habe, folge ich dem Blog.
Ich möchte daher meinen Kommentar auch hier festhalten:
cool that you share your thoughts on this. I’m coming from an engineering background and have a kid with hearing impairment. Thus I dig into it and learned quite a lot about accessibility on the web (development).
So here are some questions which could trigger further thoughts:
- Why should I bother? According to WHO ~15% of the world population has some kind of disability. That is 1 out of 7!
- But my audience does not have a disability! Could be, but you’re not only developing for them. The larger audience will benefit as well. Take the Closed Captions / Subtitles you’ve mentioned in the article. People will be able to use them if they’re in a noisy an environment and can’t turn on volume. Or high colour contrast, which is beneficial outside under direct sunlight, too.
- Okay so what shall I do? Learn more about it. As I said in the beginning I’ve researched solutions on the web. There you’ll find agencies like Knowbility, WebAIM or The Paciello Group. Some offer work for you, while others could facilitate a panel with people with special needs.
- But I don’t want to hire an agency - after all there are tools! True, you can find tools like web-axe, tenon.io or Lighthouse. But those can cover only 30% (don’t quote me on that) of all defects. Testing with real users is paramount!
Oh, an important fact. I know some groups of people who don’t like to be called disabled. A better word would be impaired. Because it’s not a defect of some sort but rather society standing in the way. Yes, you can be really smart AND disabled.
I can’t talk about accessibility outside the web. However I’ve heard about Tagged PDFs and MS Office Suite offering a mode to discover some accessibility issues.
Hope that helps