Accessibility

Last updated November 2, 2026

We want everyone to be able to read TrailCircuit and plan an outing with it. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.

What we do

• Every page has a "Skip to content" link, a clear heading structure and labelled navigation.
• Pages are built to work with a keyboard, and focused links and controls show a visible outline.
• Article images have text descriptions, and decorative images are hidden from screen readers.
• We choose colors to meet contrast requirements, and design pages to work when zoomed to 200% or on a narrow screen.
• Form fields have labels, and error messages say what to fix.
• The park finder's results are a list as well as a map, so you can browse and compare parks without using the map.

Known limits

• The park finder's map is visual. Everything on it is also in the results list and on each park's page, but the map itself isn't fully usable with a screen reader.
• Signing in with Google opens Google's own window, and the contact form's spam check is run by Cloudflare. We don't control how accessible those are. If the spam check stops you, tell us another way, such as asking someone to send a message for you, and we'll help.
• Older articles may have tables or image descriptions that could be clearer. We fix them as we find them.

Tell us about a problem

If something on TrailCircuit is hard to use, or you need information in another format, let us know through the contact form and choose "Accessibility problem". Tell us the page address, what you were trying to do, and the device, browser and assistive technology you use. We aim to reply within 5 business days.