Accessible Forms: The Complete Checklist (WCAG 2.2)

A dark panel cut with several differently shaped openings, each edge traced in coral red, representing an accessible form where every kind of user has a clearly marked field they can complete.

The cursor blinks in a field with no label. A screen reader user hears "edit text, blank." They tab to the next one. "Edit text, blank." Somewhere on this form is a required phone number, a billing ZIP, and a checkbox that controls whether the whole thing submits, and none of them say what they are out loud.

That is not a rare edge case. In WebAIM's February 2026 analysis of the top one million home pages, 33.1% of all form inputs were not properly labeled, and missing form labels showed up on 51% of pages. The average page carries just 6.9 form inputs, so this is not a volume problem. It is a care problem. The piece of your product where people hand you their name, their money, and their trust is the piece most likely to be broken for the people who most need it to work.

Here is the part nobody wants to hear: most form accessibility is not an exotic engineering challenge. It is a short list of unglamorous decisions you either made or skipped. Below is that list, built around WCAG 2.2, the current standard since it became a W3C Recommendation in October 2023. I will tell you which rules are new, which ones actually change your markup, and where teams keep failing.

The short version

An accessible form is one that every person can perceive, fill out, correct, and submit, using a mouse, a keyboard, a screen reader, voice, or a switch. In practice that means a visible programmatic label on every field, clear focus, error messages tied to the input that caused them, touch targets of at least 24 by 24 pixels, no re-typing information you already asked for, and no login puzzle that punishes memory. WCAG 2.2 Level AA is the bar most of the world now treats as the baseline.

What makes a form accessible?

A form is accessible when its structure, not just its styling, carries meaning. Structure is the word that matters. A label that merely sits visually near a box is decoration. A label that is programmatically connected to that box is information, and that connection is what a screen reader, a voice-control tool, and an autofill engine all read.

Two identical dark form fields, one with a coral label clearly attached and one with its label hanging loose, representing the difference a programmatic form label makes.

Accessibility for forms rests on four jobs. People need to perceive each field (what is this, is it required, what format). They need to operate it without a mouse. They need to understand errors and recover from them. And the whole thing needs to be robust enough that assistive technology can parse it. Miss any one and the form stops working for a real group of people, not a hypothetical one.

The complete accessible forms checklist

1. Labels on every field, always visible

Every input gets a real, persistent label connected with for/id or wrapping. Placeholder text is not a label. It vanishes the moment someone types, it fails contrast more often than not, and screen readers treat it inconsistently. This single rule would fix the biggest failure in the WebAIM data. If you do one thing, do this.

2. Group related fields

Wrap radio buttons, checkbox sets, and multi-part inputs (a date split into three fields, an address block) in a fieldset with a legend. Without it, a screen reader user hears "Monday, checkbox" with no idea what question Monday is answering. This is the quiet failure that makes a form technically labeled and still unusable.

3. Mark required fields in more than one way

Do not rely on a red asterisk alone. State it in the accessible name (aria-required="true" or the native required attribute) and in visible text. Color plus a symbol plus a word covers color-blind users, screen reader users, and the person skimming at speed.

4. Tie errors to their field

When validation fails, the message has to be programmatically associated with the input (aria-describedby), announced, and specific. "This field is invalid" is noise. "Enter a date as MM/DD/YYYY" is help. Move focus to the first error or summarize errors at the top with in-page links to each one.

5. Keyboard and visible focus

Everything that works with a mouse works with Tab, Enter, and Space, in an order that matches the visual layout. And the focused element has to be clearly visible. WCAG 2.2 added 2.4.11 Focus Not Obscured (Minimum) at Level AA precisely because sticky headers, cookie bars, and chat widgets kept covering the field a keyboard user had just landed on.

6. Touch targets of at least 24 by 24 pixels

New in WCAG 2.2: 2.5.8 Target Size (Minimum), Level AA, sets a floor of 24 by 24 CSS pixels for interactive targets, with spacing exceptions. Tiny checkboxes, cramped stepper buttons, and a submit button jammed against a link are the usual offenders. For a form someone fills on a phone with a thumb, this is not pedantry.

