chapter six

6 Help people complete tasks efficiently

 

This chapter covers

  • Designing forms that support users and their tasks
  • Helping users understand and recover from errors
  • Reducing cognitive and physical workload during tasks
  • Justifying and developing custom components with ARIA
  • Making status visible and safeguarding users against negative consequences
  • Providing enough time for task completion
  • Offering familiarity and assistance through patterns and contextual help

In the previous chapter, we looked at how to help people navigate and interact with web applications more confidently. We explored how purposeful page titles, meaningful headings, and consistent navigation support orientation. We also examined how to programmatically define page landmarks, which are particularly useful to assistive technology users who rely on them as navigation beacons within a page. Keyboard support was discussed, with particular emphasis on visible focus, logical focus order, keyboard traps, and giving users the option to skip repeated blocks of content. We then addressed accessible links before exploring design considerations for people who cannot interact with pixel-perfect precision.

6.1 Forms done right

6.1.1 Offer appropriate labels

6.1.2 Provide required fields and instructions

6.1.3 Rely on native HTML

6.1.4 Group fields, when appropriate

6.1.5 Ensure keyboard behavior is predictable

6.1.6 Handle errors and help users recover effectively

6.1.7 Close the feedback loop with status updates

6.1.8 Input type and autocompl...

6.1.9 Avoid impostor ARIA components – unless you must!

6.1.10 Revisiting the form

6.2 Interacting with tabular data

6.2.1 Layout

6.2.2 Data table and grid semantics

6.3 Safeguard users in consequential actions

6.4 Handle time-consuming tasks appropriately

6.5 Use familiar patterns

6.6 Offer help in context

6.7 Summary