W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2013

Re: Current suggestion for subheading isn't accessible

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Tue, 7 May 2013 16:54:21 +0100
Message-ID: <CA+ri+V=7116JMr3Xf=WgsX-fAyELOfi2tbE_Tdz+O_W37gwQGA@mail.gmail.com>
To: Denis Boudreau <dboudreau@accessibiliteweb.com>
Cc: WAI Interest Group <w3c-wai-ig@w3.org>
Hi Denis,

the APis that provide roles for HTML elements do not have any subheading
semantic defined (as stated previously)

many of the the new structural elements in HTML do not have API roles

In these cases ARIA role are being used (example <header>= banner) and then
these roles are exposed as properties in the APIs

i.e. a good method to develop a role that is not already defined is via



HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>

On 7 May 2013 16:43, Denis Boudreau <dboudreau@accessibiliteweb.com> wrote:

> Hi again,
> On 2013-05-07, at 11:35 AM, Steve Faulkner <faulkner.steve@gmail.com>
> wrote:
> > probably a good place to start would be in ARIA you can suggest it on
> the wai-xtech mailing list
> I'm confused.
> On the one hand, I see people creating (or wanting to create) solutions
> based on aria all the time but on the other hand, I see people advocating
> to use native html whenever native html is available.
> If we know and agree to the fact that we should always prioritize native
> html elements whenever we can, then why not create something that adresses
> this problem in html5 directly, rather than push it on the aria side of the
> fence?
> /Denis
Received on Tuesday, 7 May 2013 15:55:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:44 UTC