Light, dark, or automatic.
The site follows the operating-system preference by default and remembers an explicit choice without requiring an account.
Accessibility
Control only works when people can use it.
Identity and recovery workflows often appear on difficult days, unfamiliar devices, low bandwidth, or under stress. Accessibility is therefore part of security, continuity, and product correctness—not a visual polish pass.
This is a product commitment and assurance program, not a claim of formal WCAG certification.Product standard
Preferences should belong to the user.
Reduced means reduced.
Decorative movement and transitions are disabled or simplified when the device requests reduced motion.
Keyboard from start to finish.
Visible focus, semantic headings, skip navigation, descriptive page titles, and native controls support non-pointer navigation.
Zoom without losing the task.
Layouts reflow for small viewports and large text instead of relying on desktop-only fixed canvases.
Plain before clever.
Consequential actions explain the effect, reversibility, audience, and recovery consequence in direct language.
No single ability as the only key.
Authentication and recovery design must consider visual, motor, cognitive, hearing, device, language, and connectivity constraints.
Testing direction
Automated checks are the floor.
Recovery that excludes you is not recovery.DUIID accessibility principle
Release testing should include keyboard-only operation, screen readers, 200–400% zoom, text spacing, high contrast, reduced motion, touch targets, orientation, error recovery, slow networks, and cognitive load.
Critical journeys—sign-in, device enrollment, delegation, revocation, recovery, emergency access, export, and closure—need task testing with people who use assistive technologies. Passing a linter does not demonstrate that a person can safely finish the workflow.
Our target is WCAG 2.2 AA for public and core product experiences, with higher clarity and contrast where a security decision warrants it. Formal conformance will be claimed only after scoped evaluation and documented exceptions.
Tell us where the product creates a barrier.
Describe the page, assistive technology, device/browser, task, and what prevented completion. Screenshots or recordings help, but never include passwords, recovery material, or other sensitive data.