Chapter 5: Ensure effective navigation and interaction
This chapter introduction explains why accessible navigation and interaction matter in addition to readable text.
After this chapter you will be able to
- Accessibility Beyond Readable Text. Explain why readable text alone is not enough for an accessible web experience: people also need to know where they are, navigate predictably, understand page structure, follow links, and use controls with an input method that works for them.
- Page titles and heading cues. Explain how page titles and headings help people find content, understand its structure, and move through it.
- Page titles as orientation cues. Explain how unique, descriptive page titles help users tell where they are and what a page is about, and why repeated or generic titles weaken that cue.
- Page titles and orientation. Explain where a page title comes from and how people use it to identify pages when switching tabs, revisiting history, or opening bookmarks, especially when using a screen reader.
- Distinct and meaningful page names. Explain why each page title should describe that page’s purpose and distinguish it from other pages, rather than repeat only the site name or use a generic label.
- Native heading semantics. Explain why content headings should use <h1> through <h6> rather than elements styled to look like headings, and how semantic headings support navigation.
- Logical heading hierarchy. Describe how heading levels should represent sections and subsections, including when moving to a higher level is appropriate and why skipped levels should generally be avoided.
- Value of predictable navigation. Explain why unexpected changes to navigation, actions, or labels make a product harder to use, and why consistency helps.
- Stable navigation placement and order. Describe how repeated navigation and common functionality should be positioned across pages, including the allowance for responsive layouts.
- Consistent identification of actions. Explain how repeated actions and links should be identified consistently, including for assistive technology users.
- Native landmarks for page structure. Explain how semantic HTML elements such as <header>, <main>, <nav>, and <footer> communicate navigable page regions, and why they should be preferred over ARIA landmark roles when available.
- Landmarks as navigation beacons. Describe how landmarks help screen reader, keyboard-only, and voice-control users find and move to page regions.
- ARIA gaps and landmark names. Describe when ARIA roles or accessible names are needed for landmarks, including constrained generic containers, repeated landmarks, and regions made from <section> or <form>.
- Keyboard Access to Functionality. Explain why all website functionality should be available to keyboard-only users and how a pointer or touch action can have a keyboard equivalent.
- Logical and Visible Focus. Describe what makes keyboard navigation understandable as users move through a page.
- Visible keyboard position. Explain what a keyboard focus indicator shows and why keyboard navigation becomes difficult when it is missing or hard to see.
- Native and custom focus. Distinguish the focus visibility supplied by native interactive elements from what developers must provide for custom components, and explain why browser defaults should not simply be suppressed.
- Recognizable custom indicators. Describe how a custom focus indicator can remain obvious across controls and backgrounds, including contrast, size, and cues beyond color alone.
- Unobscured focused content. Explain how overlays can hide keyboard focus and describe how the section’s fixed-banner example keeps a focused element and its indicator in view.
- Predictable sequential focus order. Explain why interactive elements should receive focus in an order that preserves the page’s meaning and matches users’ expected reading flow.
- DOM and visual order alignment. Trace how DOM order normally determines sequential focus and why visually rearranging elements with CSS can produce a misleading tab sequence.
- Tabindex values and risks. Distinguish what negative, zero, and positive tabindex values do, and explain why positive values are a poor fix for incorrect HTML order.
- Modal dialog focus management. Trace where focus should go when a modal opens, while it remains open, and after it closes; describe what the native dialog element provides.
- Repeated content barrier. Explain why repeated navigation blocks can be a barrier for keyboard users and how skip links help.
- Skip link placement and behavior. Describe where a skip link goes and what happens when a keyboard user encounters and activates it.
- Skip link construction. Describe how the example connects skip links to destinations and reveals them on focus, including when multiple destinations are useful.
- Keyboard trap and its impact. Explain what a keyboard trap is, why it blocks keyboard-only users, and what can happen if refreshing is their only way out.
- Keyboard entry and exit requirement. State the section's no-keyboard-trap requirement, including what to do when a component needs a special key to exit.
- Default behavior and managed focus. Explain how canceling default key behavior or managing focus incorrectly creates traps, and distinguish an intentional modal focus trap from a keyboard trap.
- Keyboard trap testing path. Describe a keyboard-only test for traps across the page and in interactive components and overlays.
- Link and button semantics. Distinguish links that navigate to resources from buttons that trigger actions, and explain why a native <a> is preferable to an element given role="link".
- Visual link distinction. Explain how users identify links in surrounding text and what to preserve when overriding browser link styles.
- Meaningful link purpose. Explain how link text or programmatically determined context conveys a destination’s purpose, including why an overlaid “Read more” carousel link can fail and how to improve it.
- Image link accessible names. Describe how to name image-only or icon-only links and how to avoid redundant links when an image and adjacent text share a destination.
- Visible keyboard link focus. Explain what a link focus indicator communicates and describe how the section’s exercise checks a custom indicator across different backgrounds.
- Variable pointing accuracy. Explain why pointing and tapping should not be assumed to be pixel-perfect, using examples of how devices, circumstances, or abilities affect accuracy.
- Small crowded target risks. Explain why small, closely placed links or buttons can cause incorrect selections, especially when a thumb obscures them or a person cannot point precisely.
- Target size and spacing. Explain that target size means the area that responds to a click, tap, or eye-tracker dwell, not merely the visible icon or text. Describe why sufficiently large, nonoverlapping targets with space between them are easier to use than small, crowded ones.
- Pointing distance and effort. Explain how Fitts’ Law relates the time needed to reach a target accurately to its size and distance from the starting position. Describe why larger, conveniently placed controls especially help people using imprecise pointing methods.
What it builds on
- Keep it POSH (Plain Old Semantic HTML) (chapter 2) · The preference for semantic HTML over visually styled substitutes.
- When semantic HTML falls short: enter ARIA (and JS) (chapter 2) · The distinction between native HTML semantics and ARIA used when semantic HTML falls short.
- Assistive technologies (chapter 2) · The use of assistive technologies to interact with pages.
- Ensure sufficient contrast in UI components and graphics (chapter 3) · Contrast for UI components and graphics.
- Avoid using colors alone (chapter 3) · The limitation of communicating information through color alone.
- Use images carefully (chapter 3) · the accessibility implications of image content
- Liberate text embedded in images (chapter 4) · the limitations of text embedded in images
- Functional images (chapter 3) · alternative text for functional images
Section by section
Introduction
This chapter introduction explains why accessible navigation and interaction matter in addition to readable text.
- Accessibility Beyond Readable Text: Explain why readable text alone is not enough for an accessible web experience: people also need to know where they are, navigate predictably, understand page structure, follow links, and use controls with an input method that works for them.
Why it matters: A page people can read may still be difficult to use if they cannot find their way around or operate its controls.
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.
- Page titles and heading cues: Explain how page titles and headings help people find content, understand its structure, and move through it.
Why it matters: Readable content is more useful when people can find it and move through it confidently.
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.
- Page titles as orientation cues: Explain how unique, descriptive page titles help users tell where they are and what a page is about, and why repeated or generic titles weaken that cue.
Why it matters: A clear title helps people find their place, especially when using assistive technology or returning to a page later.
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.
- Page titles and orientation: Explain where a page title comes from and how people use it to identify pages when switching tabs, revisiting history, or opening bookmarks, especially when using a screen reader.
Why it matters: A useful title helps people recognize where they are without having to inspect the whole page. - Distinct and meaningful page names: Explain why each page title should describe that page’s purpose and distinguish it from other pages, rather than repeat only the site name or use a generic label.
Why it matters: Distinct titles make tabs, bookmarks, history entries, and search results recognizable on their own. - Practical title composition: Describe how to compose a concise, descriptive title by putting important page-specific information first, adding site context at the end, and aligning it with the level 1 heading where possible.
Why it matters: Putting the identifying words first helps when only the beginning of a tab title is visible, while a matching heading reduces confusion.
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.
- Native heading semantics: Explain why content headings should use <h1> through <h6> rather than elements styled to look like headings, and how semantic headings support navigation.
Why it matters: A heading that only looks right may be missing from the structure people use to navigate. - Logical heading hierarchy: Describe how heading levels should represent sections and subsections, including when moving to a higher level is appropriate and why skipped levels should generally be avoided.
Why it matters: A coherent heading outline helps readers understand the page and find their place in it. - ARIA heading fallback: Distinguish a native HTML heading from an ARIA heading and state when and how the ARIA alternative may be used.
Why it matters: Knowing the fallback prevents ARIA from replacing reliable native markup unnecessarily.
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.
- Value of predictable navigation: Explain why unexpected changes to navigation, actions, or labels make a product harder to use, and why consistency helps.
Why it matters: Predictability lets people spend their effort on their task rather than finding their way around. - Stable navigation placement and order: Describe how repeated navigation and common functionality should be positioned across pages, including the allowance for responsive layouts.
Why it matters: A stable arrangement helps users find familiar destinations without searching again on each page. - Consistent identification of actions: Explain how repeated actions and links should be identified consistently, including for assistive technology users.
Why it matters: A control that changes its name can seem to disappear, particularly to someone navigating by what a screen reader announces. - Consistent visual design patterns: Describe how consistency extends beyond navigation controls to visual design and structure, and how a design system can support it.
Why it matters: Familiar visual patterns can be especially helpful to people with cognitive or learning disabilities and memory impairments.
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.
- Native landmarks for page structure: Explain how semantic HTML elements such as <header>, <main>, <nav>, and <footer> communicate navigable page regions, and why they should be preferred over ARIA landmark roles when available.
Why it matters: Choosing native elements makes the page’s organization available to assistive technologies without recreating their semantics. - Landmarks as navigation beacons: Describe how landmarks help screen reader, keyboard-only, and voice-control users find and move to page regions.
Why it matters: Landmarks provide several ways to find a destination without exploring the whole page. - ARIA gaps and landmark names: Describe when ARIA roles or accessible names are needed for landmarks, including constrained generic containers, repeated landmarks, and regions made from <section> or <form>.
Why it matters: Appropriate roles and names make otherwise missing or ambiguous page regions usable for navigation. - Robust formatted email content: Explain why accessible formatted emails should prioritize robust content over appearance and be checked across clients and assistive technologies.
Why it matters: An email that looks fine in one client can still hide its message or actions from other readers.
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.
- Keyboard Access to Functionality: Explain why all website functionality should be available to keyboard-only users and how a pointer or touch action can have a keyboard equivalent.
Why it matters: A task should not become impossible just because someone cannot or does not use a pointer. - Logical and Visible Focus: Describe what makes keyboard navigation understandable as users move through a page.
Why it matters: Keyboard access is difficult to use if people cannot follow where focus moves or see where it is. - Modal Dialog Focus Behavior: State the focus behavior the section asks readers to check when a modal dialog opens and closes.
Why it matters: Focus should follow what the user can interact with and return to where they started after a modal closes.
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.
- Visible keyboard position: Explain what a keyboard focus indicator shows and why keyboard navigation becomes difficult when it is missing or hard to see.
Why it matters: A clear focus indicator lets keyboard users stay oriented and predict which control will respond. - Native and custom focus: Distinguish the focus visibility supplied by native interactive elements from what developers must provide for custom components, and explain why browser defaults should not simply be suppressed.
Why it matters: Keeping a usable default is safer than removing the only visible sign of focus. - Recognizable custom indicators: Describe how a custom focus indicator can remain obvious across controls and backgrounds, including contrast, size, and cues beyond color alone.
Why it matters: An indicator that disappears against a background or is too subtle still leaves users struggling to find focus. - Focus styling selectors: Distinguish what the CSS :focus and :focus-visible pseudo-classes match and explain why :focus-visible is often useful for custom keyboard focus styling.
Why it matters: Choosing a focus selector should never leave people who navigate by keyboard unable to locate focus. - Unobscured focused content: Explain how overlays can hide keyboard focus and describe how the section’s fixed-banner example keeps a focused element and its indicator in view.
Why it matters: Even a well-designed focus indicator fails if a banner or popup sits on top of 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.
- Predictable sequential focus order: Explain why interactive elements should receive focus in an order that preserves the page’s meaning and matches users’ expected reading flow.
Why it matters: A sensible focus path lets keyboard users follow the interface and complete tasks without getting lost. - DOM and visual order alignment: Trace how DOM order normally determines sequential focus and why visually rearranging elements with CSS can produce a misleading tab sequence.
Why it matters: Checking the HTML order prevents a visually tidy layout from becoming confusing to navigate by keyboard. - Task based focus exceptions: Describe when a predictable task sequence may take precedence over exact visual placement, including the form-action example.
Why it matters: A deliberate task sequence can help users continue their work without making focus jump unpredictably. - Tabindex values and risks: Distinguish what negative, zero, and positive tabindex values do, and explain why positive values are a poor fix for incorrect HTML order.
Why it matters: Choosing tabindex appropriately avoids fragile keyboard navigation as an interface changes. - Modal dialog focus management: Trace where focus should go when a modal opens, while it remains open, and after it closes; describe what the native dialog element provides.
Why it matters: Containing and restoring focus keeps keyboard users oriented when a dialog interrupts the page.
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.
- Repeated content barrier: Explain why repeated navigation blocks can be a barrier for keyboard users and how skip links help.
Why it matters: A shortcut can spare someone repeated, tiring navigation on every page. - Skip link placement and behavior: Describe where a skip link goes and what happens when a keyboard user encounters and activates it.
Why it matters: Making the shortcut available on the first Tab press lets users bypass repeated content before they encounter it. - Skip link construction: Describe how the example connects skip links to destinations and reveals them on focus, including when multiple destinations are useful.
Why it matters: Matching link targets and focus styling make the shortcut usable without JavaScript.
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.
- Keyboard trap and its impact: Explain what a keyboard trap is, why it blocks keyboard-only users, and what can happen if refreshing is their only way out.
Why it matters: A trap can stop someone from completing a task, not just slow them down. - Keyboard entry and exit requirement: State the section's no-keyboard-trap requirement, including what to do when a component needs a special key to exit.
Why it matters: An entry path is not accessible if the user has no usable, discoverable way out. - Default behavior and managed focus: Explain how canceling default key behavior or managing focus incorrectly creates traps, and distinguish an intentional modal focus trap from a keyboard trap.
Why it matters: Custom interaction code can silently remove the keyboard behavior people depend on. - Keyboard trap testing path: Describe a keyboard-only test for traps across the page and in interactive components and overlays.
Why it matters: Testing both ordinary navigation and complex interactions reveals traps that a quick forward-only pass can miss.
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.
- Link and button semantics: Distinguish links that navigate to resources from buttons that trigger actions, and explain why a native <a> is preferable to an element given role="link".
Why it matters: Correct elements communicate the right purpose and avoid having to rebuild native keyboard behavior. - Visual link distinction: Explain how users identify links in surrounding text and what to preserve when overriding browser link styles.
Why it matters: People must be able to spot a link before they can choose to follow it. - Meaningful link purpose: Explain how link text or programmatically determined context conveys a destination’s purpose, including why an overlaid “Read more” carousel link can fail and how to improve it.
Why it matters: Meaningful links let people find destinations quickly without guessing or repeatedly returning to surrounding content. - Image link accessible names: Describe how to name image-only or icon-only links and how to avoid redundant links when an image and adjacent text share a destination.
Why it matters: Names make icon links understandable, while grouping duplicate destinations reduces unnecessary stops. - New window link warnings: Explain why links opening a new tab or window warrant advance notice and how that notice can reach both sighted and assistive-technology users.
Why it matters: Advance notice helps people understand what changed and how to return to where they started. - Visible keyboard link focus: Explain what a link focus indicator communicates and describe how the section’s exercise checks a custom indicator across different backgrounds.
Why it matters: Without a visible focus cue, someone tabbing through links cannot tell where their next action will occur.
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.
- Variable pointing accuracy: Explain why pointing and tapping should not be assumed to be pixel-perfect, using examples of how devices, circumstances, or abilities affect accuracy.
Why it matters: Recognizing imprecise pointing helps explain why tiny targets can be hard to use.
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.
- Small crowded target risks: Explain why small, closely placed links or buttons can cause incorrect selections, especially when a thumb obscures them or a person cannot point precisely.
Why it matters: A selection that seems easy with a precise mouse can be risky or inaccessible with another way of pointing. - Eye tracking selection challenges: Describe why eye tracking makes precise target selection difficult and how dwell selection addresses accidental activation while introducing a tradeoff.
Why it matters: Designing for gaze-estimation error helps explain why a target that looks large enough for a mouse may not be forgiving enough. - Target size conformance thresholds: State the target-size thresholds given for WCAG Level AA and AAA, and explain that the AA minimum has limited exceptions.
Why it matters: The thresholds give teams a concrete minimum while the exceptions prevent treating every small link as an automatic failure. - Higher-risk control contexts: Explain which controls make target size and spacing especially important, and why inline paragraph links are exempt from the minimum size requirement.
Why it matters: These contexts help teams prioritize where an inaccurate selection is especially troublesome without disrupting paragraph layout.
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.
- Target size and spacing: Explain that target size means the area that responds to a click, tap, or eye-tracker dwell, not merely the visible icon or text. Describe why sufficiently large, nonoverlapping targets with space between them are easier to use than small, crowded ones.
Why it matters: People can activate a control more confidently when its usable area is generous and it is distinct from its neighbors. - Pointing distance and effort: Explain how Fitts’ Law relates the time needed to reach a target accurately to its size and distance from the starting position. Describe why larger, conveniently placed controls especially help people using imprecise pointing methods.
Why it matters: Target placement and size affect how tiring and error-prone even a simple action can be. - Safeguards for consequential targets: Describe how to reduce the harm of accidentally activating a consequential control: keep it safely apart from inconsequential controls and offer a way to undo the action or review it before confirmation.
Why it matters: An imprecise click should not easily cause an irreversible or serious mistake.
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
- Use familiar patterns (chapter 6) · Consistent navigation provides an earlier example of a predictable interface structure.
- Ensure keyboard behavior is predictable (chapter 6) · Keyboard focus and keyboard-friendly navigation.
- Interacting with tabular data (chapter 6) · Assumes the importance of keyboard-friendly interaction.
- Layout (chapter 6) · Keyboard focus and keyboard-friendly interaction.
- Data table and grid semantics (chapter 6) · The need for keyboard-friendly interaction.
- Revisiting the form (chapter 6) · Visible keyboard focus
- Offer mechanisms to support users (chapter 7) · Visible keyboard focus for interactive controls
- Group fields, when appropriate (chapter 6) · The importance of a logical keyboard focus order.
Concepts explained in this chapter
- focus indicatorA focus indicator is a visible visual cue showing which interface element currently has keyboard focus.
- :focus-visibleA CSS pseudo-class that matches an element when the browser determines that a visible focus indicator is appropriate.
- tabindexAn HTML global attribute that controls an element’s keyboard focusability and position in sequential focus navigation.
- semantic markupSemantic HTML is the use of HTML elements whose names and structure convey the meaning, role, and organization of content.
- skip linkA skip link is an interactive link that lets keyboard or assistive technology users bypass repeated content and move to a later page region.
- hyperlinkA link is an interface element that points to another resource or location and enables navigation to it.
- keyboard interactionOperating an interface using only a keyboard, without relying on a pointing device.
- keyboard trapA keyboard trap is a condition in which keyboard focus cannot move away from an element or component using the keyboard.
- accessible nameAn accessible name is the programmatically determined text label that identifies an interface element to users of assistive technologies.
- aria-labelledbyaria-labelledby is an ARIA attribute that supplies an accessible name by referencing one or more visible labeling elements.
- buttonA button element is an HTML control for triggering an action through built-in keyboard, pointer, focus, and accessibility behavior.
- empty linkAn empty link is a hyperlink that lacks a programmatically determinable accessible name.
- link purpose (in context)Link Purpose (In Context) is a WCAG success criterion requiring a link's purpose to be determinable from its text or programmatically determined context.
- visually hidden textVisually hidden text is text that remains available to assistive technologies while being visually concealed from sighted users.
- target size (minimum)A WCAG 2.2 Level AA success criterion specifying minimum pointer-target dimensions and permitted exceptions.
- custom controlA custom component is a developer-created interface component whose roles, states, labels, and behavior must be exposed to assistive technologies.
- focus orderA predictable keyboard-focus sequence that preserves visual or task-related relationships.
- modal dialogA modal dialog is an interface dialog that temporarily makes underlying page content unavailable until the dialog is dismissed.
- keyboard accessibilityThe ability to operate an interface through keyboard input without requiring a pointer or another input method.
- dialog elementThe HTML dialog element represents a modal or non-modal dialog interface with browser-supported dialog behavior.
- focus managementFocus management is the deliberate control of keyboard focus movement, placement, and return within an interactive interface.
- landmarkA semantic region identifying a major area of a page, such as navigation or main content, for assistive-technology navigation.
- page titleThe title element is the HTML element whose text supplies a document's page title to user agents.
- headingA heading is a structural text element that identifies and organizes a section of web content.
- focus trappingA focus trap is a technique that intentionally confines keyboard focus within an active interface component.
- Fitts' lawFitts' law is a model predicting the time and difficulty of reaching a target from its distance and size.
- target areaA target area is the region that responds to clicks, taps, or eye-tracker dwelling to activate an interactive component.
- target spacingTarget spacing is the distance separating the interactive areas of nearby controls.
- ARIA landmark roleAn ARIA landmark role is an ARIA semantic role that exposes an interface region as a navigable landmark.
- consistent identificationConsistent identification is a WCAG success criterion requiring components with the same function to be identified consistently.
- consistent navigationConsistent navigation is a WCAG success criterion requiring repeated navigational mechanisms to remain consistent in location and order across pages.
- consistent visual designConsistent visual design is the practice of applying uniform visual properties and interaction styling to equivalent interface elements throughout a product.
- design systemA design system is a shared collection of reusable interface components, patterns, guidance, and visual rules for building consistent products.
- heading hierarchyA heading hierarchy is an ordered structure in which heading levels reflect the nesting of page sections and subsections.
- heading levelThe structural rank of an HTML heading, from level 1 through level 6.
- ARIA roleAn ARIA role is a semantic classification assigned to an interface element to communicate its widget or structural type to assistive technologies.
- form fieldAn input field is an interface control that accepts user-entered data.
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.
