W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2013

Re: ARIA role restrictictions in HTML5

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Thu, 21 Mar 2013 09:48:53 +0000
Message-ID: <CA+ri+VneM0=qZjY_yxy2W0-i2Rf3gPaFD2opt-PXURmDFR7-Aw@mail.gmail.com>
To: Jonathan Avila <jon.avila@ssbbartgroup.com>
Cc: w3c-wai-ig@w3.org
Hi Jonathon,

The ARIA mappings in the HTML5 spec have been there for a few years now. I
worked on ARIA integration into HTML5 along with others. The restrictions
are authoring restrictions only (in the most part) That is from a browser
implementation perspective any ARIA role will override any native HTML
element role when applied, but some don't make sense and should be avoided,
thus the restrictions.

The ARIA tables in the HTML spec are not very user friendly and don't cover
many elements. I have developed a document which may be helpful: Using ARIA
in HTML https://dvcs.w3.org/hg/aria-unofficial/raw-file/tip/index.html

with regards

HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>

On 20 March 2013 14:25, Jonathan Avila <jon.avila@ssbbartgroup.com> wrote:

> I was looking at the latest draft version of the HTML5 specification and
> noticed in the implicit aria semantics table it indicates that only a
> limited set of ARIA roles can be used with certain elements such as the
> anchor element to conform to the HTML5 specification.  Specifically you
> could not use a role of button, radio button, etc. on anchor elements.
> This seems problematic but makes good semantic sense.  One advantage of
> using anchors with hrefs for diverse ARIA roles is there is some
> progressive enhancement support.
> http://www.w3.org/html/wg/drafts/html/master/dom.html#sec-implicit-aria-semantics
> Jonathan
Received on Thursday, 21 March 2013 09:50:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:47 UTC