RE: ISSUE: ARIA Draft UA Conformance

+1 for the UA best practices

 

Stefan

 

From: wai-xtech-request@w3.org [mailto:wai-xtech-request@w3.org] On
Behalf Of Aaron M Leventhal
Sent: Dienstag, 1. Juli 2008 09:21
To: David Bolter
Cc: James Craig; W3C WAI-XTECH; wai-xtech-request@w3.org
Subject: Re: ISSUE: ARIA Draft UA Conformance

 


Do we want to say anything about property changes? 

Something like: 
"User agents must fire events for ARIA property changes, where an
appropriate event exists for the platform accessibility API being mapped
to." 

- Aaron 






From: 

David Bolter <david.bolter@utoronto.ca> 

To: 

James Craig <jcraig@apple.com> 

Cc: 

W3C WAI-XTECH <wai-xtech@w3.org> 

Date: 

07/01/2008 05:33 AM 

Subject: 

Re: ISSUE: ARIA Draft UA Conformance

 

________________________________





+1

D
James Craig wrote:
>
>
> http://www.w3.org/WAI/PF/aria/#uaconf
<http://www.w3.org/WAI/PF/aria/#uaconf> 
>
> Current wording:
>
> User agents SHOULD expose role, state, and property information 
> provided by the author to the platform accessibility API (using the 
> values as determined in steps 2 and 3 above). Refer to Mapping States 
> and Properties to Accessibility APIs ([ARIA-PRACTICES], Section 12.1) 
> for guidance about how to expose this information. This requirement 
> parallels User Agent Accessibility Guidelines 1.0 Section 6.3: 
> Programmatic Access to non-HTML/XML Content ([UAAG], Section 6.3), 
> except that it applies even to HTML and XML content.
>
>
> I move that user agents MUST expose the information if an appropriate 
> mapping exists:
>
> User agents MUST expose role, state, and property information provided

> by the author to the platform accessibility API (using the values as 
> determined in steps 2 and 3 above) if an appropriate mapping exists. 
> Refer to Mapping States and Properties to Accessibility APIs 
> ([ARIA-PRACTICES], Section 12.1) for guidance about how to expose this

> information. This requirement parallels User Agent Accessibility 
> Guidelines 1.0 Section 6.3: Programmatic Access to non-HTML/XML 
> Content ([UAAG], Section 6.3), except that it applies even to HTML and

> XML content.
>
>