Skip to content

We count anonymous page and calculator use without cookies. May we also use optional analytics (cookies, masked replay) to improve the service?

About your privacy choices

We use essential storage to keep you signed in, remember work in progress, save your privacy choice and run sign-in bot protection. We use limited cookieless usage counts before you choose. With your permission, optional product analytics help us understand and improve the signed-in service. Account-linked analytics stay off unless you accept. Session replay is disabled on authenticated and client workspace pages; with your permission, anonymous masked replay may run only on queryless public pages. We do not use advertising trackers or sell personal data. Read our privacy policy.

ParaplanAI
Sign in

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 check that with automated tests on each change. The checks do not catch everything: what we know still falls short is listed under Known limitations below.

What we check automatically

  • Automated WCAG checks. Public pages are scanned with axe-core against the WCAG 2.0, 2.1 and 2.2 A and AA rules on each change, at mobile and desktop widths. Critical and serious findings are tracked and fixed before release where our automated checks find them. The scans run with reduced motion switched on, so they check the still frame of each animation, not the moving frames.
  • Contrast. Colour contrast (4.5:1 for body text) is one of the rules in that scan.
  • Keyboard. An automated keyboard walk on the homepage checks, on each change, that a skip-to-content link comes first and that each of the first 50 controls it reaches shows a focus indicator.
  • Touch targets. axe's WCAG 2.5.8 target-size rule (24 × 24 px minimum) is checked on 12 key pages at 6 screen widths from 375 px to 1440 px.
  • Lighthouse. A sample of 38 public pages must score at least 95/100 on the Lighthouse accessibility audit.

Known limitations

  • Only part of the signed-in product is checked automatically. Each week an automated run signs in and scans the dashboard, the calculations list, a client page and the first step of the carry-forward workflow for critical and serious WCAG 2.1 A and AA failures, and checks that the signed-in mobile menu opens, closes with Escape and keeps keyboard focus out while closed. That weekly run also carries many other end-to-end tests, and some of them currently fail, so the run as a whole does not pass; the signed-in accessibility checks named here passed in the scheduled run of 26 September 2026. One other signed-in mobile-menu check failed in that run: after the open menu is rotated to landscape, the page can stop responding to taps. A weekly scan of every signed-in page, including the mobile menu's focus trap, is written but not yet running.
  • Not every control has a clear focus indicator: some focus outlines fall below the 3:1 contrast WCAG asks for.
  • Some small text on the homepage, including text in its animated product demonstrations, falls below the WCAG AA contrast ratio of 4.5:1.
  • Some inline disclosure controls, such as “Retention details”, are less than 24 px tall on touch screens.
  • 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 · updated 26 October 2026 · how we verify the numbers