Writing an honest accessibility statement, and handling complaints

TL;DR

Difficulty: Intermediate

An accessibility statement is a public promise, and a complaint is when someone checks it.

  • In the UK no law makes a shop publish one, but the Equality Act duty to make reasonable adjustments applies, and a dated statement is your best evidence.
  • Selling into the EU, Article 13 and Annex V of the European Accessibility Act require the information in writing and orally, kept up to date. Germany also wants the market surveillance authority named.
  • Write only what you tested: say built and tested to WCAG 2.1 AA, list known issues with a workaround and a fix date, give a contact by email and phone, name the complaint routes.
  • Handle a complaint in four steps: acknowledge, help the customer finish today, fix the cause with a test, record it.

What should my accessibility statement say, and what do I do when a customer writes in to say they could not use my site? This chapter answers both for the UK and every EU market you sell into: what the law asks you to publish, the nine parts of a good statement, wording you can stand behind, a complete sample for an invented Brighton bookshop, and one complaint handled from the first email to the release that fixed it.

The two questions this chapter answers

Sooner or later every shop owner who takes accessibility seriously asks two things. What should my accessibility statement actually say? And what do I do on the day a customer writes in to say they could not use my site?

They belong together. The statement is the promise you make in public, and the complaint is the moment someone checks it. A statement that says "fully accessible" falls apart the first time a screen reader user gets stuck at the checkout. One that is honest about what works, what does not yet, and how to get help survives that email, and usually turns it into a fix and a grateful customer.

This chapter builds on testing accessibility: what tools find and what only people find, because testing is the raw material of any honest statement, and on the accessibility law article, which explains who the law reaches. I will not repeat either.

The example business runs through the whole series. Brightwater Books is an independent bookshop in Brighton with an online shop at brightwaterbooks.example. Ruth owns it, and Ade is the developer who looks after the site. Both are invented, and so is everything that happens to them here.

What an accessibility statement is

An accessibility statement is a page on your website that tells people how accessible the site is, where it falls short, and how to get help. That is the whole idea. It is not a certificate, a badge or a seal. Nobody grants it to you. You write it, you publish it, and you are responsible for it being true.

A good statement does three jobs. It tells a disabled customer, before they waste any time, what will work for them. It gives them a way round anything that does not work yet, and a person to contact. And it is your written record of what you tested and what you are fixing, the first page a regulator or a solicitor will read.

The World Wide Web Consortium (W3C), the body that publishes the Web Content Accessibility Guidelines (WCAG), puts the minimum plainly: a statement should contain at least a commitment to accessibility, the standard you apply, and contact information for people who run into problems.1 Everything else in this chapter builds on those three.

Ruth opens her own site on her phone and scrolls to the foot of the page. There is a link called "Accessibility". It leads to a page with one sentence: "Brightwater Books is committed to making our website accessible to everyone." No standard, no date, no contact.

Measured against the W3C minimum, that page has one of three parts. A screen reader user learns nothing from it: not whether the checkout works with their software, not who to call when it does not. The rest of this chapter is how Ruth replaces it.

What the law asks you to publish

The answer depends on where your customers are, not on where your company is registered. For a UK shop that ships to Ireland, Germany and Austria, that means two different legal pictures at once.

In the UK: no statement duty for a shop, but the Equality Act still applies

The UK did not adopt the European Accessibility Act. There is no law that requires a private business to publish an accessibility statement. The duty to publish one belongs to public sector bodies, and the government's sample statement exists because "publishing an accessibility statement is one of the things public sector organisations must do".2

That does not leave a shop off the hook. Section 29 of the Equality Act 2010 says a service provider must not discriminate against a person who needs its service, and applies the duty to make reasonable adjustments to every service provider.3 Section 20 sets out that duty, and where the problem is information, the reasonable steps include providing it in an accessible format.4 The Equality and Human Rights Commission's code of practice says in so many words that the obligation applies to services provided on a website.5

None of this requires a statement. It is still the cleanest evidence that you anticipated what disabled customers need and kept your service under review, which the same code recommends providers do regularly.5 A dated statement with a list of known issues is that review, written down.

Selling into the EU: the information Article 13 and Annex V require

