Accessibility roadmap
Our accessibility roadmap shows how we plan to fix outstanding accessibility issues on this website and progress made with previous issues.
Current issues
These issues are awaiting a resolution.
| Issue | WCAG criteria | Description and plan | Target date |
|---|---|---|---|
| Image without a text alternative (PDF) | 1.1.1 Non-text Content |
Some PDF images don't have a text alternative, so the information in them isn't available to people using a screen reader.
We plan to add text support for images to affected PDFs by December 2023. We will also ensure new PDFs after this date contain alternative image text. |
|
| Tables not tagged (PDF) | 1.3.1 Info and Relationships |
Some PDF documents contain tables without appropriate tagging, such as row and column titles. This means users who rely on assistive technologies like screen readers may not be able to understand the correct information.
We plan to add tagging support for tables in affected PDFs by December 2023. We will also ensure new PDFs after this date contain appropriate table tagging. |
Recently resolved issues
These issues have been resolved in the past six months.
| Issue | WCAG criteria | Description | Resolved |
|---|---|---|---|
| Empty headings | 2.4.6 Headings and Labels | A small number of pages have empty headings, which may make content confusing for users who have disabilities that make reading slow and for people with limited short-term memory. | |
| Container element is empty | Some roles are designed to contain other roles. This element has this type of role, but it doesn't contain any required-owned elements, which may be confusing for users with screen readers. | ||
| Table cell missing context | 1.3.1 Info and Relationships | Some table cells don't have an assigned header cell, so the content may lack context for somebody using a screen reader. | |
| Colour contrast does not meet minimum requirement | 1.4.3: Contrast (Minimum) | On a small number of pages, the contrast between foreground and background colors was not sufficient. This could have caused readability issues for users who are colour blind or have low vision. |