What is an accessibility statement, and how do you create one?

An accessibility statement tells users how well a digital service works for people with disabilities. In the EU, public sector bodies publish one by law, companies under the European Accessibility Act publish something different, and manufacturers issue a third document entirely. In the United States, no law requires any of them. Which document you owe depends on your role and your market.

Key points

• Three routes, three documents. Public sector bodies publish an accessibility statement. Companies providing a covered service publish accessibility information. Manufacturers of a covered product issue an EU declaration of conformity. One template does not cover all three.

• A statement does not make a service accessible. It records what an assessment found, and every claim in it needs evidence behind it.

• The EU prescribes the content. The Commission's model statement sets the categories, and each member state adds its own rules on top.

• The US requires no statement at all. What American buyers ask for instead is a VPAT completed into an Accessibility Conformance Report.

A public authority writes a formal accessibility statement with a compliance status, a list of barriers and an enforcement procedure. An online shop writes something shorter with a different structure and names a market surveillance authority. Both pages can carry the same title.

Scope reaches past websites. Apps, customer accounts, checkout and booking flows, documents and self-service terminals can all fall inside it.

This is general information rather than legal advice. Whether and how the rules apply depends on your organization, your service, your market and the national law that governs you.

Statement, conformance report or declaration of conformity?

Three documents get called the same thing, and telling them apart solves most of the confusion.

What do users get from the statement?

A good statement answers three questions in a few seconds:

• Can I use this service? The compliance status, in plain words.

• What will fail if I try? Named functions rather than general phrases, with a real alternative wherever something does not work.

• Who do I tell? A contact route that works for someone who cannot use your standard form.

It is also read by people outside your audience:

• Procurement teams, checking whether you can be bought from.

• Auditors and regulators, checking whether the claims hold.

• Journalists and competitors, because it is the one page where an organization states its own position on record.

Does a statement replace an accessibility audit?

No. Publishing changes nothing about how your service behaves. The statement is the visible output of work that happened earlier: an assessment against the Web Content Accessibility Guidelines and, in the European public sector, against EN 301 549.

In our analysis of 19 consumer-facing DAX company websites, 89 percent showed at least one digital barrier. Tested against nine selected WCAG 2.2 success criteria in May 2026, the sites missed more than three of the nine on average, and two met all nine. That analysis is a snapshot rather than a full conformance assessment, which is exactly the distinction a statement has to get right.

Who has to publish an accessibility statement?

Not every organization carries the same duty. The scope has to be checked for your specific service rather than for your sector.

Public sector bodies in the EU

Public sector bodies publish a statement for their websites and mobile applications. It names content that is not fully accessible, explains why, and points to accessible alternatives where they exist. It also offers an accessible feedback route that users can reach immediately, plus information about the enforcement procedure with a link to the responsible body.

Companies under the European Accessibility Act

The European Accessibility Act has applied since 28 June 2025. It covers defined consumer services, including e-commerce, banking, e-books, transport and telecommunications, rather than every commercial website. Providers of a covered service make information about that service's accessibility publicly available in accessible form.

Does the EAA apply to my online shop?

It turns on the service rather than on the fact that you run a website. E-commerce is one of the named categories, so a consumer-facing shop with an ordering process is a realistic candidate. Booking flows, customer accounts and payment steps belong in the same assessment. What this looks like in practice is covered in our overview of accessibility in e-commerce.

What about microenterprises?

The EAA's microenterprise exemption for services applies where a business has fewer than ten employees and either annual turnover or an annual balance sheet total of no more than two million euros. It covers services, not products across the board. It also does nothing about the orders an unusable checkout loses you.

Products rather than services: the EU declaration of conformity

A company placing a covered product on the market carries a third duty. Covered products include e-readers, ATMs, ticketing and check-in machines, self-service terminals and consumer devices with interactive computing. The manufacturer runs a conformity assessment, issues an EU declaration of conformity and applies the CE marking.

That declaration goes to authorities on request rather than onto a web page, and it is kept for five years. A company that manufactures a product and runs a shop carries both duties at once.

Which law applies to your digital service?

