Skip to content
HopPerks

Accessibility Statement

Effective 2026-06-07 · Last updated

HopPerks is committed to being usable by everyone, including people who rely on assistive technology. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.

What we do

  • Semantic HTML with landmarks, a skip-to-content link, and a single main heading per page.
  • Full keyboard operability for navigation, search, filters and forms, with visible focus.
  • Labels on every form control, status messages announced to screen readers, and ARIA used only where native HTML can't do the job.
  • Colour contrast targeting the 4.5:1 ratio for normal text, and we never rely on colour alone to convey meaning.
  • Reduced-motion support — animations and smooth-scrolling are disabled when your device requests it.

Known limitations

  • The interactive lounge map(powered by a third-party library) is mouse- and touch-driven; opening a map marker isn't fully keyboard-operable. The same information is always available in the keyboard-accessible list view and on each airport page, so no content is map-only.
  • We're an evolving project; if you hit a barrier, the data behind any visual is also exposed as plain text and via our public API.

How we test

We test with keyboard-only navigation and automated checks, and review new interactive components against the WCAG 2.1 AA criteria as they're built.

Feedback

If you encounter an accessibility barrier, please tell us at hello@hopperks.com— describe the page and the problem and we'll prioritise a fix. We welcome the feedback.