WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: H1 to H4 titles sub titles....

for

From: Sailesh Panchang
Date: May 3, 2011 3:48PM

Allen,
Right, the technical standards do not require headings.
When S508 was written, browsers and AT did not support heading
navigation. But this has changed since.
The objective of the law is to provide "comparable access" to PWD.
Now 1194.31 (A) says "At least one mode of operation and information
retrieval that does not require user vision shall be provided, or
support for assistive technology used by people who are blind or
visually impaired shall be provided".
When the page uses text / image-text styled as headers, marking them
up with h-tags will allow comparable access to headers without
requiring blind users to read complete page using an info retrieval
feature supported by AT today that was not available in 2000-01. This
is a functional outcome.

The Access Board guide says "...a recognition that future technologies
may be developed, or existing technologies could be used in a
particular way, that could provide the same functional access in ways
not envisioned by these standards. In
evaluating whether a technology results in "substantially equivalent
or greater access," it is the functional outcome, not the form, which
is important".
I think the spirit and intent of the law are guiding factors- really
important during implementing any law.
So heading markup is required only when the page uses text /
image-text styled as headers.
Sailesh


On 5/3/11, Hoffman, Allen < <EMAIL REMOVED> > wrote:
> I'd only add that inconsistent or senseless header change will affect
> different users of screen readers in different ways, there really is no
> "correct" answer. It wouldn't rise to a 508 technical failure in
> general, unless it really makes a page absolutely un-navigable, or would
> require such user memory to make reliance on the headers for navigation
> pointless.
>
>
>
> -----Original Message-----
> From: Jeevan Reddy [mailto: <EMAIL REMOVED> ]
> Sent: Tuesday, May 03, 2011 1:53 AM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] H1 to H4 titles sub titles....
>
> Hi Nancy,
> Find out wether that H4 is used for Content or template.
> if it is used for template elements, it's not a big worry. if not, it'll
> be
> a a problem for screen reader users.
> Follow the below Standards for using H1-H6:
> 1 Use H1 or H2 For different sections in the content.
> 2 Use H3 or H4 as nested headings for different sections of content.
> 3 Don't skip the headings more than one order. That is if you used H2
> then
> use H3 or H4 as nested headings, not to use H5 or H6.
> 4 Follow the consistancy across the web site, you can use H1 as content
> header, in other pages you can use H2 or at max H3, but not H4.
> 5 use H4, H5, and H6 for other than content sections. i.e for template
> elements.
>
> As your title suggests, it is not violation as per Section 508 is
> concerned,
> but it is certainly a problem for screen reader users.
>
>
> On Mon, May 2, 2011 at 7:55 PM, Nancy Johnson < <EMAIL REMOVED> >
> wrote:
>
>> Hi,
>>
>> We are producing a site and part of my job is to see if the htmls and
>> frontend javascript jquery the design company provided is 508.
>>
>> The heading on one page goes from an H1 designation to an H4
> designation,
>>
>> Will this be a problem for screen readers?
>>
>> Thanks in advance,
>>
>> Nancy
>>