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 Ireland, Regulation 14 and Schedule 3 of S.I. No. 636 of 2023 require the information in your terms or an equivalent document, in writing and orally, kept up to date. The CCPC is the authority for online shops.
- Ship to Germany and you must also name the German market surveillance authority.
- 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 Ireland and every EU market you ship to: what the regulations ask you to publish, the nine parts of a good statement, wording you can stand behind, a complete sample for an invented Galway 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. Claddagh Books is an independent bookshop in Galway with an online shop at claddaghbooks.example. Sinéad 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.
Example: what Sinéad's footer link leads to
Sinéad 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: "Claddagh 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 Sinéad 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 Galway shop that also ships to Germany and Austria, that means one European rule, written into each country's own law.
In Ireland: what the 2023 regulations ask for
Ireland brought the European Accessibility Act into force through S.I. No. 636 of 2023, the European Union (Accessibility Requirements of Products and Services) Regulations 2023, which apply from 28 June 2025. Regulation 14 says that before providing a service, you must prepare the information set out in Schedule 3, explaining how the service meets the accessibility requirements, make it available to the public in writing and in oral format, including in a manner accessible to people with disabilities, and keep it for as long as the service is in operation.2
Schedule 3 says the information goes into your general terms and conditions or an equivalent document, and contains, where applicable:2
- 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.
The compliance authority for eCommerce services is the Competition and Consumer Protection Commission (CCPC), with the National Disability Authority advising the authorities on accessibility.23
"Oral format" is easy to skim past: someone must be able to get this information without reading a web page, for example by ringing you.
The older law still applies alongside it. Under the Equal Status Acts, a service provider must do what is reasonable to accommodate a disabled person's needs where, without it, using the service would be impossible or unduly difficult, unless that costs more than a nominal amount, judged against the size and resources of the business.4 A statement is not a duty under those Acts, but it is good evidence that you thought about accommodation before anyone had to ask.
The Directive behind it, and the other markets you ship to
Every EU country took the same text from Directive (EU) 2019/882. Article 13(2) asks for the Annex V information, in written and oral format, accessible, and kept for as long as the service runs.5 The national versions differ in small ways that matter if you ship abroad:
- 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.6 Anlage 3 adds one item the Directive does not spell out: you must name the competent market surveillance authority.7 For online shops that is the Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen (MLBF) in Magdeburg.8
- Austria. § 14 of the Barrierefreiheitsgesetz (BaFG) asks for the information in Anlage 3, in written and spoken form and in accessible formats, kept for as long as the service is offered.9 Anlage 3 mirrors Annex V point for point.10
- The UK. The UK did not adopt the Act, and no law requires a private business there to publish a statement, though public sector bodies must.11 If you also sell into Britain, the Equality Act 2010 requires every service provider to make reasonable adjustments, including information in an accessible format, and its code of practice says this covers services on a website.121314
The microenterprise exemption and the other edges of who is covered are in the law article.
Example: what Claddagh Books must publish, and to whom
Sinéad has 12 staff, sells to private customers online, and about one order in ten goes to Germany or Austria.
- Is it an eCommerce service under the Regulations? It is. Private customers buy at a distance through a website.
- Is it a microenterprise? No. Twelve staff is over the line of fewer than 10.
- So Regulation 14 applies: the Schedule 3 information, in writing and orally, kept up to date, with the CCPC as the authority.
- Her orders to Cologne and Linz bring in the German and Austrian laws too, and for German customers she must name the MLBF. She names the Austrian authority as well, because it costs one line. Ade's conclusion: one statement covering all the markets, linked from every page and from the terms and conditions.
The nine parts of a good statement
Put the W3C guidance, the UK government's sample statement and the Schedule 3 list side by side and they agree on most of the structure.1112 I would build every statement from these nine parts, in this order:
- Scope. Which website or app the statement covers, by address, and what it leaves out.
- Standard and level. Which version of WCAG and which level you build and test to. Note that the harmonised European standard EN 301 549 builds on WCAG at level AA for web content.15
- How the service works. A short description in plain words: how people browse, buy, pay and get their order. This is the Schedule 3 general description and explanation of operation.
- What works, and how you know. What you tested, with which tools and assistive technology, on which pages, and when.
- 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.
- Other formats. How to get any content in another format, for example large print, an accessible document, or read out on the phone.
- Contact and response time. A named way to reach a person, by email and by phone, and how quickly you reply.
- Complaints and enforcement. What to do if the customer is not happy with your answer, including the authority for each market you serve.
- 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: Sinéad checks her old page against the nine parts
Sinéad 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). Sinéad 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 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.16 In other words, a real claim is narrow, dated and specific. "Our website is fully compliant" is none of those.
The UK government's sample statement for public bodies uses three status sentences: fully, partially or not compliant with WCAG 2.2 AA.11 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.
Example: three sentences rewritten
Ade goes through the drafts Sinéad found on other shops' sites and rewrites each into something Brightwater could defend.
| Before | Why it fails | After |
|---|---|---|
| "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 claddaghbooks.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: Claddagh Books' accessibility statement in full
Here is the complete statement Sinéad 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 claddaghbooks.example
Scope. This statement covers our online shop at claddaghbooks.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, 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 Galway 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, ring 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. Ring us and we will go through any of this statement with you.
Contact us. Email access@claddaghbooks.example or ring the shop on the number at the foot of every page, Monday to Saturday, 9am to 6pm. 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 Sinéad, the owner, will look at it personally. In Ireland the authority for online shops under the accessibility regulations is the Competition and Consumer Protection Commission (CCPC), and you can also bring a complaint under the Equal Status Acts to the Workplace Relations Commission. In Germany the authority 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 Sinéad 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. Schedule 3 asks for the information in the general terms and conditions or an equivalent document.2 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.
Example: Ade builds the footer link and the page
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).16 "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@claddaghbooks.example">access@claddaghbooks.example</a>
or phone the shop on <a href="tel:+353000000000">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:andtel: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:
- Acknowledge. Reply quickly, thank the person, and say what happens next. Do not argue, and do not ask them to prove they are disabled.
- 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.
- 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.
- 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.
Example: one complaint at Claddagh Books, from first email to fix
Monday, 10.14am. An email arrives at the accessibility inbox from Ciarán Walsh. Ciarán 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. Sinéad replies. She thanks Ciarán, 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. Ciarán chooses the phone call. Sinéad 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.16
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 theidof its input, so the visible text is the accessible name, and tapping the words selects the button. checkedon "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. Sinéad emails Ciarán: 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. Sinéad adds an entry to the accessibility log:
| Field | Entry |
|---|---|
| Received | Monday 9 November 2026, 10.14am, by email |
| Reported by | Customer (name kept in the order system, not in the log) |
| Where | Checkout, gift wrap choice |
| Barrier | Custom dropdown not announced or usable with VoiceOver or keyboard |
| Success criteria | 4.1.2 Name, Role, Value and 2.1.1 Keyboard |
| Workaround given | Order taken by phone the same morning at the same price |
| Fix | Replaced with native radio buttons, keyboard checkout test added |
| Released | Thursday 12 November 2026, 4pm |
| Statement | Not 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. Ciarán 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.
- 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.17 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.2
- 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.18 For online shops that is the MLBF, which takes reports and applications through forms on its website.8 Under § 34 BFSG, the consumer can also ask for a conciliation procedure with the Schlichtungsstelle under the Behindertengleichstellungsgesetz.19
- 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.20 Its market surveillance unit sits in Linz and takes reports online or by post.21 For a discrimination claim under the disability equality law, a free conciliation at the Sozialministeriumservice must come before any court action.22
- Britain. The Equality Advisory and Support Service (EASS) is a free helpline that advises people on equality and human rights across England, Scotland and Wales, though it does not give legal advice.23 A claim under the Equality Act goes to the county court, in general within six months of the act complained of.24
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 Sinéad sends when a customer is still not satisfied
Áine Brennan 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.
Sinéad does not argue. She writes that Áine 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, you can notify us formally under the Equal Status Acts and bring a complaint to the Workplace Relations Commission, and the Irish Human Rights and Equality Commission explains how." Naming the route costs Sinéad 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.5 The Irish, German and Austrian rules carry the same duty.269 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. In Ireland, Regulation 14 and Schedule 3 make that information a legal duty, in writing and orally, and Germany also wants the market surveillance authority named if you ship there. 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.