Accessibility Statement

This website is run by Yarnscombe Parish Council, although parts of the site refer to other aspects of our village life such as the parish church. We want as many people as possible to be able to use this website. For example, that means you should be able to:

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:

What to do if you cannot access parts of this website

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, email the website administrator. We’ll consider your request and get back to you within seven 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, email the website administrator. We’ll normally get back to you within seven days.

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).

Technical information about this website’s accessibility

Yarnscombe 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 listed below.

Non accessible content

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

Non compliance with the accessibility regulations
  1. Because this website uses HTML frames, a screen reader in conjunction with a text-based web browser will read across on each line from the main frame to the “Latest News” frame. This fails WCAG success criterion 1.3.2 (meaningful sequence). We plan to redesign the website without the use of frames by September 2020.
  2. When using the single-line dropdown navigation menu, the submenus obscure other content until the mouse pointer is moved away. Although navigation through the submenus is possible on a page-by-page basis, this non-dismissibility fails bullet point 1 of WCAG success criterion 1.4.13 (content on hover or focus). We plan to implement a different navigation method by April 2020.
  3. For screen readers in particular, it is not possible to bypass blocks of content that are repeated on multiple webpages. This fails WCAG success criterion 2.4.1 (bypass blocks). We plan to include skip-to-content links by April 2020.
  4. The page links in the page footers, and some links on other pages (including those generated dynamically by CGI scripts), do not have explanations. This fails WCAG success criterion 2.4.4 (link purpose (in context)). We plan to add the necessary link explanations by February 2020.
  5. There is nothing to show the user's location within a set of webpages. This fails WCAG success criterion 2.4.8 (location). We plan to add a “breadcrumb trail” to show locations by March 2020.
  6. When using the single-line dropdown navigation menu, pressing down the mouse button on a submenu item causes the corresponding page to be loaded immediately. This fails WCAG success criterion 2.5.2 (pointer cancellation). We plan to implement a different navigation method by April 2020.
Content that’s not within the scope of the accessibility regulations

PDFs and other documents

Many of our older PDFs 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 are essential to providing our services. For example, we have PDFs containing minutes and agendas of past Parish Council meetings.

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 and agendas published before 23 September 2018, although we believe they greatly enhance our services.

From November 2019 any new PDFs or Word documents we originate and publish will meet accessibility standards, although we cannot guarantee that PDFs originated by external organisations that have asked us to publish them on our website will meet accessibility standards.

How we tested this website

This website was last tested on 24 November 2019. The test was carried out by the website administrator.

For each of the 77 WCAG 2.1 success criteria we checked all known page types to see whether they passed or failed the criterion. The criteria that were failed by one or more pages are listed above.

This statement was prepared on 16 November 2019. It was last updated on 24 November 2019.