Ensure ARIA regions, landmarks and HTML sections are identifiable

Description

Module: 04 Settings: Schedule & Details

Multiple section elements are present on the page. Whenever sections are present these elements must be programmatically labelled so that there is an accessible name to differentiate these elements.

When there is only one landmark or region, it is still a best practice to label these elements, but when there is only one element of that type (e.g. one article element) it will be more obvious to users which element (such as the article) they are looking for will be.

  1.  

    1. Acceptance Criteria

Developers should use ids on appropriate elements, and programmatically connect these elements with their parent grouping element through the use of aria-labelledby.

Example:
<section class="group-settings basic" aria-labelledby="basic">
<h2 id="basic" class="title-2">Basic Information</h2>
...
</section>

Severity: 3

  1.  

    1. Internal Comment:

IMHO the use of the <header> element is gratuitous here. Recommend removing <header> element from each section of this page. The use of Headings on this page is sufficient for providing structure and navigation aids on this page.

Status

Assignee

Unassigned

Reporter

Mark Sadecki

Accessibility - Severity

2

Accessibility - Frequency

3

Accessibility - Effort

3

Deadline

None

Platform Area

None

Priority

CAT-4
Configure