WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: PDF and heading structure

for

From: L Snider
Date: Oct 24, 2024 9:22AM

I would agree with your assessment Claire. I almost always have one H1 in a
document. Anyone I know who uses a screen reader has always told me that is
what they wanted, and then the H2 would follow for sections, etc. I ignore
some of WCAG and go with the people I know and have talked to...Headings
are very important if you can't see the document. The 508 resource is a
good one.

Others may go different paths.

Cheers

Lisa



On Wed, Oct 23, 2024 at 12:52 PM Claire Forbes < <EMAIL REMOVED> > wrote:

> Good morning, everyone -
> I'm struggling with some PDF reviews as I'm flagging documents as
> non-compliant (under item 1.3.1: Heading tags are provided in appropriate
> sequence (<H1>, <H2>, <H3>, etc.)) because all headings in the documents
> are <H1> tags. I made the recommendation to tag the cover page title as
> <H1> and all subsequent headings as <H2>, <H3>, etc. (all headings after
> the cover page title visually look the same, so I didn't think the cover
> should be <H> and then all others <H1>)
>
> I have verbiage from WebAIM regarding headings: "Headings create an
> outline for the page, similar to a term paper outline or table of contents.
> The <h1> describes the page as a whole (and should be similar to the page
> <title>). A page should typically have only one <h1>. Headings <h2> through
> <h6> represent increasing degrees of "indentation" in our conceptual
> "outline"." (https://webaim.org/techniques/semanticstructure/)
>
> I have a table of information from Section 508.gov "<H1> Heading 1:
> Document's title; <H2> Heading 2: Chapter or main-level headings; <H3> -
> <H6> Heading 3 - Heading 6 Subsequent subheadings" (
> https://www.section508.gov/create/pdfs/common-tags-and-usage/)
>
> Anyone have other resources I can reference to help back the stance that
> it's not beneficial to have headings all tagged as <H1>?
>
> Thank you,
> Claire
> > > > >