This website is run by Uckington Parish Council. We want as many people as possible to be able to use this website. For example, that means you should be able to:
We know some parts of this website are not fully accessible:
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
We’ll consider your request and get back to you in 28 days.
If you cannot view the map on our ‘contact us’ page, call or email us uckingtonpc@gmail.com for directions.
We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: Parish Clerk using the contact details above.
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’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment.
We do not have offices, however you may visit us in person at one of our parish council meetings. If you contact us before your visit we may be able to arrange a British Sign Language (BSL) interpreter.
Find out how to contact us visit https://www.uckington-parish-council.org.uk/contact-us/
Uckington Parish Council is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
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.
The content listed below is non-accessible for the following reasons.
Some images 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).
We plan to add text alternatives for all images by September 2020. When we publish new content we’ll make sure our use of images meets accessibility standards.
There’s no way to skip the repeated content in the page header (for example, a ‘skip to main content’ option).
Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.
Our forms are built and hosted through third party software and ‘skinned’ to look like our website.
We’ve assessed the cost of fixing the issues with navigation and accessing information, and with interactive tools and transactions. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. We will make another assessment when the supplier contract is up for renewal, likely to be in six months.
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents. By September 2020, we plan to either fix these or replace them with accessible HTML pages.
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. For example, we do not plan to fix minutes of the meetings that were published prior to 23 September 2018.
Any new PDFs or Word documents we publish will meet accessibility standards.
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.
We plan to improve accessibility on this website over the next 12 months.
This statement was prepared on 7 September 2020. It was last reviewed on 7 September 2020.
This website was last tested on 3rd September 2020. The test was carried out by a member of Uckington Parish Council.
We used this approach to deciding on a sample of pages to test. Some pages were expanded. PDF links were checked and some pages were run through WAVE tool. A random selection of pages were tested.