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

AUWG Action re: browser accessibility will play a role in the accessibility of web-based user agents

From: Richards, Jan <jrichards@ocadu.ca>
Date: Tue, 12 Jun 2012 16:41:45 +0000
To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
Message-ID: <0B1EB1C972BCB740B522ACBCD5F48DEB03AAF734@ocadmail-maildb.ocad.ca>
For my action (378) from yesterday's call:
ACTION-378 - Write a note re: to A.1.1.1 that is explicit that browser accessibility will play a role in the accessibility of web-based user agents, and therefore UAAG will be relevant when choosing the browser on which to deploy. [on Jan Richards - due 2012-06-18].

To help address the concern in issue IBM1 (http://lists.w3.org/Archives/Public/w3c-wai-au/2012AprJun/att-0047/ATAG2-CommentResponses_20124010LC.html), I suggest adding some text to several of the intent sections in A.1.1

For A.1.1.1:
http://www.w3.org/TR/2012/WD-IMPLEMENTING-ATAG20-20120410/#sc_a111
(Proposed) Note: Even when a web-based user interface has met the requirements of WCAG 2.0, many factors will determine the accessibility of any particular end-user's experience, including (but not limited to): the features and settings of the end-user's user agent, platform, and assistive technology (if any). It is recommended, therefore, that developers of web-based authoring tools be familiar with the accessibility guidance that the User Agent Accessibility Guidelines (UAAG) provides to the developers of user agents. At the time of publication, UAAG version 1.0 is a W3C Recommendation and version 2.0 is under development.

For A.1.2.1:
http://www.w3.org/TR/2012/WD-IMPLEMENTING-ATAG20-20120410/#sc_a121
(Proposed) Note 2 (to follow the existing Note): Even when a non-web-based user interface has followed the relevant user interface accessibility guidelines for the platform, many factors will determine the accessibility of any particular end-user's experience, including (but not limited to): the features and settings of the platform and assistive technology (if any).

For A.1.2.2:
http://www.w3.org/TR/2012/WD-IMPLEMENTING-ATAG20-20120410/#sc_a122
(Proposed) Note 2 (to follow the existing Note): Even when a non-web-based user interface has been designed to expose accessibility information through platform accessibility services, many factors will determine the accessibility of any particular end-user's experience, including (but not limited to): the features and settings of the platform and assistive technology (if any).


Cheers,
Jan
Received on Tuesday, 12 June 2012 16:42:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 12 June 2012 16:42:12 GMT