Skip to main content

Accessibility Statement Generator

Fill in the form to create an accessibility statement for your website, then copy it or download it as HTML or text. It is free, needs no account, and follows the W3C's guidance on what a statement should contain, with options for the ADA, Section 508, AODA and the European Accessibility Act.

Free, no signupBuilt on the W3C statement modelCopy or download HTML and text

Statement details

Fields marked * are required. Everything stays in your browser until you copy or download it.

How people can reach you about accessibility *

Add an email address, a phone number, or both. Contact details are part of the W3C's minimum contents for a statement.

WCAG version
WCAG conformance level
Laws and standards to mention (optional)

Ticking the European Accessibility Act adds a section with the service information its Annex V asks for.

Measures to support accessibility (optional)
Technologies relied upon (optional)

Not sure what to write under conformance status or known limitations? Scan your site first with the free ADA compliance checker or the WCAG checker.

What is an accessibility statement?

An accessibility statement is a public page that tells visitors which accessibility standard your website aims to meet (usually WCAG Level AA), how well it meets it today, what is known not to work yet, and how someone with a disability can report a problem or get the content another way.

The W3C's Web Accessibility Initiative gives three reasons to publish one: it shows users you care about accessibility, it tells them how accessible your content is, and it demonstrates your commitment. The US Department of Justice's 2022 web guidance makes the practical case: “Websites that provide a way for the public to report accessibility problems allow website owners to fix accessibility issues.”

A statement is not a certificate and does not make a site conform. It is only as good as the work behind it. For tone, wording and the claims to avoid, read our guide on how to write an accessibility statement.

Sources: W3C WAI, Developing an Accessibility Statement (opens in new tab); DOJ, Guidance on Web Accessibility and the ADA (March 18, 2022) (opens in new tab)

What to include in an accessibility statement

The W3C says a statement should contain at least a commitment to accessibility, the standard applied and contact information, and recommends adding the rest where you can. Every row below is a field in the generator.

Elements of an accessibility statement and who expects them
ElementWhat to writeWho expects it
CommitmentOne or two sentences saying you are committed to accessibility for people with disabilities.W3C minimum
Standard appliedThe exact standard and level, for example WCAG 2.2 Level AA.W3C minimum
Contact informationAn email address or phone number that someone reads, and a response time you can keep.W3C minimum
Conformance statusFully conformant, partially conformant, non-conformant or not assessed. Few sites can honestly claim full conformance: the February 2026 WebAIM Million found detectable WCAG failures on 95.9% of the top one million home pages.W3C statement generator
Known limitationsWhat does not work yet, why, and what to do in the meantime.W3C recommended; required for EU public sector sites
Measures takenTraining, audits, procurement rules and a feedback process.W3C recommended
Compatibility and technologiesThe browsers and assistive technologies you design and test for, and the technologies the site relies on.W3C recommended
Assessment approachHow and when you checked: self-evaluation, an automated scan plus manual testing, or an external audit.W3C statement generator
Laws and policiesThe national or local laws that apply to you, such as the EAA or AODA.W3C recommended
Escalation routeWhere people can go if your response does not solve the problem.Required for EU public sector sites
DateWhen the statement was last reviewed or updated.W3C statement generator; required for US federal sites

Sources: W3C WAI statement guidance (opens in new tab); W3C statement generator (opens in new tab); Directive (EU) 2016/2102, Article 7 (opens in new tab); Section508.gov (OMB M-24-08) (opens in new tab); WebAIM Million (February 2026) (opens in new tab)

Accessibility statement example (template)

Here is a statement the generator produced for a fictional online store that sells in the US and the EU. It shows every section, including the European Accessibility Act block that only appears when you tick EAA. Use it as a template, but replace every detail with your own and only claim what you have checked.

Accessibility Statement for Northwind Outdoor Supply

Last updated: October 9, 2026

Northwind Outdoor Supply is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.

