WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Headings: requirements vs best practices

for

From: Birkir R. Gunnarsson
Date: Jun 23, 2016 8:54AM

You can nest a navigation region in another navigation region.
The regions you are not allowed to nest are banner, main and content
info (unless the page itself has nested pages within it, such as
frames).
In any case if you use headings or skip links you satisfy 2.4.1
I strongly recommend ARIA landmarks, because when used correctly they
provide consistent and clear description of how the page content is
organied, one that corresponds closely to how people inspect the page
visually.



On 6/23/16, Ryan E. Benson < <EMAIL REMOVED> > wrote:
> I am going to disagree with some of the comments in this thread.
>
> They are correct that no where in 508 you will see thou must use headings.
> However you can interpret 508 to say headings should be used. In 508, a
> common practice is to say: if something within 1194.2x is used, then
> 1194.31 and 1194.41 is applicable. Within 31, there is a requirement for
> keyboard accessibility, you could argue things like headings are included
> into this because some AT allows heading navigation
>
> Ryan E. Benson
> On Jun 21, 2016 14:55, "Alan Zaitchik" < <EMAIL REMOVED> > wrote:
>
>> Can someone help resolve the questions we've been tussling with concerning
>> headings:
>>
>> 1. Is it a legal requirement (section 508) that each web page have at
>> least one H1 heading?
>> 2. Is it a legal requirement (section 508) that each web page have at
>> most one H1 heading?
>> 3. Does WCAG 2.0 level AA require that each web page have at least one
>> H1 heading?
>> 4. Does WCAG 2.0 level AA require that each web page have at most one
>> H1 heading?
>>
>> I want to ask similar questions about the ordering of headings at other
>> levels, but let me start with H1 to begin with.
>>
>> Thanks,
>>
>> A
>> >> >> >> >>
> > > > >


--
Work hard. Have fun. Make history.