- From: Shawn Henry <shawn@w3.org>
- Date: Fri, 06 Jun 2008 10:36:39 -0500
- To: "Robison, Cole [EISU]" <Cole.Robison@da.ks.gov>
- Cc: "EOWG (E-mail)" <w3c-wai-eo@w3.org>
Thanks for the input, Cole! We discussed your comments in EOWG today, and the changes are now reflected in the updated draft at: http://www.w3.org/WAI/EO/changelogs/cl-quicktips#wcag20 Best, ~Shawn Robison, Cole [EISU] wrote: > 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 > <http://www.w3.org/TR/UNDERSTANDING-WCAG20/intro.html#introduction-fourp > 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 > understandable." > -- 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 Friday, 6 June 2008 15:37:45 UTC