WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG Extensions

for

From: Chagnon | PubCom
Date: Aug 20, 2015 12:58PM

I agree with every point Jared made below.

Especially his comment "That there's a 228 page 'Understanding WCAG 2.0' document (not to mention 385 pages for 'How to Meet WCAG 2.0') to explain a standard which has a core principle of "Understandable" is quite telling..."

A handful of good tech editors could reduce the existing 228-page and 385-page WCAG reference documents in half, at least, and put them into a more comprehendible, palatable format. WCAG's current presentation is dysfunctional and chaotic.

It's time for a complete revamp of WCAG's presentation. I don't mean changing or updating the standards themselves, but the actual WCAG 2.0 document as well as the references Jared cited. Get them edited and presented in a more understandable format that is usable -- and understandable -- by the mere mortals who have to create accessible websites and documents.

A better presentation of WCAG might give us a better foundation to build the extensions or whatever method will be used for updating the standards.

Using a building analogy can help create a strategy that improves WCAG's presentation, allows for faster and easier updates, and encourages easier formal adoption by governments. The analogy: Correct the foundation's problems first (revamp WCAG's presentation and references), and then add the 2-story addition (the extensions or amendments).

--Bevi Chagnon

PS: And I don't think extensions should be optional. Why would we allow for a group of users to be "optionally" discriminated?