WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Headings

for

From: Jorge Fernandes
Date: Jan 5, 2010 4:42AM

Hi Geof,

You could see an example at: www.acapo.pt (portuguese blind
association).

--jorge fernandes

++início do rodapé
Jorge Fernandes | <EMAIL REMOVED>
UniversalAccess.blogspot.com


On 5 Jan 2010, at 01:45, Geof Collis wrote:

> Hi All
>
> I kind of like Georges' example and have put it
> into practice on my local server, it works well
> but I'm not very familiar with definition lists
> and wonder if it is the proper use and
> construction? Will it pass WCAG? The example I
> cited a while back only said ul and ol were accepted.
>
> cheers
>
> Geof
>
>
>
> At 02:05 PM 1/4/2010, you wrote:
>> Hi,
>>
>> According to WCAG2.0 seems me that Geoff is right: hierarchy headings
>> are to apply in main content of the page and not to navigation titles
>> that surround it.
>>
>> But semantically, what is a navigation title?
>>
>> In a navigation scheme my thought is that we are semantically in
>> presence of a definition term, where "main navigation" is the <dt>
>> (definition term) and the options are the <dd> (definition data). So,
>> something like:
>>
>> <dl>
>> <dt>Main menu</dt>
>> <dd>
>> <ul>
>> <li>option 1</li>
>> <li>option n</li>
>> </ul>
>> </dd>
>> </dl>
>>
>> In that way the user agent always "know" that are in "option n" of
>> "main menu". This kind of semantic structure give context to the user
>> agent.
>>
>> What do you think about this construct?
>>
>> Regards,
>> Jorge Fernandes
>>
>> ++início do rodapé
>> Jorge Fernandes | <EMAIL REMOVED>
>> UniversalAccess.blogspot.com
>>
>>
>> On 21 Dec 2009, at 21:06, Geof Collis wrote:
>>
>>> Hi Andrew
>>>
>>> I think the argument here is that my navigation are supposed to be
>>> headings, but I dont see it that way, navigation is navigation and
>>> then there is content. I dont see a need to use headings as I have
>>> said before, all I have is bold text to signify that it is a mainn
>>> navigation and categories, if I chose not to put any text then
>>> there
>>> would be no need to put headings at all.
>>>
>>> cheers
>>>
>>> Geof
>>>
>>>
>>>
>>> At 03:59 PM 12/21/2009, you wrote:
>>>> Geof,
>>>> Maybe you already fixed it, but when I look at the code I see one
>>>> <h1> and two <h2> elements, and in my book those count as headings.
>>>>
>>>> Thanks,
>>>> AWK
>>>>
>>>> Andrew Kirkpatrick
>>>>
>>>> Senior Product Manager, Accessibility
>>>>
>>>> Adobe Systems
>>>>
>>>> <EMAIL REMOVED>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: <EMAIL REMOVED>
>>>> [mailto: <EMAIL REMOVED> ] On Behalf Of
>>>> Moore,Michael (DARS)
>>>> Sent: Monday, December 21, 2009 3:48 PM
>>>> To: WebAIM Discussion List
>>>> Subject: Re: [WebAIM] Headings
>>>>
>>>> My own personal warped opinion is that if it visibly looks like a
>>>> heading then it should be coded as a heading. Why would you want
>>>> headings for sighted users that are not available for screen reader
>>>> users? As far as the heading order goes, you can control that
>>>> through the code order with CSS and/or make the main heading an h1
>>>> and the other headings lower heading. If I want to get to the main
>>>> heading using a screen reader I can just whack the key for that
>>>> heading level - the "1" key in JAWS.
>>>>
>>>> Mike Moore
>>>> (512) 424-4159
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: <EMAIL REMOVED>
>>>> [mailto: <EMAIL REMOVED> ] On Behalf Of Geof
>>>> Collis
>>>> Sent: Monday, December 21, 2009 1:03 PM
>>>> To: WebAIM Discussion List
>>>> Subject: Re: [WebAIM] Headings
>>>>
>>>> But I want the first heading to be the main content, I have skip
>>>> links, they are marked up as lists and I use role landmarks, is
>>>> that
>>>> not enough?
>>>>
>>>> At 01:55 PM 12/21/2009, you wrote:
>>>>>> They are, but is it an WCAG issue if they aren't coded as
>>>>>> headings?
>>>>>
>>>>> Looking at the sufficient techniques for WCAG 2.0 4.1.2
>>>>> (http://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-
>>>>> rsv.html),
>>>>> I would think that they should be marked up as headings.
>>>>>
>>>>> Tim
>>>>>