Accessibility statement for Kirkby and Great Broughton Church of England Primary School

This website is run by Kirkby and Great Broughton Church of England 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:

• We are aware that some aspects of google maps are not accessible. If you need directions please use our Contact Form

Text Alternatives

Non-text Content.

Adaptable

Info and Relationships 1.3.1 with no landmark backend lables

Dinstinguishable

Contrast (Minimium) 1.4.3 with colour improvements

Images of Text 1.4.5 as the logo contains text which cannot be read through screenreader

Navigable

Bypass Blocks 2.4.1 as there are no option to skip repeated content

Link Purpose (in Context) 2.4.4 with issues due to cookies banner not being labelled

Focus Visible 2.4.7 as no elements hightlight on focus

Predictable

On Input due to a means of bypassing blocks of content that are repeated on multiple web pages must be provided.

Compatible

Name, Role, Value as the iFrame has no ‘title’ attribute or the ‘title’ attribute is empty.

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

Kirkby and Great Broughton Church of England 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

• 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 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
• 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 that user interface elements, that can receive keyboard focus, are not highlighted on focus. This doesn’t meet WCAG 2.1 success criterion 2.4.7
• 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

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.

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 [documents that contain images with text on as they cannot be read through a screen reader].

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 14/4/22. The test was carried out by Schools ICT

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 1/4/22. It was last updated on 14/4/22.

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.

• Google Chrome should offer to translate pages automatically.
• Internet Explorer can translate pages with the Google toolbar extension.
• Edge can translate pages with an extension from the Microsoft store.
• Safari on MacOS can translate pages with an extension available on the Safari extensions website.
• Safari on iOS can translate pages with with an extension from the App store.
• Firefox can translate pages with various extensions.

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 :

• Google Chrome should offer to translate pages automatically.
• Internet Explorer can translate pages with the Google toolbar extension.
• Edge can translate pages with an extension from the Microsoft store.
• Safari on MacOS can translate pages with an extension available on the Safari extensions website.
• Safari on iOS can translate pages with with an extension from the App store.
• Firefox can translate pages with various extensions