
Organise user acceptance testing
Acceptance testing checks whether a service supports expected tasks under defined conditions.
Read the practical method →
Public standards and methods for making websites and digital services more accessible.
Resource identity and purpose checked against the source on . This check does not verify all service conditions or individual data records.
Use it to turn accessibility requirements into checks during design, acceptance and maintenance.
DINUM publishes RGAA 4.1.2 and is preparing version 5. Before testing, record the version in use and the date of the review. Choose representative pages and critical journey states, such as form errors and confirmation.
A quick review is not a complete audit. Examine obligations applicable to your organisation separately.

Reference version and review date.

Sample covering templates, forms and error states.

Applicable criterion, page state, evidence and outcome of the retest after the fix.
Fictional case: a team checks a registration journey before acceptance.
DINUM · Méthode d’évaluation de la conformité · Reference for the resource; the scenario is an editorial example.

Acceptance testing checks whether a service supports expected tasks under defined conditions.
Read the practical method →Accessibilité numérique · RGAA: 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