W3C home > Mailing lists > Public > public-atag2-comments@w3.org > June 2009

Additional Comments

From: Reed Shaffner <Reed.Shaffner@microsoft.com>
Date: Mon, 15 Jun 2009 07:44:41 -0700
To: "public-atag2-comments@w3.org" <public-atag2-comments@w3.org>
Message-ID: <8B054507BA89DF48BB6DB79DCF4EB1E214DDD12682@NA-EXMSG-C110.redmond.corp.microsoft.com>
Comments from Alex Li at Microsoft:



At a more detailed level, Part A contains inconsistencies and unnecessary duplications.  An example of inconsistency is the timing guideline.  A3.2.2 restricts that the only solution to deal with time limit is to extend the timeout by 20 second response.  Yet A1.1 & A1.2 point to WCAG 2.0 and WCAG 2..0 2.2.1 offers much wider range of options including turn off, adjust, extend, real-time exception, essential exception, and 20 hour exception.  If ATAG 2.0 A3.2.2 takes all the WCAG 2.0 2.2.1 options off the table except one, very explicit statement has to be made and rationale must be given.  Timing is just an example, this inconsistency can be found for animation and other topics.  As to duplication, I see A3.1.2, A3.7.1, and WCAG 2.0 2.1.2 as duplicative.  Such duplication creates inconsistency and confusion.



I cannot discern the rationale for the operations requiring shortcuts per A3.1.1 except that they are popular in desktop apps.  The list is largely invalid outside of the desktop application space.



Check for testability issues throughout, especially in part B.


Part B is about QA.  But QA in the development world is a system of business processes, people, and tools.  Yet, the guidelines are relying too much on the tools as the primary method to achieve accessible outcome
Received on Monday, 15 June 2009 14:49:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 15 June 2009 14:49:27 GMT