A new standard is being introduced to assure the correct legal implementation of accessibility statements.

View the accessibility statement standard.

This content will be soon moving to a standalone manual. If you want to contribute to the content, contact the DesignOps team.

Accessibility assurance should not be left until carrying out an evaluation. Manual and automated accessibility testing, testing with users with access needs and design reviews should be done throughout the service delivery lifecycle.

Estimate how many people using your website might be disabled. This will help you consider the types of people who may be using your service and who you should be testing with.

We are legally required to ensure all content available through a browser (websites, services, and apps) are accessible, regardless of whether they are for staff internal use, or external users.

When we talk about accessibility we must not think of it as just for disabled people, it also means supporting everyone with temporary, situational and permanent access needs who may be using assisitve technology.

In the UK, one in five people have a disability and around 15% of people are thought to be neurodivergent.

Contribute to this page on GitHub

Changes to this page
  1. Linking to correct issue number. See GitHub issue #56
    18 July 2023