liveBook · Manning

Chapter 6: Help people complete tasks efficiently

What you will learn in chapter 6 of Architecting Accessibility

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

What it builds on

Section by section

Introduction

The chapter introduction shifts from navigation to task completion, explaining why accessible forms, support for mistakes, and enough time matter.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

Concepts explained in this chapter

← Chapter 5: Ensure effective navigation and interaction Chapter 7: Make the safest path the path of least resistance →

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.