- From: <bugzilla@jessica.w3.org>
- Date: Mon, 04 Oct 2010 13:52:45 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10914 --- Comment #11 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2010-10-04 13:52:44 UTC --- (In reply to comment #10) > Furthermore, it's non-sensical to make role="navigation menubar" conforming > when the processing model is "The first name literal of a non-abstract WAI-ARIA > role in the list of tokens in the role attribute defines the role according to > which the user agent MUST > process the element." It MUST use that role. It must also ignore abstract roles. And the WAI ARIA implementation spec makes clear that AT _may_ also use additional roles to refine their presentation: http://www.w3.org/TR/2010/WD-wai-aria-implementation-20100916/#mapping_role ]] The entire role string MUST be exposed as a text string if the API supports it. This allows assistive technologies to do their own additional processing of roles. Microsoft Active Accessibility: not supported IAccessible2: expose as an object attribute pair (role=string) User Interface Automation: expose as AriaRole property. The AriaRole property can also support secondary roles using a space as a separator. Accessibility Toolkit: expose as an object attribute pair (role=string) Apple: expose as AXRoleDescription property (AXRoleDescription=string) See the Role Mapping Table below for details. [[ -- 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 Monday, 4 October 2010 13:52:47 UTC