If you sell to consumers in the EU, the European Accessibility Act applies to you through the law of each country you sell into. The Act is Directive (EU) 2019/882. Article 13(2) says service providers must prepare information in line with Annex V, explain how their services meet the accessibility requirements, make that information available to the public in written and oral format, including in a way that is accessible to disabled people, and keep it for as long as the service runs.6

Annex V lists what the information must contain, in the general terms and conditions or an equivalent document:6

  • a general description of the service in accessible formats,
  • the descriptions and explanations needed to understand how the service operates,
  • a description of how the service meets the relevant accessibility requirements.

Each country wrote this into its own law, with small differences that matter:

  • Germany. § 14 of the Barrierefreiheitsstärkungsgesetz (BFSG) says you may only offer the service if you have prepared the information in Anlage 3 and made it available to the public in an accessible form.7 Anlage 3 adds one item the Directive does not spell out: you must name the competent market surveillance authority.8 For online shops in Germany that is the Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF) in Magdeburg.9
  • Austria. § 14 of the Barrierefreiheitsgesetz (BaFG) asks for the information in Anlage 3, made available in written and spoken form and in accessible formats, and kept for as long as the service is offered.10 Anlage 3 mirrors Annex V point for point.11
  • Ireland. Regulation 14 of S.I. No. 636 of 2023 asks for the information in Schedule 3, available to the public in writing and in oral format, including in a manner accessible to disabled people.12 The compliance authority for eCommerce services is the Competition and Consumer Protection Commission (CCPC).1213

"Oral format" is easy to skim past: someone must be able to get this information without reading a web page, for example by phoning you. The microenterprise exemption and the other edges of who is covered are in the law article.

Example: what Brightwater Books must publish, and to whom

Ruth has 12 staff, sells to private customers online, and about one order in eight goes to Ireland, Germany or Austria.

  1. Is it an eCommerce service under the Act? Yes. Private customers buy at a distance through a website.
  2. Is it a microenterprise? No. Twelve staff is over the line of fewer than 10.
  3. Does it offer the service on the EU market? Yes. It ships to Galway, Cologne and Linz.
  4. So the German, Austrian and Irish laws each ask for the Annex V information, in writing and orally, kept up to date, and for German customers it must name the MLBF. Ruth names the Irish and Austrian authorities too, because it costs one line each.
  5. For UK customers nothing requires a statement, but the Equality Act duty applies and the same page is her evidence.

Ade's conclusion: one statement covering all four markets, linked from every page and from the terms and conditions.

The nine parts of a good statement

Put the W3C guidance, the government's sample statement and the Annex V list side by side and they agree on most of the structure.126 I would build every statement from these nine parts, in this order:

  1. Scope. Which website or app the statement covers, by address, and what it leaves out.
  2. Standard and level. Which version of WCAG and which level you build and test to. For EU markets, note that the harmonised European standard EN 301 549 builds on WCAG at level AA for web content.14
  3. How the service works. A short description in plain words: how people browse, buy, pay and get their order. This is the Annex V general description and explanation of operation.
  4. What works, and how you know. What you tested, with which tools and assistive technology, on which pages, and when.
  5. Known issues. Every barrier you know about, in plain words, who it affects, what to do instead, and the date you expect to fix it.
  6. Other formats. How to get any content in another format, for example large print, an accessible document, or read out on the phone.
  7. Contact and response time. A named way to reach a person, by email and by phone, and how quickly you reply.
  8. Complaints and enforcement. What to do if the customer is not happy with your answer, including the authority for each market you serve.
  9. Preparation. When the statement was written, when it was last reviewed, and how the testing was done.

Parts 4 and 5 are where statements are usually weakest, because they require you to have tested. If you have not, read the testing chapter before you write a word. A statement without testing behind it is a guess dressed up as a promise.

Example: Ruth checks her old page against the nine parts

Ruth and Ade hold the one sentence page against the list. It has none of the nine parts. Ade gathers what fills them: the shop's address and the blog on the same domain (scope), WCAG 2.1 AA (standard), a five sentence description of browse, basket, checkout and delivery (how it works), his full test from October (what works) and its three open issues (known issues). Ruth agrees to read any page out on the phone and post large print (other formats), sets up a shared inbox with the shop's phone hours (contact), and they list the routes for the UK, Ireland, Germany and Austria (complaints) and the test date (preparation).

