Accessibility isn’t Optional
A new, lightÂweight datepickÂer widÂget, Pickadate.js, was released recentÂly, and caused a few peoÂple to conÂtact its creÂator, @Amsul, regardÂing a lack of accesÂsiÂbilÂiÂty feaÂtures in the code. His reply was quite depressing:
Our tarÂget marÂket doesÂn’t need it [accesÂsiÂbilÂiÂty], so its safe for us to use.
Most of us, I’m sure, would admit that we could do a betÂter job of makÂing our webÂsites accesÂsiÂble, but to activeÂly state that a11y isn’t required seems wilÂfulÂly stuÂpid. I don’t know how you get to serve pages only to your tarÂget marÂket. I mean, this is the web; it’s pubÂlic; stuff gets everywhere.
Through sheer serendipÂiÂty I read an artiÂcle by Karl Groves about an hour latÂer, which states clearÂly why a11y should be someÂthing you conÂcern yourÂself with: Yes, actuÂalÂly, it may be you one day. He sums it up perfectly:
If you marÂket or develÂop ICT prodÂucts and serÂvices and you’re still ignorÂing accesÂsiÂbilÂiÂty, you’re ignorÂing the comÂing realÂiÂty. One day it will be you, or someÂone you know and love.