Accessibility

Accessibility philosophy

I want this site to work without requiring a particular screen size, input device, or motion setting. I treat accessibility as part of implementation and review, alongside semantics, keyboard behavior, contrast, and reflow.

The goal is to make the site understandable and usable across different devices, input methods, zoom levels, and motion preferences. Accessibility is also ongoing work. Content, browser behavior, and the site itself will continue to change, so this page describes the current approach rather than claiming formal conformance.

Current accessibility features

The site currently uses:

• Semantic HTML and landmarks that preserve a meaningful reading order.

• A consistent heading hierarchy to make pages easier to scan and navigate.

• Keyboard-accessible navigation, links, dialogs, and controls.

• Visible focus indicators for interactive elements.

• Responsive layouts that adapt to narrow screens and increased browser zoom.

• Semantic color tokens selected to support readable contrast.

• Reduced-motion behavior that respects the visitor's system preference.

• Text alternatives and captions for meaningful images where they are needed.

• Native controls and interaction patterns where they provide the clearest accessible behavior.

Automated checks, keyboard review, browser testing, and visual inspection are part of development. They help find problems, but they do not replace feedback from people using different assistive technologies and access needs.

Content is written for clear reading rather than visual effect. Links are intended to describe their destination, long passages use a constrained reading width, and essential information is not communicated by color alone. When a visual document cannot provide a complete accessible experience, the page includes a concise text alternative that explains its major sections.

Feedback

If you encounter an accessibility barrier or have trouble using any part of this site, email [email protected]. Please include the page and a brief description of the issue if you can. I will review the report and use it to guide an appropriate correction.