This statement takes into account the following laws and standards: Americans with Disabilities Act (ADA); European Accessibility Act (EAA).

Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. They define three levels of conformance: Level A, Level AA and Level AAA.

https://www.example.com partially conforms to WCAG 2.2 Level AA. "Partially conformant" means that some parts of the content do not fully conform to the accessibility standard.

Assessment approach

This conformance status was last assessed on September 30, 2026.

Self-evaluation: an automated scan of our main page templates, followed by manual keyboard and screen reader checks of the checkout.

Scope

This accessibility statement applies to https://www.example.com.

Measures to support accessibility

Northwind Outdoor Supply takes the following measures to ensure accessibility:

  • Provide accessibility training for staff
  • Conduct regular accessibility audits
  • Maintain a feedback mechanism for accessibility issues

Technical specifications

Accessibility of https://www.example.com relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

  • HTML
  • CSS
  • JavaScript
  • WAI-ARIA

Compatibility with browsers and assistive technology

The site is designed to work with recent versions of Chrome, Firefox, Safari and Edge, and with the NVDA, JAWS and VoiceOver screen readers.

Known limitations

Despite our best efforts to ensure accessibility of https://www.example.com, there may be some limitations. Below is a description of known limitations:

Some older product videos do not have captions yet. Transcripts are available on request. The store locator map is a third-party embed that is hard to use with a keyboard. The Stores page lists the same addresses as text.

Information under the European Accessibility Act

This section gives the service information described in Annex V of the European Accessibility Act (Directive (EU) 2019/882).

Description of the service

An online store selling outdoor clothing and equipment to customers in the United States and the European Union.

How the service works

Customers browse or search the catalogue, add items to a basket, check out with a card or wallet payment, and track orders from their account.

How the service meets the accessibility requirements

We apply WCAG 2.2 Level AA to meet the accessibility requirements in Annex I of the Directive. The current conformance status is set out under "Conformance status". Known gaps are listed under "Known limitations".

How we keep the service compliant

Every release is scanned automatically before it goes live, the checkout is re-tested by hand each quarter, and accessibility reports from customers go to the product team for a fix.

You can ask for this information in another format, including spoken format, using the contact details below.

Feedback and contact information

We welcome your feedback on the accessibility of https://www.example.com. Please let us know if you encounter accessibility barriers:

  • Email: accessibility@example.com
  • Phone: +1 (555) 010-0199

We try to respond to accessibility feedback within 5 business days.

For a live statement on a real site, see CompliaScan's own accessibility statement, which follows the same structure.

Do you need an accessibility statement? ADA, Section 508, EAA and more

Whether a statement is legally required depends on who you are and where you operate. Here is what each framework says. This is general information, not legal advice.

ADA: US businesses and nonprofits open to the public

The ADA does not require an accessibility statement. The DOJ's 2022 web guidance says businesses “have flexibility in how they comply” and describes WCAG as “helpful guidance” rather than a mandated standard.

A statement is still worth having because it gives visitors a way to report barriers before they turn into complaints. Website accessibility lawsuits are common: Seyfarth Shaw counted 3,117 filed in federal court in 2025. A statement will not stop a lawsuit on its own, and an inflated “fully compliant” claim is easy to disprove. Check where your site stands with the ADA compliance checker.

Sources: DOJ web guidance (2022) (opens in new tab); Seyfarth Shaw, ADA Title III blog (March 2026) (opens in new tab)

ADA Title II: state and local governments

The DOJ's Title II rule sets WCAG 2.1 Level AA as the standard for state and local government websites. Under the current compliance dates, public entities serving 50,000 or more people must comply by April 26, 2027, and smaller entities and special districts by April 26, 2028. A statement is the natural place to say which standard you follow and how to report a problem. More on website accessibility for government agencies.

Source: Federal Register 2026-07663 (opens in new tab)

Section 508: US federal agencies