7. Stop asking for the same information twice

Another 2.2 addition: 3.3.7 Redundant Entry, Level A. If a person already gave you their shipping address in step one, do not force them to retype it as the billing address in step three. Auto-populate it or let them select it. This helps everyone, and it specifically helps people with memory and motor differences for whom every re-typed field is a new chance to fail.

8. Do not make login a memory test

3.3.8 Accessible Authentication (Minimum), Level AA, is the sleeper rule of WCAG 2.2. A login or verification step cannot require a cognitive function test, like transcribing characters, solving a puzzle, or recalling something, unless there is an alternative. In plain terms: let people paste passwords, let password managers work, and drop the "retype this distorted text" gate. If your authentication punishes a bad memory, it fails.

9. Offer help consistently

3.2.6 Consistent Help, Level A, asks that contact or help options appear in the same relative place across pages. On a long or sensitive form, a predictable "need help?" is the difference between finishing and abandoning.

WCAG 2.2: the new criteria that touch forms

Here is what changed with 2.2, filtered to what actually hits form design:

Criterion

What it requires

Level

Why it matters for forms

2.4.11 Focus Not Obscured (Min)

The focused element isn't fully hidden by other content

AA

Sticky bars stop hiding the active field

2.5.8 Target Size (Min)

Interactive targets at least 24x24 CSS px

AA

Checkboxes and buttons usable by thumb and tremor

3.3.7 Redundant Entry

Don't make users re-enter known info

A

Shorter, less error-prone multi-step forms

3.3.8 Accessible Authentication (Min)

No cognitive-function test to log in

AA

Password paste and managers allowed; no puzzles

3.2.6 Consistent Help

Help placed consistently across pages

A

Predictable escape hatch on long forms

WCAG 2.2 also retired the old 4.1.1 Parsing criterion, which is now considered obsolete. Good news: one less thing to chase.

Why this is urgent right now

Two things changed the stakes. First, the European Accessibility Act has been in force since June 28, 2025, pulling private-sector digital products, including e-commerce checkouts and banking forms, into legal scope across the EU. Second, the web got worse anyway. WebAIM found 95.9% of home pages had detectable WCAG failures in 2026, up from 94.8% the year before, and the same handful of errors, labels and contrast among them, have led the list for seven straight years. Enforcement went up. Compliance went down. That gap is where lawsuits and lost customers live.

I have shipped this work under real constraints. On the EqualWeb accessibility widget I spent most of my time not on clever features but on the boring plumbing of labels, focus, and error states, because that is where actual users got stuck. The flashy accessibility demo and the form that a blind user can actually complete are rarely the same artifact.

Key takeaways

  • The number one form failure is unlabeled inputs; a persistent, connected label on every field fixes most of the problem.

  • WCAG 2.2 added five criteria that touch forms directly: focus visibility, 24px targets, no redundant entry, accessible authentication, and consistent help.

  • Placeholders are not labels, red asterisks are not enough, and "invalid field" is not an error message.

  • Accessible forms help everyone, not a minority; redundant-entry and authentication rules reduce friction for all users.

  • With the EAA enforced and failures still rising, accessible forms are now a legal and commercial issue, not just an ethical one.

FAQ

What is an accessible form?

What are the most common form accessibility failures?

Is a placeholder the same as a label?

What did WCAG 2.2 change for forms?

What is accessible authentication?

Does accessible form design only help disabled users?

Which WCAG level should I target for forms?

Share on

Let's talk

I like to connect and see how we can work together

All trademarks, logos, and brand names are the property of their respective owners. All company, product, and service names used on this website are for identification purposes only. Use of these names, trademarks, and brands does not imply endorsement.

ยฉ 2026, Felipe Linares - flinbu. All rights reserved. | Terms and Conditions | Privacy Policy | Cookies Policy

Let's talk

I like to connect and see how we can work together

All trademarks, logos, and brand names are the property of their respective owners. All company, product, and service names used on this website are for identification purposes only. Use of these names, trademarks, and brands does not imply endorsement.

ยฉ 2026, Felipe Linares - flinbu. All rights reserved. | Terms and Conditions | Privacy Policy | Cookies Policy