Keyboard access
Critical tasks should work without a mouse and show clear keyboard focus.
We design toward WCAG 2.2 Level AA practices and continue to test the experience across devices and assistive technologies. This is not a claim of independent certification or complete conformance.
Critical tasks should work without a mouse and show clear keyboard focus.
Headings, landmarks, labels, status messages, and descriptive actions support assistive technology.
Content should reflow across mobile screens and increased text or zoom sizes.
Nonessential motion is reduced when the device preference requests it.
Errors should identify the problem, preserve work when safe, and explain the next step.
Evidence, assumptions, estimates, approvals, and confirmed outcomes are labeled clearly.
Automated checks do not replace testing by people who use assistive technologies, and no single test proves complete accessibility across every browser, device, or tool.
Reporting a barrier: include the page or task, what you expected, what happened, your browser or device, and assistive technology when relevant. Do not include passwords, keys, tokens, confidential customer content, regulated records, or other sensitive information.