Design

Website Accessibility Statement: Free Template and Guide

Clay illustration of a document with an accessibility symbol, a magnifying glass and a green tick

What a website accessibility statement is, whether a UK small business needs one, what to put in it, and a free template you can copy and fill in.

A website accessibility statement is a page that tells visitors how usable your website is for disabled people. It names the standard you aim for, lists any known issues, and explains how to get help or report a problem. UK public sector bodies must publish one. No UK law we could find requires a private business to, but the Equality Act 2010 still expects every service provider to make reasonable adjustments for disabled people, and a short, accurate statement is a simple way to show how you do that. This guide covers what to include, a free template, how to test your site and how often to update the page.

Want to check your site before you write anything? Our guide to website accessibility checkers covers the free tools and the order to run them in. For what good and bad look like on a real page, see our website accessibility examples.

What is a website accessibility statement?

An accessibility statement is a plain English page, usually linked from the footer, that sets out how accessible your website is. It says which standard you work to, what visitors can expect, which parts are known to cause problems, and who to contact when something gets in the way. It is written for the people who rely on it most: someone using a screen reader, someone moving through the site by keyboard, someone who needs to zoom in to read.

For you, it is also a record. It shows what you checked, how and when.

The W3C, which publishes the Web Content Accessibility Guidelines (WCAG), says a statement should at least include a commitment to accessibility, the standard you apply and contact details for anyone who hits a problem. It recommends adding known limitations, the steps you take to keep the site accessible, and the browsers and devices you have tested with.

Does a UK small business legally need an accessibility statement?

Not as far as we can find. The legal requirement to publish a statement applies to public sector websites and apps. A private business has a different duty, under the Equality Act 2010, to make reasonable adjustments so disabled people are not put at a substantial disadvantage. A statement is not required to meet that duty, but it is a practical way to show how you meet it. The case to watch is an online shop selling to consumers in the EU.

This is a plain summary of what we checked in the law and official guidance, not legal advice. If you need a firm answer for your business, speak to a legal adviser.

Public sector websites must publish one

The Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 require public sector bodies, such as councils and government organisations, to make their websites and apps accessible and to publish an accessibility statement. GOV.UK says meeting the requirement means meeting WCAG 2.2 at level AA.

The statement must follow a model format. Under regulation 8 it has to explain which content is not accessible and why, describe any accessible alternatives, give a way to report a problem, and link to the enforcement procedure. Most charities are exempt, unless they are mostly publicly funded, provide services essential to the public or serve disabled people. The Equality and Human Rights Commission enforces the rules in England, Scotland and Wales, and the Equality Commission for Northern Ireland does so there.

Private businesses: the Equality Act 2010 applies instead

GOV.UK states that all UK service providers have a legal obligation to make reasonable adjustments, under the Equality Act 2010 in Great Britain or the Disability Discrimination Act 1995 in Northern Ireland. If you sell to the public or offer a service, that includes you. Three points in the Act are worth knowing:

  • The duty is owed to disabled people generally. For services, the Act says the duty is to disabled persons generally, not only to a customer who has already asked. In practice, you are expected to think ahead.
  • Information counts. Where the duty relates to providing information, the reasonable steps include making sure it is provided in an accessible format.
  • Websites and standards are not named. The Act does not mention websites or set a technical standard. WCAG 2.2 level AA is the standard GOV.UK uses for public sector sites, and the one we work to.

Selling online to EU customers: the European Accessibility Act

The European Accessibility Act, Directive (EU) 2019/882, has applied since 28 June 2025. Among other things, it covers e-commerce services provided to consumers. It defines those as services provided at a distance, through websites and apps, at a consumer’s request, with a view to a consumer contract. In plain terms, an online shop selling to the public. This is what we confirmed in the text of the Directive:

  • Where you are based is not the test. A service provider is anyone who provides the service on the EU market or offers it to consumers in the EU. So a Kent online shop selling to customers in Ireland or France can fall within it.
  • Microenterprises are exempt for services. A business that employs fewer than 10 people, with an annual turnover or balance sheet total of no more than €2 million, is exempt from the Act’s accessibility requirements for services and the obligations that go with them. Many small Kent shops sit under that line.
  • Larger shops in scope must publish information. They must explain how the service meets the accessibility requirements, in their general terms and conditions or an equivalent document, and make it public in a form disabled people can access. In effect, an accessibility statement.
  • It does not cover UK sales. It is EU law, applied through each EU country’s own national rules.

