Accessibility statement

This site is built with the goal of full WCAG 2.2 level AA conformance across every reading and interaction path, including the ones that don't use the 3D map.

Conformance target

Unfinished targets WCAG 2.2 level AA. Automated checks (axe-core) run against every page template in continuous integration and block deployment on any violation. A manual audit protocol — keyboard walkthrough, screen-reader script, 200% zoom/reflow check, and forced-colors mode check — is run before each release; see docs/accessibility.md in the project repository for the full checklist.

What's covered

The interactive 3D map is one way to explore this project's questions and ideas, not the only way. Two fully accessible surfaces expose everything the map does:

• The Index lists every entity with filters, sorts, and real links — no map required.
• Every question, claim, concept, writing, territory, source, person, and path has its own server-rendered page listing every labeled connection as real, keyboard-reachable links.
• The map itself includes a DOM mirror list of every node (reachable and operable by keyboard), live-region announcements on selection, visible focus, and a static SVG fallback for browsers or devices that can't run WebGL.

Known limitations

• The editorial admin workbench (/admin) is a development-only tool, available only when running the project locally, and is English-only. It is never part of the public production site.
• Spanish translation coverage is complete for the current corpus (every entity has a Spanish version). If new content is ever published before its Spanish translation is ready, the page shows the English original with an honest on-page notice rather than hiding the content.
• The manual screen-reader audit protocol currently covers NVDA and VoiceOver on the core reading and navigation journeys; it does not yet cover every assistive technology combination.

Feedback

If you hit an accessibility barrier anywhere on this site, please open an issue in the project repository or reach out via the contact details on the home page. Specific page URLs and the assistive technology you were using help the most.

This statement was last reviewed 2026-09-09.