Digital Shields is committed to making our service accessible to as many people as possible. This statement covers www.digitalshields.co, including the parent portal, the schools portal, and our public marketing pages.
1. Conformance status
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. At the date of this statement we consider Digital Shields to be partially compliant with WCAG 2.1 AA — most success criteria are met, but the known gaps in Section 4 below mean we have not yet completed a full external audit.
2. How accessible Digital Shields is
The site is built with semantic HTML, high-contrast navy + gold theming, ARIA labels on interactive controls, and keyboard support throughout. Specifically:
- All primary navigation is reachable by keyboard (Tab / Shift+Tab / Enter).
- Modals and dialogs close on the Esc key.
- Icons are accompanied by visible labels or
aria-labelattributes. - Form fields have associated
<label>elements. - Text and interface colours come from one design system chosen for WCAG 2.1 AA contrast, in both light and dark themes.
- Both portals have a text size setting, follow your device's light or dark preference, and respect “reduce motion”.
- Every page has a skip-to-content link and uses header, navigation, main and footer landmarks.
- The site is responsive down to 360 px viewport width without horizontal scrolling on key flows.
- No content auto-plays, flashes, or rotates without user control.
3. Compatibility
Digital Shields is tested in the latest two versions of Chrome, Safari, Firefox and Edge on desktop, and Safari + Chrome on iOS and Android. We aim for compatibility with the most recent versions of NVDA, JAWS, and VoiceOver, though formal screen-reader testing is not yet complete (see Section 6).
4. Known accessibility issues
We are aware of and working on the following:
- The admin dashboard used by our own team has not been rebuilt yet and lacks skip links in places.
- The schools portal procurement documents (DPA, DPIA, sub-processor list) are designed for print and have not been audited for screen-reader navigation. We recommend the downloadable PDF version for assistive-technology users.
- Some decorative SVGs on the landing page are marked
aria-hiddenbut not all have explicitrole="presentation". - The parent and schools portals were rebuilt in October 2026. We have tested them in current browsers on desktop and phone, but a full keyboard, heading-hierarchy and screen-reader review is still to come.
- No formal external WCAG audit has been commissioned yet; we plan to engage an accredited auditor in 2026.
5. Reporting an accessibility problem
We welcome feedback on the accessibility of Digital Shields. If you encounter any barriers, please tell us:
- Email: support@digitalshields.co (subject line "Accessibility feedback" routes to the right person fastest)
- General support: support@digitalshields.co
We aim to acknowledge your report within 2 working days and propose a fix or workaround within 10 working days. For critical issues (you cannot use the service at all) we will respond within 1 working day.
6. Enforcement
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Equality Act 2010 in Great Britain. If you are not satisfied with how we respond to your accessibility complaint, you can contact the EHRC at equalityadvisoryservice.com.
7. Technical specifications
Accessibility relies on the following technologies:
- HTML5 (semantic landmarks:
<header>,<nav>,<main>,<footer>) - CSS (custom properties, responsive flex / grid)
- ARIA 1.2 (labels, live regions on toasts, modal dialog semantics)
- Modern JavaScript (the portals use Preact, a small open-source library)
8. Preparation of this statement
This statement was last updated on 7 October 2026. It will be reviewed and updated at least every six months, or sooner if we make significant changes to the service.
The assessment underlying this statement was performed by Infinity X Investments Ltd (in-house). We have used automated tools (axe-core, browser dev-tools accessibility panels) and manual keyboard testing. We have not yet completed third-party WCAG conformance testing.