ParaplanAI · accessibility
Accessibility statement.
ParaplanAI is a professional tool for paraplanners and advisers, and we want nobody locked out of it. We build to the Web Content Accessibility Guidelines (WCAG) 2.2 level AA and hold that bar with automated checks that run on every change.
What we test on every change
- Automated WCAG checks. Every public page (and the signed-in surfaces) is scanned with axe-core against the WCAG 2.0/2.1/2.2 A and AA rule set. A single critical or serious finding blocks the change from shipping.
- Contrast. The colour palette is checked for AA contrast (4.5:1 body text); most body copy exceeds the stricter AAA 7:1 ratio.
- Keyboard. A skip-to-content link is the first focusable element on every page, every interactive element shows a visible focus ring, and dialogs trap and return focus. These behaviours are asserted by automated keyboard-walk tests.
- Touch targets.Interactive targets meet the WCAG 2.5.8 24×24 px minimum (checked across six viewport sizes from 375 px to 1440 px).
- Reduced motion. Animations honour
prefers-reduced-motion. - Lighthouse. Every public route must score at least 95/100 on the Lighthouse accessibility audit.
Known limitations
- A full manual screen-reader pass (VoiceOver / NVDA) over the six core product flows is scheduled but not yet complete; automated checks cover the ARIA semantics those readers rely on, but they are not a substitute for the real thing. This statement will be updated when the audit is recorded.
- The compliance-annex PDFs we generate are designed for print-scale reading. The underlying calculation, inputs and step-by-step working are always available on-screen in the app as accessible HTML before the PDF is produced.
Report a barrier
If anything on this site or in the product is hard to use with assistive technology, email info@paraplanai.co.uk with the page and the assistive technology you were using. Accessibility reports are treated like defects in a tax figure: triaged, fixed, and covered by a regression test so they cannot come back.
Prepared 3 July 2026 · reviewed with each accessibility gate change · how we verify the numbers
