How to test
Visit pages from every section of the site. Are common elements and features in the same location on every page? Check every feature and element that occurs on most pages: header, "skip to main content" link, search box, primary navigation menu, secondary navigation menu, sidebars, footers and other elements.
Ensure the page title is brief, clear, informative and unique.
- Firefox Web Developer and Chrome Web Developer
- Information > View Document Outline
- Outline > Show Element Tag Names, then Outline > Outline Headings
- Chrome WAVE extension
- WAVE marks all headings with their heading level.
- Internet Explorer Web Accessibility Toolbar
- Structure > Heading Structure
- Structure > Headings
Skip to main content links
Tab to the "Skip to main content" link. Check that it has focus, then press the Enter key to ensure it "jumps" to the main content.
Meaningful link text
Tab through the page and ensure that the destination of every link is clear from its link text, even if the link was removed from the content. (See more on accessible links.)
Document landmark roles
To come. (See more on ARIA landmark roles.)
- Ensure the menu is keyboard accessible:
- Tab through the menu using the tab, shift+tab and right and left arrow keys.
- Ensure that submenus open on focus (by pressing the tab, enter or down arrow keys or the spacebar) and that submenus close and focus is restored to the parent menu when focus leaves the submenu (by pressing the escape, up or tab key).
- Test that submenus can be navigated using tab, shift+tab, or up and down arrow keys.
- Check that links are large enough to be easily clicked.
- Ensure that the current page’s menu item is indicated and that each link has focus as you tab through.
- Check that the site contains a sitemap and a link to the sitemap exists on every page listed in the sitemap.
- On the sitemap, check that each link leads its target page.
Relevant W3C WAI documents
- WCAG 2.1 Guideline 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
- How to Meet WCAG 2.1 Guideline 1.3.1
- WCAG 2.1 Guideline 1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.
- How to Meet WCAG 2.1 Guideline 1.3.2
- WCAG 2.1 Guideline 2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
- How to Meet WCAG 2.1 Guideline 2.4.1
- WCAG 2.1 Guideline 2.4.2 Page Titled: Web pages have titles that describe topic or purpose.
- How to Meet WCAG 2.1 Guideline 2.4.2
- WCAG 2.1 Guideline 2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.
- How to Meet WCAG 2.1 Guideline 2.4.4
- WCAG 2.1 Guideline 2.4.5 Multiple Ways: More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.
- How to Meet WCAG 2.1 Guideline 2.4.5
- WCAG 2.1 Guideline 2.4.6 Headings and Labels: Headings and labels describe topic or purpose.
- How to Meet WCAG 2.1 Guideline 2.4.6
- WCAG 2.1 Guideline 3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.
- How to Meet WCAG 2.1 Guideline 3.2.3