Our accessibility roadmap shows how we plan to fix outstanding accessibility issues on this website and progress made with previous issues.
These issues are awaiting a resolution.
|Issue||Criteria||Description and plan||Target date|
|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.
We plan to add unique link text for all pages by December 2022. When we publish new content, we'll make sure our use of link text meets accessibility standards.
|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.
These issues have been resolved.
|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.|
|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.|
|Text is clipped when resized||1.4.4: Resize Text||Some pages contain text that will be be clipped if resized, so visitors with low vision may not be able to access information if text is clipped (cut off) when scaled up.|
|Page language has not been identified||3.1.1: Language of Page||A small number of pages are missing their language, so users may experience inconsistencies with screen reader pronunciations, visual characters and video captions.|
|Page has no title||2.4.2: Page Titled||A small number of pages are missing a title, so users with a screen reader may miss important context about a page.|
|Element IDs are not unique||4.1.1 Parsing||Some elements have the same ID value, so users with screen readers may not be able to correctly understand the content of the page.|