- From: <bugzilla@jessica.w3.org>
- Date: Sat, 11 Sep 2010 16:17:22 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10481 Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bhawkeslewis@googlemail.com --- Comment #36 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2010-09-11 16:17:21 --- (In reply to comment #35) > user agents are not required to support ARIA, are they? I think conforming HTML5 user agents are required to expose ARIA semantics to platform accessibility APIs, where possible. The editor's draft says: "User agents are required to implement ARIA semantics on all HTML elements, as defined in the ARIA specifications". It references the ARIA User Agent Implementation Guide, which specifies that: "Where supported by the platform Accessibility API, WAI-ARIA semantics MUST be exposed through the standard mechanisms of the desktop accessibility API." http://www.w3.org/WAI.new/PF/aria-implementation/#mapping_general > do I, for an <img> - in HTML5 compatible ARIA supporting UA/AT - need to > insert role="img" in order to use @aria-labelledby? No, just as you don't need to use "role='textbox'" to apply "aria-required" to an text "input". But, per the current draft, you do need to specify role="img" to images with a non-empty "alt" if you want them exposed as images to platform accessibility APIs. -- 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 Saturday, 11 September 2010 16:17:23 UTC