WCAG 3.0 is an active W3C Working Draft in development by the AGWG. Requirements, assertions, the conformance model and reporting tiers are still being developed and may change. The latest published draft is the 10 September 2026 Working Draft; this site follows the editors’ draft, which also includes exploratory provisions.
developingAssertion
Error Prevention Review
Group: error-handling • Guideline: prevent-errors
Summary in Plain English
An organisational assertion: the organisation states that it has reviewed its form designs to reduce mistakes - asking for less information, marking required fields, chunking long numbers, offering valid choices, supporting autocomplete, using familiar words and units, and correcting or suggesting where it reliably can.
Why It Matters
Most form failures are design failures. Reviewing the design removes errors before anyone has to recover from them, which matters most for people with cognitive and learning disabilities.
0
Test Procedure from the W3C Draft
Upstream has a test heading for this provision but has not written
the procedure yet, and no test steps have been written here.
Generic advice would apply to almost any provision, so none is shown.
W3C Working Group Status
W3C Maturity Status:developing
Track / Group:error-handling
The draft records no open editors' notes on this provision.
W3C Threads on This Provision
1 GitHub thread carrying 0 comments,
fetched from w3c/wcag3 by the
tracker. Titles, numbers and states are the threads' own.
Nobody has read these threads and written up the positions yet, so
only the threads themselves are listed.
[Title, role, or organization] asserts that:
* For each form in the conformance claim, we have reviewed the form designs to reduce the possibility of users making mistakes.
This review includes checking to make sure that we:
* Make the user enter as little information as possible.
* Clearly indicate required fields.
* For long numbers, divide input fields into chunks (supporting autocomplete across fields).
* Use an interface where only valid input can be selected.
* Use autocomplete and personalization of form controls.
* Use common words and metrics or units that users are likely to be familiar with.
* Automatically correct input errors when possible and reliable.
* Provide the user with known suggestions and corrections.
::assertion-required
* title, role, or organization making the assertion
* date of assertion (if different from the date of the conformance claim)
::assertion-recommended
* documentation of which forms were reviewed
* documentation of any changes made as a result of the review
* date of usability testing, if applicable