Accessibility Statement Generator

Step 1 of 7

Website or app

Where will your Accessibility Statement live?

Why we ask

Select every platform the statement covers. The Accessibility Statement names each one.

Select all that apply.

Website For your website Mobile app For your app

Website URL

Why we ask

Enter the URL of the website this Accessibility Statement applies to. The URL appears in the statement so visitors know which website it covers.

Website name

Why we ask

Use the public name visitors recognize: your brand, organization, or site name. It appears throughout the Accessibility Statement.

App name

Why we ask

Enter the name of the app as users see it in the Apple App Store or Google Play Store. It appears throughout the Accessibility Statement.

Where do we send your Accessibility Statement?

We'll email you a link to choose a password for your account.

Email me product news and offers from TermsFeed. You can unsubscribe at any time.

By creating an account, you agree to our Terms of Use and confirm you have read our Privacy Policy.

Over 1.9 million customers have created a legal agreement with TermsFeed.

You already have an account with this email. Enter your password to add this Accessibility Statement to your account.

Password

Keep me logged in

Continue with Google

Wrong email? Use a different one Forgot your password?

Are you a business or running this yourself?

Why we ask

Pick business if a registered legal entity (an LLC, a corporation or a partnership) owns the website or app. Pick individual if you run it under your own name. A business adds its legal name and address, which appear in the policy.

I'm a business I'm an individual

Business name

Business address

Where are you based?

Why we ask

Your country decides which clauses the policy includes.

Country

State / Region

Who publishes this website or app?

Why we ask

Public sector bodies in the EU and the UK must publish an accessibility statement with set sections, under the Web Accessibility Directive or the UK accessibility regulations. Businesses that offer certain services to consumers in the EU, such as online shops, banking and e-books, must give accessibility information under the European Accessibility Act. Microenterprises that provide services are exempt from that act.

Pick one.

A business or organization A public sector body

Which standard do you measure your content against?

Why we ask

WCAG 2.2 level AA is the current version of the Web Content Accessibility Guidelines. EN 301 549 is the European standard the EU accessibility laws refer to; for web content, it requires WCAG 2.1 level AA. If you're not sure, choose WCAG 2.2 level AA.

Pick one.

WCAG 2.2 level AA WCAG 2.1 level AA EN 301 549

Does all of your content meet that standard?

Why we ask

Answer Yes only if every page and feature meets every requirement of the standard. Most websites have gaps. Listing them is what makes the statement useful to the people who run into them.

Yes No

How much of your content meets it?

Most of it Little of it

Content that doesn't meet the standard

Add each page, feature or type of content with a known problem: what the problem is, and what people can do instead or when you plan to fix it.

How did you check your content?

Why we ask

The statement says how it was prepared. Automated tools find only part of the problems, so most statements combine them with a manual check.

Select all that apply.

Self-assessment Audit by an external expert Automated testing tools Testing with people with disabilities

When did you last check it?

Why we ask

The statement shows this date. Check your content again and update the statement at least once a year, and after major changes.

Date of the check

Link to the audit report

Does your website or app include content from third parties?

Why we ask

For example embedded maps, videos, social media feeds, chat widgets or payment forms. You may not control how accessible they are, and the statement says so.

Yes No

Which third-party content?

Would fixing some content be a disproportionate burden?

Why we ask

A public sector body may leave content inaccessible when fixing it would be a disproportionate burden. It must first weigh the cost against the benefit for people with disabilities, and the statement must say why and what alternative it offers.

Yes No

Content and reason

Name the content, explain why fixing it would be a disproportionate burden, and say what accessible alternative you offer.

Do you publish any of this content?

Why we ask

The Web Accessibility Directive doesn't apply to these types of content. The statement lists the ones you choose as outside its scope. Skip this question if none apply.

Select all that apply.

Office documents published before 23 September 2018 Prerecorded audio and video published before 23 September 2020 Live audio and video Online maps Third-party content you don't fund, develop or control Archived content not updated since 23 September 2019

Which accessibility features does your website or app have?

Why we ask

The statement lists these so people know what to expect. Choose only what you checked.

Select all that apply.

Everything works with a keyboard Text alternatives for images Captions and transcripts Enough color contrast Text that can be enlarged to 200% Headings and landmarks A visible keyboard focus Labeled form fields A link to skip to the main content No flashing content

What do you do to keep it accessible?

Why we ask

The organizational measures behind the content. The statement lists the ones you choose. Skip this question if none apply.

Select all that apply.

An accessibility policy Training for staff Accessibility requirements when buying Regular checks A person responsible for accessibility Testing with people with disabilities

Which technologies does your content rely on?

Why we ask

Browsers and assistive technologies need these to work with your content. Most websites rely on HTML, CSS and JavaScript.

Select all that apply.

HTML CSS JavaScript WAI-ARIA SVG PDF

Which browsers and assistive technologies did you test with?

Why we ask

List the combinations you tested, so people know what to expect. Leave it empty if you didn't test specific ones.

How can people report an accessibility problem?

Why we ask

Select every way people can tell you about a barrier or ask for content in another format. The accessibility laws expect at least 1 channel, and email is the most common choice. The Accessibility Statement lists each one.

Select all that apply.

A contact page on your site

Phone

Postal mail

How soon do you reply to accessibility feedback?

Why we ask

The statement promises a reply within this time. Choose a time your team can keep.

Pick one.

2 business days 5 business days 10 business days 20 business days

Can people ask for content in another format?

Why we ask

For example large print, easy-to-read text, audio or braille. If you answer Yes, the statement tells people how to ask.

Yes No

Who handles complaints you don't resolve?

Why we ask

Leave this empty and the statement names the body your country's law sets, where there is one. Enter a body here if another one is competent, for example the arbitration board of a German state for a state authority.

Languages

We always generate English. Pick any other languages you want published, and we handle the translation.

English Spanish German French

✓

Check your inbox

We've sent an email to

Open the link in the email to choose a password and continue to your account.

Wrong address? Start over with a different one
Didn't get it? Send a new link