Keyboard use
Primary navigation, policy pages, dialogs, and buttons are intended to remain accessible to keyboard users.
AccessibilityAccessibility remains part of the public build, not an afterthought.
The site is intended to remain readable, keyboard-usable, and stable across common desktop and mobile browsers. Motion and consent controls are kept visible.
Readable motion
Motion is intended to remain restrained and functional. Where reduced-motion preferences are available on the device, the site should respect them where supported.
Contrast and legibility
Type, controls, and policy pages are intended to remain legible against the site’s dark visual system.
Reporting barriers
Accessibility barriers should be routed through the Contact and Accessibility pages with the affected route, device, browser, and a concise description of the issue.