Accessibility statement for Holy Cross Catholic Primary School
This accessibility statement applies to the website for Holy Cross Catholic Primary School.
This website is run by Holy Cross catholic 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:
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:
Feedback and contact information
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: [provide both details of how to report these issues to your organisation, and contact details for the unit or person responsible for dealing with these reports].
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.
If you cannot view the map on our ‘contact us’ page, call or email us at office@holycrossprimary.thurrock.sch.uk for directions.
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
Holy Cross catholic 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.
Compliance status
The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to [insert one of the following: ‘the non-compliances’, ‘the exemptions’ or ‘the non-compliances and exemptions’] listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).
Disproportionate burden
Navigation and accessing information
There’s no way to skip the repeated content in the page header (for example, a ‘skip to main content’ option).
It’s not always possible to change the device orientation from horizontal to vertical without making it more difficult to view the content.
It’s not possible for users to change text size without some of the content overlapping.
We’ve assessed the cost of fixing the issues with navigation and accessing information. 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 [rough timing].
Content that’s not within the scope of the accessibility regulations
PDFs and other documents
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 [example of non-essential document].
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.
What we’re doing to improve accessibility
Our accessibility roadmap [add link to roadmap] shows how and when we plan to improve accessibility on this website.
Preparation of this accessibility statement
This statement was prepared on July 2025. It was last reviewed July 2025.
This website was last tested on July 2025 against the WCAG 2.2 AA standard.
The test was carried out by Juniper. The most viewed pages were tested using automated testing tools by our website team. A further audit of the website was carried out to the WCAG 2.2 AA standard.