-
Notifications
You must be signed in to change notification settings - Fork 8.6k
Accessibility: Headings #11519
Copy link
Copy link
Closed
Labels
Project:AccessibilityTeam:Platform-DesignTeam Label for Kibana Design Team. Support the Analyze group of plugins.Team Label for Kibana Design Team. Support the Analyze group of plugins.bugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experience
Metadata
Metadata
Assignees
Labels
Project:AccessibilityTeam:Platform-DesignTeam Label for Kibana Design Team. Support the Analyze group of plugins.Team Label for Kibana Design Team. Support the Analyze group of plugins.bugFixes for quality problems that affect the customer experienceFixes for quality problems that affect the customer experience
Type
Fields
Give feedbackNo fields configured for issues without a type.
Related to #11518.
Problem
A logical heading structure greatly enhances the accessibility of a web page. Headings are used for page navigation and orientation.
Top-level
Screen reader users rely upon unique and descriptive top-level heading for each page. Each page should generally have one first-level heading (
<h1>), which should typically contain the document<title>or main heading for that page.Multi-level
There are places where the heading structure skips a level (see example below on the "Discover" page). This can cause confusion for screen reader users who rely on a logical heading structure to orient themselves within the page. Heading levels should not be skipped, though it is acceptable to have lower level headings (such as an
<h2>) precede the<h1>if the page structure requires it.Note: As part of this issue, we should migrate all headings to rely upon the UI Framework typography styles, instead of the Bootstrap styles.
Audit
Examine each route and define an appropriate H1, which should be the same as the page title.