The content listed below is non-accessible for the following reasons.
Issues with images
- Some images do not have a meaningful 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 meaningful text alternative. Purely decorative images will have blank alt text.
- 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 to include the image text.
Issues with links and keyboard operability
- 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.
- The colour of the link text does not meet the minimum contrast requirements against the background. This can limit the site’s accessibility for people with low vision, poor eyesight or colour blindness. This fails the WCAG 2.1 success criterion on 1.4.3.
- Links are not visually evident without colour vision. This can limit the site’s accessibility for people who cannot perceive colour differences. This fails the WCAG 2.1 success criterion on 1.4.1.
All links will be reviewed and fixed by September 2021.
- 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.
- Some menus, links, buttons, and other controls cannot be operated using the keyboard alone, which can cause problems for people who are blind, have low vision and/or hand tremors. This fails WCAG 2.1 success criterion 2.1.1.
- More than one element uses the same access key on a page. This fails WCAG 2.1 success criterion 1.3.1
- Some select elements missing an associated label, making them less accessible to people using assistive technology. This fails the WCAG 2.1 success criterion 1.3.1.
All keyboard operability issues will be reviewed and fixed by September 2021.
- Not all ID attribute values are unique on some web pages, which can cause problems for assistive technologies when they are trying to interact with content. This fails WCAG 2.1 success criterion 4.1.1.
All content parsing issues will be reviewed and fixed by September 2021.
Issues with language and content
- When using mobile or tablet devices, it may not be possible to dismiss or interact with some extra content (i.e. pop-up images) without moving focus, losing functionality, or it disappearing. This may cause problems for disabled or sight impaired users as pop-up content may be accidentally triggered or pop-up content may not stay on the screen. This fails WCAG 2.1 success criterion 1.4.13.
We will implement fixes for these issues by September 2021.
Issues with 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
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
We will provide an accessible alternative to any third-party content that isn’t compliant.
Third party platforms
We often create content which is hosted on third party platforms. This includes:
- content we create for social media
- video which we host on YouTube or Vimeo
We are responsible for ensuring the content we supply meets accessibility requirements; however, we are not responsible for the accessibility of the platform itself.
Any new PDFs or Word documents we publish will meet accessibility standards.
Video and audio content
This site does not have pre-recorded audio and video content.
This site does not contain archived content.