WCAG2 - Disaster Looms? (Full Version)

All Forums >> [Web Development] >> Accessibility



Message


Donkey -> WCAG2 - Disaster Looms? (7/9/2007 10:13:52)

To Hell With WCAG2


A depressing read, confirms what a lot of us have thought for a while, the people setting these standards are out of touch with the real world.




caz -> RE: WCAG2 - Disaster Looms? (7/9/2007 12:31:54)

If you continue to read the discussion following Joe Clark's article it is even more depressing when you realise that a lot of the work of the committee has been sabotaged by personality conflicts and that the final say rests with the corporate members of the group, who appear to put their own interests first. Although I could argue with most of the recommendations, this took the biscuit:-

quote:

14. You also have to provide an alternate document if a reader with a “lower secondary education level” couldn’t understand your main document. (In fact, WCAG 2 repeatedly proposes maintaining separate accessible and inaccessible pages. In some cases, you don’t necessarily have to improve your inaccessible pages as long as you produce another page.)


I thought that extra explanatory pages had gone the way of the dinosaurs, but this epitomises the depths to which this 'guidance' has sunk.
I suspect that a group of chimps with crayons and writing pads could have produced better than this committee.

"Along the way, it lost the ability to apply to the real things real developers work on every day—plain-Jane HTML, CSS, and JavaScript."

A fine epitaph for the inclusive web.




jaybee -> RE: WCAG2 - Disaster Looms? (7/9/2007 16:32:53)

First off, that article by Joe was in May 2006, over a year ago. Tailslide and I wrote something about it here back then. It was widely recognised as being a disaster of major proportions. Unsurprisingly, all standardistas jumped on it and started screaming long and loud with some effect. WCAG 2 still isn't out.

As far as I'm aware, the process was changed, the team was changed and somewhere along the line Microsoft managed to wangle a place as co-chair. Now I'm sincerely hoping that this means they don't get to vote on anything but then I always sincerely hope I'm going to win the lottery.

Updated Web Content Accessibility Guidelines 2.0 (WCAG 2.0) Working Draft documents were published 17 May 2007 with a call to review. People were being asked to join and comment to improve the process. The latest call was closed on the 29th June so you missed it. The comments are now being reviewed by the Working Group and I suspect they'll be there for some time.

This Page takes you to the comments lists. May, June and July are the relevant section for current status.




caz -> RE: WCAG2 - Disaster Looms? (7/10/2007 13:21:27)

Doh! I thought it seemed familiar but with my memory I can never tell. [;)]

I am not wading through all those mail list entries, life's too short; so I have bookmarked this for future use.

WCAG 2.0 Guidelines : current status and current updated documents May 2007.

But I did note this example of needed linguistic simplification had been accepted:

quote:

"The terms authored units, web units, authored component, baseline, and parsed unambiguously have all been replaced by more easily understood terms and explanations."


Hooray! - and at least they appear to have taken on board the need to make the guidelines themselves accessible by issuing a "dummies guide" to using them.

quote:

"The Quick Reference document has also simplified the use of WCAG 2.0. One can start from this document (which is a compilation of text from the other documents) and get an overview of all the requirements and techniques to meet them. The Quick Reference in turn has links that will take the user directly to the parts of WCAG 2.0 or Understanding WCAG 2.0 or the Techniques and Failures documents that they are interested in."


http://www.w3.org/WAI/WCAG20/quickref/Overview.php




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.046875