Accessibility

This documentation site is built to work well with keyboards, screen readers, and a range of visual needs. This page describes what's actually in place today, and where the gaps are.

Keyboard navigation

Every interactive element — sidebar links, search, code copy buttons, tabs — is reachable and operable with a keyboard alone. Focused elements show a visible outline, so you can always tell where you are on the page. Search opens with Cmd+K or Ctrl+K and can be fully operated with arrow keys and Enter, without touching a mouse.

Screen readers

Icon-only buttons (like the mobile menu toggle and code copy button) include text labels for screen readers even though they show only an icon visually. Headings follow a logical order on every page, which lets screen reader users jump between sections using their reader's heading navigation instead of reading top to bottom.

Color contrast

Body text, headings, and links are checked against the WCAG AA contrast standard (4.5:1 for normal text) against this site's dark background. If you notice text that feels too low-contrast to read comfortably, that's worth reporting — it's treated as a real bug, not a style preference.

Reduced motion

If your system is set to reduce motion, this site's animations (page transitions, hover effects) are automatically disabled rather than forced on you.

Where this falls short today

• This site hasn't been tested with every screen reader and browser combination — if something doesn't work well with the setup you use, let us know
• Some embedded code examples rely on color alone (syntax highlighting) to convey meaning, which won't fully translate for users with certain color vision differences