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 |
|---|---|---|---|
| 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.
We plan to assign all table cells by July 2023. When we publish new content, we'll make sure our use of tables meets accessibility standards. |
|
| Forms and autocomplete | 1.3.5: Identify Input Purpose |
Some forms don't have autofill enabled, so the label purpose may not immediately be known by people with cognitive disabilities.
We plan to add autofill for all forms by October 2023. When we publish new content, we'll make sure our use of forms meets accessibility standards. |
|
| 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. |
Resolved issues
These issues have been resolved in the past six months.
| Issue | WCAG criteria | Description | Resolved |
|---|---|---|---|
| Inadequate colour contrast | 1.4.3 Contrast (minimum) | Our search component has inadequate colour contrast in certain conditions, including placeholder text, focused link text and autocomplete results dropdown. | |
| Interactive control with focusable child element | 4.1.2 Name, Role, Value | Interactive controls like buttons and links should not have child elements which are focusable. This is because the child elements are not announced by screen readers, but they still appear in the tab order, making it harder to navigate. | |
| Images of text | 1.4.5 Images of Text | Images of text cause problems for users who need to adjust how visual content like font size, spacing or colours are displayed. | |
| Link without a text alternative | 2.4.4: Link Purpose in Context | Some links don't have unique text, so users might not know the difference between links with different purposes or destinations. |