This site works by keyboard and screen reader; the ground it links to is graded honestly, not rated compliant.
Two different questions live on this page. One is whether you can read and use jaspertrailguides.com. The other is whether a given mile of trail will actually work for your knees, your chair, or your kid's short legs. We answer both straight, and we keep them separate.
What we build into the site
We built this site as plain HTML with real headings, real landmarks, and real form labels, aiming at WCAG 2.1 Level AA as an internal target rather than a badge to display. That means a skip link at the top of every page that jumps straight past the header to the content. It means every navigation link, button, and form field carries text a screen reader can announce, not just an icon. It means focus is visible everywhere: tab through this page and you will see a solid orange outline follow you, not a faint dotted line that vanishes into the grey background.
Colour is never the only signal. The mega-menu under "Services" opens with a visible state change on the button itself, not just a colour shift on the panel. Form errors show up as text next to the field, read aloud by aria-describedby, not as a red border alone. Tap targets across the site, including the stepper buttons on the Trip Fit Checker, sit at 44 pixels or larger so a shaking hand or a gloved thumb can still hit them.
Motion is minimal by design, which happens to help here too. The one animated moment on the site is the hero photograph settling into place on first load, and it turns off automatically if your operating system is set to reduce motion. There is no autoplay video, no parallax, no scroll-triggered reveal that a vestibular disorder has to fight through.
- Semantic headings in order, one
<h1>per page, no heading skipped for visual effect. - Every image on this site carries written alt text describing what is actually in frame.
- Forms validate on blur and on submit, and the error list at the top links straight to the bad field.
- The chat widget traps focus while open and closes on Escape, returning focus to the button that opened it.
- Text resizes with the browser's own zoom; nothing is fixed in pixels that should scale.
Where it still falls short
Seven of us run a trail crew. None of us is a full-time accessibility engineer, and we are not going to pretend the site is finished just because it passes a checklist. Two known gaps as of this writing: the mega-panel under "Services" relies on a mouse-hover expectation for sighted users who never touch a keyboard, even though keyboard and touch both work correctly if you use Tab or a tap. Second, our JSON-LD structured data helps search engines read the page, but it is not a substitute for the visible content, and we have not audited every third-party font render at every zoom level above 300 percent.
If you hit a barrier we have not listed here, that is more useful to us than a barrier we already know about. Tell us. See the reporting section below.
Reading a trail grade before you book
None of our trails are built or rated to the Forest Service accessible-trail standard. We are not going to describe eroded root-and-rock tread on a Berkshire foothill as wheelchair accessible when it is not, and we are not going to soften a grade to sell a booking. What follows is the same honest read our guides give over the phone, laid out so you can judge it before you call rather than after you show up at a trailhead.
Maintained tread, gentle grade
Regraded sections we have rebuilt or drained within the last three years: firm footing, moderate slope, occasional hand-set stone step. Still not level, still not paved, and a cane or trekking pole helps more than it should have to.
Rock-and-root ridge tread
Most of our ridge mileage. Exposed roots, loose stone, and short scrambles over ledge. This is where the Summit Trek and most of the Ridge Walk route run. Ankles need to be sound and eyes need to be on the ground, not the view.
Off-trail navigation legs
Bushwhack sections used on the Backcountry Navigation Course and some multi-day traverses. No tread at all: compass bearing, deadfall, and wet ground. We do not run these with anyone who has not already done a marked-trail day with us first.
A grade like these tells you what to expect underfoot. It does not tell you what your body can handle on a given day, and only you know that. Call before you book if a route description leaves that open.
What footing means on our ground
Blue paint blazes fade to grey in about four years under hemlock canopy, which is why we repaint on a three-year cycle rather than let someone lose a trail at dusk. That has nothing to do with mobility, but it matters here for the same reason: our trails are working infrastructure, not a finished product. A section that was smooth in June can be root-slick by October rain, and a step we set two seasons ago can heave loose after a hard frost. When a guide tells you a route is fine, that guide has usually swung a rock bar on that exact mile within the year.
We do not carry lift equipment, and we do not have a version of any route built for a wheelchair or a walker. If you use one, tell us before you book, not after; we will tell you plainly which of our routes, if any, could work with an assist from a companion, and where the answer is simply no.
Asking for a change on a trip
We turn down trips when a group's stated experience does not match the terrain. That call has cost us bookings and it will keep costing us bookings, and it applies here too: we would rather adjust pace, route, or group size in advance than have someone struggle two miles from a trailhead. Tell the guide leading your trip about a hearing aid, a service animal, a slower pace, a medical condition, or a need for more frequent stops, and we will plan around it before the day starts, not during it.
Some accommodations are easy: a slower pace on the Ridge Walk Half-Day, a shorter loop instead of the full Summit Trek, an extra stop built into a Private Family Trek. Others are not possible on our terrain no matter how far in advance you ask, and we will say so rather than promise something the ground cannot deliver.
Reporting a problem with this site
Use the short form below for a digital barrier: a form field a screen reader skips, contrast that fails at a specific zoom level, a control that will not take focus. A person on the crew reads every submission. We do not have a large development team behind this site, so a fix might take a week rather than a day, but you will hear back either way, including if the honest answer is that we cannot fix it soon.
Common questions
No. None of our tread meets the Forest Service accessible-trail standard, and we do not describe any of it that way. A grade rating on this site tells you what the footing and slope are like, not that a wheelchair, a walker, or a stroller with small wheels will get over it.
Yes. The person who answers the phone has usually walked the mile you are asking about, and can tell you about root height, water crossings, and where the exposed ledge sections sit on a given trail.
Every input carries a programmatic label, the result panel is announced through aria-live once you press Check Fit, and the same result is reachable by pressing Enter from any field, so a screen reader user or a keyboard-only user gets the same outcome as someone dragging a slider with a mouse.
A person on the crew reads it, not a ticket queue. We will tell you honestly whether we can fix it, when, and if there is a workaround in the meantime, such as taking the request by phone instead.