Accessibility statement | Accessibility statement | Visit Canterbury

Accessibility statement

This statement applies to content published on canterbury.co.uk.

Technical information about this website's accessibility

We are committed to making our websites accessible, in accordance with the Public Sector Bodies The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 No.952.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non accessible content

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

Images missing alt text

Some images are missing alternative text. People using a screen reader may not know what the images are. This fails WCAG 1.1.1 (non-text content) success criteria. We plan to fix this in 2021.

Heading levels are skipped

Some pages skip a heading level. This means people using a screen reader may not be able to navigate the content. This fails WCAG 2.4.6 (headings and labels) success criteria. We plan to fix this in 2021.

Link text used for different destinations

Some link text is used for multiple different destinations. This means that people using a screen reader may find it hard to know what these links are for. This fails WCAG 2.4.4 (link purpose in context) success criteria. We plan to fix this in 2021.

Content formatted with HTML

Some content has been formatted using HTML. This fails WCAG 1.3.1 (info and relationships) and 4.1.1 (parsing) success criteria. We plan to fix this in 2021.

Missing iFrame titles

Some iFrames are missing a title. People who use screen readers may not be able to understand the purpose of the content. This fails WCAG 1.3.1 (info and relationships) success criteria. We plan to fix this in 2021.

Low colour contrast

Some pages have very low colour contrast. This fails WCAG 1.4.3 (minimum contrast) success criteria. We plan to fix this in 2021.

Duplicate element IDs 

Some element IDs are not unique. This can make it harder for people who use screen readers to interact with the content.This fails WCAG 4.1.1 (parsing) success criteria. We plan to fix this in 2021.

Landmarks not named

Some pages contain two or more HTML5 or WAI-ARIA landmarks of the same type that haven’t been named. This can make it harder for people who use screen readers to interact with the content. This fails WCAG 1.3.1 (info and relationships) success criteria. We plan to fix this in 2021.

Content not within landmarks

Some content sits outside landmarks. This can make it harder for people who use screen readers to interact with the content. This fails WCAG 1.3.1 (info and relationships) success criteria. We plan to fix this in 2021.

Empty descriptions

Some pages have elements with no description. This means that people using a screen reader may not be able to understand their purpose. This fails WCAG  3.3.2 (labels or instructions) success criteria. We plan to fix this in 2021.

Tabbing sequence not logical

Some pages have content where the tabbing sequence isn't logical. This means that people using a screen reader may not be able to navigate the content. fails WCAG 1.3.2 (meaningful sequence) success criteria. We plan to fix this in 2021.

Noscript element

Some content has a <noscript> element. This fails WCAG 1.3.1 (info and relationships) success criteria. We plan to fix this in 2021.

Broken or missing WAI-ARIA references

Some WAI-ARIA references are broken or missing. This means that people using a screen reader may not be able to understand their purpose. This fails WCAG 1.3.1 (info and relationships) success criteria. We plan to fix this in 2021.

Missing fieldsets

Some checkboxes or radio buttons are not enclosed in a fieldset. This means that people using a screen reader may not be able to understand their purpose. This fails WCAG 4.1.2 (name, role, value) success criteria. We plan to fix this in 2021.

Multiple title or no title elements

Some pages have more than one title or no title at all. This means that people using a screen reader may find it hard to navigate the content. This fails WCAG 2.4.2 (page titled) success criteria. We plan to fix this in 2021.

PDFs and other documents

Many documents on the website are not accessible. They may have issues such as missing text alternatives and missing document structure. 

From 1 September 2020 we will not publish new documents that do not meet accessibility standards.

How we tested this website

This website was last tested on 7 September 2020. We use an independent accessibility service called Siteimprove as well as manual testing.

Contact us about accessibility

We are always looking for ways to improve the accessibility of this website. You can let us know about part of the website that is not accessible, or ask about other ways to access content using the link below.

Contact us about accessibility

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’).

If you are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).