W3C home > Mailing lists > Public > public-html-a11y@w3.org > September 2010

[Bug 10463] provide a comprehensive HTML5 to accessibility API mapping reference

From: <bugzilla@jessica.w3.org>
Date: Wed, 08 Sep 2010 16:54:51 +0000
To: public-html-a11y@w3.org
Message-Id: <E1OtNv9-0003PL-Li@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10463





--- Comment #11 from Henri Sivonen <hsivonen@iki.fi>  2010-09-08 16:54:50 ---
(In reply to comment #10)
> The main issue with this is that the mappings are incomplete, many elements in
> the ARIA section have no default roles,state or properties. Accessibility APIs
> have role states and properties not included in ARIA. How ARIA should map to
> accessibility APIs is in the ARIA implememntation guide. How HTML5 should map
> to  accessibility APIs should be in a HTML5 to accessibility API implementation
> guide.

I think it's still appropriate for HTML5 to say that foo in HTML5 has to be
mapped to the same accessible role as ARIA role bar even we want there to be an
ARIA to accessibility API spec and an HTML to accessibility API spec.

Or do you want some HTML stuff to use accessibility API roles that are more
refined than what ARIA maps to?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 8 September 2010 16:54:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:13 UTC