Accessibility statement
People reach for flighthelp at stressful moments, often on a phone, sometimes in a language that is not their first. We aim for everyone to be able to use it: our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, and AAA contrast for body text.
What we do
- Every page works with a keyboard, and focus is always visible.
- A “skip to main content” link, landmarks, and a logical heading structure on every page.
- Text and controls meet contrast requirements in both light and dark mode; colour is never the only signal.
- Forms have visible labels, hints and specific error messages, with an error summary that links to each problem. You can show your password while typing it.
- Results are announced to screen readers, and focus moves to them.
- Text resizes with your browser settings; the layout works at 400% zoom and on small screens.
- We respect reduced-motion and high-contrast (forced colours) settings.
- The compensation checker, search, deadline calculator and all information pages work without JavaScript.
- Twelve languages, including Arabic with a right-to-left layout. Content not yet translated is marked as English so screen readers pronounce it correctly.
- Automated accessibility checks (axe) run on every change to the code.
Known limitations
- Translations were drafted by machine and are being reviewed by native speakers; some wording may be unclear.
- Explanations produced by the rules engine, some scenario details, and long-form pages such as this one are in English only.
- The claim-letter generator and the account area need JavaScript.
- We have not yet had an independent accessibility audit. One is planned.
Feedback
If something is hard to use, tell us and we will fix it: open an issue at our public issue tracker or email accessibility@flighthelp.net. We aim to reply within five working days.