W3C home > Mailing lists > Public > public-html@w3.org > October 2007

Re: aria vs html5 (was: ARIA States and Properties Meeting)

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 24 Oct 2007 20:26:55 +0200
To: "Jim Jewett" <jimjjewett@gmail.com>, public-html@w3.org
Message-ID: <op.t0pr65xt64w2qv@annevk-t60.oslo.opera.com>

On Wed, 24 Oct 2007 20:10:53 +0200, Jim Jewett <jimjjewett@gmail.com>  
wrote:
> Anne van Kesteren <annevk@opera.com> wrote:
>> If HTML5 were to be supported
>> by all vendors ARIA would not even be needed.
>
> Could you explain that?

HTML5 provides most widgets natively which the browser can then expose to  
assistive technology in some way. So there's no need for the author to  
implement them by him- or herself and set ARIA attributes on state changes  
etc. accordingly.


> If the html spec simply states:
>
>     Attribute names starting with "aria-" are
>     reserved for use by the ARIA specification.
>     These are typically used to improve accessibility.
> ...
>     role attribute values starting with "aria-" are
>     reserved for use by the ARIA specification.
>     These are typically used to improve accessibility.
>
> I think that will cover it.

Yes. Although I'm not convinced the other uses of role= make sense. I'm  
also not sure if overloading role= to do both ARIA and those other things  
makes sense.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Wednesday, 24 October 2007 18:26:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:40:04 GMT