This accessibility statement applies to the Lawley and Overdale Parish Council (LOPC) website, on the https://lawleyoverdale-pc.gov.uk/ domain.
This website is run by Lawley and Overdale 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:
- change colours, contrast levels and fonts
- zoom in up to 300% without the text spilling off the screen
- navigate most of the website using just a keyboard
- navigate most of the website using speech recognition software
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made the website text as simple as possible to understand.
AbilityNet has advice on making your device easier to use if you have a disability.
Things that work well
We have made efforts to make this website as accessible as we can.
- Alternative text has been supplied with all non-decorative images uploaded since November 2019
- The website design is responsive, enabling you to zoom with reflow up to 300%
- We have a ‘skip to content’ tab function
- Content has a contrast ratio of 15.36:1, and is viewable when the contrast is reversed
- The website can be navigated with a keyboard
- On content added since April 2020, links are distinct from each other, and their purpose can be identified from the text
- Headings are structured logically
- Articles published since April 2020 strive to use simple language and avoid jargon
- All non-live video content since February 2021 now has closed captioning and/or a transcript
- The new Full Council meeting minutes template, used since July 2021, adheres to accessibility standards
How accessible this website is
We know some parts of this website are not fully accessible:
- Some images uploaded before November 2019 do not have text alternatives (‘alt-text’)
- Some older PDF documents are not fully accessible to screen reader software
- On some pages created before April 2020, the purpose of links cannot be determined from the link text alone
- Some of our online forms are difficult to navigate using just a keyboard
Feedback and contact information
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
- email email@example.com
- call 01952 507865
We’ll consider your request and get back to you in five working days.
If you cannot view the map on our ‘contact us’ page, call or email us for directions.
Reporting accessibility problems with this website
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: Sharon George, firstname.lastname@example.org.
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).
Contacting us by phone or visiting us in person
You can call us on 01952 507865. Our office is located at Leonard Smith House, Unit 2, West Centre Way, Lawley, Telford, TF3 5HT.
Technical information about this website’s accessibility
Lawley and Overdale 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.
Non-compliance with the accessibility regulations
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 non-decorative images by September 2022. When we publish new content, we will make sure our use of images meets accessibility standards.
Some images contain text, so people with dyslexia or using a screen reader will not be able to read the information. This does not meet WCAG success criterion 1.4.5 (Images of Text). We plan to resolve this issue by September 2022. When we publish new content, we will make sure our use of images meets accessibility standards.
On some pages, the same link text is used for different link destinations. This does not meet WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context). We plan to resolve this issue by September 2022. When we publish new pages, we will make sure link text meets accessibility standards.
On some pages, the purpose of each link cannot be determined from the link text alone. This does not meet WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context). We plan to resolve this issue by September 2022. When we publish new pages, we will make sure link text meets accessibility standards.
On some pages, tables do not have a description set using the caption element. This does not meet WCAG 2.1 success criterion 1.3.1 Info and Relationships. We plan to resolve this issue by September 2022. When we publish new tables, we will make sure they meet accessibility standards.
PDFs and other documents
Some of our PDFs and other documents are not formatted so they are accessible to a screen reader. This does not meet WCAG 2.1 success criterion 4.1.2 (Name, role value). Any new documents we publish should meet accessibility standards where they are required for essential services or users who are likely to have disabilities or impairments. Essential documents will be reviewed and made accessible by September 2022.
On some pages, the tabbing order is not logical when navigating using a keyboard. This does not meet WCAG 2.1 success criterion 2.4.3 Focus Order. We plan to resolve this issue by September 2021.
On some pages HTML is used to format content rather than CSS. This doesn’t meet WCAG 2.1 success criterion 1.3.1 Information and Relationships.
Full Council meeting minutes and papers
Monthly Full Council meeting minutes and papers are available dating back at least seven years. These documents do not always use simple language, and do not use proper heading structures.
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 Full Council meeting minutes and papers, and with interactive tools. We believe that doing so now would be a disproportionate burden within the meaning of the accessibility regulations. However, all meeting minutes published from now on use a new, accessible template.
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
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 obsolete Committee membership documents.
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.
What we’re doing to improve accessibility
Our accessibility roadmap is still being planned. It will show how and when we plan to improve accessibility on this website. A link will be posted to the roadmap once it is ready.
Preparation of this accessibility statement
This statement was prepared on 22 September 2020. It was last reviewed on 27 September 2021.
This website was last tested on 27 September 2021. The test was carried out in-house.
We tested all of main pages, such as the homepage and governance sections, and a sampling of news articles. We used accessibility tools such as Siteimprove Accessibility Checker, WCAG Luminosity Contrast Ratio Analyzer (to test contrast ratios), HeadingsMap (to test heading structure), and ChromeVox (to test compatibility with screen readers) to test how the site performed for people with impairments.