Skip to main content

Accessibility Statements: Test Records and Updates

Published: •Updated: •3 min read•navable Team
accessibility statementBFSGdocumentation

An accessibility statement should explain the tested state of your service. When a checkout, form or cookie banner changes, check whether the published information still reflects it.

The Statement Generator supports drafting from audit data. Before publication, add manual test results and information about your service, then review the text.

What Section 14 BFSG requires

For covered services, Section 14(1) requires accessible information under Annex 3(1). This includes a general description, explanations of how to use the service, information on meeting the requirements and the responsible market surveillance authority. Section 14(3) requires procedures for continued adherence, taking changes to the service and relevant standards into account. It does not set a fixed statement update interval.

A snapshot versus a maintained draft

“Static” and “dynamic” describe working practices here, not statutory document types. A manually maintained page can also be updated after review.

StepOne-time snapshotRegularly reviewed draft
Test basisOne documented test stateNew findings are compared with the previous state
After a releaseInformation remains unchanged without further reviewAn owner reviews relevant changes
Manual testsPart of the original assessmentRepeated for changed journeys
PublicationEditorially approved textRevised text after renewed approval

A new scan can detect missing form labels. It cannot judge whether the entire purchase journey makes sense with a screen reader. Both results must inform the assessment. The WCAG overview helps you interpret the technical criteria.

Example: A checkout changes

  1. Test: Scan the changed checkout with the Accessibility Audit. Also test with a keyboard and screen reader, including error messages and payment completion.
  2. Document: Record tested URLs, date, version, findings and outstanding limitations. Assign an owner to each open issue.
  3. Update the draft: Add confirmed results to the statement draft. Fixing one scan finding does not establish that the whole journey has been tested.
  4. Approve and publish: Check the description, contact options and service information. Publish the approved version and retain the previous test record.

Schedule this review for relevant releases. Name the person who approves the text and a trigger for the next assessment, such as navigation, form or purchase flow changes. Readers and colleagues can then understand which tests support your information.

Questions about updates

No. It provides a draft. You must check the information, add manual findings and assess the legal requirements for your service.

The workflow described here includes review and approval. New scan data informs revisions; it does not establish that all requirements are met.

Further reading and sources

Stay Updated

Get accessibility tips and updates.