// accessibility

Accessibility

The target is WCAG 2.2 Level AA. Automated checks run on every build; the parts a machine cannot judge are listed honestly below rather than claimed.

What the site does

• Semantic headings and landmarks, with a skip link to the main content.
• Every interactive element takes a visible 2px focus ring at 2px offset.
• Text and interface colors are checked against AA contrast ratios on the dark ground.
• The only animations are a status dot and a small arrow nudge; both stop under prefers-reduced-motion.
• Images carry alt text, and an image without alt text fails the content build rather than shipping.
• Wide tables and code blocks scroll inside their own container so the page never scrolls sideways.
• Forms use real labels, inline error messages, and a polite live region for the result.
• The layout works from 320px up, and the navigation stays a single row rather than hiding behind a menu.

What is tested

Every pull request runs axe-core against the built pages at desktop and mobile widths, tagged for WCAG 2.0, 2.1, and 2.2 at A and AA. A failure blocks the build.

What is not yet verified

Automated tools catch roughly a third of accessibility problems. This site has not yet had a manual screen reader pass (NVDA, JAWS, VoiceOver), a keyboard-only walkthrough of every page, or testing at 400% zoom and with Windows High Contrast. Those are open items, not claims.

Known deviations

• The site is dark-only by design. There is no light theme yet; the color system is built so one can be added without touching components.

Reporting a problem

If something here is hard to use, tell me and I will fix it. Send a message with the page and what happened, and mention the browser and assistive technology if you can.