Legal
Accessibility statement
This is a long-form reading site, so accessible reading is a functional requirement rather than an extra.
1. Our aim
We aim to align explorenesthorizon.xyz with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Accessibility is treated as an ongoing responsibility, reviewed whenever content or layout changes.
2. What we have built in
- Semantic structure — landmark elements, a single main heading per page and a logical heading order throughout.
- Skip link — a "Skip to main content" link is the first focusable element on every page.
- Keyboard support — navigation, accordions, tabs and the cookie controls are all operable by keyboard, with visible focus styling.
- Descriptive links — link text describes its destination rather than relying on "click here", and every button and card link leads to a real page or section of this site.
- Described diagrams — every tactical illustration has an accessible name and description, plus a written caption, and no information is conveyed by colour alone: shapes, dashes and in-diagram labels carry the meaning.
- Contrast — the orange, white and dark-charcoal palette is applied so that text and interface elements meet contrast requirements.
- Reduced motion — reveal animations and smooth scrolling are disabled automatically when a visitor's system requests reduced motion.
- Responsive layout — content reflows to a single-column reading layout on small screens with no horizontal scrolling.
- Data table semantics — the comparison rail uses proper table headers, a caption and row scope.
3. Known limitations
Tactical diagrams communicate spatial relationships. Although each one carries a text description and caption, some spatial nuance is inevitably easier to grasp visually. Where a diagram illustrates a point, that point is always also stated in the surrounding prose — see the tactic notes for examples.
4. Compatibility
The site is built with standard HTML, CSS and vanilla JavaScript and is designed to work in current versions of major browsers with assistive technology enabled. If JavaScript is unavailable, all editorial content remains readable; accordions and tab panels are written so that content is not permanently hidden by a script failure on first load.
5. Reporting a barrier
If any part of this site prevents you from reading it, we want to correct it. Please see the contact page for the current position on contact channels. Accessibility reports are handled as priority editorial fixes.