E-mail List Archives
Re: H1 to H4 titles sub titles....
From: Nancy Johnson
Date: May 5, 2011 11:24AM
- Next message: Shawn Henry: "Re: WCAG 2.0 checklist"
- Previous message: Christophe Strobbe: "Re: WCAG 2.0 checklist"
- Next message in Thread: None
- Previous message in Thread: Pollard, Larry W. (DRS): "Re: H1 to H4 titles sub titles...."
- View all messages in this Thread
Thank you for this thread...It has been intersting reading through
all of your thoughts
For the purpoe of this page in question:
Dyanmically, each page has one h1, as the h1 is dyanmically used in
navigation and <title>.....</title>
But I will change the h4's to h2's...
So will be 1- h1 tag,, 3-h2 tags, nested in the last h2 will be a
number of h3 tags..
Nancy
On Thu, May 5, 2011 at 9:10 AM, Sailesh Panchang
< <EMAIL REMOVED> > wrote:
> Allen,
> I too do not consider requiring headings simply as a method of
> skipping repetitive content (H69 of WCAG 2 techniques). Headings are
> meant to expose structure and hierarchy within a section of content
> and they are just that. Heading navigation is a feature of assistive
> technology by which users are able to perceive thstructure that most
> users can do visually. (Developers need not be aware of how headings
> are used by different groups of users... they simply need to use
> headings as conceptualized and set out in the HTML specs). This AT
> feature _incidentally_ helps users skip to main content / skip
> navigation blocks if the document is marked up well thereby satisfying
> SC 2.4.1 of WCAG2 or Para (o) of S508.
> Thanks,
> Sailesh Panchang
> www.deque.com
>
>
> On 5/4/11, Hoffman, Allen < <EMAIL REMOVED> > wrote:
>> My difficulty with full use of comparable in a technical testing context
>> is that it can mean so many things to so many people.
>>
>> While I can concur that by using headings someone using some AT products
>> can navigate on that basis, the question is, is that a function of the
>> page, or a presentation style. I don't believe most site developers
>> would connect their use of heading styles to navigation, but would
>> understand the visual appeal. This would be an item which can be
>> considered a potential testable step for 1194.31(a), as you cite, if
>> header navigation is considered part of the actual page navigation in
>> general. I don't believe headers are required for skipping repetitive
>> navigation or content, but might be accepted as one success technique
>> for that.
>>
>> Sigh.
>> If you throw five IT accessibility people one a single page you get ten
>> accessibility answers! <smile>.
>>
>> Excellent evaluation discussion.
>>
>>
>>
>>
>>
>>
- Next message: Shawn Henry: "Re: WCAG 2.0 checklist"
- Previous message: Christophe Strobbe: "Re: WCAG 2.0 checklist"
- Next message in Thread: None
- Previous message in Thread: Pollard, Larry W. (DRS): "Re: H1 to H4 titles sub titles...."
- View all messages in this Thread