OMB memo M-24-08 requires federal agencies to maintain an accessibility statement on their websites, and agencies must link it from the sitewide footer. It must give or link to:

  • the accessibility standard applied and any known limitations or alternative versions
  • the name and email address of the agency's Section 508 program manager
  • a public feedback mechanism for reporting accessibility problems
  • instructions for filing a Section 508 complaint
  • reasonable accommodation procedures for employees and job applicants
  • instructions for using the telecommunications relay service
  • relevant digital accessibility policies
  • the date the statement was last updated or reviewed

The Revised 508 Standards use WCAG 2.0 Level A and AA. Vendors selling to agencies are usually asked for an Accessibility Conformance Report instead; the free VPAT starter generator builds a draft, and the Section 508 compliance checker scans a site.

Sources: Section508.gov, Developing a Website Accessibility Statement (opens in new tab); US Access Board, Revised 508 Standards (E205.4) (opens in new tab)

European Accessibility Act: EU products and services, since June 28, 2025

The EAA has applied since June 28, 2025 to listed products and to services provided to consumers, including e-commerce, consumer banking, e-books, and the websites and apps of passenger transport services (Article 2). Article 13 requires service providers to publish information explaining how the service meets the accessibility requirements, in written and oral format and in a way that is accessible to people with disabilities, and to keep it for as long as the service is in operation. Annex V places that information in your general terms and conditions or an equivalent document and lists what it should cover:

  • a general description of the service in accessible formats
  • the descriptions and explanations needed to understand how the service works
  • a description of how the service meets the accessibility requirements in Annex I
  • information showing that service delivery and its monitoring keep the service compliant

Microenterprises that provide services (fewer than 10 staff, with annual turnover or a balance sheet total of no more than EUR 2 million) are exempt. Each EU country applies the EAA through its own national law, so check the rules in each country where you offer the service. The generator's EAA option adds the Annex V sections to your statement. Our European Accessibility Act requirements guide covers scope and deadlines in more detail.

Source: Directive (EU) 2019/882, Articles 2, 3, 4, 13 and 31 and Annex V (opens in new tab)

EU public sector websites: Web Accessibility Directive

Public sector bodies in the EU must publish a detailed, comprehensive and clear accessibility statement, keep it updated, and use the European Commission's model statement. Article 7 requires it to explain which content is not accessible and why, with any accessible alternatives, to describe and link a feedback mechanism, and to link the enforcement procedure. Start from the official model; this generator covers the same core parts but is not that template.

Source: Directive (EU) 2016/2102, Article 7 (opens in new tab)

AODA: Ontario, Canada

Ontario's Integrated Accessibility Standards Regulation requires large organizations (50 or more employees in Ontario) and designated public sector organizations to make their websites conform to WCAG 2.0 Level AA, except live captions and pre-recorded audio description. Organizations other than small ones must also have accessibility policies that include a statement of organizational commitment, and must make those policies public. A website accessibility statement is a natural place to publish that commitment and your feedback route.

Source: O. Reg. 191/11, sections 3 and 14 (opens in new tab)

How to publish your accessibility statement

Give the statement its own page, for example yoursite.com/accessibility, and link it from the footer so it can be reached from every page. The W3C suggests linking it from the footer and other prominent places with a consistent link name, and US federal sites must use a sitewide footer link. “Accessibility” or “Accessibility statement” are the usual link texts.

Selling in the EU? Also link the statement from your terms and conditions, because Annex V of the EAA puts this information in your general terms and conditions or an equivalent document.

Steps by platform: Shopify · WordPress · Wix · Squarespace · Webflow

Add an accessibility statement in Shopify

  1. From your Shopify admin, go to Online Store > Pages and click Add page.
  2. Title it "Accessibility statement". To paste the HTML from "Copy HTML", click the Edit code button in the Content toolbar first. Plain text can go straight into the editor.
  3. Keep Visible selected in the Visibility section, then click Save.
  4. Go to Content > Menus, click the menu your theme shows in the footer, then click Add menu item.
  5. Name it "Accessibility", click the link field, choose Pages, select your new page, click Add, then click Save menu.