Nine gaps, filled in an afternoon, because the testing was already done. That is the usual shape: the writing is easy once the evidence exists.

Wording you can stand behind

The single most common mistake in accessibility statements is a claim the business cannot prove. "Fully accessible." "100% compliant." "Meets all accessibility standards." Each of those is a promise about every page, every state and every customer, and one barrier makes it untrue.

What a conformance claim really is

WCAG itself defines what a formal claim is, and it is stricter than most statements realise. Conformance claims are optional. Conformance is defined only for web pages, and a claim must name its date, the guidelines with their title, version and address, the level met, a description of the pages covered, and the web technologies the content relies on.15 In other words, a real claim is narrow, dated and specific. "Our website is fully compliant" is none of those.

The government's sample statement for public bodies uses three status sentences: fully, partially or not compliant with WCAG 2.2 AA.2 Those belong at the end of an audit. A business that says "fully compliant" without one is claiming something it has not checked.

The wording I use

The way I describe my own work is the way I would describe yours. I build sites and shops to WCAG 2.1 AA and say exactly that: "built to WCAG 2.1 AA". I never write "guaranteed compliant", because accessibility is something a site keeps meeting as it changes, and the honest proof is the testing and the fixes, which an independent auditor can verify if you want the assurance in writing. WCAG 2.1 AA explained sets out how that building and testing works.

My own website has an accessibility panel with text size, high contrast and reduced motion. It is a set of preferences built into the site's own code, inside a site that is built accessibly. It is not what makes the site accessible, and it would be wrong to name it in a statement as if it were. The same goes for any third party overlay script. A statement that says "we use an accessibility tool to make this site compliant" points at the wrong thing, and the overlays chapter explains why.

Tap or click to open full screen and move around

Example: three sentences rewritten

Ade goes through the drafts Ruth found on other shops' sites and rewrites each into something Brightwater could defend.

BeforeWhy it failsAfter
"Our website is fully accessible to all users."No standard, no date, no scope, and no site works for every person in every situation"We build and test brightwaterbooks.example to WCAG 2.1 AA. We last tested it on 27 October 2026."
"We use an AI accessibility tool to ensure compliance."Names a script as the reason the site is accessible, which it cannot be"If something on the site does not work for you, tell us and we will help you complete your order another way while we fix it."
"Some parts of the website may not be fully accessible."Vague. The customer cannot tell which parts or what to do"Author interview videos published before October 2026 have captions that have not been checked by a person. A checked transcript is available on request, and we will replace the captions by 31 January 2027."

The pattern in every rewrite is the same: replace an adjective with a fact, and replace a vague limitation with a specific one plus a way round it.

Example: Brightwater Books' accessibility statement in full

Here is the complete statement Ruth publishes. It is a sample, written for an invented shop, and it is meant to be copied as a structure, not word for word. Every fact in it has to be true for your own site before you publish yours. The shop speaks as "we" because it is a shop with staff, and the statement is theirs.

Accessibility statement for brightwaterbooks.example

Scope. This statement covers our online shop at brightwaterbooks.example, including the blog and events pages on the same address. It does not cover our social media accounts or emails from our payment provider.

Our standard. We build and test this website to the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. For customers in the EU, that is the level the European standard EN 301 549 relies on for web content.

How the shop works. You can browse books by subject, author or search. You add books to your basket, then check out as a guest or with an account. You enter a delivery address or choose collection from our Brighton shop. You pay by card on a payment page run by our payment provider. We email an order confirmation and a second email when your order ships. You can return books within 30 days, as set out in our returns policy.

What works. On 27 October 2026 we tested the home page, search, three product pages, the basket, the whole checkout, account sign up, the returns form and the events page. We used automated checks, a keyboard only pass, zoom to 200% and a narrow screen of 320 pixels, VoiceOver on an iPhone and on a Mac, and NVDA on Windows. You can complete every step of an order using a keyboard, a screen reader, or zoom.

