W3C home > Mailing lists > Public > public-html@w3.org > August 2009

Re: question about ARIA in HTML 5 spec text - implied use on elements not listed

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 26 Aug 2009 08:43:38 -0500
Message-ID: <dd0fbad0908260643v3f33f73dx354d59867e5735ab@mail.gmail.com>
To: Steven Faulkner <faulkner.steve@gmail.com>
Cc: Ian Hickson <ian@hixie.ch>, HTMLWG WG <public-html@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>
On Wed, Aug 26, 2009 at 8:35 AM, Steven
Faulkner<faulkner.steve@gmail.com> wrote:
> Hi Ian,
> can you tell me whether the restrcitions you have placed on the use of ARIA
> roles, states and properties on html elements are for authoring conformance
> purposes only or are you expecting browser vendors to implement these
> restrictions as well?

According to the note from the PFWG (not official yet, just a
summarization of what they felt was likely at the time), inherent
semantics win over ARIA states and properties (for example, @checked
wins over @aria-checked if both are specified on an <input
type=checkbox>), but lose to ARIA roles.  Strong inherent semantics
still lose to ARIA roles, but should trigger conformance errors when
validating.

ATs and such should respond to ARIA by those criteria.

~TJ
Received on Wednesday, 26 August 2009 13:44:40 UTC

This archive was generated by hypermail 2.3.1 : Friday, 10 October 2014 16:24:51 UTC