Many teams say "accessibility is important", but don't actually test...
Many teams say "accessibility is important", but don't actually test accessibility.
Why?
They're "too busy".
They don't know how to test accessibility.
The business doesn't seem too worried about it.
Here's how I respond: 👇
I check accessibility in code reviews.
1. I interact with the app via a keyboard.
2. I navigate the app via a screenreader. I use the rotor to browse headings and links.
3. I assure the HTML is semantic.
4. I look for automated accessibility tests. I suggest @TestingLib.
I do these checks on my own code first. To foster change, I try to set an example.
I don't ask for permission to do these things.
My motto: I don't ask for permission to do my job well.
I created a GitHub repo on accessibility, where I keep notes on everything I've learned so far in the README.
There's also an app in the repo that shows a before and after, so you can experience the (shockingly big) difference good HTML makes.
https://github.com/coryhouse/a11y