Multi-step forms accessibility: quote wizards, intake forms and progress steps

How to make multi-step quote, intake and enrollment forms work for keyboard, screen reader and phone users: step names in words, focus on each new step, labelled choices, clear errors, Back and review steps, and time limits.

Many small business forms run over several steps: a "Get a quote" wizard for roofing or moving, a new-patient intake, a school or daycare enrollment, an insurance quote, or a booking that asks for the service, then the date, then your details. Splitting a long form into steps can make it easier, but only if every step can be reached, understood and finished by keyboard, screen reader, voice control and phone users. This guide covers what to check, whichever website builder or form tool you use.

1. Say which step people are on

Show the step in words, such as "Step 2 of 4: Your property", not only as coloured dots or a progress bar (WCAG 1.4.1, 1.3.1). Put the step name in the page title or a heading so screen reader users hear where they are (WCAG 2.4.2, 2.4.6). If you show a list of steps, mark the current one with aria-current="step".

<ol class="steps" aria-label="Quote progress">
  <li>Service</li>
  <li aria-current="step">Your property</li>
  <li>Contact details</li>
  <li>Review</li>
</ol>
<h2 id="step-heading" tabindex="-1">Step 2 of 4: Your property</h2>

2. Move focus to the new step

When "Next" swaps in the next step without loading a new page, keyboard and screen reader users can be left on a button that no longer exists, or at the bottom of the page. Move focus to the new step's heading (the tabindex="-1" above makes that possible) so people start at the top of the step (WCAG 2.4.3). Don't move focus or jump to the next step just because someone picked an option; let them press "Next" (WCAG 3.2.2).

3. Real labels and grouped choices on every step

Each field needs a visible label that stays visible while typing, not just placeholder text, and groups of options, such as "Type of property", need a fieldset and legend (WCAG 3.3.2, 1.3.1). Picture cards ("Tap the type of roof") must be real buttons or radio buttons with text names, not clickable images (WCAG 4.1.2, 1.1.1). See accessible contact forms.

4. Errors before moving on

If a step can't continue, say exactly what's wrong in text next to the field and in a short summary at the top, and keep everything people already typed (WCAG 3.3.1, 3.3.3). A greyed-out "Next" button with no reason is a common dead end: people can't tell what's missing. Let them press "Next", then show the errors. See form error messages.

5. Back, review and don't ask twice

6. Time limits and saving progress

Long forms like intake or enrollment can time out while someone looks for a document. Warn people before a session expires and let them extend it, or save their progress (WCAG 2.2.1). If a form asks for files, see file and photo upload forms.

7. Phones, zoom and the final message

Check every step at 200% zoom and on a narrow phone screen: the progress bar and buttons shouldn't push fields off screen or overlap (WCAG 1.4.10), and "Back" and "Next" should be big enough to tap (WCAG 2.5.8). The final "Thanks, we'll call you within 1 business day" message should be announced or receive focus, so screen reader users know it worked (WCAG 4.1.3). Offer a phone number or email as another way to ask for a quote.

Built-in forms vs form tools

Many quote wizards come from a form plug-in or an embedded form service. You usually can't change their code, but you can choose settings like visible labels, a review step and "save and continue", and test the embedded version on your own page. If a tool's steps can't be used by keyboard, ask its support team, offer a phone or email fallback, and consider another tool. See embedded form builders.

Common mistakes

A 5-minute check you can do today

  1. Fill in your quote or intake form using only the keyboard. Can you reach every choice, see where you are, and press "Next" and "Back"?
  2. After each "Next", is your focus at the top of the new step?
  3. Leave a required field empty and press "Next". Does it say what's wrong, in words, and keep your other answers?
  4. Turn on VoiceOver or TalkBack and listen to one step and the final message; see the 10-minute screen reader test.
  5. Open the form on a phone and zoom in. Do the buttons and fields still fit?

What a scan can and can't check here

Automated scans find only part of the barriers on the pages they visit. Our scan can flag fields with no label, unnamed buttons, some invalid ARIA and many contrast problems on the step it sees. It can't press "Next" to reach later steps, check where focus lands, test errors or time-outs, or tell whether your site meets any law. Our Fix-Pack checks up to 10 pages, which can include your quote or intake page, and gives copy-paste fixes for your platform.

Building quote or intake forms for clients? The agency 5-pack gives you five white-label reports ($499, use within 12 months).

This is general technical guidance, not legal advice, and it doesn't certify compliance with the ADA or any law, or protect against claims. Altwise isn't affiliated with any website builder or form tool.

Want the fixes written for you?

Start with a free homepage snapshot. The $149 Fix-Pack scans up to 10 pages and gives copy-paste fixes for your platform within 48 hours, with a 14-day refund promise. See a sample report first.

This is general technical guidance, not legal advice, and it does not certify compliance with the ADA or any law.

Related guides

All guides

This guide is general technical information, not legal advice. Following it does not certify ADA or any legal compliance. Automated checks find only part of accessibility barriers.

Check your own site, then decide

  1. Free homepage snapshot. Your top 3 issues in about a minute. No signup, no card.
  2. $149 Fix-Pack, if you want the full list. Up to 10 pages scanned, issues ranked by impact, copy-paste fixes for your platform, delivered within 48 hours, plus one re-scan after you apply them.

Get my free snapshot Order the Fix-Pack – $149

14-day refund promise. See a sample report first. A technical report, not legal advice; automated checks find only part of accessibility barriers.