- From: Steve Faulkner <faulkner.steve@gmail.com>
- Date: Sat, 23 Mar 2013 15:34:20 +0000
- To: Jonathan Avila <jon.avila@ssbbartgroup.com>
- Cc: w3c-wai-ig@w3.org
- Message-ID: <CA+ri+VnUS+9taVhjQ=7SoJpxfD1_uiFs_ObOiZ8XJAFoSsXsnQ@mail.gmail.com>
Thanks to Jonathon. The ARIA role restrictions on a few HTML5 elements were incorrect, this has now been fixed in:http://www.w3.org/html/wg/drafts/html/master/dom.html#sec-implicit-aria-semantics on the larger question of what restrictions should be in place, I suggest people file a bug [1] against the HTML specification raising any issues. Note you need to set up an account for the W3C bugzilla to file bugs, but this is a simple process. [1] https://www.w3.org/Bugs/Public/enter_bug.cgi?product=HTML%20WG&component=HTML5%20spec&priority=P3 with regards -- SteveF HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/> <http://www.paciellogroup.com/resources/wat-ie-about.html> 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 Saturday, 23 March 2013 15:35:28 UTC