The Misconception
Many organizations believe that simply documenting their accessibility efforts equates to compliance. As the European Accessibility Act (EAA) deadline approaches, the assumption is that publishing an accessibility statement and showing intent to improve will suffice to avoid penalties.
Guidance from the EAA emphasizes demonstrating commitment, maintaining transparency, and keeping records. The logic seems straightforward: prove you're working towards conformance, and enforcement agencies might be lenient with first-time violators.
The Reality
Documentation alone doesn't equal compliance; it supports it.
The EAA sets a firm deadline of June 28, 2025, with no grace period beyond that. Since the directive Web Accessibility Specialist approved in April 2019, organizations have had ample time to prepare. Market surveillance agencies are aware of this timeline.
While documentation shows good faith, it won't shield you from penalties if your service remains inaccessible after the deadline. An accessibility statement can actually serve as evidence of your awareness of the requirements and your failure to meet them.
Consider what an accessibility statement communicates: "We understand EN 301 549 requires WCAG 2.1 Level AA conformance. Here are the ways we currently fail to meet those requirements." This isn't a defense; it's an admission.
The Evidence
The enforcement framework is clear. Germany, for example, can impose fines up to EUR 100,000 for non-compliance. While the regulation encourages support for small and medium enterprises (with turnover up to EUR 50 million) and allows for fixes before sanctions, this assumes active remediation efforts. It doesn't mean indefinite patience while you maintain a static list of issues.
The EAA's exemption structure underscores the seriousness of the obligation. Only microenterprises (fewer than 10 employees and turnover not exceeding EUR 2 million) are exempt. For everyone else, conformance is mandatory, not optional.
Documentation is meant to inform users with disabilities about your service's accessibility status and to report issues to agencies. Whether public or on-demand, the statement serves users first, not your compliance strategy.
Listing unresolved issues without addressing them creates a paper trail of noncompliance. Each update that repeats the same problems strengthens the case against you.
What to Do Instead
Shift your focus from documentation to actual conformance.
Your immediate priority should be to stop creating new accessibility debt. Release only features that pass accessibility review and testing. This prevents the cycle of developing inaccessible features, testing, and then fixing them, which keeps you behind. If you're adding inaccessible features while fixing old ones, you're not progressing.
Address existing barriers in order of priority. Map key user journeys through your service. For an e-commerce site, prioritize the purchase flow over supplementary content. Test these critical paths against EN 301 549, which includes WCAG 2.1 Level AA. Consider WCAG 2.2 Level AA to avoid future remediation cycles.
For complex interactions, evaluate whether the complexity benefits users or just looks impressive. Simplifying your interface often costs less than making an elaborate pattern accessible. A straightforward form is better than an inaccessible wizard.
Seek professional support if you lack in-house expertise. Look for experience with similar projects, not just certifications. The International Association of Accessibility Professionals offers certificates, but you need practitioners who have solved similar problems.
Document your work as you complete it, not as a substitute for completing it. When you fix the checkout flow, update your accessibility statement to reflect that improvement. When you establish an accessibility review gate for new features, document that process change. Show progress, not empty promises.
Report issues to market surveillance agencies as required, but remember that reporting doesn't pause your obligation to fix them. Keep records of what you reported and when, but don't confuse reporting with remediation.
When Documentation Helps
Documentation is valuable when you're making measurable progress.
If you're genuinely improving and can show completed work, an accessibility statement helps users understand what's accessible now and what's planned. It sets expectations and respects people with disabilities who need to know if your service is usable.
For organizations that started late but are moving quickly, documentation creates accountability. Publishing specific timelines and scopes forces you to follow through. If you commit publicly to making your checkout flow conformant by August 2025, that deadline becomes real.
Documentation also protects you if you face complex technical barriers that require significant re-architecture. If you can show steady progress on most of your service while tackling a difficult component, that context matters during enforcement discussions.
But all these scenarios assume you're actually fixing things. The documentation should reflect real work, not aspirations.
Publishing an accessibility statement to appear compliant while your service remains inaccessible isn't managing risk. It's documenting it.
The EAA deadline doesn't care about your statement. It cares about your conformance.
