Home / Accessibility Statement
Accessibility Statement
We target WCAG 2.2 Level AA. Here is what that means in practice, and what we know is still imperfect.
How the site is built
The site is static HTML with one stylesheet and no client-side framework. That is deliberate. It means pages work with JavaScript disabled, load quickly on a slow connection, and behave predictably with a screen reader.
- One
h1per page, with headings in order and no skipped levels. - A skip-to-content link as the first focusable element.
- Visible focus outlines on every link, button and control.
- Tap targets at least 24 pixels tall on touch screens.
- Text reflows without horizontal scrolling down to 280 pixels wide, tested on ten viewport sizes.
- Data presented in real tables and definition lists rather than images of tables.
- Decorative elements, such as the direction arrow on a trip page, hidden from assistive technology.
- Colour never used as the only way to convey meaning. Peak fares are labelled as well as coloured.
Standard we aim for
We target WCAG 2.2 Level AA. We have not commissioned a formal third-party audit, so we describe this as our target rather than a certified result. Saying otherwise would be a claim we cannot back.
Known limitations
- Typefaces load from Google Fonts. If that request is blocked, the site falls back to system fonts and remains readable.
- Some station names are long and may wrap awkwardly at the very narrowest widths.
- Long timetables are presented as tables, which can be slow to navigate cell by cell with a screen reader.
Station accessibility is a separate thing
This page is about the website. Whether a station is step-free is a different question, and we publish that on each station page using the MTA's own accessibility data.
That data describes the station as designed and cannot tell you whether a lift is in service today. Check with the operator before you travel. See the disclaimer.
Tell us about a barrier
If something on this site is difficult or impossible to use, we want to know. Tell us the page, what you were trying to do, and what assistive technology and browser you were using. We treat these with the same priority as a wrong fare.