Skip to content

Reigate School

    • Accessibility Statement

    How We Aim to Make Our Website Accessible

    Accessibility Features

    Our website includes a range of features to support different users and assistive technologies:

    • Responsive design that works on desktops, tablets and mobile devices.
    • Keyboard‑friendly navigation for users who cannot operate a mouse. Users can navigate most of the website using a keyboard or speech recognition software
    • Clear and readable text, including consistent fonts and strong colour contrast.
    • Compatibility with screen readers, allowing most content to be read aloud (including the most recent versions of JAWS, NVDA and VoiceOver).
    • Zoom capability up to 400% without loss of content or functionality.
    • Subtitles available on videos, where provided.
    • Simple, easy‑to‑understand language used throughout the site.

    We've also made the website text as simple as possible to understand. We also signpost users to accessibility support such as AbilityNet which has advice on making your device easier to use if you have a disability.

    Our Commitment to Accessibility

    Reigate School strives to meet the WCAG 2.2 AA standard. While the website is partially compliant, we are actively working to improve its accessibility and usability. Where certain improvements would place a disproportionate burden on the school, this will be documented in line with Government accessibility regulations

    School exemption

    Non-compliant content

    We know some parts of this website are not fully accessible. This website is partially compliant and we are working on increasing its accessibility and usability. In line with WCAG guidelines, we may rely on the disproportionate burden exception where the cost or effort to meet requirements is deemed excessive in relation to the benefit.

     

    We are continually working to improve the accessibility of our website by:

    • Screen reader compatibility: whilst our website has been built include functionality that works with screen readers, we may need to make some improvements by working with our website provider.

    • Regular audits and user testing: We commit to annual audits and user testing.

    • User feedback: We will incorporate feedback from users to enhance accessibility.

    • Keeping up-to-date: We will endeavour to keep up to date with evolving accessibility standards and best practices.

    While we aim to ensure all content on our website is accessible, some third-party materials or linked resources may not fully meet accessibility standards. We encourage you to contact us if you have difficulties accessing external content.

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

    Reigate School is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

    The website is partially exempt with the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard due to the exemptions and non compliances listed above.

    Need Assistance?

    If you encounter any accessibility barriers or have suggestions to improve your experience, please contact us:

    • Email: info@reigate-school.surrey.sch.uk

    • Phone: 01737 243166

    • Mailing Address: Reigate School, Pendleton Road, Reigate, RH2 7NT

    When reporting an issue, please include:

    • The webpage or feature you experienced difficulties with.

    • Your contact information (optional, if you would like a response).

    Commitment to Improvement

    Reigate School values diversity and inclusion and is committed to providing an accessible online experience for all members of our community. Your feedback is essential in helping us achieve this goal.

    This statement was first prepared on February 2025. 

    This statement was last updated on March 2026

     

    • Cookie Policy