- From: <bugzilla@jessica.w3.org>
- Date: Sat, 31 Mar 2012 09:14:17 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16586 Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bhawkeslewis@googlemail.com --- Comment #1 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2012-03-31 09:14:15 UTC --- (In reply to comment #0) > This is a comment/bug report on [1]. > > Section 3 (HTML element to Accessibility API Role Mapping Matrix) contains a > mapping of elements to accessibility roles. I see that both math and svg are > missing from that "matrix". I don't know enough to suggest mappings for svg, > but for math, the following entries are appropriate: > > HTML 4: no > HTML 5: yes > WAI-ARIA: math role > MSAA: ROLE_SYSTEM_EQUATION > > I don't have direct knowledge of the other values, but most are found in > section 5.4.1 in [2]. The children of the math element (eg, mrow, mfrac) > should NOT be exposed to AT. Say I were extending an accessibility client to render mathematical notations to speech or nemeth. If the accessibility tree does not include a representation of the mathematical content, how would that transformation work? Is your recommendation that user agents should hand over access to the DOM using a specific interface that is *not* part of the the platform accessibility APIs? If so, can we spell out what that specific interface could be? What's the progress on representing mathematical content directly in all platform accessibility APIs? Is anyone working on that or is that dead in the water? -- Configure bugmail: https://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 Saturday, 31 March 2012 09:14:19 UTC