Known issues.

  • Author interview videos published before October 2026 have automatic captions that a person has not checked. A checked transcript is available on request. We will replace these captions by 31 January 2027.
  • The spring events programme is a PDF without tags, so a screen reader may read it in the wrong order. Every event is also listed as a normal page on our events page.
  • Our card payment page is provided by our payment provider. We tested it with a keyboard and VoiceOver on 27 October 2026 and found no barriers. If you meet one, phone us and we will take your payment over the phone instead.

Other formats. If you need any page, our returns policy or an order summary in another format, such as large print, a plain text email or read out over the phone, ask us and we will send it within three working days.

Contact us. Email access@brightwaterbooks.example or phone the shop on the number at the foot of every page, Monday to Saturday, 9am to 5.30pm. We reply to every accessibility message within one working day, and we will help you complete your order while we look into the problem.

If you are not happy with our response. Tell us first, and Ruth, the owner, will look at it personally. In the UK you can contact the Equality Advisory and Support Service (EASS) for free advice. In Ireland the authority for online shops is the Competition and Consumer Protection Commission (CCPC). In Germany it is the Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF). In Austria it is the Sozialministeriumservice.

How we prepared this statement. We prepared this statement on 2 November 2026. It is based on testing carried out on 27 October 2026 by the developer who maintains our site. We review it whenever we change the checkout, the account area or the page design, and at least once a year.

The statement does not claim the site is perfect. It promises a reply within a working day and a way to finish the order now. Those are promises Ruth can keep, the only kind worth publishing.

Where the statement lives, and how to mark it up

A statement nobody can find is not published in any useful sense. Two places matter.

  • Every page. A link named "Accessibility" in the site footer, so it is one keyboard trip from anywhere.
  • Your terms. Annex V asks for the information in the general terms and conditions or an equivalent document.6 A short clause in your terms that links to the statement keeps the two together.

The page itself must be as accessible as the rest of the site. A statement that a screen reader cannot read properly undermines itself in the first line. That means real headings, a real list for known issues, real links with descriptive text, and a date a machine can read.

The footer link, before and after. The old version used a vague label and opened a new window without warning:

<!-- Before: vague text, opens a new window without saying so -->
<a href="/accessibility" target="_blank">Click here</a>

<!-- After: says where it goes, stays in the same window -->
<footer>
  <nav aria-label="Footer">
    <ul>
      <li><a href="/terms">Terms and conditions</a></li>
      <li><a href="/returns">Returns</a></li>
      <li><a href="/accessibility">Accessibility</a></li>
    </ul>
  </nav>
</footer>

What each part does:

  • <nav aria-label="Footer"> marks the block as navigation and names it, so a screen reader user who jumps between landmarks hears "Footer navigation".
  • <ul> and <li> make it a list, so a screen reader announces "list, 3 items".
  • The link text "Accessibility" says where it goes, which meets WCAG 2.4.4 Link Purpose (In Context).15 "Click here" did not.
  • Without target="_blank" the page no longer opens a new window without warning, which disorients anyone who cannot see that it happened.

Then the statement page itself. The structure matters more than the styling:

<main id="main">
  <h1>Accessibility statement</h1>
  <p>Last reviewed on <time datetime="2026-11-02">2 November 2026</time>.</p>

  <h2>Known issues</h2>
  <ul>
    <li>
      Author interview videos published before October 2026 have
      unchecked automatic captions. Ask us for a checked transcript.
      Fix expected by <time datetime="2027-01-31">31 January 2027</time>.
    </li>
  </ul>

  <h2>Contact us</h2>
  <p>
    Email <a href="mailto:access@brightwaterbooks.example">access@brightwaterbooks.example</a>
    or phone the shop on <a href="tel:+440000000000">the number in our footer</a>.
  </p>
</main>
  • One <h1> for the page, then <h2> for each part, so a screen reader user can list the headings and jump straight to "Known issues" or "Contact us".
  • <time datetime="..."> gives the date in a format software can read, while people still see "2 November 2026".
  • mailto: and tel: links let a customer on a phone write or call in one tap.

Because the site runs on Ruby on Rails, Ade keeps the review date in one place and renders it in the view, so the date on the page and the date in his test record cannot drift apart:

