Meet the requirements of equality and accessibility regulations
All digital or technology activity must be in full compliance with the Public Sector Bodies Accessibility Regulations 2018 and the Equality Act 2010
To meet this commitment as part of Digital and Data function’s strategic commitments your plans must show how you will comply with equality and accessibility regulations.
Public sector bodies accessibility regulations
Accessibility means making sure your services and content can be used and understood by the widest possible audience.
The accessibility regulations came into force for public sector bodies on 23 September 2018. They say you must make your website or mobile app more accessible by making it ‘perceivable, operable, understandable and robust’.
Your service or mobile app must:
-
meet the international WCAG 2.2 AA accessibility standard
-
publish an accessibility statement that explains the accessibility of your service or mobile app
Intranet and extranet websites are also covered by the accessibility regulations. These are internal websites which disabled employees may use, working in or with the public sector.
Further information on understanding accessibility requirements for public sector bodies.
The Equality Act 2010
In 2010, the Equality Act replaced previous anti-discrimination laws with a single act. Making the law easier to understand and strengthening protection in some situations, it legally protects people from discrimination in the workplace and in wider society. It sets out the different ways in which it’s unlawful to treat someone.
When building IT infrastructure and digital services make sure you consider accessibility from the start of your project or programme. Do research with users who have a range of abilities and decide on your accessibility requirements
You must meet the guidance on the WCAG 2.2 AA standard. You should apply this standard throughout the lifecycle of your service in order to comply with this strategic commitment.
You might want to consider:
- using GOV.UK design system to help your service meet WCAG 2.2
- paying to get your product audited against WCAG 2.2 by an accessibility expert
All digital services should undertake an accessibility audit upon entering Private Beta and again upon entering Public Beta.
If there are failings against the WCAG 2.2 AA standard in Private Beta, you should address these by Public Beta.
If you’re going through the spend control process you must explain how you’re meeting this commitment if your spend request has been rated high on the Risk and Importance Framework or has an assurance rating of control.
Answering ‘no’ will not lead to an automatic rejection and you will need to explain why your spend cannot align to the commitment.