Accessibility statement for Quidhampton Parish Council
This accessibility statement applies to the website for Quidhampton Parish Council (parishcouncil.quidhampton.org.uk). This page is based on the gov.uk template.
This website is run by Quidhampton 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.
How accessible this website is
We know some parts of this website are not fully accessible:
- some older PDF documents are not fully accessible to screen reader software
- some of our online forms may be difficult to navigate using just a keyboard
- not all of our images have alt text
Our website uses the WordPress Content Management System (CMS) and complies with all required elements of WordPress accessibility guidelines. We use WordPress as the developers are committed to making the platform accessible.
Please see the following links for information on how accessible individual features are:
- Keyboard Navigation
- Skip Links
- ARIA Landmark Roles
- Content Links
- Repetitive Link Text
- Screen Reader Text
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
We’ll consider your request and get back to you in 14 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 the Parish Clerk.
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
We provide a text relay service for people who are deaf, hearing impaired or have a speech impediment.
We don’t currently have any offices nor do we have audio induction loops, but if you contact us we can try to arrange a British Sign Language (BSL) interpreter.
Technical information about this website’s accessibility
Quidhampton 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
Links opening in new windows/tabs
Some links use the
target attribute to specify that they should open in a new window as described in WCAG 2.0 F22. As these are identified, target attribute settings will be fixed.
Some text uses
text-align:justify to apply justified formatting as described in WCAG 2.0 F88. As occurrences are identified, this formatting will be removed.
The website is run by volunteers and we have no capacity for major works to improve accessibility. As such, all current accessibility problems described below are classed as disproportionate burden. We intend to implement new versions of WordPress with improved accessibility features as soon as they are released.
Alt text for images
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 do not plan to add text alternatives for all images but will do so whenever we come across missing alt text attributes. When we publish new content we’ll make sure our use of images meets accessibility standards.
Names of some elements
WordPress currently applies names to some div elements. This includes naming a div containing the navigation elements with
aria-label="Menu". This is contrary to ARIA1.2.
Cannot use aria-label or aria-labelledby on elements and roles that prohibit naming: The div and span elements have an implicit role of generic and cannot be named unless they have a role attribute. The following roles cannot be named:
caption code deletion emphasis generic insertion paragraph presentation strong subscript superscript
Non-unique ID attributes
WordPress uses the same ID attribute for linked css stylesheet elements. This is technically a breach of the HTML spec and so may cause rendering issues as detailed by W3C.
WordPress currently uses
:hover transition: transform 0.1 as a means to highlight social media icons. This is contrary to WCAG 2.1 SC 2.3.3. An alternative would be to use
@media (prefers-reduced-motion) to respect user preferences. This is likely to be updated in a future release of WordPress.
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
Some of our pdf documents are not accessible. Some of these are produced by volunteers and not under the control of the Parish Council. Some are produced by the Parish Clerk who did not have access to suitable software to produce accessible versions.
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 the archive of village newsletters.
What we’re doing to improve accessibility
WordPress aims to make the WordPress Admin and bundled themes fully WCAG 2.0 AA compliant, where possible. We will implement new versions of WordPress and its themes as soon as they are released.
Where we have identified accessibility issues, these will be fixed wherever possible as part of ongoing maintenance and development of the website.
Preparation of this accessibility statement
This statement was prepared on 6th June 2023. It was last reviewed on 6th June 2023.
Ten pages were tested linked from the homepage. The following items were tested:
|JAWS Screen Reader Compatibility||Not Checked|
|NVDA Screen Reader Compatibility||Not Checked|
|VoiceOver Screen Reader Compatibility||Not Checked|
|PDF/UA – Matterhorn Protocol 1.02||Not Checked|
|Section 508 of the Rehabilitation Act – 82 FR 5790 (2017)||Checked|
|Web Content Accessibility Guidelines 2.0 (WCAG 2.0 – 2008)||Not Checked|
|Web Content Accessibility Guidelines 2.1 (WCAG 2.1 – 2018)||Checked|
|Android Browser Compatibility||Checked latest version|
|Chrome Browser Compatibility||Checked latest version|
|Edge Browser Compatibility||Checked latest version|
|Internet Explorer Browser Compatibility||Not Checked|
|Firefox Browser Compatibility||Checked latest version|
|Opera Browser Compatibility||Checked latest version|
|Safari Browser Compatibility||Checked latest version|
|iPhone/iPad Browser Compatibility||Checked from version 14|
|Content Issues||Checked – No Spell Check|
|User Defined Errors||Checked|
|HTTP Status Codes||Checked|
|Search Engine Guidelines|
|Google Webmaster Guidelines||Checked|
|Google SEO Starter Guide||Checked|
|Google Blogs and Webmaster Videos||Checked|
|Bing Webmaster Guidelines||Checked|
|SEO Best Practice – General||Checked|
|Yahoo Webmaster Guidelines||Checked|
|Usability.gov: Research-Based Web Design & Usability Guidelines||Checked|
|W3C Usability Best Practices||Checked|
|W3C CSS Validation||Checked|
|W3C Deprecated Features||Checked|
|W3C HTML Validation||Checked|