Shangralachia
Access belongs in the path
A private site is still a site people have to be able to use. Shangralachia should work without requiring a particular body, device, input method, or way of reading.
Last reviewed
The target
Shangralachia targets the Level A and AA success criteria of WCAG 2.2 across every page, public and members-only alike. This is an ongoing self-assessment, not third-party certification, and not a promise that no one will ever hit a barrier.
The same target is used by earthsong.io, so the two sites make one consistent claim.
What this site supports
- Semantic landmarks — every page has a
mainregion, and a skip link is the first thing a keyboard reaches - Full keyboard operation, with a visible focus indicator on every control, on both the light and dark surfaces
- Text contrast of at least 4.5:1, and 3:1 for interface components. The brand palette is pinned to those ratios and checked by a script rather than by eye
- Form fields with real labels, errors announced to screen readers, and support for password managers and autofill
- Reduced-motion support, honoring the setting in your operating system
- Layouts that reflow to narrow widths and tolerate zoom
What it deliberately has none of: autoplaying audio or video, flashing content, drag-only interactions, and accessibility overlays or automated remediation widgets.
The policy
Scope
The target covers every page this site serves — the public pages and the whole members area alike.
Applications embedded from elsewhere are outside it. So are external destinations and whatever calendar app opens a downloaded .ics file.
How we test
The August 2026 self-assessment covered:
- a source-level audit of every page and component for landmarks, heading order, accessible names, and form semantics
- contrast ratios computed from the actual color tokens rather than estimated — the check runs from a script in the repository and fails the build if a pair regresses
- keyboard-only navigation of every page and form
- automated checks in the test suite, run on every change
That assessment found real problems, and they were fixed before this statement went up. Source-level and automated checks are useful and incomplete; they are not a substitute for testing by people with disabilities.
Known limitations
- No independent third-party audit has been done.
- There's no formal assistive-technology test matrix. VoiceOver and NVDA have not been run systematically across the site.
- The tools embedded on the Tools and Adventures pages are other people's applications. They haven't been assessed and can't be fixed here.
- Trip briefings are authored content rather than application pages, and get a lighter review than the app around them.
- The briefing PDFs are not tagged. A PDF without tags has no reliable reading order or table structure for a screen reader. The PDF exists to be printed and carried where there's no signal — treat the HTML briefing as the accessible version, not the PDF.
- Some trip tables are wide enough to need horizontal scrolling on a small screen.
Report a barrier
If something here blocks you, say so and it gets fixed. Tell any TAG admin directly.
It helps to know what you were trying to do, the page you were on, and the browser and any assistive technology you were using — but a one-line "this doesn't work" is a perfectly good report and better than silence.
Changes
Meaningful changes to this statement will be dated on this page. The conformance target itself won't be lowered to make the claim easier to keep.
Maintenance
This statement is maintained alongside the site and reviewed when anything ships that changes how a page is built.