Accessibility Statement (sample)

The following sample Accessibility statement was sourced from Gov.uk

Guidance Sample accessibility statement (for a fictional public sector website)
Updated 30 September 2024

[Note: you can have a single accessibility statement that covers multiple domains, or a separate statement for each domain or subdomain. As long as the user can access relevant accessibility information easily from any page on your website.

For mobile apps also include the application’s version information and publication date.

This wording is legally required and must not be changed.]

This accessibility statement applies to [scope of statement, for example, website or domain to which the statement applies].

[Note: use this section to make a brief, general statement about what the website allows disabled users to do. Base it on the evaluation covered in detail in the ‘Technical information about this website’s accessibility’ section.

It must be specific to your own website. If you’re not confident that something is accurate, leave it out. If you’re not confident enough to say anything specific here, leave this section out completely.]

This website is run by [name of organisation]. We want as many people as possible to be able to use this website. For example, that means you should be able to:

• change colours, contrast levels and fonts using browser or device settings
• zoom in up to 400% without the text spilling off the screen
• navigate most of the website using a keyboard or speech recognition software
• listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

[Note: use this section to provide a summary of accessibility issues that a disabled user can act on – for example, avoid a particular section of the website, or request an alternative version rather than waste time trying to make it work with their assistive technology. Try to list in order of most impact to least impact.]

We know some parts of this website are not fully accessible:

• you cannot modify the line height or spacing of text
• most older PDF documents are not fully accessible to screen reader software
• live video streams do not have captions
• you cannot skip to the main content when using a screen reader
• there’s a limit to how far you can magnify the map on our ‘contact us’ page

Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: [provide both details of how to report these issues to your organisation, and contact details for the unit or person responsible for dealing with these reports].

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

• email [email address]
• call [phone number]
• [add any other contact details]

We’ll consider your request and get back to you in [number] days.

If you cannot view the map on our ‘contact us’ page, call or email us [add link to contact details page] for directions.

Enforcement procedure

[Note: this wording is legally required and must not be changed.]

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

[Note: if your organisation is based in Northern Ireland, refer users who want to complain to the Equality Commission for Northern Ireland (ECNI) instead of the EASS and EHRC.

You must link to either the EASS or ECNI websites.]

Technical information about this website’s accessibility

[Note: this wording is legally required and must not be changed.]

[Name of organisation] is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.

[Note: say that the website is fully compliant if the website meets the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard in full.

Say that it’s partially compliant if it meets most requirements of the WCAG 2.2 AA standard.

If it does not meet most requirements of the WCAG 2.2 AA standard, say that it’s not compliant.

If your website is either partially compliant or not compliant with the WCAG 2.2 AA standard, you’ll need to explain why. This will be due to one or both of the following:

• non-compliances – this means the content in question is in scope of the regulations, but there’s an accessibility problem with it
• an exemption – this means the inaccessible content is out of scope of the regulations, or it’d be a disproportionate burden for you to make it accessible

There’s a legally required way of expressing the compliance status of your website, so do not change it. Choose one of the options below, for example (a), (b) or (c), and delete those not applicable.

[Select (a) only if all requirements of the technical specification are fully met without exceptions for WCAG 2.2.]

(a) This website is fully compliant with the Web Content Accessibility Guidelines version 2.2 AA standard.

[Select (b) if most requirements of the technical specification are met, but with some exceptions. This means not yet fully compliant and that the necessary measures are to be taken in order to reach full compliance.]

(b) This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to [insert one of the following: ‘the non-compliances’, ‘the exemptions’ or ‘the non-compliances and exemptions’] listed below.

[Select (c) if most requirements of the technical specification are not met.]

(c) This website is not compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. The [insert one of the following: ‘non-compliances’, ‘exemptions’ or ‘non-compliances and exemptions’] are listed below.

[Note: delete the options that do not apply.]

Below is a table insert that can be added anywhere on your statement which provides the WCAG checks which are identified by Phew to address from our monthly monitoring with estimated dates of resolution