Accessibility Statement
Our commitment to digital inclusion and accessibility
Last updated: December 2024
Effective date: December 2024
Our Commitment
Pupil Protect is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards.
We believe that everyone should have equal access to safeguarding technology, regardless of their abilities or the assistive technologies they use.
Conformance Status
WCAG 2.1 Level AA Compliance
The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.
Pupil Protect is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.
Standards We Follow
- • Web Content Accessibility Guidelines (WCAG) 2.1
- • Section 508 of the Rehabilitation Act
- • EN 301 549 European Standard
- • Equality Act 2010 (UK)
Accessibility Features
Keyboard Navigation
- • Full keyboard accessibility
- • Logical tab order
- • Visible focus indicators
- • Skip navigation links
Screen Reader Support
- • Semantic HTML structure
- • ARIA labels and descriptions
- • Alternative text for images
- • Descriptive link text
Visual Design
- • High contrast color schemes
- • Scalable text up to 200%
- • Clear visual hierarchy
- • Color is not the only indicator
User Control
- • Adjustable time limits
- • Pause/stop animations
- • Customizable interface
- • Multiple input methods
Known Accessibility Issues
Areas for Improvement
We are actively working to address the following accessibility issues:
- • Some complex data visualizations may not be fully accessible to screen readers
- • Certain third-party components may not meet full WCAG 2.1 AA standards
- • Some PDF documents may require accessibility improvements
- • Mobile touch targets in some areas may be smaller than recommended
Timeline: We are committed to addressing these issues by Q2 2025.
Supported Assistive Technologies
Pupil Protect is designed to be compatible with the following assistive technologies:
Screen Readers
- • JAWS (Windows)
- • NVDA (Windows)
- • VoiceOver (macOS/iOS)
- • TalkBack (Android)
Other Technologies
- • Voice recognition software
- • Switch navigation devices
- • Eye-tracking systems
- • Magnification software
Accessibility Testing
Our Testing Approach
- • Automated accessibility testing tools
- • Manual testing with assistive technologies
- • User testing with people with disabilities
- • Regular accessibility audits by third-party experts
Testing Tools We Use
- • axe-core automated testing
- • WAVE Web Accessibility Evaluation Tool
- • Lighthouse accessibility audits
- • Color contrast analyzers
Feedback and Contact Information
We Welcome Your Feedback
We welcome your feedback on the accessibility of Pupil Protect. Please let us know if you encounter accessibility barriers:
Phone
Post
Accessibility Team
Pupil Protect Limited
123 Safeguarding Street
London, EC1A 1BB
United Kingdom
We try to respond to accessibility feedback within 5 business days.
Formal Complaints Procedure
If you are not satisfied with our response to your accessibility concern, you may:
- Contact our Customer Service Manager at complaints@pupilprotect.com
- File a complaint with the Equality and Human Rights Commission (EHRC)
- Contact the relevant regulatory body for your sector
We are committed to resolving accessibility issues and will work with you to find a suitable solution.
Technical Specifications
Accessibility of Pupil Protect relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:
- • HTML5
- • CSS3
- • JavaScript
- • WAI-ARIA
These technologies are relied upon for conformance with the accessibility standards used.
Continuous Improvement
Our Ongoing Commitment
Accessibility is an ongoing effort. We are committed to:
- • Regular accessibility training for our development team
- • Incorporating accessibility into our design and development process
- • Conducting regular accessibility audits
- • Staying up-to-date with accessibility best practices and standards
- • Engaging with the disability community for feedback and guidance