Accessibility Statement Template (Free, WCAG 2.1 AA)

Think of it as a short block of text. Copy it, tweak it, and drop it on your site so visitors know you’re actually making things usable for everyone. Simple, right? The template below sticks to the international accessibility guidelines at the AA level, leaves a spot for you to list what’s already broken, and gives users an easy way to flag barriers they hit...

Why a statement actually matters

About one in four adults in the U.S. has a disability, per the CDC, and these folks really need clear info about how accessible your site is. When they see you’re actively working to clear away roadblocks, they’re more likely to stick around, buy something, or reach out.

Here’s the legal reality check! The U.S. Department of Justice hasn’t set up a notice-and-cure period for website violations under Title III of the ADA. Basically, that means a demand letter could land in your inbox any day. This might sound obvious, but a UsableNet report from 2024 counted roughly 4,000 digital-accessibility lawsuits filed each year, and about 70% of those aimed straight at ecommerce businesses. In the EU, the European Accessibility Act kicks in on 28 June 2025 and requires covered service providers to publish accessibility information, usually via a statement (Annex V).

A statement won’t save you from a lawsuit. But it proves good-faith effort. That documentation helps when a regulator or a plaintiff asks for proof.

Core checklist for a compliant statement

Here’s a step-by-step list of what to include. In plain English, each item points to the relevant WCAG 2.1 AA success criteria so you can see why it matters.

1. Identify the website and the governing standard Example: “This statement applies to <www.yourstore.com> and follows the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA.” Why: It shows you’re lining up with the recognized benchmark (WCAG 2.1 AA – criteria such as 1.4.3 contrast, 2.1.1 keyboard, 3.3.2 labels).

2. State the date of the latest accessibility audit Example: “The most recent automated scan was performed on 15 October 2026.” Why: It gives a timestamp that auditors and users can verify.

3. Summarize your current conformance level Example: “Our site meets most of the WCAG 2.1 AA success criteria. Automated testing finds that 83 % of the most common issues, low contrast, missing alt text, missing form labels, empty links, empty buttons, and missing page language, have been addressed.” Why: This paints a realistic picture without promising the moon. Automated tools are great, but Deque's research shows they only catch about 57% of issues by volume, so you still need that human review to catch what the bots miss.

4. List the known barriers Example:

   • Some product images on older collection pages still lack descriptive alt text (1.1.1).  
   • The checkout “Apply coupon” button does not have a visible focus outline on high-contrast mode (2.4.7).  
   

   Why: Transparency goes a long way. It helps users understand where you are and shows you're actively tracking the problems.

5. Describe your remediation plan Example: “We're fixing the remaining issues on a weekly basis. The checkout page will be re-scanned every Friday and any new barrier will be addressed within 7 days.” Why: This shows you're working on it. That matters for your customers, and it counts if your site ever faces legal scrutiny.

6. Provide a contact method for reporting accessibility problems Example: “If you encounter any difficulty using our site, please email accessibility@yourstore.com or use the ‘Report a problem’ button in the lower-right corner of every page.” Why: This gives visitors a direct, easy way to let you know about barriers they find.

7. Include a short accessibility policy commitment Example: “We're committed to making our online store accessible to the widest possible audience, regardless of ability or disability.” Why: It reinforces your business intent and aligns with best-practice guidelines.

8. Add language-specific or regional notes when needed If you serve EU customers: add a paragraph that points to the European Accessibility Act and where users can complain to their national market-surveillance authority. Why: The EU has a requirement for a statement under the EAA, so you need to meet it.

9. Link to the statement page from every footer How: Add a simple text link “Accessibility Statement” in the site footer. No extra script is required.

Common mistakes and shortcuts that don't work

Keep your statement honest and current

1. Schedule your automated scans. Grab our free scanner at /scanner and check up to three pages a week without signing up. If you pay for a plan, the system keeps an eye on up to 100 pages. It automatically re-scans your core pages, like home, product, cart, and checkout, every week.
2. Spend 15 minutes on manual tests monthly. Check keyboard navigation. Zoom in to 200%. Try a screen reader like VoiceOver on Mac or NVDA on Windows. Write down any new barriers in the dashboard.
3. Update the statement whenever you fix something. When you resolve a known issue, change the “known barriers” list. Adjust the audit date. Republish the page.
4. Use a permanent URL for the statement. Accessibility Shield hosts a public page at /statement/[siteId]. This version automatically displays the latest scan date, score, and newly resolved issues. It also comes in English, German, French, Spanish, Italian, and Dutch.
5. Add a “Report a problem” widget. The optional help button at /install is tiny, just 8 KB. It loads asynchronously and stores visitor preferences locally. It won't rewrite your code. It gives users a direct line to you.
6. Keep a record of your effort. The dashboard creates a printable CSV that logs scans, manual checks, and barrier reports. This record helps corporate counsel or compliance officers demonstrate good-faith effort.

Where Accessibility Shield fits

Here's the thing: need a quick, free look at where your site stands? Try the scanner at /scanner. We get why this trips people up: Want a continuously updated, multi-language statement that pulls the latest audit data automatically? Use the hosted statement service at /statement. Both tools work without heavy scripts and pair well with the no-code fix guides at /fix. Ready for ongoing monitoring? Check out the plans on /pricing. To be fair, the first site is free, and paid plans start at $12 a year.

Common questions

What is an accessibility statement?

Think of it as a short, honest page for your visitors. Sound familiar? You tell them which accessibility standards you follow and show you're paying attention! It includes when the site was last checked, what barriers are currently known, how you plan to fix them, and how users can report problems.

Do I legally have to publish an accessibility statement?

In the United States, no law forces a private business to post a statement. However, it's strongly recommended because it shows good-faith effort. The EU is different. The European Accessibility Act requires covered service providers to provide accessibility information, usually in the form of a statement.

Can I just copy a template from the internet and be done?

You can start with a template, but that's not the finish line. You must update the audit date, list any current barriers, and provide a real contact method. A stale or generic statement looks like a checkbox. It does not help users.

How often should I update my statement?

Now, here's where it gets interesting. Update it whenever you run a new accessibility scan, fix a known issue, believe it or not, or add a major feature! A weekly automated scan plus a monthly manual check is a practical rhythm for most small-business sites.

Where can I get a free, ready-to-use template?

Our free statement generator at /tools/statement-generator creates a basic statement in English and offers an EU/EAA version. You can copy the output, tweak it for your brand, and then publish it on a permanent URL.

The information in this article is general and not legal advice. For specific legal questions, consult a qualified attorney.