The Web Accessibility Directive and the EU model statement

Directive (EU) 2016/2102 created the duty for public sector bodies. The Commission set the form in Implementing Decision (EU) 2018/1523, which is where the recognized content categories come from. Member states transpose it, and they add the review cadence, the enforcement body and often extra requirements.

Why does the same duty look different in each member state?

The directives set the floor. National law decides what you actually publish, and the differences are not cosmetic.

What applies in the United States?

No US law requires you to publish an accessibility statement. Three things matter instead.

• ADA Title II. The 2024 Department of Justice rule sets WCAG 2.1 Level AA for state and local government web content. Deadlines moved in April 2026, to 26 April 2027 for entities serving 50,000 or more people and 26 April 2028 for smaller ones.

• ADA Title III. No technical standard exists in regulation for private businesses. Courts have filled the gap, and WCAG 2.1 AA is the practical bar. Website accessibility lawsuits run into the thousands each year.

• Section 508 and the VPAT. Federal agencies and their suppliers follow Section 508. Buyers request a VPAT completed as an Accessibility Conformance Report, which is the document US procurement actually asks for.

What has to be in an accessibility statement?

For public sector bodies, six elements make up the statement. Each becomes a section of the published page.

1. Scope. The service, the relevant URLs, and where applicable the app with its version and date.

2. Compliance status. Fully, partially or non-compliant, chosen on the basis of an actual assessment.

3. Non-accessible content. The concrete barriers, the reason, any applicable exception, the accessible alternative and a remediation plan where you have one.

4. Preparation and review. The creation date, the date of the last review, and whether the assessment was internal or third-party.

5. Feedback and contact. An accessible route to report a barrier or request information, and the unit that handles it. Make sure it works for the people most likely to need it.

6. Enforcement procedure. The correct procedure and contact details for your jurisdiction.

Three additions are worth making even though they are optional: a link to the assessment report, the remediation schedule, and a phone contact for people who cannot use a web form.

How do I describe a barrier concretely?

Vague wording is the most common weakness in published statements. "Some areas are not yet accessible" tells a user nothing and gives your own team nothing to work from.

That version names the function, the barrier, who it blocks, the alternative and a timeline.

What do companies publish under the EAA?

Providers of a covered service make four things available, in accessible form and somewhere users can find them:

• an accessible general description of the service;

• the explanations needed to understand how the service is provided;

• a description of how the service meets the relevant accessibility requirements;

• the competent market surveillance authority.

The Act prescribes content rather than form, so no official template exists for this one. Put it behind a clearly labelled accessibility link in the header or footer rather than inside your terms and conditions. Do not carry the public sector enforcement section across, since it belongs to a different legal route.

How do I create an accessibility statement?

Six steps, in this order. The first two decide everything that follows, which is why the template comes fifth.

Step 1: Establish the legal route Public sector body, covered service provider, manufacturer, several of these or none. Then check the national law in each market you operate in.

Step 2: Define the scope Write down every touchpoint the statement will cover, and get it agreed before anyone starts testing.

Step 3: Run a real assessment Combine automated checks with manual testing of keyboard operation, screen reader compatibility, forms, contrast, heading structure, media alternatives and your central transaction paths. Audit and remediation covers what a team cannot reach in-house.

A compliance status written on the strength of an automated score is a claim your own assessment does not support.

Step 4: Document the findings precisely For each finding, record who owns it and what its remediation status is. That record feeds every document you publish.

Step 5: Draft the right page Use the public sector template or the service information structure below, and fill every placeholder with verified facts. Keeping it current over time is what the accessibility statement service is for.

Step 6: Publish and set a review date Assign an owner and a date before the page goes live.

Accessibility statement templates: which one do you need?

Two templates follow. The first is for public sector bodies and mirrors the Commission's model. The second is for companies providing a covered service. Neither is a substitute for an assessment, and using the wrong one produces a document that satisfies no rule at all.

Template: accessibility statement for public sector bodies

An editable structure rather than a guarantee of compliance. Check your national framework before publishing.

# Accessibility statement

## Scope
This accessibility statement applies to [name and URL of the service / name, version and date of the app].

