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 15:59:13 +0000
To: public-html-a11y@w3.org
Message-Id: <E1OtN3J-0000vT-VB@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10463





--- Comment #10 from steve faulkner <faulkner.steve@gmail.com>  2010-09-08 15:59:13 ---
(In reply to comment #9)
> (In reply to comment #8)
> > But then the normative implementation statements in regards to
> > ARIA must be removed from the HTML5 spec as they are mandating accessibility
> > API mappings by proxy.
> The whole point of implementation statement by reference to ARIA is to say that
> certain things must map the same way as certain ARIA things without having to
> say what that way is in terms of any concrete platform API.
> I think saying that something has to map the same way as something else is
> completely compatible with externalizing what the concrete mapping is.



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.

-- 
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 15:59:15 UTC

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