Before you publish, scan the site with the Shopify accessibility checker so your known limitations are accurate.

Steps checked in October 2026 against the Shopify Help Center (adding pages (opens in new tab); editing menus (opens in new tab)). Menus change, so follow the help center if a label differs.

Add an accessibility statement in WordPress

  1. In your WordPress admin, go to Pages > Add New.
  2. Title it "Accessibility statement". Add a Custom HTML block and paste the HTML from "Copy HTML", or paste the text into regular blocks.
  3. Click Publish.
  4. Block theme: go to Appearance > Editor, open Patterns > Template Parts > Footer, add a link to the new page and save. Footer changes apply to every page that uses the footer.
  5. Classic theme: go to Appearance > Menus and select your footer menu. In the Pages pane, tick the new page, click Add to Menu, then click Save Menu.

Before you publish, scan the site with the WordPress accessibility checker so your known limitations are accurate.

Steps checked in October 2026 against the WordPress.org documentation (Create pages (opens in new tab); Site Editor (opens in new tab); Appearance Menus screen (opens in new tab)). Menus change, so follow the help center if a label differs.

Add an accessibility statement in Wix

  1. Add a page to your site and name it "Accessibility Statement".
  2. Add text boxes and paste in the statement. Use a separate text box for the title and for each section heading so they get heading tags and the body text gets paragraph tags.
  3. Create a text link or button named "Accessibility Statement" that points to the page.
  4. Attach the link or button to your site's footer (or header) so it appears on every page.

Before you publish, scan the site with the Wix accessibility checker so your known limitations are accurate.

Steps checked in October 2026 against the Wix Help Center (Adding an accessibility statement to your site (opens in new tab)). Menus change, so follow the help center if a label differs.

Add an accessibility statement in Squarespace (version 7.1)

  1. Open the Pages panel and click + in the Not linked section. Pages there stay out of your main menu, but you can still link to them.
  2. Click + Add Blank, type "Accessibility statement" as the page title and press Enter.
  3. Click Edit, add a section with a Text block, paste the statement and format each section title as a heading.
  4. To link it on every page, click Edit on any page, hover over the footer and click Edit footer. Add a text link to the new page, then click Save.

Before you publish, scan the site with the Squarespace accessibility checker so your known limitations are accurate.