## Compliance status
[Name of the organization] is committed to making [service] accessible in accordance with [applicable national legislation].

This service is [fully compliant / partially compliant / non-compliant] with [applicable requirements].

## Non-accessible content
The content listed below is non-accessible for the following reasons:

- [specific page, content or function]: [specific barrier], [reason], [accessible alternative], [planned remediation and timeframe, if any].

## Preparation of this statement
This statement was prepared on [date].
The assessment is based on [self-assessment / third-party assessment; method or basis of testing].
The statement was last reviewed on [date].

## Feedback and contact
Have you encountered barriers using [service]? Please tell us through [accessible contact form / email / phone].
Responsible for handling reports: [unit, contact details].

## Enforcement procedure
If you do not receive a satisfactory response within [applicable deadline], you can contact [competent enforcement body]: [link and contact details].

Check before publishing:

• every placeholder replaced and every inapplicable option deleted;

• "fully compliant" selected only where an assessment supports it;

• the enforcement body for your jurisdiction named, not a default copied from elsewhere;

• the page published as accessible HTML.

Template: accessibility information for a covered service

For providers of a covered consumer service, not for public sector bodies.

# Accessibility information

## About our service
[Short, accessible description of the service, for example an online shop for …]

## How to use the service
[The steps and information needed for ordering, booking, registration, payment or account management.]

## Accessibility of the service
[Description of how the relevant accessibility requirements are met, based on measures actually implemented and tested.]

## Competent market surveillance authority
[Name and contact details of the competent market surveillance authority.]

Where the scope or the claims are uncertain, legal and accessibility specialists should review it before it goes live.

Where should the statement sit, and does that include apps?

In the footer, on every page, labelled as plainly as your privacy policy. For public sector bodies the statement has to be reachable from the homepage and every other page. Mobile apps need the statement reachable from the app itself or from the download page, depending on the national rule.

HTML, PDF or both?

Accessible HTML is the better default. Assistive technology reads it directly, it adapts to display settings, and it stays current more easily. A PDF is not automatically non-compliant, but if you publish one it has to be accessible itself, and you then maintain two versions of the same facts.

How often does the statement need updating?

Public sector bodies review annually and after every substantial change. Everyone else should review after a redesign, a new checkout or booking path, a CMS migration, an app release, a document update or a newly identified barrier. Keeping several statements current by hand is where most of them go stale, which is the case for a continuous web accessibility solution rather than a one-off project.

Frequently asked questions

We are a public sector body and a covered service provider. Do we need two documents?

In most cases yes. The duties sit on different legal bases and cover different things, so a merged page tends to satisfy neither. Publish the statement for the website or app, publish the service information for the covered service, and link the two.

Can private companies call their page an accessibility statement?

Yes. The title is not regulated, the content is. There is no statutory accessibility statement for private companies in the way there is for public sector bodies. What is required is the four pieces of information under the EAA. Many companies publish them under the more familiar heading, which is fine as long as the page claims no conformance an assessment cannot support.

Can I take a template or a generator output as it is?

No. A template gives you the structure. The content comes from your own assessment: your scope, your barriers, your dates, your contacts, your authority. An unedited template claiming full conformance is a documented false statement rather than a shortcut.

Does a statement protect us from a US lawsuit?

No. It creates no safe harbor. It can evidence good faith when backed by real work, and it can create a written admission when it overclaims. Both effects come from the same page, and the difference is whether an assessment sits behind it.

Does the EAA apply to a US company with no European entity?

It can. The EAA follows the market rather than the company's address. A US business offering covered services to consumers in the EU can fall within scope, and the microenterprise exemption turns on headcount and turnover rather than location.

Where to begin?

One assessment supports every document you need. Start there rather than with a template.

1. Run a free scan to see what an automated check already flags.

2. Count your obligations: one per market, per role. That number tells you how many documents you owe.

3. Decide who owns the findings record, because every document you publish will be generated from it.

Read next

• What the European Accessibility Act requires

• EN 301 549 and how it maps to WCAG

• The ADA and digital accessibility

• WCAG explained