- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Wed, 05 Mar 2014 16:56:01 -0500
- To: Jason Kiss <jason@accessibleculture.org>
- CC: Alexander Surkov <surkov.alexander@gmail.com>, Steve Faulkner <faulkner.steve@gmail.com>, Cynthia Shelly <cyns@microsoft.com>, Rich Schwerdtfeger <schwer@us.ibm.com>, David Bolter <dbolter@mozilla.com>, W3C WAI Protocols & Formats <public-pfwg@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Hi Jason,
> Actually, looking at the outline for the new core UA implementation
> guides [1], it looks like the "Exposing attributes that do not
> directly map to accessibility API properties" section will only exist
> in the core guide, so that's good.
>
> [1]http://www.w3.org/WAI/PF/wiki/Outline_Core_User_Agent_Implementation_Guide
Sounds like a plan.
BTW, David Bolter pointed out to me yesterday that there other places in
the UAIG that reinforce the notion of providing this information
"elsewhere", where "elsewhere" depends on the specific a11y API. The
wording is more explicit. The "Role Mapping" section [1], point 5 says:
"User agents MUST expose the WAI-ARIA role string if the API supports a
mechanism to do so. This allows assistive technologies to do their own
additional processing of roles.
- MSAA: not supported
- IAccessible2: expose as an object attribute pair (xml-roles:"string")
- UIA Express: expose as AriaRole property. The AriaRole property
can also support secondary roles using a space as a separator.
- ATK/AT-SPI: expose as an object attribute pair (xml-roles:"string")
"
There is similar wording in the "State and Property Mapping" section [2]
(point 5).
[1] http://www.w3.org/TR/wai-aria-implementation/#mapping_role
[2] http://www.w3.org/TR/wai-aria-implementation/#mapping_state-property
--
;;;;joseph.
'A: After all, it isn't rocket science.'
'K: Right. It's merely computer science.'
- J. D. Klaun -
Received on Wednesday, 5 March 2014 21:56:29 UTC