Three things I do not look for when testing accessibility
I was doing some web accessibility training with a client recently, and started out by telling them the three things I do * not * test for when doing accessibility evaluations.
- Colour contrast
- Alternative text on visual media
- Keyboard focus, and related success criteria
There is a very simple reason. Developers are well positioned to test for these three items on their own. None of them takes much additional time at all if done at the source (once tools are acquired and learned). This is what I would consider to be stage one of placing the responsibility for accessibility into the hands of developers.
This obviously takes into consideration that this particular development team wants to become better at building accessible user experiences, and are willing to take the time to learn how to test for these items on their own. It also takes into consideration that my client listens to me when I tell them what to expect out of my accessibility evaluations.
If you are looking for an accessibility consultant who will provide a straight pass / fail on the WCAG 2.0 success criteria related to a set of web pages, then I am not the droid you're looking for :) If you are looking for someone who has experience teaching accessibility concepts, and providing consulting, to decentralized development teams then please contact me.