How accessible our website is
We're aware of the following:
- images in historic news stories may not have alternative text
- PDF or MS Word documents on our website may not be fully accessible to screen reader users
- online form issues, which we outline later in this statement
PDF and MS Word docs
Many of our older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader.
We'll improve these as much as possible so they are accessible. We'll also replace as many PDFs as possible with accessible HTML pages.
If you struggle with accessibility on any of these documents, please contact us.
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018, if they’re not essential to providing our services.
Any new PDFs or MS Word documents we publish on our website will meet accessibility standards.
Some of these issues can be fixed by our developers and we're working to resolve them as soon as possible. For other issues, we're working with our supplier.
These following in our forms may not meet the following WCAG 2.1 AA criteria:
- Non-text content – button’s missing descriptive value or text label (1.1.1)
- Info and relationships – page landmarks not identified (1.1.3)
- Info and relationships – caption attribute incorrectly used within (1.3.1)
- Identify input purpose - autocomplete attribute not present (1.3.5)
- Low non-text contrast (1.4.11)
- No keyboard trap - user unable to navigate full page with keyboard (2.1.1 and 2.1.2)
- Timing adjustable – no mechanism present to turn-off or extend page time-out (2.2.1)
- Focus visible - focus does not remain consistently visible (2.4.7)
- On input – tab focus returns to top of page when radio button is selected (3.2.2)
- Loading overlays should be labelled with aria-live (4.1.3)
The affected forms will start with one of these addresses: