My Tool Studio
WCAG

Accessibility Statement Generator

This accessibility statement generator builds a statement for your website from a form that follows the W3C structure. Enter your organization, website, WCAG version and level, conformance status, measures, contacts, compatible browsers, technologies, known limitations with alternatives, assessment approach, approval and complaints process. Pick a template for the ADA, Section 508, AODA, the European Accessibility Act, the EU directive or the UK regulations, and write the fixed wording in English, French, Spanish or German. Copy Markdown or HTML, or download an HTML page, Word file or text file. Save a draft file to edit it later. No signup or email is needed, and nothing you type leaves your browser. The generator writes the statement; it cannot check that the claims in it are true.

Always freeNo sign upRuns in your browser

No signup or email needed. The statement is built in your browser as you type.

Your details

1. Basic information
2. Your efforts
Measures you take
3. Feedback and contact
4. Technical information
Technologies relied upon

Known limitations and alternatives

Describe each barrier in plain words, why it exists, and what people can do instead.

    5. Assessment and evaluation
    Assessment approach
    6. Approval, complaints and dates

    Preview

    Accessibility Statement for [Organization name]

    [Organization name] 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.

    Measures to support accessibility

    [Organization name] takes the following measures to ensure accessibility of [website address]:

    • Include accessibility as part of our mission statement
    • Include accessibility throughout our internal policies
    • Perform regular automated and manual accessibility audits

    Conformance status

    The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. [website address] is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

    Feedback

    We welcome your feedback on the accessibility of [website address]. Please let us know if you encounter accessibility barriers on [website address]:

    • [Add a contact email and/or phone number]

    We try to respond to feedback within 5 business days.

    Technical specifications

    Accessibility of [website address] 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
    • WAI-ARIA
    • CSS
    • JavaScript

    These technologies are relied upon for conformance with the accessibility standards used.

    Assessment approach

    [Organization name] assessed the accessibility of [website address] by the following approaches:

    • Self-evaluation

    Link the published page from your footer, for example at /accessibility/.

    How to use

    01

    Fill in the basics

    Enter your organization and website, pick the statement language and a law or region template, then the WCAG version, target level and conformance status. Click Load example to see a finished one.

    02

    Open the other sections

    Tick your measures, add contacts and response time, list compatible browsers and technologies, then add each known limitation with why it exists and an alternative. Sections you leave empty are left out.

    03

    Copy or download, then publish

    Click Copy Markdown or Copy HTML, or download HTML, Word, MD or TXT. Publish it at a stable address such as /accessibility, link it from your footer, and keep the draft file for the next update.

    Why Accessibility Statement Generator

    Sample accessibility statement

    Here is part of what the generator produces in English for a dental practice that chose WCAG 2.1, Level AA, partially conformant, self-evaluation, and one known limitation.

    "Riverside Dental 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."

    "riversidedental.example is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard."

    Under Limitations and alternatives, the practice's one entry appears as a bullet: "Patient forms: Older forms are PDFs that are not yet tagged for screen readers. Alternative: Call reception and we will fill in the form with you."

    "Riverside Dental assessed the accessibility of riversidedental.example by the following approaches: Self-evaluation."

    The full statement also includes the measures section, the feedback section with contact details, and the date it was created.

    What different laws expect from a statement

    The generator follows the W3C structure, which works as a base everywhere. Some rules ask for extra parts. Pick the matching template and the generator adds a legal framework paragraph, and for EU and UK public sector sites an enforcement procedure section. For the EU directive, fill in your national enforcement body where the placeholder shows.

    RuleStatement required?What to add beyond the generator
    EU Web Accessibility Directive (public sector)YesYour national enforcement body in the enforcement section; reasons in each limitation
    UK Public Sector Bodies Accessibility RegulationsYesTemplate adds the EHRC and EASS procedure; set the statement and review dates
    European Accessibility ActAccessibility information requiredHow the service meets the requirements, per national rules
    ADA (US)NoNothing required; the standard sections are enough
    AODA (Ontario)Published policies required for 50+ and public sectorLink to your accessibility policy and multi-year plan

    Common questions

    Is an accessibility statement legally required?
    It depends where you are. Public sector bodies in the EU (Web Accessibility Directive) and the UK (Public Sector Bodies Accessibility Regulations) must publish one. The European Accessibility Act asks covered service providers to publish accessibility information, and many do it as a statement. The ADA does not require one, but it is still widely used.
    Where should I put the accessibility statement on my website?
    Publish it at a stable address such as /accessibility and link it from the footer of every page, next to your privacy policy. People look for it there, and a footer link keeps it one click away from any page.
    What should an accessibility statement include?
    At minimum: your commitment, the standard you aim for, your conformance status, known limitations, a way to contact you about barriers, and the date. This generator covers all of those and adds the measures you take and how you assessed the site.
    Should I claim full or partial conformance in an accessibility statement?
    Claim full conformance only if both automated and manual testing support it. Partially conformant, with a list of known limitations and a plan to fix them, is the honest choice for most sites. Pick working toward conformance if remediation has only just started.
    How often should I update my accessibility statement?
    Update it after a redesign, after an audit, and whenever a known limitation is fixed or a new one appears. Reviewing it at least once a year is a sensible habit. Enter the review date in the form so readers can see how current it is.
    Does the European Accessibility Act require an accessibility statement?
    The EAA, which applies from 28 June 2025, requires service providers to publish information on how their service meets the accessibility requirements. Many meet this with an accessibility statement. Pick the European Accessibility Act template to add a legal framework paragraph that names the directive and EN 301 549, then check what your national law asks for on top.
    Which WCAG version should my accessibility statement name?
    Name the version and level you actually tested against. WCAG 2.1 AA is the version most laws cite, and WCAG 2.2 AA is the latest W3C Recommendation. Pick both in the form and the conformance sentence updates to match.
    Does the accessibility statement generator store what I type?
    No. The statement is built in your browser as you type, and copying and downloading happen locally. Your details are not sent to our server. To keep your answers, click Save draft to download a JSON file, and Load draft to open it again later.
    How do known limitations appear in the generated statement?
    Each limitation you add has three fields: the content or page, what the problem is and why, and an alternative or planned fix. They appear as bullets under Limitations and alternatives, in the order you set with the up and down buttons. Add none and the section is left out.
    Is the accessibility statement HTML download ready to publish?
    The HTML download is a complete page with a lang attribute, a title and light styling, so you can upload it as it is. Copy HTML gives just the headings, paragraphs and lists, which take on your site's CSS when pasted into a CMS. Set the response time field to match your real process.

    More WCAG tools

    View all

    Website Accessibility Scanner

    Full-site WCAG 2.1 audit with fix code for every issue

    WCAG
    URL-first

    Color Contrast Checker

    WCAG AA/AAA contrast ratio with passing colors

    WCAG

    WCAG Accessibility Checker

    Check one page or HTML against 70 WCAG 2.1 rules

    WCAG
    URL-first

    ADA Title II Compliance Checker

    WCAG 2.1 AA scan, deadline calculator and Title II readiness checklist

    WCAG
    URL-first