This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8481 - Clarify how WIA-ARIA data is passed as a text string
Summary: Clarify how WIA-ARIA data is passed as a text string
Status: RESOLVED FIXED
Alias: None
Product: ARIA
Classification: Unclassified
Component: Core AAM (show other bugs)
Version: 1.0
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Cynthia Shelly
QA Contact: ARIA UA Implementors
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-11 20:39 UTC by Andi Snow-Weaver
Modified: 2010-11-29 16:30 UTC (History)
1 user (show)

See Also:

Attachments

Description Andi Snow-Weaver 2009-12-11 20:39:10 UTC 
Rich commented on 4.3 Exposing attributes that do not directly map to accessibility APIs

<change>
user agents MUST expose the raw WAI-ARIA data as a text string
</change>
<to>
user agents MUST expose the raw WAI-ARIA data as a text string of name-value pairs
</to>

But only IA2 and ATK use name-value pairs. Need to clarify how this is done for other APIs.
Comment 1 Andi Snow-Weaver 2010-11-29 16:30:12 UTC 
Per the 29 November ARIA TF meeting, we have agreed to change the text as follows:

<change>
When WAI-ARIA roles, states and properties do not directly map to an accessibility API, and there is a way in the API to expose a text string, user agents MUST expose the WAI-ARIA data as a text string.
</change>

<to>
When WAI-ARIA roles, states and properties do not directly map to an accessibility API, and there is a mechanism in the API to expose the WAI-ARIA role, states, and properties and their values, user agents must expose the WAI-ARIA data using that mechanism.
</to>