Steps checked in October 2026 against the Squarespace Help Center (Layout pages (opens in new tab); The Not linked section (opens in new tab); Edit your site's footer (opens in new tab)). Menus change, so follow the help center if a label differs.

Add an accessibility statement in Webflow

  1. Open the Pages panel, click the Create new page icon, then click New page.
  2. Type "Accessibility statement" in the Page name field and click Create.
  3. Add the statement text to the page, keeping each section title as a heading.
  4. If your footer is a component, edit the main component and add a link to the new page. Edits to the main component affect every instance, so the link appears site-wide.
  5. Publish your site.

Before you publish, scan the site with the Webflow accessibility checker so your known limitations are accurate.

Steps checked in October 2026 against the Webflow Help Center (Pages panel overview (opens in new tab); Components overview (opens in new tab)). Menus change, so follow the help center if a label differs.

How to keep your accessibility statement up to date

  • Review it at least once a year and change the “Last updated” date each time. The W3C's statement generator says the date should ideally be no more than a year old, or the statement may be considered unmaintained. US federal statements must show the date.
  • Review it after redesigns, new themes or apps, new checkout flows and new third-party embeds. These changes can add new barriers.
  • When you fix a reported problem, remove it from known limitations. When you find a new one, add it with a workaround.
  • Re-scan regularly. Automated scans catch only part of WCAG, so pair them with manual keyboard and screen reader checks. Our testing methodology explains what our scanner checks and what it cannot.
  • Under the EAA, service providers must have procedures that keep the service in conformity, taking account of changes to the service and to the standards it relies on (Article 13(3)).

Sources: W3C statement generator (opens in new tab); Section508.gov (opens in new tab); Directive (EU) 2019/882, Article 13 (opens in new tab)

Free generator vs. an auto-updating statement

This free generator gives you a one-time statement from your own answers. CompliaScan's paid plans build the statement from your scan results and keep it current as you fix issues.

Free generator
  • One-time statement from your answers
  • WCAG version, level and status you choose
  • EAA Annex V section on request
  • Copy text or HTML, download HTML or TXT
  • No account required
Paid plansfrom $69/mo
  • Statement generated from your scan results
  • Updates as your accessibility improves
  • Issue details and remediation status
  • Embed with a snippet, or link or iframe the hosted page
  • Scanning, monitoring and reports included
Compare plans

Accessibility statement generator FAQ

Is this accessibility statement generator free?

Yes. The generator is free, needs no account and runs in your browser. Your entries are not sent to our servers; we only count that the tool was used. Copy the result or download it as HTML or plain text.

Is there an accessibility statement template I can copy?

Yes. The example statement on this page is a complete template, and the generator fills the same structure with your details. For notes on wording and the claims to avoid, see our guide on how to write an accessibility statement.

Is an accessibility statement legally required?

It depends on who you are. US federal agencies must keep one on their websites under OMB memo M-24-08. EU public sector bodies must publish one based on the European Commission's model statement. Service providers covered by the European Accessibility Act must publish information on how their service meets the accessibility requirements. The ADA does not require a statement from businesses, although it is good practice. The section on which laws apply has the details and sources.

What is an ADA accessibility statement?

It is an accessibility statement for a US website that serves the public. The ADA does not require one, and the Department of Justice's 2022 web guidance leaves businesses flexibility in how they make their websites accessible. A practical target is WCAG 2.1 or 2.2 Level AA. The DOJ's Title II rule for state and local governments uses WCAG 2.1 Level AA, and WCAG 2.2 is the current W3C version. Add a contact for reporting barriers and list known limitations, then tick ADA in the generator to mention it.

What should a WCAG accessibility statement say?

Name the exact version and level you aim for, such as WCAG 2.2 Level AA, and state your conformance status honestly. The W3C uses four statuses: fully conformant, partially conformant, non-conformant and not assessed. Few sites can honestly claim full conformance, so partially conformant is usually the accurate and more credible choice. A WCAG checker scan helps you fill in known limitations.

Does an accessibility statement protect me from ADA lawsuits?

No. A statement does not make a site conform and is not a legal defense on its own. It gives people a way to report barriers so you can fix them, which the DOJ's guidance describes as useful. Keep your claims accurate and fix what you find. Our ADA compliance checker shows where to start.

What does an EAA accessibility statement need to include?

Annex V of the European Accessibility Act asks service providers to describe the service, explain how it works, describe how it meets the accessibility requirements, and show how service delivery and monitoring keep it compliant. The information belongs in your general terms and conditions or an equivalent document, in written and oral format. Microenterprises that provide services are exempt. Tick EAA in the generator to add these sections.

Where should I put my accessibility statement?

On its own page, linked from the footer of every page with a clear name such as "Accessibility" or "Accessibility statement". See the publishing steps for Shopify, WordPress, Wix, Squarespace and Webflow.

How often should I update an accessibility statement?

At least once a year, and also after redesigns, new themes or apps, and new third-party tools. The W3C's statement generator says a statement dated more than a year ago may be considered unmaintained. Update the "Last updated" date each time and keep the known limitations list current.

How is an accessibility statement different from an accessibility report or a VPAT?

A statement is a short public page for visitors: the standard you aim for, how close you are, what does not work yet and how to get help. An accessibility report lists the specific issues found on your pages, such as the results of a free WCAG checker scan. A VPAT, once filled in, is an Accessibility Conformance Report that goes through a product criterion by criterion, and buyers often ask vendors for one. The free VPAT starter generator builds a first draft.

Get Accessibility Compliance Updates

Receive tips on accessibility statements, legal requirements, and WCAG compliance.