AccessibilityScore.in
Run a free accessibility score

Accessibility guide

Free Accessibility Statement Generator

Answer a few questions and get an accessibility statement you can copy into your website as text or HTML. The generator runs entirely in your browser, so nothing you enter is sent to or stored by AccessibilityScore.in.

Last reviewed by the HalfAccessible accessibility team

Short Answer

An accessibility statement tells visitors how accessible a website is, which standard it aims to meet, its known problems, and how to report barriers. W3C recommends at least a commitment to accessibility, the standard applied and contact details. UK and EU public sector websites must publish one by law.

Generate your accessibility statement

Fill in what you know. The statement updates as you type and stays in your browser.

Conformance status
How did you test?

Preview

Accessibility statement for this website

Our commitment

[Organisation name] is committed to making this website accessible to as many people as possible, including people with disabilities.

Compliance status

We aim to meet WCAG 2.2 Level AA. This website partially conforms with WCAG 2.2 Level AA, for the reasons listed under known limitations.

Known limitations

We are reviewing which parts of this website do not yet meet the standard and will list them here.

Feedback and contact information

If you find an accessibility problem, or need information in a different format such as large print or audio, contact us:

  • [Add an email address or phone number]

How we tested

We assessed this website using automated testing with accessibility checking tools. We review this statement regularly and update it when we make changes.

Key facts

W3C minimum content
A commitment to accessibility, the standard applied, and contact information
Also advisable
Known limitations, measures taken, technical requirements, tested environments and applicable laws
Legally required for
UK public sector bodies and public sector bodies in EU countries under the Web Accessibility Directive
Where to publish
A dedicated page linked from every page, usually in the site footer
How often to update
Whenever you fix or find issues, and at least once a year
Privacy
This generator runs in your browser; nothing you type is stored

What should an accessibility statement include?

The W3C Web Accessibility Initiative says a statement should contain at least a commitment to accessibility for people with disabilities, the accessibility standard applied, and contact information for when people run into problems. It also advises including:

  • Known limitations, so people are not surprised by barriers
  • Measures your organisation takes to ensure accessibility
  • Technical requirements, such as supported browsers
  • The environments the content has been tested in
  • References to the laws and policies that apply to you

Who has to publish an accessibility statement?

Public sector bodies in the UK must publish one under the Public Sector Bodies Accessibility Regulations 2018, and public sector bodies in EU countries must publish one under the Web Accessibility Directive. Under the European Accessibility Act, businesses providing covered services must also make information available on how their services meet the accessibility requirements.

For everyone else a statement is voluntary, but it shows users and buyers that you take accessibility seriously, and it gives people with disabilities a way to reach you before they give up.

What does a UK public sector statement need?

The GOV.UK sample statement sets out the expected sections: how accessible the website is, feedback and contact information, the enforcement procedure, technical information and compliance status, non-accessible content (including any disproportionate burden and content outside the regulations), what you are doing to improve, and how the statement was prepared. Tick the UK public sector option in the generator to add the enforcement procedure, then compare the result with the GOV.UK sample before publishing.

How do you write an honest accessibility statement?

A statement is only useful if it is accurate. Base it on real testing, not on what you hope is true:

  • Scan your key pages first; AccessibilityScore.in shows which WCAG failures are present.
  • Test the main tasks with a keyboard and a screen reader, and list what does not work.
  • Choose partially conforms if any known issue remains; most sites honestly fall here.
  • Give a contact that a person actually monitors, and a time frame for replies.
  • Date the statement and update it when you fix or find issues.

Minimal vs complete accessibility statement

PartMinimal statementComplete statement
CommitmentYesYes
Standard and conformance statusYesYes
Contact for problemsYesYes, with response times
Known limitations and workaroundsRecommendedYes, with fix dates
How the site was tested, and whenRecommendedYes
Technical requirements and tested environmentsOptionalYes
Legal and enforcement informationWhen required by lawYes

Common Questions

Is this accessibility statement generator free?

Yes. It is free, needs no account, and runs in your browser without storing anything you enter.

Is an accessibility statement legally required?

For UK public sector bodies and EU public sector bodies, yes. For most private businesses it is voluntary, though the European Accessibility Act requires covered service providers to publish accessibility information.

Where should I put my accessibility statement?

On its own page, linked from every page of the site, usually in the footer next to the privacy policy.

Can I say my site is fully compliant?

Only if a full evaluation against the standard found no failures. If any known issue remains, say partially conforms and list the issues; an inaccurate statement can mislead users and regulators.

How often should I update my accessibility statement?

Whenever you fix or discover issues, and at least once a year. UK public sector bodies must review theirs regularly.

Does a statement make my website accessible?

No. A statement describes accessibility; it does not create it. Use it alongside testing and fixing, and keep it honest.

Sources

  1. W3C WAI: Developing an accessibility statement
  2. W3C WAI: Accessibility statement generator
  3. GOV.UK: Sample accessibility statement
  4. GOV.UK: Understanding accessibility requirements for public sector bodies
Run a free accessibility score
Free Accessibility Statement Generator | AccessibilityScore.in