Using Pupil Protect
We want as many people as possible to be able to use Pupil Protect. You should be able to:
- choose a light, dark or high contrast theme in your display settings
- make text larger with the Standard, Large and Largest text sizes, and zoom up to 400% without text spilling off the screen
- reach everything with a keyboard, with a clear focus outline showing where you are
- use a screen reader, with headings, labels and status messages announced
- turn on Reduce motion, so panels and status dots no longer move (it’s on automatically if your device asks for less motion)
- use touch targets of at least 44 pixels on phones, tablets and reception kiosks
- understand every status without relying on colour, because each is written in words
Hide names shows pupils’ initials only, and Blank screen covers the screen at once. They’re there for staff working in shared spaces, and they’re on every screen.
We write in plain English. AbilityNet has advice on making your device easier to use if you have a disability.
How accessible Pupil Protect is
We aim to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 to level AA. Text meets a 4.5:1 contrast ratio, and borders, icons and focus outlines that carry meaning meet 3:1, in every theme. In the high contrast theme, text reaches 7:1.
We don’t know of any parts that are not fully accessible. If you find one, please tell us.
What we test
Every new screen is checked before release. We test:
- with automated checks during development
- by hand, using only a keyboard
- with screen readers: [NVDA, JAWS, VoiceOver and TalkBack, to confirm]
- at 200% and 400% zoom, and at every text size
- in the light, dark and high contrast themes
- on phones, tablets and the reception kiosk, for touch targets and layout
[Whether we test with disabled users, and how, to confirm]
Reporting a problem
If you find something hard to use, or you need information in a different format such as large print or audio, tell us. We’re always looking to improve.
- email accessibility@pupilprotect.co.uk
- if you’re a customer, contact support from inside Pupil Protect
Tell us the page or screen, what you were trying to do and what assistive technology you use, if any. Please don’t include details about a child. We’ll reply within 2 working days.
Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations for public sector websites and apps. Many of the schools and trusts that use Pupil Protect are covered by them, so we write this statement in the same format.
If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Technical information
Pupil Protect is [fully / partially compliant, to confirm after audit] with WCAG version 2.2 AA.
Non-accessible content
We don’t know of any content that fails WCAG 2.2 AA.
Content that’s not within scope
Documents that schools upload, such as letters from other agencies, may not be accessible. We show them as they were received. [Other exemptions to confirm]
Preparation of this statement
This statement was prepared on . It was last reviewed on .
Pupil Protect was last tested on by [who carried out the test]. We tested [which screens and how they were chosen].
More about how we build Pupil Protect
Accessibility is one of four commitments behind every screen. Read about how it’s built, or see how we protect your data.