<%# app/views/pages/accessibility.html.erb %>
<p>
  Last reviewed on
  <time datetime="<%= Accessibility::LAST_REVIEWED.iso8601 %>">
    <%= l(Accessibility::LAST_REVIEWED, format: :long) %>
  </time>.
</p>

When he finishes a test, he updates Accessibility::LAST_REVIEWED in the same commit as the test notes, and the page changes with it.

Handling a complaint: acknowledge, offer a way now, fix, record

The statement promises a reply and a way round. A complaint is when you keep that promise. Four steps, in this order:

  1. Acknowledge. Reply quickly, thank the person, and say what happens next. Do not argue, and do not ask them to prove they are disabled.
  2. Offer a way to finish now. The customer came to buy something. Help them buy it today, by phone, by email or with a manual order, at the same price and with the same delivery. This is the reasonable adjustment in its most literal form.
  3. Fix the cause. Reproduce the barrier, find which success criterion it fails, fix it in the code, add a test so it cannot come back, and release.
  4. Record it. Log the report, the barrier, the workaround, the fix and the release date. Update the statement if the issue was not listed. Tell the customer it is fixed.

Step 2 is the one businesses skip, and it is the one that matters most to the customer. A fix in three weeks does not buy the birthday present that is needed on Saturday.

Tap or click to open full screen and move around

Example: one complaint at Brightwater Books, from first email to fix

Monday, 10.14am. An email arrives at the accessibility inbox from Daniel Okafor. Daniel is blind and shops on his iPhone with VoiceOver, the screen reader built into iOS. He writes that he is trying to buy a book as a birthday present and wants it gift wrapped, but when he reaches the gift wrap option at checkout, VoiceOver reads "Choose wrapping" and nothing else. He cannot open the list or tell what is selected. The birthday is on Saturday.

Monday, 10.40am. Ruth replies. She thanks Daniel, says she is sorry the checkout let him down, and offers two ways to finish the order today: she can phone him and take the order with gift wrap at the same price, or he can reply with the book and the wrapping he wants and she will send a payment link by email. She tells him Ade will look at the problem this week and that she will let him know when it is fixed.

Monday, 11.05am. Daniel chooses the phone call. Ruth takes the order, with the same free delivery the website offers, and the book goes out that afternoon.

Monday, 2pm. Ade reproduces the problem with VoiceOver on an iPhone and on a Mac. The gift wrap choice is a custom dropdown built from div elements. It looks like a menu, but to assistive technology it is just text. It has no role, no name and no state, and it cannot be reached or opened with a keyboard either. That fails WCAG 4.1.2 Name, Role, Value and 2.1.1 Keyboard.15

The broken version:

<!-- Before: looks like a menu, means nothing to a screen reader -->
<div class="wrap-picker" onclick="openWrapMenu()">
  Choose wrapping
  <div class="wrap-options" hidden>
    <div onclick="pickWrap('none')">No gift wrap</div>
    <div onclick="pickWrap('kraft')">Brown paper and string, £2.50</div>
    <div onclick="pickWrap('print')">Patterned paper, £3.50</div>
  </div>
</div>

The fixed version uses native radio buttons, which browsers and screen readers already understand:

<!-- After: a real group of choices, announced and usable by keyboard -->
<fieldset>
  <legend>Gift wrap</legend>
  <input type="radio" id="wrap-none" name="gift_wrap" value="none" checked>
  <label for="wrap-none">No gift wrap</label>

  <input type="radio" id="wrap-kraft" name="gift_wrap" value="kraft">
  <label for="wrap-kraft">Brown paper and string, £2.50</label>

  <input type="radio" id="wrap-print" name="gift_wrap" value="print">
  <label for="wrap-print">Patterned paper, £3.50</label>
</fieldset>

What changed, attribute by attribute:

  • <fieldset> groups the three choices, and <legend> names the group, so VoiceOver reads "Gift wrap" before the options.
  • type="radio" tells the browser these are mutually exclusive choices. The screen reader announces each as "radio button, 1 of 3" and says whether it is selected, which covers the role and the state.
  • name="gift_wrap" ties the three buttons together, so choosing one clears the others, and the arrow keys move between them.
  • Each <label for="..."> points at the id of its input, so the visible text is the accessible name, and tapping the words selects the button.
  • checked on "No gift wrap" means there is always a sensible default.

