If you manage a website for a public sector organization, university, or a larger private company serving the public in Europe, accessibility statements are no longer optional. Understanding the legal requirements for accessibility statements in 2026 means the difference between staying compliant and facing enforcement action – or worse, alienating the very people you’re supposed to serve.
I learned this the hard way back in 2020, working on a municipal website project. We assumed a brief paragraph about caring for all users would satisfy the requirement. An audit quickly proved us wrong – multiple deficiencies, a scramble to fix them, and a lesson I haven’t forgotten since. Accessibility statements demand real substance, not surface-level gestures.
Who Actually Needs an Accessibility Statement in 2026?
The legal landscape is clearer than it’s ever been. Under the EU Web Accessibility Directive (2016/2102) and its national implementations, all public sector websites and mobile applications must publish an accessibility statement. Government agencies, municipalities, public universities, hospitals, libraries – if public money is involved, you’re covered.
But it doesn’t stop there. The European Accessibility Act reached full effect in June 2025, extending obligations to private companies providing banking, e-commerce, and transportation services. If your business falls into these categories, you need a statement even without any public funding.
The practical test is simple: does your organization serve the public, receive public funding, or provide essential services? If any of those apply, you almost certainly need a formal accessibility statement right now.
What the Law Requires in Your Statement
A compliant accessibility statement isn’t a feel-good paragraph. It contains specific legal elements, and missing even one creates a violation. This is where treating accessibility as more than a checkbox really matters.
Compliance status declaration. You must honestly state whether your website is fully compliant, partially compliant, or not compliant with WCAG 2.1 Level AA – the legal baseline across most EU countries. Overstating your compliance creates bigger problems than admitting gaps, because auditors will verify your claims.
Non-accessible content listing. Every page or feature that doesn’t meet standards must be identified specifically. Untagged PDFs, videos without captions, interactive elements that fail with screen readers – list them all. For each issue, explain whether it falls under the disproportionate burden exception or include a timeline for fixing it.
Feedback mechanism. Users need a clear, dedicated channel – email, phone, or contact form – to report accessibility problems or request alternative formats. Most countries require a response within 15 to 30 working days.
Enforcement procedure information. If a user isn’t satisfied with your response, they must know where to escalate. Provide contact details for your country’s national enforcement body responsible for web accessibility monitoring.
The Disproportionate Burden Exception – Handle With Care
This clause lets organizations claim that certain accessibility improvements would impose an unreasonable burden relative to the benefits. But it’s not a blanket excuse to ignore problems.
To invoke it legitimately, you need a documented assessment covering organization size, estimated costs, content usage frequency, and available resources. Simply saying “it’s too expensive” without evidence won’t hold up.
In practice, small municipalities sometimes succeed with this for large archive collections that see minimal traffic. For main navigation, essential services, or frequently accessed pages, the claim almost never survives scrutiny. Regulators have seen too many organizations try to stretch this loophole beyond its intent.
Technical and Format Requirements
Your statement must itself be accessible – obvious in theory, overlooked constantly in practice. Use plain language, proper heading structure, and ensure it works with assistive technologies. If your accessibility statement fails basic accessibility checks, the irony won’t amuse an auditor.
Place the link in your site footer so it’s reachable from every page. Many countries require it within three clicks maximum from any location on the site. Standard URL patterns like “/accessibility” or your language equivalent are expected.
Mobile Applications Need Their Own Statements
If your organization has a mobile app, it requires a separate accessibility statement covering both iOS and Android versions. Make it accessible from within the app itself – typically in settings or help sections.
Mobile statements follow the same content requirements but should address platform-specific considerations: gesture controls, screen orientation support, and compatibility with VoiceOver and TalkBack. Don’t just copy your website statement – mobile accessibility has its own challenges.
Keeping Statements Updated – Where Most Organizations Fail
Here’s where compliance often breaks down. Accessibility statements aren’t one-time documents. Every significant website change, content update, or functionality modification should trigger a review.
Best practice in 2026 is a formal annual revision at minimum, with the revision date displayed prominently. Auditors specifically look for recent dates as evidence of ongoing effort. A statement dated 2022 on a site that was redesigned in 2025 raises immediate red flags.
This is exactly the kind of issue that real-time compliance monitoring catches before it becomes a problem – your statement’s availability and currency aren’t things you should be checking manually once a quarter.
Myth: Having a Statement Means You’re Compliant
This is the most dangerous misconception I encounter. An accessibility statement documents your compliance level – including shortcomings. It’s a transparency tool, not a legal shield. Publishing a statement that says “partially compliant” doesn’t excuse you from working toward full compliance. It means you’ve acknowledged the gaps and committed to addressing them.
Similarly, even fully compliant sites need statements. The document confirms your status and provides the required feedback mechanism. And size doesn’t grant exemptions – a two-person public body has the same obligation as a ministry with hundreds of staff.
How to Build a Proper Statement Step by Step
Start with an honest audit. Automated tools like WAVE or Axe DevTools catch roughly 30% of accessibility issues – useful as a starting point, but never sufficient alone. For complex sites, invest in a manual expert review. The broader digital compliance landscape in 2026 demands this level of thoroughness.
Document findings systematically: each issue, its severity, affected pages, and your remediation plan. This becomes your non-compliant content section.
Use your national authority’s official template if one exists – many countries provide them specifically to prevent omissions. Customize with your actual compliance status and contact details.
Then implement the feedback mechanism properly. Don’t create an email alias that nobody monitors. Assign a real person responsibility for responding within your promised timeframe. Nothing undermines an accessibility commitment faster than silence when someone actually reaches out.
Enforcement Is Real in 2026
Consequences vary by country but are no longer theoretical. Some jurisdictions impose direct fines from several thousand to tens of thousands of euros. Others issue enforcement notices with deadlines – and escalating penalties for non-compliance.
Beyond fines, the reputational damage matters. When users with disabilities can’t access your services and find no way to get help, those experiences get shared publicly. In a world of social media reviews, accessibility failures become PR crises fast.
There’s a positive angle too. Accessible websites work better for everyone – clear navigation, good color contrast, keyboard support. These aren’t just legal requirements. They’re good design that expands your audience and improves everyone’s experience, including the accessibility of your privacy policies and other legal documents.
FAQ
Do private companies need accessibility statements in 2026?
Yes, if they provide services covered by the European Accessibility Act – including banking, e-commerce, transportation, and certain digital services. The requirement is no longer limited to public sector organizations.
How often should I update my accessibility statement?
At minimum once per year, and additionally whenever significant website changes occur. Always display the revision date prominently – auditors treat outdated statements as a compliance failure.
Can I use the disproportionate burden exception to avoid fixing accessibility issues?
Only with a documented assessment proving the fix is genuinely unreasonable relative to your resources and the content’s usage. It applies mostly to low-traffic archive material – not to core services, main navigation, or frequently accessed pages.
If your accessibility statement currently lives as a static page you last touched a year ago, today is a good day to revisit it. Check the content, verify the contact email works, update the revision date, and confirm every required element is present. It takes an hour. The alternative – explaining gaps to an auditor – takes considerably longer.