{"id":3160,"date":"2025-09-11T12:54:58","date_gmt":"2025-09-11T19:54:58","guid":{"rendered":"https:\/\/wsu.edu\/digital-accessibility\/?page_id=3160"},"modified":"2026-04-16T15:51:12","modified_gmt":"2026-04-16T22:51:12","slug":"headings-and-accessibility","status":"publish","type":"page","link":"https:\/\/wsu.edu\/digital-accessibility\/core-concepts\/headings\/headings-and-accessibility\/","title":{"rendered":""},"content":{"rendered":"
\r\n \n
\r\n\t\n\n

Headings and Accessibility <\/h2>\n\n\n\n

This web page is intentionally created with accessibility errors to demonstrate the functionality of automatic accessibility checkers for web pages. View this webpage in an accessibility checker (WAVE)<\/a> to help identify accessibility issues in other forms of digital content. <\/p>\n\n\n\n

Error Types<\/strong>: Errors must<\/strong> be fixed. Alerts should<\/strong> be fixed. These fixes, both errors and alerts, improve the accessibility and usability of the content. <\/p>\n\n\n\n

Best Practice<\/strong>: Use a hierarchical sequence of headings. Headings provide an outline of your content. It enables people to navigate to the information they seek by scanning a web page or digital document, or using assistive technology to extract headings or navigate by headings.<\/p>\n\n<\/div>\r\n\n<\/div>\n\n\n

\n\n\n
\r\n \n
\r\n\t\n\n

Missing Heading 1<\/h2>\n\n\n\n

The missing heading 1 is an alert. A Heading 1 helps identify the page topic for people and search engines. This alert should be fixed. <\/p>\n\n\n\n

Notice<\/strong>: At the top of the web page, the breadcrumb does not include this page because this web page is missing the page title\/heading 1. Adding a page title block does not solve the breadcrumb issue. <\/p>\n\n\n\n

Error Type<\/strong>: Alert<\/p>\n\n\n\n

Best Practice<\/strong>: Each web page or electronic document<\/a> should have one heading level 1 that represents the main topic of the digital document.  <\/p>\n\n\n\n

Missing Page Title<\/h3>\n\n\n\n

If the web page is missing the title tag<\/a>, it is an error and must be fixed. A web page must have a meaningful page title. <\/p>\n\n\n\n

WordPress<\/strong>: In WordPress, the page or post title (Add title) of a web page supplies the heading 1 and the document title for the web page. Leaving the page or post title\/heading 1 empty, like this web page, or only adding a Heading block with an H1 to a page, does not populate the document title. A missing document title is an error and must be fixed. <\/p>\n\n\n\n

Error Type<\/strong>: Error<\/p>\n\n\n\n

Best Practice<\/strong>: Each web page or electronic document<\/a> should have a document title that represents the main topic of the digital document.  <\/p>\n\n<\/div>\r\n\n<\/div>\n\n\n

\n\n\n
\r\n \n
\r\n\t\n\n

One Heading Level 1 Per Page<\/h2>\n\n\n\n

The heading above is a heading 1. If it were a heading 1, it would override the missing page title\/heading 1 at the top of the page. <\/p>\n\n\n\n

Pages should only have one heading 1. A Heading 1 should begin the main content of the web page. This allows assistive technology to easily jump to the beginning of the content (the heading 1) on the web page. This alert should be fixed. <\/p>\n\n\n\n

Error Type<\/strong>: Alert<\/p>\n\n\n\n

Best Practice<\/strong>: Use only one heading level 1. <\/p>\n\n<\/div>\r\n\n<\/div>\n\n\n

\n\n\n
\r\n \n
\r\n\t\n\n

Skipped Heading Level<\/h4>\n\n\n\n

A skipped heading level interrupts the hierarchy and outline of the page. This alert should be fixed.<\/p>\n\n\n\n

Error Type<\/strong>: Alert<\/p>\n\n\n\n

Best Practice<\/strong>: Do not skip down in heading levels.<\/p>\n\n<\/div>\r\n\n<\/div>\n\n\n

\n\n\n
\r\n \n
\r\n\t\n\n

<\/h2>\n\n\n\n

There is an empty heading block between this sentence and the previous sentence. Missing headings are errors and must<\/strong> be fixed. Wave will identify the heading level and the missing heading. WAVE and Web Developer (Browser Add-on) will catch this issue. This error must be fixed.<\/p>\n\n\n\n

Error Type<\/strong>: Error<\/p>\n\n\n\n

Best Practice<\/strong>: Remove empty headings. People using assistive technology will be alerted to empty headings, which could be confusing.<\/p>\n\n<\/div>\r\n\n<\/div>\n\n\n

\n\n\n
\r\n \n
\r\n\t\n\n

Heading 2? <\/strong><\/p>\n\n\n\n

This heading above is intentionally styled to look like a heading. The application formatting tool, like WordPress’s Heading block, was not used to create this text. Not all automatic accessibility checkers will catch that this could be a heading. If this is a heading that identifies and describes the following content, then it is an alert that should be fixed.<\/p>\n\n\n\n

Error Type<\/strong>: Alert<\/p>\n\n\n\n

Best Practice<\/strong>: Use an application\u2019s formatting tools<\/a> or apply HTML tags to properly format headings.<\/p>\n\n<\/div>\r\n\n<\/div>\n\n\n

\n\n\n
\r\n \n
\r\n\t\n\n

Fake heading<\/strong><\/p>\n\n\n\n

Oftentimes, bold text is used to represent a heading. If the bold text is part of the content’s organization, then it should be fixed with the appropriate formatting tools. This is a manual check. An automatic accessibility checker will not catch that this should be a heading. <\/p>\n\n\n\n

Error Type<\/strong>: None (usually), but it is an Alert<\/p>\n\n\n\n

Best Practice<\/strong>: Avoid manually styling text with bold or italics to indicate a heading.<\/p>\n\n<\/div>\r\n\n<\/div>\n\n\n

\n\n\n
\r\n \n
\r\n\t\n\n

Headings should be front-loaded and concise to help people easily navigate to their intended content. <\/h2>\n\n\n\n

Headings should be concise and front-loaded with informative words. Assistive technology can list the headings for people, allowing them to easily navigate to the content. The heading for this section of content is long and disruptive to the flow of the heading list. Also, it isn’t front-leaded with important details. <\/p>\n\n\n\n

Error Type<\/strong>: None. This is a best practice<\/p>\n\n\n\n

Best Practice<\/strong>: Provide short descriptive headings. Descriptive headings provide people with the information used to scan and navigate to the information they seek.<\/p>\n\n<\/div>\r\n\n<\/div>\n\n

\r\n
\n
\r\n \n
<\/div>\n\n
\r\n \n\n

Accessibility Checks<\/h2>\n\n\n\n

This list of accessibility checks for Core Concept Headings includes whether it is an automatic check or manual check<\/p>\n\n\n\n