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

Re: Minor Editorials

From: Jan Richards <jan.richards@utoronto.ca>
Date: Fri, 12 Jun 2009 15:43:45 -0400
Message-ID: <4A32AFF1.4060800@utoronto.ca>
To: WAI-AUWG List <w3c-wai-au@w3.org>
Hi all,

Here are my initial responses to Bruce's comments:

> Hi, I am commenting on ATAG 2.0 "next to last call" working draft.   
> These comments reflect only my own opinion, and not my employer, nor  
> any working group I might be a part of.
> 
> I am anxious that a few non-web authoring tools be validated against  
> ATAG as part of the TR application.  There are tools which produce  
> accessible HTML, and are accessible to screen readers, so it would be  
> quite important to know how a few rank against the ATAG benchmarks.

Reed, Greg? :)

> Minor Editorial
> 
> Introduction
> Definition of authoring tool
> Note 2 is confusing because authors, per ATAG definition, have author  
> permission.

JR: AGREE (already flagged in Editor's draft that should be coming out 
today)


> Suggestion:
> 
> Any ATAG 2.0 guideline that requires authors to modifyification of Web  
> content in some way, always assumes that the person has author  
> permission.
> Understanding Levels of Conformance
> The phrase "look & feel" (with the quotation marks) appears three  
> times and may be too colloquial. WCAG 2.0 restricts this term to the  
> understanding document, and then only once.

JR: All three uses are in the "informative" sections. So I think it is ok.


> ATAG 2.0 Guidelines
> Part A Applicability Notes, Note 1 Scope. Suggest avoiding term  
> "chrome" (with or without quotes) as it causes ambiguity. Some people  
> think the term refers only to the decoration, not the control. Most  
> people would not think of menus as Chrome. Toolbar and palette could  
> be added to example list. Two opposing definitions:
> 
> http://en.wikipedia.org/wiki/User_interface_chrome
> http://www.catb.org/~esr/jargon/html/C/chrome.html

JR: I'm ok either way.


> Trivial Editorial
> 
> Table of Contents
> There is an empty list item (<li></li>) between “ATAG 2.0 Layers of  
> Guidance” and “Relationship to the Web Content Accessibility  
> Guidelines (WCAG) 2.0”. This cause undesirable vertical white space  
> when I printed.

JR: Agree to remove.

> Introduction
> Definition of authoring tool
> Note 3 (Live content authoring tools…), Liveshould be a defined term  
> (as it is in WCAG).

JR: Maybe we should replace "Live" with "Real-time"

> 
> Integration of Accessibility Features
> The phrase "look-and-feel" (with the quotation marks) is used in this  
> paragraph when in the immediately previous section, "look &  
> feel" (also with the quotes) appears (twice). Usage should be  
> consistent.

JR: AGREE (already fixed in Editor's draft that should be coming out today)


> ATAG 2.0 Guidelines
> B.2.2.2.7 Save Status For Repair: delete space between “checking” and  
> comma.

JR: AGREE

Cheers,
Jan
-- 
Jan Richards, M.Sc.
User Interface Design Lead
Adaptive Technology Resource Centre (ATRC)
Faculty of Information
University of Toronto

   Email: jan.richards@utoronto.ca
   Web:   http://jan.atrc.utoronto.ca
   Phone: 416-946-7060
   Fax:   416-971-2896
Received on Friday, 12 June 2009 19:44:20 UTC

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