W3C home > Mailing lists > Public > public-html@w3.org > May 2011

normative differences in ARIA requirements between HTML5 and the WHATWG spec

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Fri, 6 May 2011 21:38:07 +0100
Message-ID: <BANLkTi=_X3F89Rg1jvA1uFiJAx-M8KDm0g@mail.gmail.com>
To: "Michael(tm) Smith" <mike@w3.org>
Cc: HTMLWG WG <public-html@w3.org>, Henri Sivonen <hsivonen@iki.fi>
Hi Mike,

I know you are working on the conformance rules for ARIA in HTML5 at the

There is now a difference between the conformance requirments for use of
ARIA in the W3C HTML5 specification and the WHATWG spec.

The WHATWG document[1] contains this additional restriction:

"Authors must not set the ARIA role and aria-* attributes to values that
match the default implicit ARIA semantics defined in the following two

so the example below is conforming under the w3c html5 spec but not under
the whatwg

<button role=button aria-pressed=true>play</button>

note: in cases where aria-* attributes are specific to a particular role(s)
it is required (as implemented) to explicitly add the role even when the
default implied role is the same.

Are you going to be implementing the conformance rules as per HTML5 or as
per the WHATWG spec?

with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
HTML5: Techniques for providing useful text alternatives -
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Friday, 6 May 2011 20:38:55 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:37 UTC