Within-Page Navigation

Accessibility Techniques for Within-Page Navigation
Topic	Technique	WCAG AA Requirement
Methods to Bypass Blocks of Content	Bypass Blocks: A method MUST exist to bypass repeated blocks of content. Possible techniques applicable to almost all pages include skip links, headings, and landmarks. It's best to use all of these techniques, if possible. Other techniques include page-specific table of contents links and expandable/collapsible regions. Testing methodology 2.4.1.a	Required WCAG 2.4.1
Reading/Focus Order	Reading Order: The reading order MUST be logical and intuitive. Testing methodology 1.3.2.a	Required WCAG 1.3.2
Reading/Focus Order	Focus Order: The navigation order of focusable elements MUST be logical and intuitive. Testing methodology 2.4.3.a	Required WCAG 2.4.3
Skip Links	Provide a Skip Link: A keyboard-functional "skip" link SHOULD be provided to allow keyboard users to navigate directly to the main content.	Best Practice
	First Focusable Element: The "skip link" SHOULD be the first focusable element on the page.	Best Practice
	Skip Link Visibility: A skip link MUST be either visible at all times or visible on keyboard focus.	Best Practice
Table of Contents	Table of Contents Links: A table of contents for the page MAY be included at the top of the content or in the header.	Best Practice
Table of Contents	Reflect the Heading Structure: If a table of contents for the page is included, it SHOULD reflect the heading structure of the page.	Best Practice
Paginated Views	Visual "You Are Here" Indicator: A paginated view SHOULD include a visible method of informing users which view is the currently active/visible view.	Best Practice
Paginated Views	Non-Visual "You Are Here" Indicator: A paginated view SHOULD include a method available to assistive technologies of informing non-visual users which view is the currently active/visible view.	Best Practice
Single-Key Shortcuts	Single-Key Shortcuts: If a single-character-key shortcut exists, then at least one of the following MUST be true: single-character-key shortcuts can be turned off, remapped, or are only active when the relevant user interface component is in focus.	Required WCAG 2.1.4 (WCAG 2.1)