Website accessibility statement
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Some of our PDF files that have been published since September 2018 are not accessible. This fails WCAG 2.1 success criterion 1.3.1 (info and relationships) and WCAG 1.1.1 (non-text content). We are working on making these accessible as soon as possible.
Our sub-domain sites for planning applications, payments and council meetings have various accessibility issues. We are working with the suppliers of each of these systems to make these accessible as soon as possible.
Content that’s not within the scope of the accessibility regulations
Some embedded Google Maps have been flagged as images that 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 (non-text content). Unfortunately, while we have investigated possible fixes, as this is a third party product we have no control over this.
PDFs and other documents
Many of our older PDFs and Word documents do not meet accessibility standards - for example, they may not be structured so they’re accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (name, role value).
Some of our PDFs and Word documents are essential to providing our services. For example, we have files with information on how users can access our services, or forms to be completed. We are working on making these accessible (either by fixing the PDFs or replacing them with accessible HTML pages) as soon as possible.
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. However, we do still plan to fix these over time.
Any new PDFs or Word documents we publish will meet accessibility standards.
Third party content
Some PDFs hosted on our website are owned by third parties and some do not meet accessibility standards.
The accessibility regulations do not require us to fix content that is owned by third parties.