A quiet room should open for everyone.

Conformance target

WCAG 2.1 Level AA, now — 2.2 AA, ongoing.

Our target is conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We treat WCAG 2.2 Level AA — the newer standard, which adds criteria around focus visibility, target size, and consistent help — as an active, ongoing goal we are working toward rather than a box we have already checked. This statement will be updated as that work lands.

What we’ve built

The concrete work behind the target.

• ·Semantic HTML throughout. Every page uses real headings, landmarks (header, main, nav, footer), and labeled form fields rather than div soup with visual styling standing in for structure.
• ·Keyboard-navigable forms and interfaces. Booking, checkout, the volunteer form, and the community wall can all be completed with a keyboard alone. The oracle's casting interface and the Gene Keys lens selector are both operable without a mouse or touch, with visible focus at every step.
• ·Alt text on imagery. Informative images (the guide's portrait, coin and booklet photography, chart illustrations) carry descriptive alt text; purely decorative imagery and background flourishes are marked aria-hidden="true" or given empty alt="" so screen readers skip them instead of reading noise.
• ·prefers-reduced-motion honored site-wide. Every page collapses scroll-reveal animation, the oracle's casting animation, and ambient decorative motion to near-zero duration when a visitor's system requests reduced motion — not just on one showcase page.
• ·Visible focus states. A consistent :focus-visible outline, in the site's gold accent color, appears on every interactive element in both themes — links, buttons, form fields, and the theme toggle.
• ·Contrast-checked dark and light themes. Both the dark-default palette and the light palette were built and checked against WCAG AA contrast minimums (4.5:1 for body text, 3:1 for large text and UI components), not just designed to look good and hoped for.
• ·A working skip link. Every page opens with a "Skip to content" link, visible on keyboard focus, so keyboard and screen-reader visitors don't have to tab through the header on every page load.

Known limitations

What we know still falls short.

We would rather name the gaps we know about than let this statement read as a claim of perfection.

• ●The ambient hero video and animated oracle-casting scene are decorative. Both are marked aria-hidden="true" and are not required to understand or use the page — the reading, its text, and every control needed to request or receive it are fully accessible without the animation ever running. Under reduced motion, the video is replaced with a static poster image and the casting scene renders in its resting state.
• ●Older or less common assistive technology combinations are not individually tested. We test primarily with current versions of VoiceOver, NVDA, and keyboard-only navigation in modern browsers; less common pairings may surface issues we have not yet found.
• ●Some third-party embeds inherit their own accessibility posture. The Google Meet video call for booked sessions and the Stripe checkout flow are built and maintained by those companies; we cannot directly fix an accessibility issue that originates inside their interface, though we will help you find a workaround and will pass confirmed reports upstream.
• ●PDF exports (readings, receipts) are generated programmatically. We tag headings and reading order where the export tool supports it, but we have not yet run a full PDF/UA conformance pass on every export template.

Compatibility

Built and checked against.

The site is built to work with current versions of major screen readers (VoiceOver, NVDA, JAWS) paired with current versions of Safari, Chrome, Firefox, and Edge; with keyboard-only navigation; with browser and OS-level text resizing up to 200% without loss of content or function; and with both light and dark operating-system themes, in addition to the in-page theme toggle.