Non-accessible content

The content listed below is non-accessible for the following reasons:

Non-compliance with the accessibility regulations

Navigable

Ensure controls change appearance when they are selected - Controls on a page, such as links, buttons and fields may not show when they have been selected by the keyboard.  This is not compliant with WCAG 2.1 success criterion 2.4.7.  We are working with our supplier to fix this by end of December 20.

Avoid linking to anchors that do not exist- To help navigation, some pages have a ‘Back to the top’ link or links at the top of the page that takes you to a section.  Some of these may not work.  This is not compliant with WCAG 2.1 success criterion 2.4.1.  We will correct these over time as we review each page.

Ensure links explain their purpose - Some pages may have links that do not describe where they take you e.g. ‘click here’ or ‘link to page’, this is not helpful for users with screen readers.  This is not compliant WCAG 2.1 success criterion 2.4.4.  We will correct these over time as we review each page.

Avoid using the same link text for different destination - We have a few pages where the same link name has been used but may link to a different location.  This may be confusing for users using a screen reader.  This is not compliant with WCAG 2.1 success criterion 2.4.4.  We will correct these over time as we review each page.

Specify a title for all inline frames - Where we have videos embedded into a webpage, a title has not been applied which may affect users of screen readers.  This fails WCAG 2.1 success criterion 2.4.1.  We are working with our suppliers to fix this by end of December 20.

Ensure pink-to-zoom is enabled - There are 4 pages that you may not be able to magnify on a smaller device, such s a mobile or tablet.  This is not compliant with WCAG 2.1 success criterion 1.4.1.  We are working with our supplier to fix this by end of December 2020.

Back to top

Mobile

Ensure pages don’t scroll in two dimensions on small screens - We have a few pages that may require a user to scroll vertically and/or horizontally to view it when it should resize automatically.  This does not include the use of maps. This is not compliant WCAG 2.1 success criterion 1.4.10.  We are working with our supplier to fix this by December 20.

Back to top

Lists

Allow users to quickly skip to content - We have a few pages that do not contain the correct coding to enable users who use assistive technology to skip to the main content.  This is not compliant WCAG 2.1 success criterion 2.4.1.  We are working with our supplier to fix this by December 20.

Mark navigation as lists - To help users who use assistive technology, we need to review pages to ensure any listed items have bullet points or are numbered to help them navigate the page.  This is not complaint WCAG 2.1 success criterion 1.3.1.  We will correct these over time as we review each page.

Back to top

Legibility

Ensure links are distinguished by more than just colour - Currently when we have a link on a page, we only use colour to as a visual aid, we need to also underline them to assist users how may have a visual impairment.  This is not compliant WCAG 2.1 success criterion 1.4.1.  We are working with our supplier to fix this by December 20.

Back to top

Headings

Ensure every page contains a heading - One of our templates does not have a defined heading which may be confusing for users of assistive technology.  This is not compliant with WCAG 2.1 success criterion 1.3.1.  We are working with our supplier to fix this by December 20.

Add headers to tables / Add a scope to table headings - Where we have tables on a page, users using assistive technology, or a keyboard may not be able to navigate them correctly and understand the content.  This is not compliant with WCAG 2.1 success criterion 1.3.1.  We are working with our supplier to fix this by December 20.

Ensure headings include text - We have some pages that have a blank heading which may confuse a user using assistive technology.  This is not compliant with WCAG 2.1 success criterion 1.3.1.  We will correct these over time as we review each page.

Back to top

Alternative Text

Combine adjacent links with the same destination

Specify alternative text for all media - The template used for our directory pages include images which are decorative but do not have alternative text which may confuse users using assistive technology. Some embedded video may also be missing alternative text.  This is not compliant WCAG 2.1 success criterion 1.1.1.  We are working with our supplier to fix this by December 20.

Back to top

Links

Ensure links can be used for screen readers - We use anchors on some of our pages to help user navigate the page quickly.  A code correction needs to be made to ensure users using assistive technology can also use these links.  This is not compliant WCAG 2.1 success criterion 4.1.2.  We are working with our supplier to fix this by December 20.

Back to top

Predictability

Add a submit button to all forms - One of our templates has a search function that asked users to click on enter once search word has been entered.  This needs to have a submit button.  This is not compliant WCAG 2.1 success criterion 3.2.2.  We are working with our supplier to fix this by December 20.

Back to top

Forms

Wrap items with the same name inside a fieldset - Our feedback form at the end of each page requires a code change to ensure users using assistive technology can identify the radio buttons correctly.  This is not compliant WCAG 2.1 success criterion 1.3.1.  We are working with our supplier to fix this by December 20.

Identify the purpose of fields programmatically - Currently our feedback form at the end of each page does not allow you to automatically complete of fields like Name or Email Address.  This is not compliant WCAG 2.1 success criterion 1.3.5.  We are working with our supplier to fix by December 20.

Add a legend for all fieldsets - For simple forms embedded into some of our pages, we need to ensure users using assisted technology can hear the correct information in the correct order.  This is not compliant WCAG 2.1 success criterion 1.3.1.  We are working with our supplier to fix this by December 20.

Ensure form controls have labels - Some of our forms on the website may not have the correct text labels to help users using assistive technology to understand the layout of the form.  This is not compliant with WCAG 2.1 success criterion 1.3.1.  We are working with our supplier to fix this by December 20.

Specify the language of every page - We have a few forms on our website that has no specified a language which could affect a user when using assisted technology.  This is not compliant with WCAG 2.1 success criterion 3.1.1.  We are working with our supplier to fix this by December 20.

Back to top

Colour Contrast

Ensure text has sufficient contrast - When presenting text, it has to meet a contrast ratio to ensure users with a visual impairment can still read it.  There are some areas of our website where we are not meeting this contrast ratio.  This is not compliant WCAG 2.1 success criterion 1.4.3.  We are working with our supplier to fix this by December 20.

Back to top

Code Validation

Fix duplicate IDs

A field on the footer of our website has the same name as a field on some of our pages, this could confuse someone using assisted technology to know which field they need.  This is not compliant with WCAG 2.1 success criterion 4.1.1.  We are working with our supplier to fix this by December 20.

Back to top

PDFs

There are several errors that need to be corrected to enable a user using assisted technology to be able to use PDFs.  Those errors along with where it is not compliant are:

  • Ensure PDFs are machine readable – WCAG 2.1 success criterion 1.1.1
  • Ensure PDF headings follow a logical order – WCAG 2.1 success criterion 1.3.1
  • Specify headings for every PDF – WCAG 2.1 success criterion 1.3.1
  • Fix untagged PDFs – WCAG 2.1 success criterion 1.3.1
  • Ensure the first heading in a PDF is a H1 – WCAG success criterion 1.3.1
  • Define a title for all PDFs – WCAG success criterion 2.4.2
  • Ensure PDFs specify a default language – WCAG success criterion 3.1.1
  • Improve weak PDF titles – WCAG success criterion 2.4.2
  • Ensure long PDFs use bookmarks to aid navigation – WCAG success criterion 2.4.5

The accessibility regulations don’t require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.

Due to the high volume and complexity/length of some of our PDFs, we are working towards getting PDFs accessible by end December 2020.

Back to top

Last Updated: 10 September 2020