“Accessibility” tends to be a word that’s easily thrown into conversations to convey a sense of inclusivity but oftentimes comes with a lack of understanding.
Accessibility end to end retrospective. Accessibility (often abbreviated to A11y — as in “a” then 11 characters then “y”) in Web development means enabling as many people as possible to use Web sites, even when those people’s abilities are limited in some way.
This story will give you detailed insight on Web Accessibility(A11y) based WAI-ARIA HTML attributes, why, how, when, and where to use them?
I attended a talk last year by Mike Gifford where he said, “the web has actually become LESS accessible since 2011.” It’s cheap and easy for anyone to create a website these days, and hardly anyone considers accessibility. And why would you? If it’s not in your daily purview, it’s not going into your list of website requirements. Heck, most people don’t even think of the end user, Disabled or not, when creating a website.
In May 2001, an article published by Tim Berners-Lee (the inventor of the World Wide Web), James Hendler, and Ora Lassilain in Scientific America, publicized a new vision for the future of the web .
It is easy for many developer (myself inclusive) to conclude that our apps can be used by everyone. Most times, that is usually not the case.