EAA Accessibility Statement Template (Free)

Livana Team6 min29 April 2026

An accessibility statement tells users how accessible your digital product or service is, what limitations exist, and how to get help. Under the European Accessibility Act, publishing one isn't optional - it's a core part of demonstrating compliance.

This guide covers what your statement must include, provides a free template, and highlights the mistakes enforcement bodies look for.

Why you need an accessibility statement

The EAA requires businesses to provide information about the accessibility of their products and services. While the directive doesn't prescribe an exact format the way the WAD does for public sector sites, the practical expectation is clear: you need a published, findable accessibility statement.

An accessibility statement serves three purposes:

**Transparency** - it tells users with disabilities what to expect before they invest time in your product
**Compliance documentation** - it demonstrates to enforcement authorities that you've assessed your accessibility and are actively working on it
**Feedback channel** - it gives users a way to report barriers, which is required under most national EAA implementations

What your statement must include

Based on the EAA directive and common requirements across EU member state implementations, your accessibility statement should include the following sections.

1. Conformance status

State your current level of conformance with the applicable standard. Be honest. The options are:

- **Fully conformant** - your content fully meets EN 301 549 / WCAG 2.1 Level AA with no exceptions
- **Partially conformant** - most content meets the standard, but some areas have known issues
- **Non-conformant** - significant parts of the content do not meet the standard

Most businesses will be "partially conformant" - and that's fine, as long as you're transparent about the gaps and actively working to close them. Claiming full conformance when issues exist is worse than honestly stating partial conformance.

2. Standard referenced

Specify which standard you're measuring against. For EAA compliance, this should be:

- **EN 301 549 V3.2.1 (2021-03)** - the harmonised European standard
- **WCAG 2.1 Level AA** - the web content guidelines incorporated by EN 301 549

If you're also targeting WCAG 2.2, mention it as an additional goal.

3. Scope

Clearly define what your statement covers:

- Which websites (list specific URLs)
- Which mobile applications (by name and platform)
- Which features or sections, if the statement doesn't cover everything
- Any third-party content or embedded services that are outside your control

Being specific about scope prevents misunderstandings. If your statement covers www.example.com but not app.example.com, say so.

4. Known limitations

List any accessibility barriers you're aware of but haven't yet fixed. For each limitation, include:

- **Description** of the barrier (what users will experience)
- **Affected content** (which pages, features, or components)
- **Reason** (why it hasn't been fixed yet)
- **Alternative** (how users can accomplish the same task another way)
- **Timeline** (when you expect to fix it, if known)

This section is critical. Enforcement bodies understand that accessibility is an ongoing process. What they won't accept is a statement that ignores known issues.

5. Feedback mechanism

Provide a clear way for users to report accessibility barriers. Include:

- **Contact method** - email address, phone number, or contact form
- **Expected response time** - how quickly you'll acknowledge and respond to reports
- **What happens next** - explain that you'll investigate reported issues and work to resolve them

The feedback mechanism should itself be accessible. Don't make the only contact option a phone number (excludes deaf users) or only a form (may be inaccessible).

6. Enforcement procedure

Explain what users can do if they're not satisfied with your response. Depending on the member state, this might include:

- Filing a complaint with the national enforcement authority
- Contacting a national equality body or ombudsman
- Taking legal action under national consumer protection laws

Include the relevant contact details for the enforcement body in each country where you operate.

7. Assessment method

Describe how you evaluated your accessibility:

- **Self-assessment** using automated tools
- **External evaluation** by a third-party accessibility firm
- **Combination** of automated scanning and manual testing

Mention the tools used (e.g., "Automated scanning with Lumi's multi-engine scanner, supplemented by manual keyboard and screen reader testing").

8. Date

Include the date the statement was last reviewed or updated. A statement dated more than a year ago signals that accessibility isn't being actively maintained.

Free template

Here's a template you can adapt for your organisation. Replace the bracketed sections with your specific information.

Accessibility Statement for [Your Service Name]

Last updated: [Date]

[Your Company Name] is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.

Conformance status

The [website/application] at [URL] is [fully/partially/non]-conformant with EN 301 549 V3.2.1, which references WCAG 2.1 Level AA.

Scope

This statement applies to [list specific URLs, apps, or services covered].

Known limitations

Despite our efforts, some content may not yet be fully accessible:

- [Description of limitation 1] - Affected area: [pages/features]. We expect to resolve this by [date]. In the meantime, [alternative method].
- [Description of limitation 2] - Affected area: [pages/features]. We expect to resolve this by [date]. In the meantime, [alternative method].

Assessment approach

This statement was informed by [self-evaluation / external audit / combination]. Automated scanning was performed using [tool names]. Manual testing included keyboard navigation and screen reader testing with [assistive technology names].

Feedback

We welcome your feedback on the accessibility of [service name]. If you encounter accessibility barriers, please contact us:

- Email: [accessibility@yourcompany.com]
- Phone: [phone number]
- Form: [URL to accessible contact form]

We aim to respond to accessibility feedback within [X] business days.

Enforcement procedure

If you are not satisfied with our response, you can file a complaint with [name of national enforcement body] at [contact details/URL].

Common mistakes

Claiming full conformance without evidence

This is the most common mistake - and the most damaging. If an enforcement body or user finds issues on a site that claims full conformance, it suggests either negligence or dishonesty. Be honest about your status.

Vague or missing limitations section

Writing "we are working to improve accessibility" without listing specific known issues is not sufficient. Enforcement bodies expect concrete details about what's broken and what you're doing about it.

Inaccessible statement page

Your accessibility statement itself must be accessible. This means proper heading structure, sufficient colour contrast, keyboard navigability, and screen reader compatibility. An inaccessible accessibility statement is a bad first impression.

Outdated information

A statement from 2023 on a site that's been redesigned since then tells enforcement bodies nothing about current accessibility. Review and update your statement at least annually, and whenever you make significant changes to your site.

No feedback mechanism

Omitting a way for users to report issues is a compliance gap in most member state implementations. Always include multiple contact channels.

Boilerplate without substance

Copying a template verbatim without filling in your actual conformance status, known issues, and assessment details is obvious and unhelpful. Enforcement bodies have seen every generic template - they're looking for evidence that you've actually done the work.

When to update your statement

Review and update your accessibility statement:

- **After every major release** - new features can introduce new accessibility issues
- **After an accessibility audit** - update your conformance status and known limitations
- **At least annually** - even if nothing major has changed, a current date signals active maintenance
- **When you fix known issues** - remove resolved limitations and add any new ones discovered
- **When legislation changes** - if your member state updates its requirements, update your statement to reflect the new standard

Generate your statement

We built a free Accessibility Statement Generator that walks you through each section and produces a properly formatted statement you can publish immediately. It covers both EAA and WAD requirements and lets you customise the output for your specific situation.

Pair it with a Lumi scan to populate the conformance status and known limitations sections with real data from your site.