Crew GO!Everyone gets home.
Crew GO! gets used in the worst conditions a screen ever faces: one hand on a bag, a gate agent talking, bright sun through a terminal window, and a four-hour-old pair of eyes at the end of a red-eye. Designing for that is the same work as designing for a screen reader, a switch, voice control or a 200% font — so we treat it as one job, not as a feature for somebody else.
What we aim for
We are working to WCAG 2.2, Level AA on this website and in the app.
We are not claiming we have finished. Below is what is done, and under it what is not — written plainly, because an accessibility statement that overstates itself is worse than no statement at all.
What is done
- Real headings, lists, labels and landmarks, so a screen reader can move through a page instead of reading it as one block.
- Everything works from a keyboard, with a focus outline you can actually see.
- Nothing is explained by colour alone. A delay, a status or a warning is always written in words as well.
- Text meets AA contrast, and the colours are fixed in one shared stylesheet rather than chosen page by page, so a new page cannot quietly fall below it.
- Pages work at 200% zoom and at phone width without sideways scrolling.
- No time limits, nothing flashes, and nothing moves on its own. The app honours your phone's "reduce motion" setting.
- This site needs no JavaScript to read. The only script on it checks whether the page has been republished.
- Tap targets are at least 24×24 px, or spaced far enough apart to make up for it (WCAG 2.2's new 2.5.8).
- Nothing you drag is the only way to do something — dragging always has a tap or a button alternative (2.5.7).
- Help is in the same place on every page, and nothing asks you to type the same thing twice (2.4.13, 3.3.7).
- Signing in needs no puzzle, no memory test and no copying a code from one place to another by hand, and it works with a password manager and with Face ID or Touch ID (3.3.8).
What is not done
- Nobody who relies on assistive technology has tested Crew GO! for us. Our checks are our own, and our own checks are the weakest kind. If you use a screen reader, a switch, magnification or voice control and you are willing to tell us what breaks, we would rather hear it from you than guess — and we will act on it.
- Our automated checks read the markup of each page. They do not drive a real browser, so they cannot measure focus order or contrast as drawn. Those are checked by hand when the design changes.
- The app has not been audited against 2.2 end to end. It is built to the list above, but "built to" is not "audited against".
- Flight and airport data arrives from outside feeds as plain text we do not control. Some airline and airport names come through abbreviated or in capitals.
- Some of the densest parts of the app — a full airport board, a routing with several legs — are tables of numbers. They are readable, but they are not yet as pleasant with a screen reader as the simpler screens.
If something does not work
Email support@crewgotravel.com. Tell us the page or screen, what you were using, and what happened. We aim to reply within 3 business days.
And if a part of Crew GO! will not work for you, we will do the thing it would have done. Email us what you needed — a routing looked up, a load asked about, a sign-up completed — and a person will do it and write back. That is not a lesser service; it is the same service through a different door, and it stands until the thing itself is fixed.
How to complain further
If we do not put something right, see Complaints for where else to take it. You never have to come to us first.