Points of view like this are so misguided. #a11y isn't defined by disability but by enablement. It is an environment that makes someone disabled, not their different abilities.
Just fully realized the accuracy of the term "Web Standards Evangelist" when my dear, devilish Web pal poked me: "Say I develop for a product, motorcycles. I sure ain't paying more to add #a11y as no blind person buys..." Hellfire! Brimstone! A litany of passionate fire and word!
1
2
You have controls for your stereo, your phone, your lights, and your horn on the steering wheel of your car because the designer understood you shouldn't let go of the wheel to use them. This is #a11y.
1
1
The web or an app should allow you to use it with whatever controls are best designed for your situation. This means not just relying on a huge screen, or a mouse, but also providing well designed keyboard navigation and content/structure that makes sense when narrated.
1
1
Thoughtful inclusive design at all layers (visual, user journeys, information architecture, content etc.) provides an enabling environment for all users, regardless of their capabilities or equipment. I believe this is the most important lesson anyone can learn about #a11y.
1
1
(As a final disclaimer, I believe all this was @mholzschlag's original point. At least, that's definitely what I learned from her and other Web Standards Evangelists at the beginning of my career.)
1
2
