• 01765 604362
  • Contact Us
  • Facebook
Arrange a Visit

Web Accessibility Statement

Accessibility statement for Sharow CofE Primary School

This website is run by Sharow CofE Primary School. 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 aren’t fully accessible:

    What to do if you can’t 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 our Contact Form

    We will consider your request and get back to you in asap.

    If you can’t view the map on our ‘contact us’ page, call or email us [Please use our Contact Form] for directions.

    Reporting accessibility problems with this website

    We’re always looking to improve the accessibility of this website. If you find any problems that aren’t listed on this page or think we’re not meeting accessibility requirements please use our Contact Form

    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.

    Find out how , please use our Contact Form

    Technical information about this website’s accessibility

    Sharow CofE Primary School 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

    • We are aware that some aspects of google maps are not accessible. If you need directions please use our Contact Form
    • Some images don’t have a text alternative, so the information in them isn’t available to people using a screen reader.  This doesn’t meet WCAG 2.1 success criterion 1.1.1
    • We do not have audio description for existing video content on this website, we will consider this issue when adding any new content. This does not meet WCAG 2.1 success criterion 1.2.3 (audio description).
    • Some of our older videos don’t have accurate edited captions or transcripts. This fails WCAG 2.1 success criterion 1.2.1 (audio-only and video-only pre-recorded), 1.2.2 (captions pre-recorded), 1.2.3 (audio description or media alternative pre-recorded) and 1.2.5 (audio description pre-recorded).
    • Presentational attributes such as ‘border’, ‘align’, or ‘bgcolor’ are used within the HTML.  This doesn’t meet WCAG 2.1 success criterion
    • We are aware there various colour contrast issues throughout our website . This doesn’t meet WCAG 2.1 success criterion 1.4.3 and 1.4.1
    • We are aware of images containing text appearing within the site. This doesn’t meet WCAG 2.1 success criterion 1.4.5
    • The visual presentation of text and images of text does not have a contrast ratio of at least 7:1. This doesn’t meet WCAG 2.1 success criterion 1.4.6
    • We are aware that keyboard users cannot tab through the website. This fails WCAS 2.1 2.4.3 A (Focus Order).
    • We are aware that the same link text is used for links going to different destinations. This doesn’t meet WCAG 2.1 success criterion 2.4.4
    • We are aware of some difficulties using our select lists on forms with assistive technology because of the conditions surrounding selections made in these fields. These conditions are necessary for accurate filing, and we are continuing to work on a better solution for accessibility than the one currently implemented. This doesn’t meet WCAG 2.1 success criterion 3.2.2.
    • Some input fields do not contain a description. This doesn’t meet WCAG 2.1 success criterion 3.3.2
    • We are aware that WAI-ARIA roles should correspond to the intended function of the element. As they do not in places This doesn’t meet WCAG 2.1 success criterion 4.1.2
    • We are aware that the ID used for an element on the page is also used for another element on the page. This doesn’t meet WCAG 2.1 success criterion 4.1.1

    Disproportionate burden

    Although the principle of having no text visible within an image file has been detected we cannot go through all PDF’s that have images on and add any alt text or provide the text that will be formatted through an image.

    There are no subtitles on the opening hero video due to no sound generating from that file so a descrption is not required and the text overlaying this media described clearly what is being displayed.

    Third-party interactive tools, transactions and software products that are not within NYES Digital branding cannot be modified to improve accessibility however if we believe the sites to be difficult to use then we would create an alternative resource.

    Our contact form is provided by an external plugin ‘Ninja Forms’ and cannot change any user expeirence issues related to accessibility after configuration. Please let us know if you experience issues and we can contact the developer.

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

    PDFs and other documents

    Many of our older PDFs and Word documents don’t meet accessibility standards – for example, they may not be structured so they’re accessible to a screen reader. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role value).

    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 2020, we plan to either fix these or replace them with accessible HTML pages.

    The accessibility regulations don’t 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 don’t plan to fix [example of non-essential document].

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

    Live video

    Live video streams don’t have captions. This doesn’t meet WCAG 2.1 success criterion 1.2.4 (captions – live).

    We don’t plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations.

    How we tested this website

    This website was last tested on 12/08/2024. The test was carried out by NYES Digital

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

    • We tested the homepage of the site as this is feature rich and allowed us to test the core template for issues.
    • We tested all pages where we use 3rd party plugins and contact forms
    • Random selection of pages created by the website content editors

    What we’re doing to improve accessibility

    This statement was prepared on 12/08/2024. It was last updated on 12/08/2024.

    Translation Statement

    Popular web browsers include the option to translate web pages by default when they detect that the website language is different to the language installed on the computer, tablet or smartphone. When browsers do not offer to automatically translate, plug-ins are often available to help you do this :