Accessibility

A lot of the people who support this ride are not on the newest phone or the fastest connection, and some of them need larger text or a screen reader. This site is built for them.

What we are aiming at

The target is WCAG 2.2 Level AA. We believe the site meets it. That is our own assessment, not an audit by an outside firm, and we would rather say so plainly than imply a certificate we do not have.

What that means in practice

• Text meets the 4.5:1 contrast minimum against its background, and large text meets 3:1. Every page is checked automatically on a desktop and a phone layout before it goes live.
• Every control can be reached and used with a keyboard alone, in an order that matches what you see, and shows a visible focus outline when you get there.
• Form fields have real labels, say what went wrong when something is rejected, and never rely on colour alone to do it.
• Buttons and links say what they do. There is no "click here" and no icon-only control without a name a screen reader can read.
• Images that carry meaning have descriptive alternative text. Images that are decoration are marked as decoration so a screen reader skips them.
• Headings run in order so a screen reader can navigate by structure, and there is a skip link to jump straight to the content.
• The slideshow at the top of the home page has a pause button, and it does not start at all if your device asks for reduced motion.
• All animation stops when your device asks for reduced motion.
• Text reflows to a phone screen with no horizontal scrolling and stays readable zoomed to 200 percent.
• The site works with JavaScript switched off. You lose the map and the slideshow; you lose no information.

Where we fall short

Some older photographs carry text inside the image, and a few archived documents are scanned PDFs that a screen reader cannot read aloud. The route map is a visual map; every stop it shows is also written out as a name and a street address above it, which is the part you can act on. If you need the contents of any of those, email us and we will send the information as plain text.

Tell us about a problem

If any part of this site gets in your way, email us with the page you were on and what happened, and we will fix it. You do not need to know the technical term for it. This is the fastest route to getting it changed, and we would rather hear about it than not.