How to meet the accessibility statement standard

If you're building a new product or website, start with identify issues.

If you have an existing product or website, or are reviewing your statement, go to keep your statement updated.

1. Identify issues

   You need to test your product and website and identify any issues.

   You can do this by:

   • testing you've carried out
   • getting feedback from users
   • carrying out third-party or internal accessibility audits
   • using automated testing tools

   You should follow the managing issues guidance for good practice on identifying, tracking, and managing accessibility issues in your product or website.

   Doing this also ensures you meet the report and manage accessibility issues standard.

2. Write your accessibility statement

   Statements contain legally-required wording so it's important you use the correct statement for your website.

   We have created templates to help you write your statement.

   Declare conformance and compliance

   You must declare the level of conformance you have achieved with the WCAG (Web Content Accessibility Guidelines) 2.2.

   We aim to meet Level AA as a minimum. Unless you have a reason to meet level AAA, we do not expect teams in DfE to meet this level.

   You will be breaking the law if you falsely declare your service to be fully compliant but have accessibility issues.

   Detail accessibility issues

   The statement must include details of all known WCAG criteria failures you have identified.

   You should also detail any disproportionate burden you are applying for any issues.

   Mitigation and resolution actions

   You must state clearly what actions you're taking to mitigate or resolve any accessibility issues. Include any expected timelines for resolution.

   This provides users with assurance that their concerns are being actively addressed and that improvements are being made to enhance their user experience.

   Contact information

   Provide contact information for users to report accessibility issues. This could be an email address or phone number, or a link to an online form.

3. Publish your statement

   Once you have written your statement, you must make it available to users before they start using your website or app.

   Publishing for a website

   You must link to the statement from the footer of every page on the website. The link text for the statement must say "Accessibility".

   Publishing for an app

   You must link to the statement from the app store listing description. The link text for the statement must say "Accessibility statement".

4. Keep your statement updated

   It's important to keep your statement up-to-date. You should review and update it whenever:

   • you carry out accessibility testing or have an audit
   • you identify new accessibility issues
   • you resolve existing accessibility issues
   • the legislation or mandatory content changes

5. Review your statement annually

   The accessibility statement must be reviewed and updated at least every 12 months. Even if no interim testing or audits happen.

   This regular review process shows ongoing compliance with accessibility standards. It also demonstrates a commitment to maintaining an accessible digital product for all users.

---

Information about this page

• Created: 15 July 2024
• Last reviewed: 15 July 2024
• Last updated: 15 July 2024
• Reason this page exists: This page exists to help people understand how to apply the DfE accessibility statement standard.
• Suggest a change or comment: Issue 30