Ade adds an automated end to end test that completes a checkout with gift wrap using only the keyboard, so a future redesign cannot quietly bring the custom dropdown back. How to write those tests is in the testing chapter, and the checkout as a whole is in the accessible checkout chapter.

Thursday, 4pm. The fix is released. Ade checks it once more with VoiceOver on the live site.

Thursday, 4.30pm. Ruth emails Daniel: the gift wrap choice now works with VoiceOver, thank you for telling us, and if he has a minute next time he shops, she would be glad to hear whether it works for him.

Thursday, 4.45pm. Ruth adds an entry to the accessibility log:

FieldEntry
ReceivedMonday 9 November 2026, 10.14am, by email
Reported byCustomer (name kept in the order system, not in the log)
WhereCheckout, gift wrap choice
BarrierCustom dropdown not announced or usable with VoiceOver or keyboard
Success criteria4.1.2 Name, Role, Value and 2.1.1 Keyboard
Workaround givenOrder taken by phone the same morning at the same price
FixReplaced with native radio buttons, keyboard checkout test added
ReleasedThursday 12 November 2026, 4pm
StatementNot listed before. No change needed now it is fixed. Review date updated

From email to finished order: under an hour. From email to fix: three days. Daniel got his present, the shop kept the sale, and the next screen reader user will never meet the problem.

Where an unhappy customer can go, market by market

Most complaints end with step 4. Some do not, and your statement should be honest about where a customer can take it next. Here is the route in each market, so you can name the right ones.

  • UK. The Equality Advisory and Support Service (EASS) is a free helpline that advises people on equality and human rights issues across England, Scotland and Wales, though it does not give legal advice.16 A customer can bring a claim under the Equality Act in the county court, and in general must do so within six months of the act complained of.17
  • Ireland. Under the Equal Status Acts, the customer first notifies the business, usually with form ES.1, within two months of the incident. If there is no reply after a month, or the reply does not resolve it, they can complain to the Workplace Relations Commission within six months.18 Separately, the accessibility regulations make the CCPC consider complaints about eCommerce services, and allow a consumer to ask the Circuit Court for an order directing compliance.12
  • Germany. A consumer who cannot use a service because of a suspected breach can apply to the market surveillance authority to act against the business, under § 32 BFSG.19 For online shops that is the MLBF, which takes reports and applications through forms on its website.9 Under § 34 BFSG, the consumer can also ask for a conciliation procedure with the Schlichtungsstelle under the Behindertengleichstellungsgesetz.20
  • Austria. Consumers can report suspected breaches to the Sozialministeriumservice, which must examine the report and answer in writing, in an accessible format, within eight weeks.21 Its market surveillance unit sits in Linz and takes reports online or by post.22 For a discrimination claim under the disability equality law, a free conciliation at the Sozialministeriumservice must come before any court action.23

None of these routes is something to fear if you have done the work. Each starts by asking what the business did when it heard about the barrier, and a dated statement, a quick reply, a finished order and a logged fix are the best answer.

Example: the reply Ruth sends when a customer is still not satisfied

Helen Marsh has low vision and zooms her browser to 200%. She writes that the event booking page cut off the date and time, and by the time Ade fixed it she had missed the event she wanted. She is not happy.

Ruth does not argue. She writes that Helen is right to be disappointed, refunds the ticket, offers a place at the next session, explains what was fixed and when, and adds: "If you would like to take this further, the Equality Advisory and Support Service gives free advice at equalityadvisoryservice.com." Naming the route costs Ruth nothing. Hiding it would cost her trust.

Keeping the statement true after launch

A statement starts going stale the day you publish it, because the site keeps changing. Three habits keep it true.

  • Review on change. Read the statement again whenever you change the checkout, the account area, the templates or the design. If a release touches the critical path, retest it and update the date.
  • Keep the log. Every report, every workaround, every fix, with dates. That log is what makes the statement provable rather than hopeful.
  • Close the loop. When a known issue is fixed, take it off the list and say so. When a new one is found, add it with a workaround before the fix, not after.

