When Did You Last Update Your Accessibility Statement?
11 December 2025 - Keith Allan
If you run a website or digital service, you probably spend time updating content, tweaking navigation, and fixing bugs. But there is one page many teams forget about: the accessibility statement. It sits quietly on your site, often untouched, yet it tells users more about your values than most people realise. For someone who relies on assistive technology, that page can be the first sign of whether they can trust you to deliver a fair and usable experience.
Why it Matters
An accessibility statement explains how your digital product supports disabled people. It outlines the standards you aim to meet, the barriers you already know about, and how people can reach you when something goes wrong. It is both a guide and a commitment, and it carries more weight than many organisations expect.
What different regions require
UK public sector
- Must publish an accessibility statement under the Web Accessibility Regulations.
- Must meet WCAG 2.2 AA or explain clearly why not.
- Must detail known issues, timelines for fixes, and provide accessible alternatives.
- Must give users a clear route to report problems and escalate complaints.
UK private and third sector
- Not legally required to publish a statement, but expected to comply with the Equality Act.
- A statement shows due care, reduces legal risk, and builds trust. Many organisations choose to publish one for exactly these reasons.
European Union
- Public sector bodies must publish and maintain an accessibility statement under the EU Web Accessibility Directive, using the standard template aligned with EN 301 549.
- Statements must describe conformity, list non‑accessible content and justified exemptions, and provide feedback and enforcement routes.
- Under the European Accessibility Act (EAA), many private‑sector providers (for example e‑commerce, banking, transport, and e‑reading services) must also publish clear accessibility information.
- This information should explain how requirements are met and be easy to find, understandable, and available in accessible formats for as long as the product or service is offered.
United States
- While no single mandated statement format exists, ADA and Section 508 enforcement expect clarity about accessibility efforts.
- Many organisations publish statements to show intent, document progress, and strengthen their position in compliance reviews or litigation.
Why Keeping it Current Matters
Digital products evolve fast. New features roll out, audits reveal issues, and content grows. An outdated statement signals risk and erodes trust. People with disabilities often check accessibility statements before choosing a service. A clear, current statement shows honesty, responsibility, and respect.
How We can help
At User Vision, we help organisations understand, measure, and improve the accessibility of their digital services. Whether you need a full accessibility audit, support writing or updating your statement, help planning a roadmap, or guidance on meeting WCAG and legislative requirements, we can step in at any stage. Our team works with public sector bodies, private organisations, and global brands to raise quality, reduce risk, and create digital experiences that everyone can use.
If you can’t remember the last time you reviewed your statement, now is the time. Let’s make accessibility part of your workflow - not an afterthought.
You might also be interested in...
B Corp web accessibility requirements: what organisations need to know
27 July 2026B Corp’s updated standards now require organisations to assess the accessibility of public-facing websites. Here’s what that means, why it matters, and how to approach it properly.
Read the article: B Corp web accessibility requirements: what organisations need to knowInclusive authentication: why the best MFA doesn’t treat everyone the same
14 July 2026Multi-factor authentication is vital for security, but it can unintentionally lock legitimate users out. This article explores why inclusive authentication matters, how different needs and contexts affect MFA journeys, and what organisations can do to make security and inclusion work together.
Read the article: Inclusive authentication: why the best MFA doesn’t treat everyone the sameNothing About Us Without Us: What CRPD at 20 Means for UX
16 June 2026As the Convention on the Rights of Persons with Disabilities turns 20, this article asks what “Nothing About Us Without Us” should mean for UX in practice. It argues that accessibility is not just about testing whether something works for disabled people, but involving disabled people earlier in shaping what gets built.
Read the article: Nothing About Us Without Us: What CRPD at 20 Means for UX