1.6 Multiple level 1 headings used incorrectly on form pages (Low)

1.6.1 WCAG 1.3.1 (A) - Desktop

On the Personal Details page, there are three level 1 headings. The first heading is appropriate, labelling the page with the question “Does the wearer have any of the disabilities?”. However, the second and third level 1 headings are used for questions within the form, which is unexpected and causes confusion with the document structure. This makes it seem as though subsequent H2 headings like “Get help” or “Support” are subheadings of the question, rather than the overall page.

Multiple level 1 headings on a single page break the hierarchical heading structure expected by both sighted and screen reader users. Heading levels should descend logically to reflect content relationships and support clear navigation.

A similar issue occurs on the Curfew Timetable page, where each form section (day of the week) is marked up as a level 1 heading along with the actual title of the page, “Curfew Details”.

The purpose of heading elements is to provide structure to the document and facilitate keyboard navigation for assistive technology users. The WebAIM screen reader survey has found that headings are the number one means by which screen reader users get a sense of a complex page. The presence of multiple Level 1 headings can make it difficult for users to navigate and comprehend the main topics and sections of the pages.

Headings on Device Wearer page

FIGURE 1.7: Headings on Device Wearer page

Headings on Curfew Timetable page

FIGURE 1.8: Headings on Curfew Timetable page

1.6.2 Recommendation

Review heading levels across the service and ensure there is only one level 1 heading per page, representing the page’s main topic or purpose. Questions or sections within the page should use level 2 or level 3 headings as appropriate to indicate their relationship to the main heading.

For example, on the Curfew Timetable page:

<h1>Curfew details</h1>

<h2>Monday</h2>
<!-- Content for Monday -->

<h2>Tuesday</h2>
<!-- Content for Tuesday -->

<!-- and so on -->

On the Device Wearer page, the additional headings could be removed as they are questions already associated with the form inputs.