One more line in the European law is worth knowing. Article 13(4) says that where a service is not in conformity, the provider must take corrective measures and immediately inform the competent authorities of the Member States where it is provided.6 The German and Austrian laws carry the same duty.710 How an authority expects that to work for a bug fixed within days is a question for your lawyer. A business with a log and dated fixes is in a far better position to answer it than one without.

Example: Ade's release checklist line

Ade adds one line to the checklist he runs before every release of the Brightwater site:

If this release changes the checkout, account, templates or navigation: run the keyboard and screen reader pass on the changed pages, update the known issues list, update Accessibility::LAST_REVIEWED, and note it in the log.

About 20 minutes on a normal release, and the difference between a statement that was true in November and one still true next November.

Conclusion

An accessibility statement is a promise in public, and a complaint is when someone checks it. Write only what you have tested. Name your standard, list what does not work yet with a way round it and a date, give a person to contact by email and by phone, and name the routes a customer can take if you get it wrong. If you sell into the EU, the Annex V information is a legal duty in every market you serve, and Germany also wants the market surveillance authority named. When the email comes, acknowledge it, help the customer finish today, fix the cause with a test, and write it down. That is how a business keeps the duty that sits with it, because no plugin, platform or badge can hold it for you.

If you want a statement you can stand behind, and a site that earns it, book the free workshop: we go through your site and your current statement together, and the first two weeks of work are on me.

