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

Re: Current suggestion for subheading isn't accessible

From: Denis Boudreau <dboudreau@accessibiliteweb.com>
Date: Tue, 07 May 2013 16:13:34 -0400
Cc: WAI Interest Group <w3c-wai-ig@w3.org>
Message-id: <5A3B7A2F-FCCF-4E53-B02C-8B13C0B11CC3@accessibiliteweb.com>
To: Steve Faulkner <faulkner.steve@gmail.com>
But that hardly seems perfect (is anything ever?).

If your header only contained your heading and tagline that'd be great (in which case it'd be a lot like hgroup), but you'll also get other things in there, most of the time.

I would feel much better knowing these two pieces that are meant to go together were actually contained in the same wrapper, whatever that wrapper is - hence the first proposal with the tagline being a part of the h1.

Otherwise, it feels diluted to me.

/Denis




On 2013-05-07, at 3:51 PM, Steve Faulkner <faulkner.steve@gmail.com> wrote:

> my preferred approach would be:
> 
> <header>
> 	<h1>Main heading information</h1>
> 	<p role="subheading">Subheading information</p>
> </header>
> 
> as it would cover more of the use cases
> 
> 
> --
> 
> Regards
> 
> SteveF
> HTML 5.1
> 
> 
> On 7 May 2013 19:01, Denis Boudreau <dboudreau@accessibiliteweb.com> wrote:
> Steve,
> 
> Aaahhh. got it for aria. Makes perfect sense, thanks. That actually helps a lot.
> 
> So, my take would be that your prefered approach would be one of the following then?
> 
> <header>
> 	<h1>Main heading information</h1>
> 	<p role="subheading">Suheading information</p>
> </header>
> 
> <header>
> 	<h1>Main heading information 
> 		<div role="subheading">Suheading information</div>
> 	</h1>
> </header>
> 
> /Denis
> 
> 
> On 2013-05-07, at 11:54 AM, Steve Faulkner <faulkner.steve@gmail.com> wrote:
> 
>> 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 defined.
>> 
>> 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 ARIA.
>> 
>> 
>> --
>> 
>> Regards
>> 
>> SteveF
>> HTML 5.1
>> 
>> 
>> 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 20:13:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:48 UTC