We found no UK government guidance on how the Act applies to UK businesses. If you sell to EU consumers and sit above the microenterprise line, take advice from a legal adviser.

What should an accessibility statement include?

A useful statement answers five questions for the reader. What standard do you aim for? How well does the site meet it? Which parts cause problems? How do I get help? How recent is this? In practice, that means:

  1. What the statement covers. Your web address, plus any booking system or shop that runs on a different address.
  2. The standard you work to. WCAG 2.2 level AA is the usual choice.
  3. What visitors can expect. For example, that they can move through the site by keyboard, zoom to 200 percent and use a screen reader.
  4. Known issues. Each one named in plain words, with the pages it affects, who it affects and when you plan to fix it.
  5. Other ways to get the information. A phone call, an email, or a large print version on request.
  6. How to report a problem. An email address and phone number, and how quickly you reply.
  7. How and when you tested. An automated check, a manual check or an independent audit, with the date.
  8. Dates. When the statement was prepared and when it was last reviewed.
  9. Where to go next. The GOV.UK model statement points unhappy visitors to the Equality Advisory and Support Service. Adding it is optional for a business, and helpful.

Our own statement, as an example

Our accessibility statement follows this shape. It lists what we do across the site: a proper heading structure, text that reflows when you zoom, alt text on images that carry meaning, visible focus states, layouts tested on real phones, and animation that respects the reduced motion setting on your device. It names each issue an automated check against WCAG 2.1 AA found, such as some light grey text on dark backgrounds that falls below the 4.5 to 1 contrast minimum, and says what each one affects. It gives an email address and a phone number, with a target of replying within one working day.

The detail that does the most work is how far the claim goes. The page says the check was automated and explains what an automated check cannot see, so a reader knows exactly what the statement covers.

What should you leave out of an accessibility statement?

  • Claims you have not tested. “Fully compliant” is a written claim about your website. The GOV.UK model reserves it for sites that meet every requirement of the standard. If you ran an automated scan, say that.
  • Another business’s statement. Copied text describes someone else’s website. On one live shop we audited, the terms and conditions named a different company altogether. A copied statement goes wrong in exactly the same way.
  • Overlay widget badges. A single line of script that promises compliance does not fix the site underneath. Our accessibility checkers guide explains why we avoid them.
  • Promises with no contact route. “We are committed to accessibility” on its own does nothing for someone stuck on your booking form. Give them a person to reach.

Free accessibility statement template

Copy this into a new page on your website and replace the words in square brackets. Delete any line that does not apply, and only list what you have actually checked. It follows the GOV.UK model statement and the W3C’s guidance, cut down for a small business.

SectionWhat to write
HeadingAccessibility statement for [business name]
What this coversThis statement covers [website address]. [Add any booking system or online shop on a different address.]
Our aimWe want everyone to be able to use this website, including people who use a screen reader, a keyboard or voice control, and people who need to zoom in. We aim to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 at level AA.
What you can do on this siteYou should be able to zoom in to 200 percent without text spilling off the screen, move through the whole site using only a keyboard, and use the site with a screen reader. [Only list what you have tested.]
Known issuesSome parts of this site are harder to use: [describe each issue in plain words, the pages it affects and who it affects]. We plan to fix this by [month and year].
Other formatsIf you need information from this site in a different format, such as large print or a phone call, contact us and we will help.
Reporting a problemIf something on this site is hard to use, email [email address] or call [phone number]. Tell us the page and what went wrong. We aim to reply within [number] working days.
How we testedThis site was last tested on [date] using [an automated check, a manual check of named pages, or an independent audit by a named company]. We tested [list the pages].
DatesThis statement was prepared on [date]. It was last reviewed on [date].
If you are not happyIf you are not happy with our response, you can contact the Equality Advisory and Support Service (EASS).

How do you test your website before writing the statement?

Run a free automated checker first, then check the same pages by hand. Automated tools only catch part of the problem, so the manual checks matter more. Test a sample rather than every page: your homepage, your main service pages, your contact form and any booking or checkout. Write down what you tested and when, because that goes in the statement.

The manual checks that find most real problems on a small business site:

  • Keyboard. Press Tab from the top of the page. You should reach every link, button and form field, see where you are at all times, and never get stuck.
  • Zoom. Zoom the browser to 200 percent. WCAG asks that text can be resized to 200 percent without losing content or function.
  • Contrast. Body text needs a contrast ratio of at least 4.5 to 1 against its background. Large text can go down to 3 to 1.
  • Images. Images that carry meaning need alt text that describes them. Purely decorative images should have an empty alt attribute, so screen readers skip them.
  • Links and headings. Each link should make sense read on its own, and each heading should describe the section below it.
  • Forms. Every field needs a label, and error messages should say what went wrong and how to fix it.
  • Video. Anything with speech needs captions, checked by a person, because automatic captions are often wrong.

