W3C home > Mailing lists > Public > public-html@w3.org > April 2010

Re: Removal of other semantic elements

From: Maciej Stachowiak <mjs@apple.com>
Date: Sun, 04 Apr 2010 16:00:32 -0700
Cc: Jonas Sicking <jonas@sicking.cc>, HTML WG <public-html@w3.org>, Shelley Powers <shelley.just@gmail.com>
Message-id: <AC915571-B639-43AC-B7BD-C7EFE0B5B310@apple.com>
To: Steven Faulkner <faulkner.steve@gmail.com>

On Apr 4, 2010, at 1:17 PM, Steven Faulkner wrote:

> hi Jonas,
>
> If new interactive elements such as form controls are included in the
> spec, I would hope that they are implemented in browsers to be
> accessible to people with disabilities, as yet that has not occurred.
> I don't think that the spec currently provides detailed advice or
> requirements on how accessible implementations are to be achieved, I
> am unsure the HTML5 spec is necessarily the place for this
> information.

You can expect that when new interactive elements are fully  
implemented in WebKit, they will provide the same quality of  
accessibility support that native buttons and checkboxes do today.

>
> Even when all the elements in HTML5 are supported by browsers and AT,
> there will still be an important place for ARIA in HTML5, as there are
> many features of ARIA that plug gaps in HTML5 one example is "live
> regions" another is landmark roles and another is the many roles
> provided in ARIA that do not have a corresponding HTML5 element or
> attribute. (e.g.s alert, dialog, scrollbar, status, tab, tabpanel,
> tooltip, treeitem etc)

I don't think anyone has argued to remove ARIA. It's clearly a  
necessary technology, even if we expand the set of things that can be  
done with built-in semantic elements.

Regards,
Maciej
Received on Sunday, 4 April 2010 23:01:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:07 GMT