Chapter 6: Help people complete tasks efficiently
The chapter introduction shifts from navigation to task completion, explaining why accessible forms, support for mistakes, and enough time matter.
After this chapter you will be able to
- Accessible form task support. Explain why forms are central to online tasks and how labels, hints, and instructions help people complete them with less effort.
- Forms as task enablers. Explain why forms should be judged as part of a person’s task flow, not merely as collections of input fields, and how poor design can prevent task completion.
- Barriers in the example form. Describe concrete accessibility barriers in the example form and explain the user difficulty each creates, such as disappearing placeholders, color-only error cues, or unsuitable input fields.
- Visible and associated form labels. Explain why every form control needs a permanently visible label associated with the control, preferably using a <label> whose for attribute matches the control’s id. Distinguish a label from a placeholder and describe how the association helps screen-reader and voice-interaction users.
- Clear required field indicators. Explain how a form should distinguish required from optional fields both visibly and programmatically, and why stating “required” beside each label is clearer than relying on an asterisk or a form-level instruction.
- Accessible labels and field hints. Distinguish a field’s brief label from supplementary instructions, and describe how to present and associate hints so they remain available while the user enters information.
- Native form elements. Explain why accessible forms should use native semantic HTML elements rather than making generic elements imitate controls.
- Appropriate input types. Describe what an appropriate type attribute tells the browser about an <input> and what assistance the browser may provide.
- Programmatic form field grouping. Explain when to group related form fields with <fieldset> and <legend>, and why visual grouping alone is insufficient.
- Logical multi-step form division. Justify when a multi-step wizard can help and how its steps should be divided.
- Accessible wizard progress and recovery. Describe the accessibility obligations introduced when a form becomes a multi-step wizard.
- Predictable keyboard form operation. Describe how a form should behave for keyboard and screen reader users, and how to check that behavior. Explain what native HTML provides and why custom validation or dynamic interactions need additional attention.
- Contained dynamic form updates. Explain when an automatic form update is acceptable and how to make it available to screen reader users. Contrast that approach with offering a button to request the update.
- Safe single-character shortcuts. Explain why unmodified single-character shortcuts can interfere with users and describe the controls required for those shortcuts.
- Validation layers and native behavior. Explain why forms use both client-side and server-side validation, and describe what native HTML validation provides and where it can fall short.
- Actionable field error cues. Describe how to make an individual field error understandable and accessible, including what to change when the user corrects it.
- Multi-error recovery and focus. Describe how focus and an error summary help users recover when a submission has multiple errors, including when a dynamically created summary can receive focus.
- Timely accessible validation updates. Explain how to time client-side feedback and distinguish a field description from a live-region announcement.
- Preserving work after rejection. Explain what must happen to entered values when server-side validation returns errors and why it matters for accessibility.
- Form task feedback stages. Describe when forms may need status updates and why a clear outcome message closes the feedback loop. Explain why an important transaction may warrant a confirmation page rather than a temporary success message.
- Live region announcement mechanism. Explain why dynamic messages away from focus can be missed and how a pre-existing live region lets a screen reader announce changes without requiring navigation to them.
- Announcement urgency and roles. Distinguish polite, assertive, and off live-region behavior, and explain when to choose status rather than alert for an update.
- Accessible toast status pattern. Apply the section’s toast pattern to form-processing updates: explain why an ordinary toast is missed, why moving focus is unsuitable, and how to make its messages available without interrupting the user.
- Prefilled and carried-forward information. Explain when to pre-populate fields and carry information forward across forms or pages, and why doing so helps users.
- Input types and native behavior. Describe what an input type tells the browser and how appropriate types provide useful behavior, using password or date fields as an example.
- Programmatically identified input purpose. Distinguish an input's data type from its purpose, and explain how appropriate autocomplete tokens help browsers and assistive technologies support form filling.
- Native controls over impostors. Explain why native HTML controls are the default and why adding an ARIA role to a generic element does not make it function like that control.
- Custom component justification. Describe how to decide whether a custom component is warranted, including why a desired visual style alone is insufficient.
- Custom role behavior commitments. Explain the behavior a team commits to when it gives a custom component an ARIA role, including appropriate keyboard conventions and synchronized states.
- Real usability testing. Explain why custom components need testing with assistive technologies rather than relying only on ARIA inspection or automated scans.
- Form labels and structure. Explain how the revised form identifies fields, names the form, groups related fields, and indicates required fields.
- Form error recovery pattern. Trace what happens when submission finds validation errors and how users are guided to correct them.
- Table versus grid choice. Distinguish a data table from a data grid and explain when to use each for information arranged in rows and columns.
- Grid semantics and behavior. Explain what ARIA role="grid" communicates and what developers must still provide for a data grid.
- Contained tabular scrolling. Explain when a table or grid may scroll horizontally and how to contain that scrolling without making the whole page scroll in two dimensions.
- Keyboard access to hidden data. Distinguish how keyboard users reach off-screen content in a scrollable table versus a grid.
- Native table relationships. Explain how native table markup identifies headers and data cells, and how scope preserves the relationship between them for screen reader users.
- Choosing grid semantics. Distinguish a data table from a grid, and describe how native table elements or ARIA roles provide a grid's structural semantics.
- Grid keyboard focus. Explain why grid semantics alone are insufficient and describe the roving tabindex approach to keyboard navigation.
- Limits of automatic validation. Explain why valid input does not necessarily mean a consequential action reflects the user’s intent.
- Risk matched safeguard selection. Apply the section’s recommendations to choose reversible actions, review and correction, or stronger barriers according to an action’s risk and reversibility.
- Purposeful and proportionate timeouts. Justify when a time limit may be needed, rather than applying one by default, and describe the exceptions the section identifies.
- User control over deadlines. Describe the three ways the section offers users control over a necessary time limit, including how an extension warning must be accessible and why minimum timing thresholds may not be generous enough.
- Recognition over memory recall. Explain why interfaces should help users recognize controls and actions instead of requiring them to remember where things are or how they work.
- Familiar patterns as meaningful chunks. Describe how familiar interface patterns help users understand whole areas of a page, and how to choose patterns without treating familiarity as a ban on creativity.
- Help within the task. Explain why instructions should appear where users need them, and describe ways to provide help while they complete a form.
- Visible essentials and optional tooltips. Distinguish information that must remain visible from supplementary information suitable for a tooltip, and explain why tooltips alone can be unreliable.
- Accessible tooltip behavior. Describe how a tooltip relates to its trigger and how people should be able to access and dismiss it.
What it builds on
- Keep it POSH (Plain Old Semantic HTML) (chapter 2) · Assumes the preference for semantic HTML.
- When semantic HTML falls short: enter ARIA (and JS) (chapter 2) · Assumes the distinction between semantic HTML and ARIA.
- Set out a logical focus order (chapter 5) · The importance of a logical keyboard focus order.
- Build keyboard-friendly websites (chapter 5) · Keyboard focus and keyboard-friendly navigation.
- Assistive technologies (chapter 2) · Assistive technologies, including screen readers.
- Avoid using colors alone (chapter 3) · The need to convey meaning without relying on color alone
- The accessibility tree (chapter 2) · the accessibility tree through which page semantics reach assistive technology
- Ensure sufficient contrast in UI components and graphics (chapter 3) · Contrast in UI components
Section by section
Introduction
The chapter introduction shifts from navigation to task completion, explaining why accessible forms, support for mistakes, and enough time matter.
- Accessible form task support: Explain why forms are central to online tasks and how labels, hints, and instructions help people complete them with less effort.
Why it matters: A form that makes requirements clear and reduces effort helps people finish the task they came to do. - Support for user mistakes: Explain why applications should support people when they make mistakes.
Why it matters: Treating mistakes as expected helps keep a task completable. - Different task time needs: Explain why task completion must accommodate people who need different amounts of time.
Why it matters: Allowing for different paces helps people complete tasks safely.
Key terms: forms, labels, hints and instructions, cognitive workload, physical workload, mistakes, forgiving and supportive, time, complete tasks
6.1 Forms done right
Introduces how HTML forms submit data, why accessible forms matter to task completion, and the barriers visible in an example form.
- Form submission and request methods: Describe how an HTML form collects input and submits it to the destination in its action attribute. Distinguish GET from POST by whether the client asks the server to change its state.
Why it matters: Understanding what submission does gives context to the task a form helps a person complete. - Forms as task enablers: Explain why forms should be judged as part of a person’s task flow, not merely as collections of input fields, and how poor design can prevent task completion.
Why it matters: A form that blocks the next step can make an otherwise usable task impossible to finish. - Barriers in the example form: Describe concrete accessibility barriers in the example form and explain the user difficulty each creates, such as disappearing placeholders, color-only error cues, or unsuitable input fields.
Why it matters: Spotting a barrier and its effect helps distinguish a form that merely looks usable from one people can use effectively.
Key terms: HTML form, submit button, action attribute, GET, POST, safe method, task flows, barriers, assistive technology users, placeholders
6.1.1 Offer appropriate labels
This section explains how to give form controls visible, programmatically associated labels that work for visual, screen-reader, and voice-interaction users.
- Visible and associated form labels: Explain why every form control needs a permanently visible label associated with the control, preferably using a <label> whose for attribute matches the control’s id. Distinguish a label from a placeholder and describe how the association helps screen-reader and voice-interaction users.
Why it matters: The same label helps people identify a field visually, hear its name, or select it by voice. - Predictable label placement and targets: Describe where to place labels in relation to text fields, checkboxes, and radio buttons, and explain why associating checkbox and radio labels improves activation.
Why it matters: Predictable placement makes fields easier to understand, and a larger target makes small controls easier to activate. - Accessible naming with ARIA: Distinguish the preferred native <label> association from exceptional ARIA naming approaches, and explain the risk when an ARIA name overrides a native label.
Why it matters: A mismatched or overridden name can prevent people from finding a field by the label they see. - Separate labels and supplementary guidance: Explain how to present hints, constraints, and formatting guidance without making them part of the field’s label.
Why it matters: Keeping a field’s name concise while connecting its guidance makes both easier to use.
Key terms: <label>, for, id, placeholder, accessible name, labels, checkboxes, radio buttons, clickable targets, aria-label
6.1.2 Provide required fields and instructions
This section shows how clear requirements, accessible hints, fewer fields, and appropriate input aids make forms easier to complete.
- Clear required field indicators: Explain how a form should distinguish required from optional fields both visibly and programmatically, and why stating “required” beside each label is clearer than relying on an asterisk or a form-level instruction.
Why it matters: Clear requirements help people enter the right information before they submit the form. - Accessible labels and field hints: Distinguish a field’s brief label from supplementary instructions, and describe how to present and associate hints so they remain available while the user enters information.
Why it matters: People can check a field’s instructions when they need them, including when they focus on it with assistive technology. - Necessary form fields: Justify reviewing both optional and required fields for removal when they are unnecessary to the task.
Why it matters: A shorter form can feel less demanding before the user even starts filling it in. - Contextual typing assistance: Describe how autocapitalize and spellcheck can make entry more efficient, and give examples of fields where their use does or does not fit.
Why it matters: Appropriate typing assistance can spare users keystrokes without applying unwanted changes to their input.
Key terms: required, optional, required attribute, asterisk, accessible name, accessible description, <label>, aria-describedby, placeholder, hint
6.1.3 Rely on native HTML
This section explains how native HTML form controls, appropriate input types, and inputmode make forms easier to use and enter data into.
- Native form elements: Explain why accessible forms should use native semantic HTML elements rather than making generic elements imitate controls.
Why it matters: Native controls provide useful behavior without requiring the team to recreate and maintain it. - Appropriate input types: Describe what an appropriate type attribute tells the browser about an <input> and what assistance the browser may provide.
Why it matters: Choosing the right type lets the browser help people enter and validate the expected data. - Virtual keyboard hints: Explain how inputmode helps touch-device users enter data and illustrate it with email or numeric entry.
Why it matters: A keyboard suited to the task can make touch-device entry less tiring.
Key terms: semantic HTML, native elements, built-in semantics, keyboard behavior, type attribute, input type, browser validation, novalidate, inputmode, virtual keyboard
6.1.4 Group fields, when appropriate
This section explains how to group related form fields and when to use multi-step forms without making them harder to navigate or complete.
- Programmatic form field grouping: Explain when to group related form fields with <fieldset> and <legend>, and why visual grouping alone is insufficient.
Why it matters: A visible boundary helps sighted users, but a programmatic group gives screen reader users the same context. - Native grouped control behavior: Describe the keyboard behavior supplied for a native radio-button group and what a custom implementation must reproduce.
Why it matters: Using native controls avoids having to recreate their keyboard interaction and accessibility information. - Logical multi-step form division: Justify when a multi-step wizard can help and how its steps should be divided.
Why it matters: Meaningful steps can make a complex task easier without adding unnecessary navigation. - Accessible wizard progress and recovery: Describe the accessibility obligations introduced when a form becomes a multi-step wizard.
Why it matters: Splitting a form into steps helps only if users can tell where they are and continue or correct their work without getting stuck.
Key terms: <fieldset>, <legend>, label, visual grouping, radio button group, Tab key, arrow keys, Spacebar, ARIA, multi-step wizard
6.1.5 Ensure keyboard behavior is predictable
This section explains how to keep forms predictable and usable from a keyboard, including focus behavior, dynamic updates, and single-character shortcuts.
- Predictable keyboard form operation: Describe how a form should behave for keyboard and screen reader users, and how to check that behavior. Explain what native HTML provides and why custom validation or dynamic interactions need additional attention.
Why it matters: A form is not usable from a keyboard if people lose track of focus, get trapped, or cannot complete and correct it. - Contained dynamic form updates: Explain when an automatic form update is acceptable and how to make it available to screen reader users. Contrast that approach with offering a button to request the update.
Why it matters: People need to learn that a value changed without an unexpected shift in focus or unnecessary announcements. - Safe single-character shortcuts: Explain why unmodified single-character shortcuts can interfere with users and describe the controls required for those shortcuts.
Why it matters: A convenient shortcut can otherwise trigger unwanted actions or block someone from using a function.
Key terms: keyboard focus, visible focus indicator, native HTML elements, HTML validation attributes, dynamic updates, ARIA live region, Recalculate Shipping, character key shortcuts, modifier key, WCAG Success Criterion 2.1.4
6.1.6 Handle errors and help users recover effectively
This section explains how to validate forms and help users find, understand, and recover from errors without losing their work.
- Validation layers and native behavior: Explain why forms use both client-side and server-side validation, and describe what native HTML validation provides and where it can fall short.
Why it matters: Reliable validation should protect the transaction while still making errors practical for people to fix. - Actionable field error cues: Describe how to make an individual field error understandable and accessible, including what to change when the user corrects it.
Why it matters: Clear, current cues let users recognize an error and act on it without having to guess. - Multi-error recovery and focus: Describe how focus and an error summary help users recover when a submission has multiple errors, including when a dynamically created summary can receive focus.
Why it matters: A clear starting point and an overview keep users from hunting through a long form for errors. - Timely accessible validation updates: Explain how to time client-side feedback and distinguish a field description from a live-region announcement.
Why it matters: Useful feedback can guide the next step without repeatedly interrupting someone who is still entering information. - Preserving work after rejection: Explain what must happen to entered values when server-side validation returns errors and why it matters for accessibility.
Why it matters: An error should not erase work that may have taken considerable effort to enter.
Key terms: client-side validation, server-side validation, native HTML validation, required, type, pattern, error message, aria-invalid, aria-describedby, error summary
6.1.7 Close the feedback loop with status updates
This section explains how to keep users informed during form tasks and make dynamic status updates accessible to screen reader users.
- Form task feedback stages: Describe when forms may need status updates and why a clear outcome message closes the feedback loop. Explain why an important transaction may warrant a confirmation page rather than a temporary success message.
Why it matters: Users need to know whether their action is still underway and whether it succeeded. - Live region announcement mechanism: Explain why dynamic messages away from focus can be missed and how a pre-existing live region lets a screen reader announce changes without requiring navigation to them.
Why it matters: A visible update does not necessarily reach someone using a screen reader. - Announcement urgency and roles: Distinguish polite, assertive, and off live-region behavior, and explain when to choose status rather than alert for an update.
Why it matters: Choosing the wrong urgency can interrupt users or bury an important warning. - Live region update controls: Describe what aria-atomic, aria-relevant, and aria-busy control, including how to avoid announcing an incomplete asynchronous update.
Why it matters: These controls help make announcements complete and meaningful rather than premature or ambiguous. - Accessible toast status pattern: Apply the section’s toast pattern to form-processing updates: explain why an ordinary toast is missed, why moving focus is unsuitable, and how to make its messages available without interrupting the user.
Why it matters: People using assistive technology should receive the same processing and completion updates as sighted users without losing their place. - Reduced motion for toasts: Explain how the toast example respects a user’s reduced-motion preference and what kinds of motion this approach targets.
Why it matters: A status update should not require motion that distracts or causes discomfort.
Key terms: status messages, feedback loop, confirmation page, live region, DOM, accessibility tree, accessibility events, aria-live="polite", aria-live="assertive", aria-live="off"
6.1.8 Input type and autocompl...
This section explains how prefilled fields, appropriate input types, and autocomplete tokens can reduce form-filling effort while avoiding incorrect autofill.
- Prefilled and carried-forward information: Explain when to pre-populate fields and carry information forward across forms or pages, and why doing so helps users.
Why it matters: Reusing information can make a demanding form easier to finish and less prone to errors. - Input types and native behavior: Describe what an input type tells the browser and how appropriate types provide useful behavior, using password or date fields as an example.
Why it matters: Choosing a suitable input type lets the browser provide behavior developers would otherwise have to recreate. - Programmatically identified input purpose: Distinguish an input's data type from its purpose, and explain how appropriate autocomplete tokens help browsers and assistive technologies support form filling.
Why it matters: A machine-readable field purpose helps people complete forms without requiring every browser to handle that purpose the same way. - Third-party autofill risks: Explain why autocomplete intended for the form-filler's own details can be harmful on fields collecting someone else's details, and describe the cautious alternatives.
Why it matters: Incorrect autofill can create extra work or lead to a form being submitted with the wrong person's details. - Repeated-field autofill contexts: Describe how shipping and billing tokens and named sections distinguish repeated kinds of fields in a complex form.
Why it matters: Distinguishing similar fields helps prevent one set of saved details from being applied indiscriminately across a complex form.
Key terms: pre-populate, multi-page forms, wizards, type attribute, password field, date picker, native controls, autocomplete, input purpose, given-name
6.1.9 Avoid impostor ARIA components – unless you must!
The section explains why teams should prefer native HTML controls and what they must justify, implement, and test when a custom ARIA component is necessary.
- Native controls over impostors: Explain why native HTML controls are the default and why adding an ARIA role to a generic element does not make it function like that control.
Why it matters: A control that is announced correctly but cannot be operated is still inaccessible. - Custom component justification: Describe how to decide whether a custom component is warranted, including why a desired visual style alone is insufficient.
Why it matters: Choosing a native option can meet the task’s needs without taking on a custom component’s ongoing maintenance cost. - APG guidance and limits: Describe what the ARIA Authoring Practices Guide offers for necessary custom components and what responsibility it does not remove.
Why it matters: A pattern guide can inform a design, but it cannot certify the component a team builds from it. - Custom role behavior commitments: Explain the behavior a team commits to when it gives a custom component an ARIA role, including appropriate keyboard conventions and synchronized states.
Why it matters: Users need a custom control to behave as its announced role promises, not merely look or sound like that control. - Real usability testing: Explain why custom components need testing with assistive technologies rather than relying only on ARIA inspection or automated scans.
Why it matters: A component can pass a markup scan yet still prevent someone from completing a task.
Key terms: native HTML, ARIA, impostor element, native elements, custom ARIA components, CSS, ARIA Authoring Practices Guide (APG), ARIA roles, interaction patterns, ARIA role
6.1.10 Revisiting the form
Revisits a form to show how accessible structure, input choices, error handling, controls, status updates, and visual cues help people complete it efficiently.
- Form labels and structure: Explain how the revised form identifies fields, names the form, groups related fields, and indicates required fields.
Why it matters: These choices make the form’s purpose and fields clearer both on screen and through assistive technology. - Input and entry optimizations: Describe how the revised form selects controls and attributes to make data entry more appropriate and efficient.
Why it matters: Matching fields and browser hints to the expected data reduces unnecessary typing and effort. - Form error recovery pattern: Trace what happens when submission finds validation errors and how users are guided to correct them.
Why it matters: A user needs to discover what went wrong, reach the affected fields, and understand how to fix them. - Native buttons and reset caution: Explain why the form uses clearly distinguished native buttons and why its reset action needs care.
Why it matters: Users should be able to operate and distinguish actions without accidentally losing their work. - Programmatic form status updates: Describe how the form communicates statuses such as submission and clearing to users.
Why it matters: Users need feedback when an action changes the form’s state. - Contrast and visible focus: Explain how the revised form helps users see its content and track keyboard navigation.
Why it matters: Readable form cues and a visible focus position help users navigate and complete the form.
Key terms: <label>, for, id, aria-labelledby, <fieldset>, <legend>, input type, <textarea>, autocomplete, inputmode
6.2 Interacting with tabular data
This section explains when tabular data needs a native table versus a spreadsheet-like grid, and what accessibility responsibilities both approaches carry.
- Table versus grid choice: Distinguish a data table from a data grid and explain when to use each for information arranged in rows and columns.
Why it matters: Choosing by the interaction people need avoids turning an ordinary table into an unnecessarily complex grid. - Grid semantics and behavior: Explain what ARIA role="grid" communicates and what developers must still provide for a data grid.
Why it matters: Adding a grid role without delivering its promised keyboard interaction can mislead assistive technology users. - Shared table accessibility requirements: State the accessibility requirements that apply to both tables and grids.
Why it matters: Choosing the right component does not remove the need for understandable data relationships and predictable keyboard access.
Key terms: tabular data, data table, data grid, spreadsheet-like experience, native <table> element, ARIA role="grid", keyboard behavior, focus management, relationships between headers and cells, programmatically determinable
6.2.1 Layout
Explains how to keep tables and grids usable when horizontal space is limited without making the whole page scroll in two dimensions.
- Contained tabular scrolling: Explain when a table or grid may scroll horizontally and how to contain that scrolling without making the whole page scroll in two dimensions.
Why it matters: Containing scrolling preserves access to wide data without making the rest of the page difficult to navigate. - Limits of the reflow exception: Distinguish the permitted scrolling of a table or grid as a whole from content that should still reflow, including nearby controls and individual cells.
Why it matters: Allowing a component to scroll does not excuse its labels or cell content from remaining readable at narrow widths. - Keyboard access to hidden data: Distinguish how keyboard users reach off-screen content in a scrollable table versus a grid.
Why it matters: A visible scrollbar alone does not ensure keyboard-only users can reach hidden rows and columns. - Readable alternatives for complex tables: Explain why shrinking tabular content is discouraged and what alternatives to consider when a complex table cannot work on a small screen.
Why it matters: Preserving readable data can require another way to inspect it rather than squeezing it into the available width.
Key terms: two-dimensional scrolling, responsive container, overflow-x: auto, Reflow, captions, overflow-wrap: break-word, tab sequence, tabindex="0", keyboard-only users, grid
6.2.2 Data table and grid semantics
This section explains how to preserve accessible table relationships and when to add the semantics and interaction behavior of a data grid.
- Native table relationships: Explain how native table markup identifies headers and data cells, and how scope preserves the relationship between them for screen reader users.
Why it matters: Preserving header context helps screen reader users make sense of each data cell. - Choosing grid semantics: Distinguish a data table from a grid, and describe how native table elements or ARIA roles provide a grid's structural semantics.
Why it matters: Choosing a grid sets an expectation of interaction that an ordinary data table does not carry. - Virtualized dataset position: Describe how a virtualized table or grid communicates the full dataset's size and the positions of rendered rows and cells.
Why it matters: Otherwise, the small portion in the DOM can obscure where a user is in the complete dataset. - Grid keyboard focus: Explain why grid semantics alone are insufficient and describe the roving tabindex approach to keyboard navigation.
Why it matters: A grid must deliver the keyboard interaction its semantics promise. - Grid selection state: Describe how a selectable grid exposes and updates cell selection while supporting keyboard selection.
Why it matters: The exposed selection state needs to stay in step with what users select. - Current sort state: Explain where aria-sort belongs and what it communicates when a table or grid is sorted.
Why it matters: Assistive technology users need the actual sort order, not a misleading indication that every column controls it.
Key terms: <table>, <caption>, <th>, <td>, scope, data table, data grid, role="grid", role="row", role="gridcell"
6.3 Safeguard users in consequential actions
The section explains why consequential actions need safeguards beyond input validation and how to choose and make those safeguards accessible.
- Limits of automatic validation: Explain why valid input does not necessarily mean a consequential action reflects the user’s intent.
Why it matters: A transfer can pass every format check and still go to the wrong recipient. - Error prevention conformance options: State the safeguards allowed by WCAG SC 3.3.4 and distinguish its coverage from SC 3.3.6.
Why it matters: The criteria identify both the actions that need protection and the acceptable kinds of protection. - Risk matched safeguard selection: Apply the section’s recommendations to choose reversible actions, review and correction, or stronger barriers according to an action’s risk and reversibility.
Why it matters: A safeguard that fits the risk helps prevent mistakes without adding a routine confirmation people may ignore. - Accessible safeguards and feedback: Describe how to keep users informed and make undo, confirmation, and cancellation controls accessible.
Why it matters: A safeguard helps only if people can operate it and tell what happened. - Limits of timed undo: Explain why a short undo window may not be an adequate recovery mechanism for important actions.
Why it matters: An undo option is not useful to someone who cannot reach or understand it before it disappears.
Key terms: automatic validation, user’s intent, consequential actions, SC 3.3.4, SC 3.3.6, Error Prevention, reversal mechanism, review and confirmation pages, stronger barriers, transaction’s status
6.4 Handle time-consuming tasks appropriately
This section explains why timed tasks need flexibility and how to impose justified time limits without putting users under undue pressure.
- Variable task completion time: Explain why people need different amounts of time to complete a task, including differences in the task, how people interact with the page, and their need for breaks.
Why it matters: A time limit that seems ample to one person may prevent another from finishing the same task. - Purposeful and proportionate timeouts: Justify when a time limit may be needed, rather than applying one by default, and describe the exceptions the section identifies.
Why it matters: A justified timeout can protect users or a service without treating accessibility and security as opposing goals. - User control over deadlines: Describe the three ways the section offers users control over a necessary time limit, including how an extension warning must be accessible and why minimum timing thresholds may not be generous enough.
Why it matters: These options let people finish timed tasks with more control and less pressure.
Key terms: time needed to complete a task, switches, voice input, magnification, screen reader, time limits, timeouts, real-time activity, critical to the functionality, Timing Adjustable
6.5 Use familiar patterns
This section explains how recognizable controls and familiar interface patterns reduce memory demands and help people complete tasks efficiently.
- Recognition over memory recall: Explain why interfaces should help users recognize controls and actions instead of requiring them to remember where things are or how they work.
Why it matters: Recognizable cues let people spend less effort figuring out the interface and more effort completing their task. - Familiar patterns as meaningful chunks: Describe how familiar interface patterns help users understand whole areas of a page, and how to choose patterns without treating familiarity as a ban on creativity.
Why it matters: A recognizable page structure lets users understand related controls together instead of learning each one from scratch.
Key terms: recognition, recall, short-term memory, familiar UI patterns, meaningful chunks, mental models, established conventions
6.6 Offer help in context
This section explains how to provide accessible help within a task, from visible form hints to supplementary tooltips and human or AI support.
- Help within the task: Explain why instructions should appear where users need them, and describe ways to provide help while they complete a form.
Why it matters: People can get the information they need without losing their place in the task. - Visible essentials and optional tooltips: Distinguish information that must remain visible from supplementary information suitable for a tooltip, and explain why tooltips alone can be unreliable.
Why it matters: Required instructions remain available even when someone does not discover or cannot operate a tooltip. - Accessible tooltip behavior: Describe how a tooltip relates to its trigger and how people should be able to access and dismiss it.
Why it matters: A tooltip must not hide help from some users or trap others behind content they cannot dismiss. - Human and AI support boundaries: Explain when human or AI assistance complements self-service help and what limits should apply to AI support.
Why it matters: Users can ask for help in their own words without being forced to rely on an AI agent for essential information. - Consistent help placement: State how help mechanisms should be presented across pages where they recur and why.
Why it matters: Predictable placement makes help easier to locate when users need it.
Key terms: context-sensitive help, hints, accessible descriptions, inline help links, tooltip, hint, aria-describedby, role="tooltip", trigger, Escape
6.7 Summary
Where this is used later
- Offer mechanisms to support users (chapter 7) · Accessible handling of form inputs
- Handle session timeouts and session state gracefully (chapter 7) · Accessible form interactions
- Two-factor authentication (chapter 7) · password-manager support for sign-in and authentication tasks
- Accessibility versus security – the tradeoff fallacy (chapter 7) · Connects to the discussion of accessibility and security as compatible goals.
Concepts explained in this chapter
- status messageA status message communicates information about a task or interface state without requiring a change of context.
- autocomplete attributeAn HTML attribute that indicates whether and how a browser may automatically complete a form field using stored information.
- live regionA live region is a dynamically updated area of web content whose changes can be announced by assistive technologies.
- fieldset elementThe HTML fieldset element groups related form controls.
- legend elementThe HTML legend element provides a caption for a fieldset.
- web formAn interface for collecting and submitting user-provided information through a web page.
- cognitive loadCognitive load is the mental effort required to process information or complete a task.
- label elementAn HTML element that labels a form control and can programmatically associate the control with its visible label.
- validation summaryAn error summary is a collection of form validation errors that identifies affected fields and explains the problems requiring attention.
- form hintSupplementary guidance that helps users understand how to complete a form field or task.
- aria-livearia-live is an ARIA attribute that specifies how updates to a live region should be announced by assistive technologies.
- status roleThe ARIA status role identifies a live region for non-urgent updates that should not interrupt the current announcement.
- table elementThe HTML table element represents tabular data organized into rows and columns.
- data gridA data grid is an interactive, spreadsheet-like tabular widget with two-dimensional keyboard navigation between cells.
- inputmode attributeThe HTML inputmode global attribute hints which virtual keyboard is appropriate for entering text.
- form labelText associated with a form control that identifies its purpose or the information it requires.
- form fieldAn input field is an interface control that accepts user-entered data.
- contextual helpContextual help is assistance presented in relation to the current task or interface context to resolve user uncertainties.
- required attributeAn HTML attribute that indicates that a form control must have a value before its form can be submitted.
- accessible nameAn accessible name is the programmatically determined text label that identifies an interface element to users of assistive technologies.
- for attributeAn HTML attribute on a label element that associates the label with a form control by matching the control’s id.
- native HTML validationNative HTML validation is browser-provided form validation based on constraints declared through HTML attributes.
- WAI-ARIA Authoring Practices GuideThe ARIA Authoring Practices Guide is an informative, example-driven W3C resource describing ARIA semantics, interaction patterns, and expected keyboard behavior for interface components.
- grid roleThe grid role is an ARIA role that identifies a widget as a grid with spreadsheet-like interaction expectations.
- autocomplete tokenAn autocomplete token is a standardized value of the HTML autocomplete attribute that identifies the kind or context of information requested by a form field.
- autofillAn HTML attribute that allows a browser to provide or select suggested values for a form control based on stored information.
- consequential actionA consequential action is an operation that may have significant effects on a person's finances, legal status, data, or resources.
- review pageA review page presents information about a pending action so a user can inspect or correct it before final confirmation.
- consistent helpConsistent Help is a WCAG success criterion requiring repeated help mechanisms to appear in the same location and relative order across pages.
- content on hover or focusContent on Hover or Focus is a WCAG success criterion requiring additional content shown on hover or focus to be dismissible, hoverable, and persistent.
- table header cellA table header cell is an HTML table cell that identifies a row or column of data.
- accessible descriptionSupplementary programmatically associated text that provides instructions, examples, or constraints for an interface control.
- time limitA time limit is a maximum period allowed for completing a task or remaining active in a session.
- WCAG success criterionA WCAG success criterion is a testable requirement for meeting a WCAG guideline at a specified conformance level.
- focus orderA predictable keyboard-focus sequence that preserves visual or task-related relationships.
- keyboard accessibilityThe ability to operate an interface through keyboard input without requiring a pointer or another input method.
- client-side validationClient-side validation is checking form data in software running on the user's device before it is submitted to a server.
- aria-invalidaria-invalid is an ARIA attribute that communicates that an element's entered value does not conform to the expected format or constraints.
- server-side validationServer-side validation checks submitted values on a server before the system accepts or processes them.
- alert roleThe alert role is an ARIA live-region role for urgent, time-sensitive messages that require immediate attention.
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.
