- From: James Craig <jcraig@apple.com>
- Date: Thu, 13 Feb 2014 15:48:27 -0800
- To: James Teh <jamie@nvaccess.org>, Steve Faulkner <faulkner.steve@gmail.com>, Jason Kiss <jason@accessibleculture.org>
- Cc: Bryan Garaventa <bryan.garaventa@whatsock.com>, Michael Curran <mick@nvaccess.org>, Sailesh Panchang <sailesh.panchang@deque.com>, "Schnabel, Stefan" <stefan.schnabel@sap.com>, Joseph Scheuhammer <clown@alum.mit.edu>, WAI XTech <wai-xtech@w3.org>
+ Steve Faulkner and Jason Kiss On Feb 13, 2014, at 4:33 AM, James Teh <jamie@nvaccess.org> wrote: > The question that doesn't seem to be covered explicitly by the spec as far as I can see (and I'm very happy to be informed otherwise) is when aria-label(ledby) should completely override the content (e.g. links and buttons) and when it shouldn't (e.g. landmarks and regions). My personal opinion is that the W3C could make some general informative recommendations here, but no normative statements for AT. > To complicate matters further, spans and divs without an ARIA role but with both aria-label(ledby) and content are a very grey area. So, it's a lot less simple than it seems on the surface. We’re talking about adding a more complete role mapping, that would include 1-to-1 mappings for things like paragraphs and divs, and spans, but this will rely on browser and HTML heuristics, too, so the HTML mapping could indicate that a div was presentational in some contexts, like we do for layout tables and layout lists. The HTML mapping guide, for example, indicates that a table or list element should always mapped to platform roles like AXTable [1] or AXList [2], but determining things like whether something should be exposed as a data table is a lot more complicated than that [3], and over time, the specs may grow to catch up to where the browsers are today [4]. For now, these are just called “implementation details” and depending on the specific detail, some rendering engines do a better job than others. Some are open-source, and some are not. 1. http://www.w3.org/TR/html-aapi/#el-table 2. http://www.w3.org/TR/html-aapi/#el-ul 3. http://trac.webkit.org/browser/trunk/Source/WebCore/accessibility/AccessibilityTable.cpp#L93 4. https://www.w3.org/Bugs/Public/show_bug.cgi?id=24482
Received on Thursday, 13 February 2014 23:48:56 UTC