Less to think about: cutting cognitive load in online forms

Every question on a form asks the person filling it in to stop, understand, remember and decide. Each of those steps uses up attention. When a form asks for too much at once, people make mistakes, call the help line, or give up. That is cognitive load, and reducing it is one of the most reliable ways to raise completion rates.

These are the changes we recommend most often after usability testing forms for government departments and businesses.

Ask only what you need

For every question, ask who uses the answer and what they do with it. If no one can say, remove it. Optional questions still cost attention, so mark them clearly or move them to the end.

One thing per page

Long forms are easier when each page asks one question, or a few closely related ones. It feels like more pages, but people move faster because each step is obvious, and errors are easier to fix.

Use the words people use

Replace internal terms with everyday language. "Date you arrived in Canada" is easier than "Date of landing". Put examples right under the label, not in a help link.

Don't make people remember

Show earlier answers when they matter, fill in what you already know, and let people check everything on a summary page before they submit. Avoid asking them to look up a number on one screen and type it on another.

Make errors easy to fix

Say what went wrong and how to fix it, next to the field, in plain words: "Enter a postal code like K1A 0B1." Keep everything the person already typed. A list of errors at the top, linked to each field, helps people using screen readers and keyboards.

Show progress and what's next

Tell people how many steps there are, what they'll need before they start, and what happens after they submit: when they'll hear back, and how.

Test it with real people

Five people working through your form will show you most of the places where they slow down or get confused. Watching just one session is often enough to convince a team to make these changes.

Many of these practices also help you meet WCAG 2.2, including the new rule against asking for the same information twice.

Tell us what you’re working on

Whether it’s a redesign, an accessibility audit or a service that isn’t working as it should, send us a short note. We’ll reply the same day with practical next steps.

Phone
1-819-210-7760
Email
info@nineseconds.com
Location
National Capital Region (Ottawa–Gatineau)
Reply time
Same day

[nineseconds_contact_form]