Accessibility Known Issues
The content listed below is non-accessible for the following reasons.
Issue with video, audio and images
- Not all video content has a transcript, making the content inaccessible to users who cannot see. This fails the WCAG 2.1 success criterion 1.2.1.
- Not all video content has captions that are synchronised to the audio content of the video, making them inaccessible to people who cannot hear. This fails the WCAG 2.1 success criterion 1.2.2.
- Not all video content has audio descriptions of important visual information that doesn’t have audio, making this inaccessible to people who can’t see. This fails the WCAG 2.1 success criterion 1.2.5.
All video content created and published after 23 September 2020 will have the appropriate transcript, and/or captions /audio descriptions of important visual information.
- Not all audio only files have a transcript, making the content inaccessible to website users who cannot hear. This fails the WCAG 2.1 success criterion 1.2.1.
All audio only files created and published after 23 September 2020 will have transcripts.
- Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1.
By September 2021, all images will have text alternative. Purely decorative images will have blank alt text and infographics and charts will have a link to a full description of the content.
- Some images include text as part of the image, so people using a screen reader cannot access the information. This fails the WCAG 2.1 success criterion 1.4.5.
By September 2021, all images containing text will have a suitable text alternative which will include the image text.
Issue with navigation, structure, links and keyboard operability
- Tables do not have a table header row, making them less accessible to people using assistive technology. This fails the WCAG 2.1 success criterion 1.3.1.
We are working with our developers to implement fixes for this navigation issue over the coming months.
- Not all headings are hierarchical, making the site more difficult for users of assistive technology such as screen readers to access. This fails the WCAG 2.1 success criterion 1.3.1.
We are working with our developers to implement fixes for these structural issues over the coming months.
- Headings have on occasion been used to highlight information rather than for headings, making the site more difficult for users of assistive technology to use. This fails the WCAG 2.1 success criteria 1.3.1 and 2.4.6.
All content published after 23 September 2018 will be viewed and amended by September 2021.
- Some links do not use text that is meaningful out of context, which can result in users of screen readers not being able to understand the link without reading the surrounding text and users of speech recognition software being less able to target links accurately using voice commands. This fails the WCAG 2.1 success criterion 2.4.4.
All links will be reviewed and fixed by September 2021.
- Some links to external sites open in a new browser window and some open in the same browser window making the site behaviour unpredictable, which can result in the site being less accessible for people with some cognitive disabilities and people who use screen readers. This fails the WCAG 2.1 success criterion 3.2.2.
Our developers are working on implementing both visual and code signals for users that will make it explicit if a link is going to open in a new window or tab.
- Carousels do not have obvious controls for users to stop the auto-rotate, which can cause people with cognitive disability that affect focus and concentration to be distracted making the site less accessible. This fails the WCAG 2.1 success criterion 2.2.2.
We are working with our developers to implement fixes for these keyboard operability issues over the coming months.
Issues with contrast, use of colour and visual characteristics
- Some elements have low contrast levels (e.g. image copyright), which can result in text being difficult to read, especially for people with low vision, poor eyesight or colour blindness. This fails the WCAG 2.1 success criteria 1.4.3.
We are working with our developers to implement a fix for this issue over the coming months.
Issues with content, documents & content management system (CMS)
- The line height, spacing between paragraphs and letter and word spacing cannot be changed without loss of content or functionality. This means that people with low vision, dyslexia or cognitive disabilities may struggle to read the text, or lose content or functionality. This fails WCAG 2.1 success criterion 1.4.12.
We are working with our developers to implement fixes for these issues over the coming months.
- Some of the documents (including Word, PowerPoint and PDF) on this site do not meet accessibility standards, which could result in them not being fully accessible to users of screen readers.
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
PDFs, PowerPoints, or Word documents published on or after 23 September 2018 will be converted to HTML pages, or replaced with accessible versions by September 2021. Any new PDF, PowerPoint, or Word documents we publish will meet accessibility standards.
Content management system (CMS)
- The CMS code is being checked to ensure that it meets the robust accessibility criteria 4.1.1, 4.1.2 & 4.1.3.
This will be done as part of an accessibility upgrade of the Haiku Content Management System to be completed in Autumn 2020.
We do not consider any of the accessibility issues to be a disproportionate burden and aim to make the site fully compliant by September 2021.
Content that's not within the scope of the accessibility regulations
Third party content
Our site includes third party content and functionality. This may direct you to a related service, link to another site or supporting documentation. We are not responsible for the accessibility of third-party content or to other sites we link to.
- YouTube videos
- Sound Cloud audio files
- Google maps
Third party platforms
We sometimes create content hosted on third party platforms. This includes:
- content we create for social media
- video which we host on YouTube, SoundCloud
We are responsible for ensuring the content we supply meets accessibility requirements; however, we are not responsible for the accessibility of the platform itself.
This site has a number of documents which were published before September 2018. These aren’t essential to the service we provide and won’t be replaced. If you experience any difficulties accessing these documents, please email email@example.com.
Video and audio content
This site has pre-recorded audio and video content that was published before 23 September 2020, which is exempt from the accessibility regulations.
This site contains historical content, which is exempt from the accessibility regulations. The historical content is external news stories published prior to 23 September 2018 and which have not been updated since.