All web delivery platforms must adhere to the WCAG 2.1 AA standard as a minimum to comply with the 2018 Digital accessibility legislation. This includes an accessibility statement, which also has it's own requirements.
It's not always possible to be compliant with the standards for a range of reasons but in those cases the accessibility statement must declare this and the reason for non compliance.
Clear signposting to alternatives must also be included.
There are four main principles in the WCAG standard:
- Perceivable: Information and user interface components must be presentable to users in ways they can perceive. Examples: alt text for image, contrast ratios, audio descriptions and captioning for video
- Operable: User interface components and navigation must be operable. Examples Keyboard accessible, functionality beyond keyboard
- Understandable: Information and the operation of user interface must be understandable. Examples: Language, No jargon or abbreviations, Input assistance in the form of error identification, labels or instructions when content requires input.
- Robust: Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. Examples: Parsing (complete tags, names, roles and values)
Accessibility Statements
All digital platforms need to publish an accessibility statement from:
- 23 September 2019 for new websites created from 23 September 2018
- 23 September 2020 for existing websites
- 23 June 2021 for mobile apps
For websites, the statement should be published as an html page, linked to from a prominent place like the website footer.
For mobile apps, make the statement available in an accessible format where users can download the app.
All central systems will have accessibility statements published to comply with the legislation to meet the above deadlines.
Other system owners are responsiblle for their own accessibility statements
The accessibility statement must say:
- which parts of your service do not meet accessibility standards and why
- how people with access needs can get alternatives to content that’s not accessible
- who to contact to report accessibility problems - and a link (this will be standard for UoS – (to be confirmed) to the website that they can use if they’re not happy with your response