A thought-provoking piece by Mike Davies:
Creating an accessible web experience involves the co-ordination number of independent groups. The website builders have an important role, but they cannot cover the entire spectrum of accessibility issues. The user-agent vendors (typically browsers, but not limited to that) play an equally important role, taking accessible content and rendering it in an accessible way. They are also tasked with the responsibility of easing visitor access to content by features such as font-resizing, alternate stylesheets, colour filters, print functionality. The assistive technology provider also plays an important role, making sure that content is conveyed to the user in a way they can perceive and operate…
To that, I’d add a question: what about the responsibility of the end users? The onus also needs to be on them to know which tools are available to them and how to use them properly?
GAWDS has failed. Accessifyforum has failed. Accessites is fundamentally flawed. WCAG 2.0 is in trouble. Joe Clark’s WCAG Samurai remains as a glimmer of hope, so to is WaSP’s Accessibility Task Force. We need something that doesn’t repeat the same mistakes as GAWDS and Accessifyforum, but at the same time be open to involvement by the community, for the community