Testing tools should be operable
XZETO is designed toward WCAG 2.2 AA fundamentals, with honest notes where hardware-focused interactions create unavoidable constraints.
Keyboard navigation
Navigation, forms, buttons, disclosure widgets, and non-keyboard tool controls use native focusable elements with visible focus rings. Keyboard-capture tests require an explicit entry action and provide a visible exit action so users are not trapped.
Screen readers and status
Headings follow the visual hierarchy, controls have text or accessible labels, and important status changes use polite live regions. Fast-changing raw metrics are summarized rather than repeatedly announced.
Color, motion, and sizing
Meaning is paired with text or icons rather than color alone. Light and dark themes use semantic tokens and visible boundaries. Interactive targets are at least 44 by 44 CSS pixels. The interface respects prefers-reduced-motion.
Known limitations
Some tests are inherently visual, auditory, or depend on physical input. Display patterns, subjective audio checks, pointer traces, and controller axes may not have an equivalent sensory result. Where possible, the page includes text instructions, numeric summaries, skip controls, and alternative related tools.
Send feedback
If a control is unreachable, a status is unclear, text does not resize, or a test conflicts with assistive technology, use the Contact page and select Accessibility feedback. Include the page and browser, but do not send raw recordings or sensitive screenshots.