Sources

  1. 1.

    W3C Web Accessibility Initiative, Developing an Accessibility Statement (minimum and recommended components, and the statement generator), W3C, updated 11 March 2021, https://www.w3.org/WAI/planning/statements/

  2. 2.

    Government Digital Service and Central Digital and Data Office, Sample accessibility statement (for a fictional public sector website), with the headings, the three compliance status sentences, the feedback and contact section and the enforcement procedure, GOV.UK, first published 17 May 2019, updated 30 September 2024, https://www.gov.uk/government/publications/sample-accessibility-statement/sample-accessibility-statement-for-a-fictional-public-sector-website

  3. 3.

    UK Parliament, Equality Act 2010, section 29, Provision of services, etc., legislation.gov.uk, https://www.legislation.gov.uk/ukpga/2010/15/section/29

  4. 4.

    UK Parliament, Equality Act 2010, section 20, Duty to make adjustments, legislation.gov.uk, https://www.legislation.gov.uk/ukpga/2010/15/section/20

  5. 5.

    Equality and Human Rights Commission, Equality Act 2010 Code of Practice for Services, Public Functions and Associations, paragraphs 3.6, 3.14 and 3.53, GOV.UK, updated 5 August 2026, https://www.gov.uk/government/publications/equality-act-2010-draft-code-of-practice-for-services-public-functions-and-associations-2026/equality-act-2010-draft-code-of-practice-for-services-public-functions-and-associations-2026

  6. 6.

    European Parliament and Council, Directive (EU) 2019/882 of 17 April 2019 on the accessibility requirements for products and services (European Accessibility Act), article 13 and Annex V, EUR Lex, 2019, https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32019L0882

  7. 7.

    Bundesministerium der Justiz, Barrierefreiheitsstärkungsgesetz (BFSG), § 14 Pflichten des Dienstleistungserbringers, gesetze im internet, https://www.gesetze-im-internet.de/bfsg/__14.html

  8. 8.

    Bundesministerium der Justiz, Barrierefreiheitsstärkungsgesetz (BFSG), Anlage 3 (zu § 14 Absatz 1 Nummer 2), Informationen über Dienstleistungen, die die Barrierefreiheitsanforderungen erfüllen, including the name of the competent market surveillance authority, gesetze im internet, https://www.gesetze-im-internet.de/bfsg/anlage_3.html

  9. 9.

    Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF), Magdeburg, tasks, reporting of barriers and applications under § 32 BFSG, mlbf-barrierefrei.de, 2026, https://www.mlbf-barrierefrei.de/

  10. 10.

    Republik Österreich, Barrierefreiheitsgesetz (BaFG), § 14 Pflichten der Dienstleistungserbringer, RIS Open Government Data, 2023, https://ogd.ris.bka.gv.at/Dokumente/Bundesnormen/NOR40254374/NOR40254374.html

  11. 11.

    Republik Österreich, Barrierefreiheitsgesetz (BaFG), Anlage 3, Informationen über die Konformität von Dienstleistungen gemäß § 14 Abs. 2, RIS Open Government Data, 2023, https://ogd.ris.bka.gv.at/Dokumente/Bundesnormen/NOR40254407/NOR40254407.html

  12. 12.

    Minister for Children, Equality, Disability, Integration and Youth, S.I. No. 636 of 2023, European Union (Accessibility Requirements of Products and Services) Regulations 2023, regulations 4, 14, 30 and 41 and Schedule 3, electronic Irish Statute Book, 2023, https://www.irishstatutebook.ie/eli/2023/si/636/made/en/print

  13. 13.

    Competition and Consumer Protection Commission, CCPC role and responsibilities, Accessibility for businesses (eCommerce services and the other compliance authorities), ccpc.ie, 2025, https://www.ccpc.ie/enforcement-and-regulation/market-surveillance/accessibility/accessibility-for-businesses/ccpc-role-and-responsibilities

  14. 14.

    CEN, CENELEC and ETSI, EN 301 549 V3.2.1 (2021 03), Harmonised European Standard, Accessibility requirements for ICT products and services, clause 9.0, ETSI, 2021, https://www.etsi.org/deliver/etsi_en/301500_301599/301549/03.02.01_60/en_301549v030201p.pdf

  15. 15.

    W3C, Web Content Accessibility Guidelines (WCAG) 2.1, W3C Recommendation, updated 6 May 2025, section 5.3 Conformance Claims (Optional) and success criteria 2.1.1 Keyboard, 2.4.4 Link Purpose (In Context) and 4.1.2 Name, Role, Value, https://www.w3.org/TR/WCAG21/

  16. 16.

    Equality Advisory and Support Service (EASS), helpline for England, Scotland and Wales, equalityadvisoryservice.com, https://www.equalityadvisoryservice.com/

  17. 17.

    UK Parliament, Equality Act 2010, section 118, Time limits, legislation.gov.uk, https://www.legislation.gov.uk/ukpga/2010/15/section/118

  18. 18.

    Irish Human Rights and Equality Commission, How to take a case to the WRC (form ES.1 within two months, complaint within six months), ihrec.ie, https://www.ihrec.ie/your-rights/make-a-complaint-to-the-wrc/

  19. 19.

    Bundesministerium der Justiz, Barrierefreiheitsstärkungsgesetz (BFSG), § 32 Rechte von Verbrauchern, anerkannten Verbänden und qualifizierten Einrichtungen im Verwaltungsverfahren, gesetze im internet, https://www.gesetze-im-internet.de/bfsg/__32.html

  20. 20.

    Bundesministerium der Justiz, Barrierefreiheitsstärkungsgesetz (BFSG), § 34 Schlichtung, gesetze im internet, https://www.gesetze-im-internet.de/bfsg/__34.html

  21. 21.

    Republik Österreich, Barrierefreiheitsgesetz (BaFG), § 35 Rechtsdurchsetzung, RIS Open Government Data, 2023, https://ogd.ris.bka.gv.at/Dokumente/Bundesnormen/NOR40254395/NOR40254395.html

  22. 22.

    Sozialministeriumservice, Marktüberwachung digitale Barrierefreiheit, Allgemeine Informationen zum Barrierefreiheitsgesetz (reports online or by post to the Landesstelle Oberösterreich, Linz), sozialministeriumservice.gv.at, 2025, https://www.sozialministeriumservice.gv.at/Marktueberwachung_digitale_Barrierefreiheit/Allgemeine_Informationen_zum_Barrierefreiheitsgesetz/Allgemeine-Informationen-zum-Barrierefreiheitsgesetz.de.html

  23. 23.

    Sozialministeriumservice, Schlichtung nach dem Behindertengleichstellungsrecht, Informationen für Unternehmen, sozialministeriumservice.gv.at, https://www.sozialministeriumservice.gv.at/Unternehmen/Gleichstellung/Schlichtung/Schlichtung.de.html