Council website

Compliance status

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

Unless planned resolution target is specifically stated against an item, we are working routinely with content creators and application suppliers to address all issues and to fully comply with WCAG 2.1 AA as soon as possible.

Non-accessible content

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

Non-compliance with the accessibility regulations by site and WCAG 2.1 success criterium

WCAG 1.1.1  Non-text content

Some pages have missing alt text on images.

WCAG 1.3.1 Info and relationships

Some pages are missing their level 1 heading.

Visual presentation (using <b> for emphasis) has been used on some pages.

Some pages have missing level 1 headings

Some pages use duplicate ids. Duplicate ids can make it difficult for assistive technologies to identify parts of the page successfully.

Some pages have labels points to non-existent ids.

Some news pages use headings as styles rather than document hierarchy.

It is not possible to view the heading one on some pages. The heading one exists but is hidden by CSS.

Some PDF documents do not provide information on the structure or the roles of components to help you navigate, such as headings.

WCAG 1.3.2  Meaningful sequence

The reading order of some PDF documents is not correct, making it difficult to access these using a screen reader.

WCAG 1.3.3 Sensory characteristics

The bin day calendars rely on visual perception of shape and colour to understand your bin day.

WCAG 1.4.12 Text spacing

The chat bot does not let you adjust text spacing or size.

WCAG 1.4.3 - Contrast, minimum

The placeholder text in the chat bot does not have sufficient contrast.

Some PDFs lack sufficient contrast, especially in charts and graphs.

WCAG 1.4.10 Reflow

At 400% the chat bot window is obscured by the cookie panel.

Above 300%, close chat bot Yes/No buttons cannot be seen.

WCAG 1.4.11 Non-text contrast

Some PDF graphs and charts that rely on colour to provide information do not provide enough contrast.

WCAG 2.4.2 Page titles

Some pages have more than one title (automated test)

Some page search results have ambiguous titles, such as 'Records starting with A'.

WCAG 2.4.4 Link purpose, in context

It is not possible to determine the purpose of some download icons on the Shared repairs page using a screen reader.

WCAG 2.4.6 Headings and labels

The contact telephone numbers page contains some headings with no text.

WCAG 2.4.7 Focus visible

The search icon in the main page header is not easy to see it has been selected when navigating using the keyboard.

WCAG 3.1.1 Language of page

Language of page not set (automated test).

WCAG 3.3.2  Labels or instructions

Some form input fields contain no labels.

WCAG 4.1.1 Parsing

Many pages don’t confirm to strict HTML specifications. This reduces compatibility with some assistive technologies.

WCAG 4.1.2 Name, role, value

It is not possible to determine the purpose of some download icons on the Shared repairs page using a screen reader.