RE: ARIA semantics for secondary navigation

>I don't think it is ideal to rely on aria-labelledby property because,
>in many instances, there will be no visible label to hook onto.
And when there is a visible label (in a heading tag as recent examples on
this thread indicate), and there is proper structure surrounding the list of
nav elements (like a list to group them), a role that says 'navigation' may
be redundant.
And when there is no such visible label, a role that   unambiguously
conveys, well, the role of the element in the context would be helpful. I
listed some this morning for starters.    

Sailesh Panchang
Accessibility Services Manager (Web and Software)
Deque Systems Inc. (www.deque.com)
11130 Sunrise Valley Drive, Suite #140,
Reston VA 20191
Phone: 703-225-0380 (ext 105)
E-mail: sailesh.panchang@deque.com

-----Original Message-----
From: wai-xtech-request@w3.org [mailto:wai-xtech-request@w3.org] On Behalf
Of Victor Tsaran
Sent: Tuesday, May 19, 2009 2:04 PM
To: Ryan Doherty; wai-xtech@w3.org
Subject: RE: ARIA semantics for secondary navigation

I don't think it is ideal to rely on aria-labelledby property because,
in many instances, there will be no visible label to hook onto. 

-----Original Message-----
From: wai-xtech-request@w3.org [mailto:wai-xtech-request@w3.org] On
Behalf Of Ryan Doherty
Sent: Tuesday, May 19, 2009 8:30 AM
To: wai-xtech@w3.org
Subject: Re: ARIA semantics for secondary navigation


   Thanks everyone for their input. It seems that 'aria-labelledby' is
the best option for now, even though screen readers won't announce it.  
Future-proofing I guess :)

It would be nice (although probably too late) to have some sort of
'secondary' or 'subnav' roles available for situations like this, which
is quite common.

-Ryan


On May 18, 2009, at 6:49 PM, Jon Gunderson wrote:

> This is the proper markup using ARIA:
>
> <div role="navigation" aria-labelledby="nav1">
> <h2 id="nav1">main menu</h2>
> ...
> </div>
>
> ---- Original message ----
>> Date: Mon, 18 May 2009 23:44:11 +0200
>> From: "Simon Pieters" <simonp@opera.com>
>> Subject: Re: ARIA semantics for secondary navigation
>> To: "Victor Tsaran" <vtsaran@yahoo-inc.com>, 
>> sailesh.panchang@deque.com , "Ryan Doherty" <rdoherty@mozilla.com>, 
>> wai-xtech@w3.org
>>
>> On Mon, 18 May 2009 23:23:00 +0200, Victor Tsaran 
>> <vtsaran@yahoo-inc.com
>> > wrote:
>>
>>>> I thought there was a way to name landmarks already: using one of 
>>>> the <h1>-<h6> elements.
>>
>>> Do you mean by embeding landmarks inside headings?
>>>
>>
>> No, by placing a heading in the landmark.
>>
>>  <div role="navigation">
>>   <h2>main menu</h2>
>>   ...
>>  </div>
>>
>> I looked briefly at the ARIA spec and didn't find anything about 
>> this, so I was probably wrong. However, I think it's the logical 
>> thing to use and it would be nice if the association would just work.
>>
>> (In HTML5, the <nav> element creates a section, and the outline 
>> algorithm will associate an <hgroup> or <h1>-<h6> element with the 
>> section, if there is one.)
>>
>> --
>> Simon Pieters
>> Opera Software
>>
> Jon Gunderson, Ph.D.
> Coordinator Information Technology Accessibility Disability Resources 
> and Educational Services
>
> Rehabilitation Education Center
> Room 86
> 1207 S. Oak Street
> Champaign, Illinois 61821
>
> Voice: (217) 244-5870
>
> WWW: http://www.cita.uiuc.edu/
> WWW: https://netfiles.uiuc.edu/jongund/www/
>
> ---------------------------------------------------------------
> Privacy Information
> ---------------------------------------------------------------
> This email (including attachments) is covered by the Electronic 
> Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and 
> may be legally privileged. It is intended for the use of the 
> individual or entity to which it is addressed and may contain 
> information that is privileged, confidential, and exempt from 
> disclosure under applicable law. If the reader of this email is not 
> the intended recipient, or agent responsible for delivering or copying

> of this communication, you are hereby notified that any retention, 
> dissemination, distribution, or copying of this communication is 
> strictly prohibited. If you have received this communication in error,

> please reply to the sender that you have received the message in 
> error, then delete it. Thank you.
>

Ryan Doherty
rdoherty@mozilla.com

Received on Tuesday, 19 May 2009 18:31:35 UTC