Accessibility

Updated October 22, 2026

We want Crossing Watch to be usable by everyone, including people who use screen readers, keyboards or larger text. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 level AA.

What we do

• Every crossing shown on the map can also be found without the map: search by crossing ID, road, city, county, railroad or address gives a text list, and "Near me" and My Crossings list crossings as text. These work with a keyboard and screen readers.
• Buttons, links and form fields have names that screen readers announce; images have text alternatives.
• Text meets the WCAG contrast ratios (4.5:1, or 3:1 for large text) in both the light and the dark theme.
• Every control works with a keyboard, and the keyboard focus is always shown with a visible outline.
• Pages have a language, a title, a main content area and headings in order, so screen readers can move around them.
• Animations are reduced when your device asks for reduced motion.
• Crossing alerts (Premium) arrive as normal notifications with your device's own sound, so they work without looking at the screen.
• Driving alerts in the phone app are sounds and notifications, so they work without looking at the screen.

How we check

On October 22, 2026 we checked every page of the website, in the light and the dark theme, with the accessibility tools built into Chrome (names of controls, text alternatives, contrast, page structure) and by keyboard, and fixed what we found. Automated checks do not catch everything, so we also rely on your feedback.

Known limits

• The map itself is visual. Use the crossing lists and search for the same information.
• Some train-time details are dense tables; we are improving how they are read aloud.

Feedback

If something is hard to use, tell us on the support form or email crossingwatch.support@gmail.com with the page and what happened. We reply within 5 business days and will help you get the information another way.