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.

Current issues
Issue WCAG criteria Description and plan Target date
No dark mode support Some users utilising high contrast mode might have a preference to view the site in a dark theme, as high contrast mode can have a negative impact on how certain elements are presented.

We plan to add dark mode support by March 2023. We will also ensure any site redesign includes a dark mode option.
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 March 2023. When we publish new content, we'll make sure our use of forms meets accessibility standards.
Live chat 1.4.3: Contrast (minimum) Some of our live chat software doesn't meet the minimum contrast ratio for visual presentation of text, so it may be difficult to read for users with moderately low vision.

We plan to review our live chat offering early in 2023, and will make sure any new provider 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.

Resolved issues
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.
Image without a text alternative 1.1.1: Non-text Content Some images don't have a text alternative, so the information in them isn't available to people using a screen reader.
Links in the same context with the same text alternative 2.4.4 Link Purpose (In Context) A very small number of pages have two or more links in the same context with the exact same link text — despite pointing to different pages. This can be problematic for assistive technology users — especially if they're unable to see the visual context.
Empty headings 2.4.6 Headings and Labels A small number of pages had empty headings, which may make content confusing for users who have disabilities that make reading slow and for people with limited short-term memory.
Role not inside the required context 5.2.6: Required Context Role A small number of pages have the wrong ARIA role applied to an element, which may cause confusion when using a screenreader.
Visible label and accessible name do not match 2.5.3: Label in Name Using two different names for a single page element can create a confusing user experience for assistive technology users.