W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > April to June 2008

Updated: WCAG 2.0 at a Glance card [was: A Quick Tips Idea for WCAG 2.0]

From: Shawn Henry <shawn@w3.org>
Date: Tue, 03 Jun 2008 19:50:47 -0500
Message-ID: <4845E6E7.1020104@w3.org>
To: "EOWG (E-mail)" <w3c-wai-eo@w3.org>, Judy Brewer <jbrewer@w3.org>

EOWG,

I took a pass at integrating comments into the now-tentatively-titled "Web Accessibility: WCAG 2.0 at a Glance", a quick-tips-sized card. See the updated version at:
   <http://www.w3.org/WAI/EO/changelogs/cl-quicktips#wcag20>

Please review this, send comments to the list, and be prepared to discuss it at the EOWG teleconference this week. A good companion for reviewing this is to use "How to Meet WCAG 2.0" and turn off the Sections "Show Sufficient Techniques and Failures" and "Show Advisory Techniques" -- which gives you just the guidelines & success criteria (SC).

For discussion:
* Is the goal for this to be a gentle introduction to WCAG 2.0? Other goals?
* Should we stick closer to the wording & meaning from WCAG itself, or be more flexible to be easier to understand on first read?
* For example, Guideline 2.2 says: "Provide users enough time to read and use content". The Level A SC are about allowing the user to adjust any timing, moving, blinking, scrolling, or auto-updating information. Level AAA SC are about timing, interruptions and re-authenticating. Options:
1. "Provide users enough time to use content." is closer to the guideline text.
2. "Allow users to control timing." is more specific.
* What do you think about the parenthetical words after the principles, e.g., "sense" after "Perceivable"? Ideas for others?

Note:
* Previous version <http://www.w3.org/WAI/EO/changelogs/cl-quicktips#glance29May>
* Minutes from last week's discussion: <http://www.w3.org/2008/05/30-eo-minutes#item02>
* I did not incorporate some of EOWG's ideas from last week because either 1. we need to cut words, or 2. they are not part of the SC for that guideline (e.g., Guideline 2.3 discusses seizures only, not distraction or other movement).

Regards,
~Shawn


-------- Original Message --------
Subject: Re: A Quick Tips Idea for WCAG 2.0
Date: Thu, 29 May 2008 14:08:13 -0500
From: Shawn Henry <shawn@w3.org>
To: Wayne Dick <wed@csulb.edu>, w3c-wai-eo@w3.org
References: <380-22008552351023963@M2W017.mail2web.com> <4838BC62.9010205@csulb.edu>

Wayne,

Thanks much for the starter on this!

I've run it by a few people and adapted it for continuing discussion. See:
http://www.w3.org/WAI/EO/changelogs/cl-quicktips for discussion within EOWG...

Thanks,
~Shawn

Wayne Dick wrote:
> 
> The idea is this.  Use the guidelines almost directly, but phrase them 
> so the title is included in the statement. Make them short enough to fit 
> on one line.  Group them by layer: perceivable, operable, understandable 
> and robust.
> 
> Look at
> http://www.csulb.edu/~wed/public/WCAG20/QuickTips.html
> 
> Wayne
> 
> 
> 
> 
> 
> 

-- 
Shawn Lawton Henry, W3C Web Accessibility Initiative (WAI)
about: http://www.w3.org/People/Shawn/
phone: +1-617-395-7664
e-mail: shawn@w3.org
Received on Wednesday, 4 June 2008 00:51:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 10:33:49 GMT