Built to be usable, and honest about what still is not.
The commitment
This site targets WCAG 2.2 level AA. Accessibility is treated as part of the build rather than a later audit.
What is in place
Every page starts with a skip-to-content link and uses semantic landmarks and a single, ordered heading structure.
All interactive controls are reachable and operable by keyboard, with a visible focus ring that is never removed.
Interface colours are chosen for contrast in both light and dark themes, and no information is carried by colour alone.
Motion respects your operating system's reduced-motion setting: entrance animations, the theme transition, and the rotating capability sphere all stop or shorten automatically.
Interface sound is off-by-default-capable, clearly labelled, and can be disabled from the header at any time.
The capability sphere is decorative; the same technologies are available to screen readers as a plain list.
Known gaps
Some areas are still being built, and new features can regress accessibility before they are reviewed.
Automated accessibility test coverage is not yet part of the build pipeline; checks are currently manual.
Embedded third-party content, such as a scheduling widget or a video player, is outside my direct control.
Reporting a problem
If something on this site blocks you, please tell me what you were trying to do and what got in the way. I treat accessibility bugs as defects, not feature requests.