Skip to main content

Accessibility Statement

for Ashton-under-Hill Parish Council Website

This accessibility statement applies to Ashton-under-Hill website with the domain https://ashtonunderhill.org.uk.

This website is run by Ashton-under-Hill 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:

  • increase text size and letter spacing
  • highlight headings, links and buttons
  • increase the size of the cursor
  • image alt text and aria-labels as tooltips
  • change colour contrast of website pages
  • enable keyboard navigation
  • stop animations
  • to adjust font family

We’ve also, where possible 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:

  1. some pages are missing headings, not nested properly or have incorrect heading order.
  2. some images are missing alt or empty
  3. some links have empty anchor or ambiguous anchor tags
  4. some text missing alt text anchor
  5. most older PDF documents are not fully accessible to screen reader software
  6. you cannot skip to the main content when using a screen reader on all of the pages.
  7. some pages of the visual presentation of text and images of text has not a contrast ratio of at least 4.5:1
  8. some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.
  9. live video streams that before published on September 2020 do not have captions

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:

We’ll consider your request and get back to you in 7 days.

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: 

You can report the issue that you are having with our contact form below and we aim to get back to you within 7 days. 

  • https://ashtonunderhill.org.uk/contact/

 

Enforcement procedure

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 D/deaf, hearing impaired or have a speech impediment.

Our offices have audio induction loops, or if you contact us before your visit we can arrange a British Sign Language (BSL) interpreter.

Technical information about this website’s accessibility

Ashton-under-Hill 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. 

Compliance status

  • non-compliances – this means the content in question is in scope of the regulations, but there’s an accessibility problem with it
  • an exemption – this means the inaccessible content is out of scope of the regulations, or it’d be a disproportionate burden for you to make it accessible

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.

There are some parts of the website that are a disproportionate burden for us to make it accessible for you.

Non-accessible content

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

Non-compliance with the accessibility regulations

  • Some images and texts do not have a text alternative or/and missing alt text anchor, 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 2022. When we publish new content we’ll make sure our use of images meets accessibility standards.

  • Some pages are missing headings, headings are not nested properly or have incorrect heading order. Therefore when the content is read by a screen reader, the page is not presented correctly. This fails WCAG 2.1 success criterion 1.3.1 (Info and relationship). 

We plan to add and correct headings by September 2022. When we publish new content we’ll make sure the headings meet accessibility standards.

  • Some pages have ambiguous anchor tag, so when the content is read by a screen reader, it does not make sense out of context.This fails WCAG 2.4 success criterion 2.4.4 (Navigable). 

We plan to correct ambiguous anchor tags by September 2022. When we publish new content we’ll make sure the links are anchored correctly and meet accessibility standards.

  • Some pages cannot skip to the main content. Skip links allow screen reader users to bypass navigation links and go directly to the main content. This fails WCAG 2.4 success criterion 2.4.1 (Navigable). 

We plan to add skip links on pages by September 2022. When we publish new content we’ll make sure the skip links are added correctly and meet accessibility standards.

Disproportionate burden

Navigation and accessing information

It’s not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content.

Interactive tools and transactions

Some of our 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 September 2022.

 

Content that’s not within the scope of the accessibility regulations

PDFs and other documents

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 2022, 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 third party non-essential documents.

Any new PDFs or Word documents we publish will meet accessibility standards.

Live video

We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

Distinguishable

In some cases there’s no way to alter the contrast ratio of 4.5:1 between page text and the background color due to the theme files. However, this issue is bypassed in some cases with the widget implemented for the users. This is not within the scope until we change the theme in a future date.

What we’re doing to improve accessibility

Our accessibility priority list outlined below and when we plan to improve accessibility on our website.

  1. Add missing headings and nest the headings properly 
  2. Add the missing alt description to images
  3. Add links that have empty anchor or ambiguous anchor tags
  4. Add alt description text to missing alt text anchor
  5. Add a skip link to the main content 

All issues listed above will be improved and be accessible by September 2022

Preparation of this accessibility statement

This statement was prepared on 29 September 2020. It was last reviewed on 1 October 2020.

This website was last tested on 28 September 2020. The test was carried out by Webbees Web Design.

We used this approach to deciding on a sample of pages to test. 

  1. We have used a third party scanning tool to evaluate the website. 
  2. We have identified and used WAVE Web Accessibility Evaluation Tool and W3C Validator to determine what we needed to action.
  3.  I have deep scanned the website on 22 September 2020. You can read the full accessibility error result
  4. I have used the third party plug-in tools to navigate to the error reporting pages to correct them between 22-28 September 2020. 

You can read the full accessibility test result after we have fixed the errors.

hide