Known issues
WCAG A 1.3.1 Ensure form controls have labels
We have some navigation elements which are not labelled. This issue has been referred to our third party design agency. We aim to have resolved this by the end of Q1 2021.
WCAG A 1.3.1 - Ensure dialogs have labels
All dialogs (sometimes knows as 'pop up windows') should declare an accessible label that can be read out. We are working with the design agency to resolve this issue on two pages. We expect to have a solution in place by the end of Q1 2021.
WCAG A 1.3.1 Ensure every page contains a Heading
Every page should have a clearly defined heading – we are working with the third-party developer to remedy this. We aim to have resolved this by the end of Q1 2021.
WCAG A 1.4.1 - Ensure links are distinguished by more than just colour
WCAG AA 2.4.7 - Avoid linking to anchors which do not exist
There are a number of corrections to be implemented to address these issues. We aim to have resolved this by the end of Q1 2021.
WCAG A 2.4.4 - Avoid using the same link text for different destinations
In some cases we have images embedded in slideshow galleries that have the same title, in nearly all cases this is because they are multiple images of the same thing. Because these images are linked from thumbnails to larger versions they register to assistive technologies as links with duplicate titles. We plan to review these and edit the text where possible to minimise any potential confusion.
WCAG A 2.4.1 Allow users to quickly skip to content
Webpages should provide a way to skip to the main content of the page. This issue has been referred to our third party design agency. We aim to have resolved this by the end of Q1 2021.
WCAG A 4.1.2 Ensure links can be used by screen readers
Links must be defined in a specific way to be accessed by screen readers, which are used by blind and the partially-sighted. This issue has been referred to our third party design agency. We aim to have resolved this by the end of Q1 2021.
WCAG A 4.1.1 Fix duplicate IDs
All ID attributes on a page must be unique, or accessibility technology used by the page can stop working. This issue has been referred to our third party design agency. We aim to have resolved this by the end of Q1 2021.
PDF Documents
WCAG A 1.3.1 Fix untagged PDFs (2 PDFs)
WCAG A 1.3.1 Specify headings for every PDF (2 PDFs)
WCAG A 3.1.1 Ensure PDFs specify a default language (2 PDFs)
WCAG A 2.4.2 Define a title for all PDFs (2 PDFs)
Back to the Website Accessibility Statement
Updated 16 November 2020