Accessibility statement
Our WCAG 2.2 AA target and how we check it·Source: docs/legal/ACCESSIBILITY.md
Last reviewed: 6 November 2026
HallPal is committed to keeping its admin dashboard usable for school administrators, teachers and support staff, however they use a computer. This page sets out the standard we aim for, how we check it, what does not meet it yet, and how to tell us about a problem.
Our target
We aim for WCAG 2.2 Level AA across the dashboard and the public website. That includes:
- Text contrast of at least 4.5:1, or 3:1 for large text.
- Every control reachable and usable with a keyboard, with a visible focus indicator.
- Tap targets of at least 24 by 24 CSS pixels.
- Content that reflows without sideways scrolling at 320 CSS pixels wide (400% zoom on a 1280-pixel display). Data tables are exempt, as WCAG 1.4.10 allows: they scroll sideways inside their own area.
- Animation that follows your device's reduce-motion setting.
- Status messages announced to screen readers through live regions.
- Landmarks, so a screen reader can jump between parts of a page: a main region on every page, a banner on the public pages, and navigation in the dashboard.
- A "Skip to main content" link as the first stop when you press Tab, on every page except the sign-in page (see Known limitations).
This is the standard we build and test against. The sections below say what is checked, and what still falls short of it.
How we check
Automatically, on every change
Every pull request into our main branch, and every change pushed to it, runs these checks in a browser against a production build of each public page: the home page, the contact page, the sign-in page, this statement, the privacy notice, the terms of use, each of the other legal pages, the invitation page and the page-not-found page.
- axe-core checks the WCAG 2.0, 2.1 and 2.2 Level A and AA rules, in both the light and the dark theme. A critical or serious finding fails the check.
- Page structure: exactly one top-level heading, no skipped heading levels, one main region and a banner.
- Keyboard: the skip link is the first Tab stop and moves focus to the main content, and tabbing through the page (up to 60 stops) never drops focus back to the page itself. On the sign-in page the check confirms the exception below instead.
- Reflow: at 320 CSS pixels wide, no content outside a scrollable area sticks out past the window by more than 20 CSS pixels (a margin for rendering differences). Decoration that is hidden from screen readers, such as the moving sample passes behind the sign-in form, is not counted.
ESLint's accessibility rules (jsx-a11y) also run on every change. A label that is not tied to its form control, a positive tabindex value, or a focusable element hidden from screen readers fails the build; the other rules report warnings.
The signed-in dashboard
The dashboard's main pages have their own automated checks: axe in both themes, a keyboard walk, a test that dialogs hold focus and return it when they close, reflow at 320 CSS pixels, accessibility-tree snapshots, checks that every control has a name, and runs with forced colours and with reduced motion. They need a signed-in test account, which our automated build does not have at present, so they do not run on every change. They run when a developer runs them.
By hand
Some things only a person can judge, such as how a screen reader actually reads a page or whether a focus ring is easy to see at arm's length. We keep a written checklist for these, covering the NVDA and VoiceOver screen readers and keyboard-only use of common tasks.
Known limitations
- On the sign-in page the cursor starts in the email field, so pressing Tab moves through the sign-in form rather than to the skip link. The skip link is still first on the page: moving backwards with Shift+Tab reaches it.
- Data tables (students, passes, teachers, Homebases) can scroll sideways at narrow widths. Every row stays reachable by keyboard.
- In the dashboard, the top bar sits inside the main region, so screen readers do not announce it as a banner.
- Charts and generated PDFs may not fully meet the target. We are working to replace or wrap them.
- The automated checks run without the sign-in page's bot check (Cloudflare Turnstile), so that widget is not covered by them.
- We have no third-party accessibility audit and no VPAT (Voluntary Product Accessibility Template) yet. Everything on this page is our own testing.
Report an issue
If you hit a barrier in HallPal (a page you can't read, a control you can't reach, an announcement that doesn't make sense), please tell us. We treat these as bugs and fix them ahead of new features.
Email support@hallpal.net with a description of the problem, the address of the page where it happened and, if you are comfortable sharing it, the assistive technology you were using. We aim to reply within 5 business days.
Standards
- Our target is WCAG 2.2 Level AA.
- We write this statement with the Americans with Disabilities Act (Titles II and III), Section 508 and the European Accessibility Act in mind. HallPal is not a Section 508 vendor.