W3C home > Mailing lists > Public > public-wsc-wg@w3.org > April 2007

ISSUE-43: don\'t disable assistive technology (public comment)

From: Web Security Context Issue Tracker <dean+cgi@w3.org>
Date: Sun, 15 Apr 2007 14:59:55 +0000 (GMT)
To: public-wsc-wg@w3.org
Message-Id: <20070415145955.C0270BDA8@w3c4.w3.org>


ISSUE-43: don't disable assistive technology (public comment)

http://www.w3.org/2006/WSC/Group/track/issues/43

Raised by: Bill Doyle
On product: Note: use cases etc.

>From public comments
raised by: Al Gilman Alfred.S.Gilman@ieee.org

http://lists.w3.org/Archives/Public/public-usable-
authentication/2007Apr/0000.html


don't disable assistive technology 
where it says, in 4.2 User agents
   Use cases considered by this Working Group must involve a web user
   agent, operated by a human user. 
where it says, in 5.3 Security context information for consumption by 
automated agent
The Working Group will only consider Web interactions that include a human 
user. Situations in which all security relevant information is consumed and 
acted upon my automated agents are out of scope.
you must change
The latter statement is incompatible with standard accessibility requirements, 
in particularly the W3C Recommendation on User Agent Accessibility 
Guidelines.  Please review UAAG 1.0, Guideline 6.  On the client side the user 
must have the option to employ automated assistance that accesses either the 
W3C DOM or a platform-defined accessibility API.  The machinability of the 
security information (information characterizing the security aspect of the 
user's current browse context) is a matter of importance to people with 
disabilities, and must not be neglected.
where it says, in  4.4 Third-party recommendation
The recommendations of certificate authorities,
   visited web sites or reputation services integrated into the user
   agent are in scope for this Working Group.
please consider 
 The architecture needs to support reputation services integrated with the AT 
as well as integrated with the base browser.
Why? 
People with disabilities who use heavy-duty Assistive Technology such as a 
screen reader, voice command software, or on-screen-keyboard for switch input 
management, will find the Assistive Technology a more natural  bundle host for 
recommendation-service access funtions, as opposed to the base browser.
Received on Sunday, 15 April 2007 14:59:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 5 February 2008 03:52:46 GMT