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

Processing ATAG2 Comments (comment: "general approaches & trivial details")

From: Jan Richards <jan.richards@utoronto.ca>
Date: Tue, 26 May 2009 11:28:54 -0400
Message-ID: <4A1C0AB6.6030804@utoronto.ca>
To: WAI-AUWG List <w3c-wai-au@w3.org>
Comment at:
http://lists.w3.org/Archives/Public/public-atag2-comments/2009May/0000.html

My comments marked with JR:

========
> I'm finding it difficult with both WCAG 2.0 & ATAG 2.0 to have web accessibility & desktop accessibility merged together like this.  Perhaps it is useful for the sake of the overlap in standardized approaches.  However, for a web developer working with a popular open source content management system (Drupal), I find that most folks get lost in the documentation.  Stripping it down to what is relevant for particular audiences is key.  It's disappointing that W3C isn't taking the initiative to provide concise guides for different developer communities.  Would really aid adoption I am sure.  Web based interfaces are a big enough challenge for accessibility that they could use having a shorter checklist, tailored using more standardized web specific language, and with links to best practices which are available in existing open source packages if possible. The desktop software people speak a different language I assume.

JR: It is important to note that ATAG 2.0 is not intended to be a 
"one-stop shop" for guidance on creating accessible Web-based or desktop 
applications in general. ATAG 2.0 guidelines A.1.1 and A.1.2 require 
developers to consult relevant existing guidance for this general 
purpose. ATAG 2.0 (Part A) focuses instead on the set of accessibility 
issues that are more specific to authoring tools.

> There is a link from:
>     http://www.w3.org/TR/ATAG20/checklist.html
> 
> to:
>     http://www.w3.org/TR/ATAG20/Overview.html#minimum_accessibility
> 
> where the anchor doesn't exist.  Same issue with:
>     http://www.w3.org/TR/ATAG20/Overview.html#enhanced_accessibility
>     http://www.w3.org/TR/ATAG20/Overview.html#def-UI-Chrome
>     http://www.w3.org/TR/ATAG20/Overview.html#def-UI-Content-Display
> 
> Further down, there's a mising space in this paragraph:
> 
>  <li><strong class="sc-handle">B.3.1.1 At Least as Prominent:</strong> If <a href="Overview.html#def-Author" title="definition: author">authors</a>are provided with a choice of <a href="Overview.html#def-Authoring-Action">authoring actions</a> to achieve the same <a href="Overview.html#def-Authoring-Outcome-Mainstream">mainstream rendered </a><a href="Overview.html#def-Authoring-Outcome-Mainstream"> outcome</a>, then actions that implement <a href="Overview.html#def-Acc-Auth-Practice" title="definition: accessible authoring practice">accessible
>             authoring practices</a> are at least as <a href="Overview.html#def-Prominence" title="definition: prominence"> prominent</a> as the other action(s)  (e.g., text can be made bold with either style sheets or <a href="Overview.html#def-Presentation-markuo">presentational markup</a>).</li> 

JR: These editorial corrections should be made.


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 Tuesday, 26 May 2009 15:29:38 UTC

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