Accessibility

Website Accessibility and Our Responsibilities to You

This website has been designed to be as usable and accessible as possible for every visitor by using easier to read colours, larger fonts and allowing navigation by using only a keyboard. External and internal links are coloured blue and underlined. Additionally, visitors who are visually impaired will be able to use screen readers to hear the alternative text linked to images conveying important information. Where an image is used for decorative purposes the alternative text attribute has been left blank. If you do have any difficulty in accessing this site, do let us know by emailing the webmaster so that we can put things right.

Accessibility Statement

This statement applies to content published on the www.granbycumsutton.org domain on behalf of GranbycumSutton Parish Council. It is designed to be used by as many people as possible. The text should be clear and simple to understand. You should be able to:

Zoom in up to 300% without problems
Navigate most of the website using just a keyboard
Navigate most of the website using speech recognition software
Use most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

How Accessible this Website Is

Parts of this website are not fully accessible. For example:

Some pages and document attachments are not written in plain English
Some tables do not have row headings
Some documents have poor colour contrast
Some heading elements are not consistent
Some images do not have image descriptions
Some buttons are not correctly identified
Some error messages are not clearly associated with form controls
Many documents are in PDF format and are not accessible

We will update the statement when issues are fixed or when we expect them to be fixed.

Compliance Status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard.

Non-accessible Content

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

Non-compliance with the accessibility regulations

Some tables in content do not have table row headers when needed. This means assistive technologies will not read the tables correctly. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
Images on some pages do not always have suitable image descriptions. Users of assistive technologies may not have access to information conveyed in images. This fails WCAG 2.1 success criterion 1.1.1 (Non-text Content).
Some pages have duplicate titles. This may make it difficult for users to orient themselves and find the right content. This fails WCAG 2.4.2 success criterion (Page Titled).
The change in the default written language is not correctly identified on some pages. This means screen readers will not read content correctly. This fails WCAG 2.1 success criterion 3.1.2 (Language of Parts).
Some features are inconsistently named, for example accordions, tables of contents, search boxes and translation navigation. This fails WCAG 2.1 success criterion 3.2.4 (Consistent Identification).
Some pages cannot be found through more than one type of navigation. This fails WCAG 2.1 success criterion 2.4.5 (Multiple Ways).
Some pages have inconsistently-placed language navigation. This fails WCAG 2.1 success criterion 3.2.4 success criterion (Consistent Identification).
Some content looks like headings but is not. This makes it difficult for screen reader users to navigate the page. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
Some pages have poor colour contrast. This fails WCAG 2.1 success criterion 1.4.1 (Use of Colour).
Many documents are in less accessible formats, for example PDF. Non-HTML documents published on or after 23 September 2018 must have an accessible format.

PDFs and non-HTML documents
Many documents are not accessible in a number of ways including missing text alternatives and missing document structure.

Content that's not within the scope of the Accessibility Regulations
Non-HTML documents published before September 2018 do not need to be accessible - unless users need them to use a service.

Further Help

AbilityNet provides guidance about how to: