- From: <bugzilla@jessica.w3.org>
- Date: Sun, 10 Oct 2010 23:34:40 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11003 --- Comment #5 from Tab Atkins Jr. <jackalmage@gmail.com> 2010-10-10 23:34:40 UTC --- (In reply to comment #4) > However, the purpose of mapping HTML semantics to platform accessibility APIs > is to avoid platform accessibility API clients having to become direct DOM > consumers to provide user interfaces on top of those semantics. > > So the fact that the semantics are extractable with direct DOM access does not > reduce the utility of documenting how to map the extracted semantics to > accessibility APIs. Ah, okay. Different definitions of "extractable". ^_^ > > Was there some additional specific structure that should be exposed? Is there a precedent for > > talking about Accessiblity API-specific data structures? > > I don't understand what you're talking about. Do the Apple Accessibility API > and UI Automation examples above constitute the sort of precedents you're > looking for? Not quite. What I meant was, are there precedents for HTML5 to define exactly how features map into some accessibility APIs, beyond straightforward cases like ARIA? -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Sunday, 10 October 2010 23:34:42 UTC