liveBook · Manning

Chapter 5: Ensure effective navigation and interaction

What you will learn in chapter 5 of Architecting Accessibility

This chapter introduction explains why accessible navigation and interaction matter in addition to readable text.

After this chapter you will be able to

What it builds on

Section by section

Introduction

This chapter introduction explains why accessible navigation and interaction matter in addition to readable text.

Key terms: readability, navigation, interaction, input method

5.1 Page title, headings, and consistent navigation

Explains why page titles and headings help people find and navigate readable content.

Key terms: page titles, headings, navigate by structure

5.1.1 Carefully crafted page titles and content headings

This section explains how unique, descriptive page titles help users identify and return to a page.

Key terms: page titles, unique, descriptive page titles, navigational cue

5.1.2 Set unique page titles

This section explains why every web page needs a descriptive, distinct title and how to write one that helps people identify the page in different browsing contexts.

Key terms: page title, <title> element, tabs, history entries, bookmarks, screen reader users, unique, meaningful, page’s subject, Page Titled

5.1.3 Set page headings properly

This section explains how semantic HTML headings create a navigable content hierarchy and why native headings are preferable to ARIA substitutes.

Key terms: HTML heading elements, accessibility tree, screen reader navigation, heading levels, content hierarchy, <h1>, skipped levels, ARIA heading role, role="heading", aria-level

5.1.4 Ensure a consistent navigation experience

This section explains how consistent placement, naming, and visual design make navigation more predictable and less demanding for users.

Key terms: consistency, cognitive load, recognition, navigation mechanisms, relative order, responsive layouts, skip links, consistent identification, labels, icons

5.2 Ensure proper use of landmarks

The section explains how semantic landmarks help people navigate a page, when ARIA is needed to supplement them, and how to make formatted emails robust across clients.

Key terms: semantic HTML, landmarks, ARIA landmark roles, screen readers, skip links, voice-control users, accessible name, aria-label, aria-labelledby, role="region"

5.3 Build keyboard-friendly websites

This section explains why websites must support keyboard-only use and introduces basic checks for keyboard access and focus.

Key terms: keyboard-only users, keyboard equivalent, form controls, focus, logical focus ordering, visible focus indicator, modal dialogs, triggering action

5.3.1 Ensure keyboard focus is visible

This section explains how to make keyboard focus easy to see, including when custom styles or overlapping content could hide it.

Key terms: keyboard focus indicator, keyboard navigation, interactive element, native interactive elements, custom components, browser defaults, focus indicator, custom focus indicators, contrast ratio, two-color focus indicator

5.3.2 Set out a logical focus order

This section explains how to make sequential keyboard focus predictable through DOM order, careful use of tabindex, and focus management in modal dialogs.

Key terms: focus order, Tab, Shift+Tab, logical order, DOM, Flexbox, float, HTML, logical task order, visual reading order

5.3.3 Help users skip repeated blocks

This section explains why skip links matter to keyboard users and shows how to build links that bypass repeated page content.

Key terms: skip links, repeated blocks of content, keyboard users, skip link, keyboard focus, first focusable element, <main>, HTML document fragment, id attribute, :focus pseudo-class

5.3.4 Avoid keyboard traps

This section explains why keyboard users must be able to leave every component they can enter, how traps arise, and how to test for them.

Key terms: keyboard trap, keyboard focus, keyboard-only users, No Keyboard Trap, WCAG Success Criterion 2.1.2, special key, event.preventDefault(), Tab, Shift+Tab, semantic HTML

5.4 Links done right

This section explains how to make links semantically correct, recognizable, meaningful, and operable for people using visual, keyboard, and assistive-technology navigation.

Key terms: <a>, <button>, role="link", inline links, underline, visited, link purpose, programmatically determined context, descriptive link text, aria-labelledby

5.5 Design for imprecision: touch, gaze, and mouse pointing

This section explains why interfaces cannot assume that people point or tap with pixel-level precision.

Key terms: pointing, pixel-perfect, targets

5.5.1 Understand error traps

This section explains how small, crowded pointer targets become error traps and why target size and spacing matter for different users and interactions.

Key terms: targets, error traps, target size, spacing, eye trackers, calibration drift, dwell selection, Midas touch, gaze estimation error, SC 2.5.8

5.5.2 Design forgiving targets

This section explains how larger, well-spaced, thoughtfully placed targets make pointer interactions more forgiving and reduce accidental activation.

Key terms: target size, target area, CSS px, spacing, Fitts’ Law, starting position, travel distance, eye-tracking input, serious consequences, undo

5.6 Summary

5.7 References

This section lists sources cited in the chapter without explaining new concepts.

Where this is used later

Concepts explained in this chapter

← Chapter 4: Make text easy to understand Chapter 6: Help people complete tasks efficiently →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.