Edit comment LC-1028 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-952 Next: LC-1258

Comment LC-1028: Comment Shortname:; Commenter: Gian Sampson-Wild <gian@tkh.com.au>; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
Baseline - From reading the Baseline documents, it appears that if a baseline technology does not have particular functionality (for example, the ability to navigate using only the keyboard), then the site can still be compliant with WCAG2 (but obviously not accessible). I think it is reprehensible that the main body advocating accessibility is about to release a set of guidelines that patently allow inaccessible web sites.

Proposed Change:

Remove the baseline theory, or allow only UAAG compliant programs in baseline.; Related issues: LC-1092
(space separated ids); WG Notes: [TEAMA] BASICALLY THE SAME AS 1029 BUT 1029 IS LONGER COMMENT. [AL] Commenter does not understand baseline. Propose to {not-accept} upon publication of better baseline document. Discussed in the 26 April 2007 telecon: Resolution: send LC-1028 and LC-1029 back for tuning. http://www.w3.org/WAI/GL/2007/04/26-wai-wcag-minutes.html refer to http://www.w3.org/2002/09/wbs/35422/200604260-misc/results#x1028 Discussed in the 03 May 2007 telecon: Resolution: Accept as ammended http://www.w3.org/WAI/GL/2007/05/03-wai-wcag-minutes.html Response: http://lists.w3.org/Archives/Public/public-comments-wcag20/2007Jun/0164.html; Resolution: Your concern seems to arise from a different understanding of the meaning of Baseline than that intended by the Working Group. To help address this the conformance section has been completely rewritten, and the term "baseline" has been replaced by "accessibility-supported Web technologies". In order to claim conformance, a Web page must satisfy the WCAG success criteria using a technology that has assistive technology support and works with the accessibility features in user agents. If a technology does not have a particular functionality that is necessary to satisfy some WCAG success criterion (such as keyboard support), then it is impossible to create a conforming Web page relying on that technology. The page would need to meet that success criterion using one of the other technologies upon which it relies. NOTE: The technologies referred to are not the user agents, so they couldn't conform to UAAG. They are the technologies used to build the page (like HTML, CSS etc.) The question of whether a technology is accessibility supported is affected by the behavior of user agents and assistive technology for the technology.; (Please make sure the resolution is adapted for public consumption)