Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

Accessibility · 17 Nov 2026 · 7 min read

Accessibility statement: what to include on your website

An accessibility statement tells visitors what works, what does not and who to contact. This guide shows what to write and how to keep it honest.

The short answer

An accessibility statement is a short page that says how usable your website is for disabled visitors. It should state your commitment, what you have tested, known problems with alternatives, a real contact route and a review date. A duty to publish one depends on your country, so ask a qualified lawyer.

What an accessibility statement is

An accessibility statement is a short page on your website that tells visitors how accessible the site is, what you have done about it, what still does not work, and how to reach a person if they hit a barrier. It is written for the visitor, not for a regulator or a search engine.

It is not a badge and it is not a certificate. A statement describes the current state of the site honestly. A visitor who uses a screen reader, a keyboard only, voice control or large text wants to know two things: will this site work for me, and who do I tell if it does not.

The page matters most when it is accurate. A statement that promises full access to everyone, while the booking form cannot be used without a mouse, is worse than having no statement. It sets an expectation that the site then breaks.

Do you need an accessibility statement?

It depends on where you operate and what kind of organisation you are. Some countries require public bodies, and in some cases larger private businesses, to publish one. Others have no such rule for small businesses but still have accessibility or anti-discrimination law that can apply to websites. The rules differ by country, they change, and they are applied differently to a public service and a local shop.

So the honest answer is that we cannot tell you from here. Ask a qualified lawyer in the countries where your customers live, or read the guidance from the official regulator in each country. Do not copy a statement from a competitor and assume it covers your legal position.

Even where there is no requirement, a statement is useful. It gives disabled visitors a named contact route, and it gives your own team a written record of what has been checked. If you are choosing between publishing one and not publishing one, and you have done at least a basic review, publish a short and accurate one.

Check the site before you write a word

A statement is only as good as the review behind it. Before drafting, spend time with the actual site. Try these checks on your main pages, which usually means the home page, a key service or product page, the contact page and any form or checkout.

  • Put the mouse aside and move through the page with the Tab key. Can you reach every link, button and field, and can you always see where you are?
  • Zoom the browser in until the text is much larger. Does the layout still work, or does content overlap or disappear?
  • Turn on a screen reader and listen to one page. Do headings, links and images make sense when heard, not seen?
  • Look at text against its background. Is anything hard to read, such as pale grey on white?
  • Watch for anything that moves, flashes or plays sound by itself.

Write down what you find, including the failures. Those notes become the "known limitations" part of the statement. If you want a structured review, the Web Content Accessibility Guidelines from the W3C are the usual reference, and the current version is on the W3C site. Check the current documentation for the version and level you are aiming at.

What the statement should say

Keep the page short, in plain language, and in this order. Start with the fact, not a mission speech.

Your commitment, in one or two sentences

Say that you want the site to be usable by as many people as possible, and name the standard you are working towards if you have one. Do not name a conformance level unless someone has tested the site against it. "We aim to meet" is honest. "We meet" needs evidence.

The current state

Describe what you know. For example: most pages work with a keyboard, the main navigation has been tested with a screen reader, and some older PDF files are not fully accessible. Be specific about which parts have been checked and how.

Known problems and what you plan to do

List the parts that do not yet work well. A line such as "the map on the contact page cannot be used with a keyboard; the address and directions are also written out in full below it" is far more useful than a general apology. If you give a date for a fix, keep it. If you cannot promise a date, say the issue is known and you are working on it.

Alternatives

Where something is not accessible, offer another route. A phone number or email address for requesting information in another format is the usual choice.

How to contact you

Give a real address that a person reads. Say what details help, such as the page address and the device or assistive technology used. If you use a feedback form, make sure that form is itself accessible. Our guide to accessible forms covers labels, errors and keyboard use.

The date

Show when the statement was written and when the site was last reviewed. A statement with no date cannot be trusted, and an old date tells the reader the page was forgotten.

Wording that causes trouble

Some phrases look reassuring and create risk. Avoid claiming that the site is "fully accessible", "compliant" or "accessible to all users". Accessibility is not a fixed state, because content changes every week. Avoid legal language you do not understand. Avoid naming a law or standard you have not read.

Also avoid blaming users or technology. Lines such as "please use a modern browser" or "some users may find the site difficult" tell the reader nothing. Say what fails, where, and what they can do instead.

Third party content needs a sentence. Embedded video players, booking widgets, payment pages and chat tools may be outside your control. Say which parts come from another provider, and that those parts may behave differently.

If the statement is going to be used as evidence of your legal position, have a lawyer read it. For most small business sites a plain, factual statement is enough, but that is a question for someone qualified in the relevant country.

Where to link it

Put a link to the statement in the footer of every page, so that it is reachable from wherever a visitor lands. The footer is where people expect to find legal and policy pages. Use clear link text such as "Accessibility statement", not an icon alone. If your navigation and menu structure includes a utility or help area, the statement can sit there too.

It also helps to link to it from the contact page and from any form or checkout where a person might get stuck. A visitor who cannot complete a booking should not have to hunt for the route to help.

Give the page a plain address, for example a short path that includes the word accessibility. The page should be served over a secure connection like the rest of the site, as explained in our guide to HTTPS and SSL certificates. Make the statement itself easy to read: real headings, short paragraphs, good contrast and no text inside images.

Keep it true over time

A statement goes stale quickly. Each time the site changes in a big way, such as a redesign, a new booking system or a new checkout, check the statement again. A good habit is to review it on a fixed schedule and after every major release.

Small details count. Images need useful alternative text, and the file type you choose matters less than whether the image is described properly; our guide to website image formats explains the technical side. Videos need captions, and downloadable documents need to be readable by assistive software.

Treat the statement as part of the site, not as a separate document. Keep a copy of each version so you can show what you said and when, and include the page in your routine website backups. If a visitor reports a barrier, log it, fix it, and update the statement if the problem was listed there.

When accessibility work is part of a build or a redesign, it is cheaper and more effective to plan it from the start than to patch it later. If you want help planning that, our website development service page explains how we work on sites for business owners.

Related guides

Questions and answers

Do I need an accessibility statement?

It depends on your country, your sector and the size of your organisation. Some places require one for public bodies and some larger organisations, and others do not. Rules change, so ask a qualified lawyer or read the official regulator's guidance. Even where it is optional, a short honest statement helps visitors.

What should an accessibility statement say?

It should state your commitment, describe what has been tested, list known problems with any alternatives, give a real contact route and show a date. Keep the language plain. Only name a standard or conformance level if the site has actually been tested against it.

Where should an accessibility statement be linked from?

Link it from the footer of every page so it is reachable from anywhere. Add links from the contact page and from forms or checkout steps where a visitor might need help. Use clear text such as Accessibility statement.

Can I copy another company's accessibility statement?

No. Their statement describes their site, their testing and their legal position, not yours. Copying it risks claiming things that are not true for your pages. Use it as a structure at most, and write your own findings.

How often should I update my accessibility statement?

Review it on a regular schedule and after any large change, such as a redesign or a new booking or checkout system. Update the review date each time. If a reported problem is fixed, remove it from the known issues list.

Is an accessibility statement the same as being accessible?

No. The statement describes the site. It does not make the site usable. A page can have a polished statement and still fail keyboard or screen reader users, so the testing and fixing come first, and the statement reports honestly on the result.

Tell us what you are building.

A short call, a written plan and a fixed quote. No obligation.

Get a free quote