Our accessibility checkers guide covers which free tools to use and in what order. GOV.UK also publishes a basic accessibility check for teams without technical knowledge, which works well as a checklist for any small site.

Whatever you find, the statement should match it. If your test was an automated scan of five pages, say so. A modest, accurate statement is worth more than a confident one you cannot back up.

How often should you update an accessibility statement?

Review it at least once a year, and whenever the website changes in a big way. That is the rule GOV.UK sets for public sector bodies, and it works just as well for a small business. Change the “last reviewed” date each time, even if nothing else changes, so readers can see the page is current.

Update it sooner when:

  • you redesign the site or move to a new platform;
  • you add a booking system, an online shop, a new form or a chat widget;
  • you fix a known issue, so it comes off the list;
  • someone reports a problem you did not know about.

The easiest way to keep it current is to make it part of your routine upkeep, alongside updates and backups. Our guide to website maintenance covers what that routine looks like.

Where should the statement go on your website?

Give it its own page at a simple address, such as /accessibility/, and link to it from the footer of every page. GOV.UK calls a footer link on every page good practice for public sector sites, and the same logic holds for yours. Publish it as a normal web page rather than a PDF, built with the same care as the rest of the site, so the statement itself is easy to read with a screen reader or at high zoom.

How we handle accessibility on the sites we build

Accessibility is part of how we build, not an extra bolted on at the end. If you already have a website, send us the address and we will tell you what we find, including the parts a scanner cannot see, so your statement describes your site accurately. Planning a new one? Start with web design for small business, and use our website launch checklist for the other pages a UK site needs before it goes live.

How we put this together

The legal points come from GOV.UK’s guidance for public sector bodies, the Equality Act 2010 and the 2018 regulations on legislation.gov.uk, and the text of the European Accessibility Act as adopted, all checked on 15 November 2026. The list of what to include follows the GOV.UK model statement and the W3C’s guidance on accessibility statements. The example is our own published statement, and the audit finding comes from our own client work, anonymised. We are a web design agency, so this is a plain summary, not legal advice.

Sources

Helen Marsh

Written by

Helen Marsh

Lead Designer

Helen designs clean, easy to use websites for small businesses across Kent, with a focus on turning visitors into enquiries.

More guides by Helen Marsh →

FAQs

Only for public sector bodies, under the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. We found no UK law that requires a private business to publish one. The Equality Act 2010 still requires every service provider to make reasonable adjustments for disabled people, and a statement is a practical way to show how you do that.

It can. Since 28 June 2025 it has covered e-commerce services provided to consumers in the EU, and it counts anyone offering those services to EU consumers as a service provider, wherever they are based. Businesses with fewer than 10 staff and turnover or balance sheet of no more than €2 million are exempt for services. It does not cover UK sales.

The standard you aim for, usually WCAG 2.2 level AA, what visitors can expect, any known issues with the pages they affect and when you plan to fix them, other ways to get information, how to report a problem and how fast you reply, how and when you tested, and the dates it was prepared and last reviewed.

Only if it has been tested against every requirement of the standard, including manual checks. The GOV.UK model statement reserves "fully compliant" for sites that meet all of WCAG 2.2 AA. If you have only run an automated scan, say so in the statement and describe what was checked, because automated tools catch only part of the problem.

Review it at least once a year and whenever the website changes in a big way, such as a redesign, a new booking system or shop, or a fix to a known issue. That is the rule GOV.UK sets for public sector bodies, and it works well for a small business. Update the last reviewed date every time.

On its own page at a simple address, such as /accessibility/, linked from the footer of every page. Publish it as a normal web page rather than a PDF, so the statement itself is easy to read with a screen reader or at high zoom. GOV.UK calls a footer link on every page good practice.

WCAG 2.2 at level AA. GOV.UK uses it as the standard for public sector websites. The Equality Act 2010 does not name a technical standard for private businesses, but WCAG 2.2 AA is the usual benchmark and the one we work to. It covers things like contrast of at least 4.5 to 1 and text that resizes to 200 percent.

New website

Thinking about a new website?

We design clean, modern sites that turn visitors into enquiries.

Start a project