Organise user acceptance testing
Acceptance testing checks whether a service supports expected tasks under defined conditions.
Read the practical method →W3C WAI · Formulaires accessibles
Accessible forms tutorial covering labels, grouping, instructions, validation and notifications. Apply it to actual journeys, keyboard interaction and assistive technologies.
Resource identity and purpose checked against the source on . This check does not verify all service conditions or individual data records.
When it helps
Use the examples to check labels, grouped controls, instructions and error recovery.
How to start
Review the form using one valid scenario and deliberate errors. Check labels, instructions and keyboard recovery; use fictional data and a setup that sends nothing for real.
Limits to keep in mind
The tutorial guides design; it does not automatically validate your final form.
Check before using
Three points to record with the decision.
- 01
Associated label for each field.
- 02
Error explaining the required correction.
- 03
Focus and retained input after an error.
A method and complementary resources.
Source and verification
W3C WAI · Formulaires accessibles — primary source. Link checked . The checklist is editorial guidance; link availability does not guarantee completeness or suitability.
Read the editorial method · Report a correction with its source