Accessibility statement

How accessible this site is

We are aiming for the Web Content Accessibility Guidelines version 2.2 at level AA. We believe this site is partially conformant with that standard: it was designed against it from the start, but it has not been independently audited and the gaps listed below are real.

What has been built in

• Every page is built from real headings, lists, buttons and links, so screen readers and browser reading modes can make sense of the structure.
• Every form field has a visible label above it. Placeholders are examples, never the only label.
• Errors are written in plain language, appear next to the field they belong to, and are announced when they appear.
• Status is never shown by colour alone. Errors and confirmations carry an icon and words as well.
• Body text is at least 16px and meets a contrast ratio of 4.5:1 or better against its background.
• Everything can be operated by keyboard, in a logical order, with a focus ring that is always visible and never removed.
• Buttons, links in lists and form controls are at least 44px on their shorter side — well above the WCAG minimum of 24px.
• A skip link goes straight to the main content.
• Expandable sections use native browser disclosure controls, so they work with or without JavaScript.
• The layout reflows to a single column and stays usable at 200% zoom and on a 360px-wide screen.
• Animation is limited to small state changes, and is removed entirely if your device asks for reduced motion.
• Pages are readable without JavaScript. The booking form needs it; the phone number does not.

What we know is not right yet

Listing these is the point of a statement like this one. If you hit something that is not here, please tell us.

• This site has not yet had an independent accessibility audit. Everything above comes from our own testing, so it is a self-assessment.
• We have not yet tested with every screen reader and browser combination. Testing so far has covered common desktop and mobile pairings, not all of them.
• Address entry is a plain text field for now. The predictive address search that will replace it has to be fully keyboard operable and announced before it goes live.
• The fare table scrolls sideways on narrow screens. It is marked up as a proper data table with row and column headers, but the sideways scroll is awkward on a small phone.
• Date and time fields use your browser's own controls. Those are accessible, but they behave differently from one browser to another and we cannot change that.
• When card payment is connected, part of that step will be provided by a payment company. We will test it and say here what we find.
• PDFs, if we ever publish any, are not yet covered by this statement.

Accessible vehicles and travelling with support

This statement is about the website. What the vehicles themselves can do is a separate question, and it is one we will answer honestly rather than optimistically: please call and ask, and the office will tell you exactly what can be arranged for your journey and with how much notice.

An assistance dog travels with you. That is a legal right, and no driver licensed to carry passengers may refuse it or charge extra for it.

Anything you tell us about a health condition or disability is treated as sensitive information: access to it is restricted to the people arranging your journey, and access is logged. See section 4 of our privacy notice.

Tell us about a problem

If you cannot do something on this site, we want to know which page, what you were trying to do, and what you were using — the browser, the phone, any assistive software. That is usually enough for us to reproduce it.

Call 01206 701701, email info@abairporttransfers.co.uk, or use the message form. If you would rather make it a formal complaint, our complaints procedure sets out the timescales we work to and how to escalate it.