A new, lightweight datepicker widget, Pickadate.js, was released recently, and caused a few people to contact its creator, @Amsul, regarding a lack of accessibility features in the code. His reply was quite depressing:
Our target market doesn’t need it [accessibility], so its safe for us to use.
Most of us, I’m sure, would admit that we could do a better job of making our websites accessible, but to actively state that a11y isn’t required seems wilfully stupid. I don’t know how you get to serve pages only to your target market. I mean, this is the web; it’s public; stuff gets everywhere.
Through sheer serendipity I read an article by Karl Groves about an hour later, which states clearly why a11y should be something you concern yourself with: Yes, actually, it may be you one day. He sums it up perfectly:
If you market or develop ICT products and services and you’re still ignoring accessibility, you’re ignoring the coming reality. One day it will be you, or someone you know and love.
RT @stopsatgreen: Blogged: Accessibility isn’t optional http://t.co/oAVwMrCh
dannyamey [November 22nd, 2012, 11:19]
RT @stopsatgreen: Blogged: Accessibility isn’t optional http://t.co/oAVwMrCh
onishiweb [November 22nd, 2012, 11:20]
RT @stopsatgreen: Blogged: Accessibility isn’t optional http://t.co/oAVwMrCh
pekingspring [November 22nd, 2012, 11:24]
RT @stopsatgreen: Blogged: Accessibility isn’t optional http://t.co/oAVwMrCh
anagasston [November 22nd, 2012, 12:44]
[…] Hacker News http://www.broken-links.com/2012/11/22/accessibility-isnt-optional/ This entry was posted in Uncategorized by admin. Bookmark the […]
Accessibility isn’t Optional | My Daily Feeds [November 22nd, 2012, 12:57]