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

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

From: Robison, Cole [EISU] <Cole.Robison@da.ks.gov>
Date: Wed, 4 Jun 2008 16:13:12 -0500
Message-ID: <0C3ADB4D8E7B0E4BA44983F3EB128C9902C58E33@mailbe02.Mail.Ks.Gov>
To: "EOWG (E-mail)" <w3c-wai-eo@w3.org>

All in all, this looks excellent to me.

On 2.2, I'd opt for the alternate wording, "Give users enough time to
use content." I think it much more clearly conveys what the guideline is
about, so it's easier to understand. ("Control timing" may be more
specific, but is likely confusing without context.)

I like the idea of providing a bit of elaboration after the principles
-- if the right wording can be found. Unfortunately, I don't think the
words in the current draft are that helpful. I understand the need for
brevity here, but the principle heading itself is already the best
single word distillation of the concept, so I'm skeptical that another
single word is the right approach here. The explanations in the
Understanding document
rincs-head> are, I think, what's desired, but I'm frankly at a loss as
to how to make them concise enough and still retain their meaning. (I
hate to criticize without offering a possible solution, but hopefully
this can at least serve as food for thought. FWIW.)

The only other tiny suggestion I would make would be that the word
"content" could be cut from 3.1, making it "Make text readable and

Cole Robison
Director of Statewide Web/IT Accessibility
Division of Information Systems and Communications
State of Kansas
(785) 291-3016

P.S. I should also say "hi" and introduce myself, since I'm de-lurking
with this post. My sig, above, conveys what I do and where I'm from. My
position is a new one that I've occupied since January (at which time I
joined the mailing list). My prior background was in IT training at a
university, which included teaching web accessibility. Suffice it to say
that I very much appreciate the work done and resources provided by the

-----Original Message-----
From: w3c-wai-eo-request@w3.org [mailto:w3c-wai-eo-request@w3.org] On
Behalf Of Shawn Henry
Sent: Tuesday, June 03, 2008 7:51 PM
To: EOWG (E-mail); Judy Brewer
Subject: Updated: WCAG 2.0 at a Glance card [was: A Quick Tips Idea for
WCAG 2.0]


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:

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

For discussion:
* Is the goal for this to be a gentle introduction to WCAG 2.0? Other
* 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.
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?

* Previous version
* Minutes from last week's discussion:
* 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).


-------- 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>


Thanks much for the starter on this!

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


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
> on one line.  Group them by layer: perceivable, operable,
> 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 21:14:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:57 UTC