Accessibility Statement

Our commitment

We want Airport Parking Exchange to be usable by everyone, including disabled travelers — for example blind and low-vision users browsing with a screen reader or magnifier, D/deaf and hard-of-hearing users, and people who navigate by keyboard or switch device rather than a mouse or touchscreen. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA.

What we've built in

• Screen readers (blind / low vision): photos across the site carry descriptive alt text, form fields have associated labels, and pages use semantic HTML headings and landmarks so screen readers can navigate them in order.
• Keyboard navigation: booking, sign-in, sign-up, operator application and check-in/check-out forms can all be operated without a mouse, with a visible focus state on interactive elements.
• Colour and contrast: text and interactive elements are checked against WCAG AA contrast ratios; information (like booking status) is never conveyed by colour alone — it’s always paired with a text label.
• D/deaf and hard-of-hearing users: the site is entirely text- and image-based — we don’t currently publish any audio or video content. If we add video in future, we’ll caption it.
• Zoom and reflow: pages are built with a responsive layout that reflows for browser zoom and small screens rather than requiring horizontal scrolling.
• Reduced motion: the site avoids essential information conveyed only through animation.

Known limitations

Accessibility is an ongoing effort, not a one-off checklist — some parts of the site (particularly newer console screens) haven’t had a full accessibility audit yet, and third-party components we embed (like Stripe Checkout) are accessible to the extent Stripe has made them so, which is outside our direct control.

Let us know

If you hit an accessibility barrier anywhere on this site, or need booking information in a different format, please tell us — we treat these as bugs to fix, not feedback to file away. Email ops@airportparkingexchange.com and include the page you were on and, if you can, the assistive technology (screen reader, switch device, etc.) you were using — it helps us reproduce and fix the issue faster.