W3C home > Mailing lists > Public > public-html@w3.org > September 2010

Re: ARIA mapping status

From: Maciej Stachowiak <mjs@apple.com>
Date: Thu, 09 Sep 2010 09:44:56 -0700
Cc: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>, Henri Sivonen <hsivonen@iki.fi>, HTML WG <public-html@w3.org>, Richard Schwerdtfeger <schwer@us.ibm.com>, Cynthia Shelly <cyns@microsoft.com>
Message-id: <C8257F4B-4302-44DA-85D8-B81AD134F171@apple.com>
To: Steven Faulkner <faulkner.steve@gmail.com>

On Sep 9, 2010, at 9:11 AM, Steven Faulkner wrote:

> hi Benjamin,
> >As we are very likely to want to update API mapping advice for HTML5 as implementing platforms and available AT change, and as presenting information inline >is clearer for readers, it would be best to use a Note.
> I think thats reasonable. 
> There are many elements which currently have no default role specified or 'no role' specified as a strong semantic. It appears that currently for the 'no role' strong semantic, User Agents must not map them to a role in an accessibility API, if I am incorrect in this assumption then I would be happier with what's in the spec

My reading is that for elements with a strong semantic or default role of 'no role', the spec is saying that none of the ARIA roles are guaranteed to always match the full semantics of that element, and therefore UAs should expose it however appropriate. For example, <input type=file> would be exposed in a specialized way that reflects its nature as a compound control. 'no role' doesn't mean 'hide from AT', it means 'expose this to AT however appropriate, but there's no ARIA role that is clearly a good math'. That is how I would expect implementors to interpret it, and in particular I can report that this is the approach that WebKit's accessibility implementors have taken. 

Received on Thursday, 9 September 2010 16:45:30 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:04 UTC