- From: Shawn Henry <shawn@w3.org>
- Date: Mon, 09 Jun 2008 11:12:08 -0500
- To: Wayne Dick <wed@csulb.edu>
- Cc: "EOWG (E-mail)" <w3c-wai-eo@w3.org>, Judy Brewer <jbrewer@w3.org>
Thanks for the perspective, Wayne. I agree. > The main reason developers have problems with WCAG 2.0 is because it is > user centered not technology centered. I remember my first reading > thinking, "That's good but what do I do with tables?". The Sufficient > Techniques have tables, forms, frames, titles, labels and any other > thing you could want. Yes. In case you missed it from the minutes or analysis doc, EOWG agreed we need to have specific tips/techniques for developers, in addition to the WCAG 2.0 at a Glance cards. ... > pull-back page might also be interesting. For example start with > "table" and pull back isolated the techniques that pertain to tables and > then pull back to guidelines via success criteria. Yes, we have something like this in the plan for WAI deliverables. "WAI has been focusing on developing the technical aspects of WCAG 2.0. We are also planning material to help Web developers who are not accessibility experts develop accessible Web content that conforms to WCAG 2.0, such as: * "Application Notes" (working title) would provide guidance for a specific topic, such as images, links, or tables. For example, an Application Note on forms would start with simple examples and include the WCAG 2.0 success criteria, techniques, and strategies for developing accessible forms." - http://www.w3.org/WAI/intro/wcag20 ~Shawn
Received on Monday, 9 June 2008 16:13:26 UTC