Accessibility

This page was last updated on Sep 29 at 12:51 PM.

Published Aug 30

Digital accessibilityUX designInformation designPlain-language writing

Summary

Version 0.1 should be usable by as many people as reasonably possible across devices, abilities, languages, and connection conditions. The release targets WCAG 2.2 AA.

Interface requirements

The website uses semantic structure, keyboard access, visible focus, clear labels, sufficient contrast, understandable errors, and reduced-motion support where relevant.

Responsive access

Content and essential actions should work across current desktop and mobile browsers without requiring a precise screen size, pointer device, or high-performance connection.

Testing

Accessibility is part of release acceptance. Automated checks should be combined with keyboard testing, screen-reader testing, zoom and reflow checks, and review of the principal user journeys.

Ongoing work

Reported barriers should enter the issue process described in Waitlist, contributing, feedback, and issue reporting. Accessibility requirements should be reviewed whenever the interface or content changes.