Re: ISSUE-39: cooperate with WAI-ARIA \'politeness\' (from public comments)

Pretty interesting; I'm glad Al pointed this out. It may very well be a 
WAI technique that helps app developers make some of our recommendations 
accessible. If anyone knows of any usability studies, or deployment 
experience, with @live, whether or not it's on security related 
interactions, please let the group know (now or in the future). 

          Mez

Mary Ellen Zurko, STSM, IBM Lotus CTO Office       (t/l 333-6389)
Lotus/WPLC Security Strategy and Patent Innovation Architect




Web Security Context Issue Tracker <dean+cgi@w3.org> 
Sent by: public-wsc-wg-request@w3.org
04/15/2007 10:51 AM
Please respond to
Web Security Context WG <public-wsc-wg@w3.org>


To
public-wsc-wg@w3.org
cc

Subject
ISSUE-39: cooperate with WAI-ARIA \'politeness\' (from public comments)








ISSUE-39: cooperate with WAI-ARIA 'politeness' (from public comments)

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

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

cooperate with WAI-ARIA 'politeness' of live regions in your quest for 
assured 
presentation 
where it says, 2.5 Reliable presentation of security information
   The Working Group will recommend presentation techniques that
   mitigate deceptive imitation, or hiding, of the user agent's
   presentation of security information.
please consider
One of the aspects of verbosity control in some delivery contexts adapted 
for 
people with disabilities is the filtering and buffering of events.  In the 
WAI-
ARIA
specifications, we have introduces values of the @live attribute that 
denote
politeness, or the urgency with which the user's attention should be given 
to
this event.  You have a similar need with yet more authority, in a way. It 

would be great
if we had event politeness wired into the backplane and we could piggyback
our functionality for  the access API bindings on top of your 
functionality for