Accessibility

Keyboard use

Every interactive element — navigation, choices in a dilemma, perspective cards, the reflection form — is reachable and operable with a keyboard alone, with a visible focus outline distinct from hover. A dilemma can be completed start to finish without a mouse or touchscreen. A "skip to content" link is the first focus stop on every page, ahead of the navigation.

Screen readers

Pages use real heading structure and landmarks (one page title, a primary navigation region, a footer navigation region) rather than styled text standing in for headings. Decorative illustrations are hidden from assistive technology; the meaning they carry is always also present as real text next to them, never only in the picture.

Motion

If your system is set to reduce motion, this site honours it site-wide: animation and transition durations collapse to effectively zero. Nothing here relies on motion to convey information that isn't also stated in text.

Color and contrast

Light and dark mode share the same set of design tokens, so a color decision made for one theme is deliberately re-checked for the other rather than left to whatever the browser happens to compute. Interactive elements meet a minimum 44×44px touch target. No choice, option, or answer in a dilemma is ever distinguished by color alone — color is never the only signal carrying meaning.

Reading level and structure

Reading level and clear structure are part of the editorial review checklist every dilemma goes through before publication — see our editorial policy. Text reflows at 200% browser zoom without loss of content or function, and body copy is capped at a comfortable line length rather than stretching full-width on a wide screen.

What we know is incomplete

This is a small, actively built site, and an honest accessibility page names gaps rather than hides them. As of this review, the site has not yet had a full automated and manual audit against every WCAG 2.2 AA success criterion — the gates that run before every deploy check for critical and serious automated violations on the primary templates, which is real coverage but not a substitute for a complete audit. If a gap affects you, please tell us — see below.

Reporting a problem

If something doesn't work with a keyboard, a screen reader, magnification, or reduced motion, use contact and corrections and say which browser and assistive technology you were using — that's the fastest path to a fix, and accessibility problems are treated as bugs, not feature requests.

Last reviewed 2026-09-16.