Accessibility
Accessibility you can inspect
AbsoluteUI targets WCAG 2.2 Level AA and tests it automatically on every release. This page reports that testing and its scope. It is not a conformance claim for your application.
Latest run
Recorded 29 September 2026 at commit f9ec31d in Chromium bundled with Playwright (headless, Desktop Chrome profile).
Every release
What is tested automatically
axe-core scans
WCAG 2.0, 2.1, and 2.2 A and AA rules on every component harness page, in the default, dark, and high-contrast themes, with popups and edit modes open.
Keyboard flows
The documented keyboard matrix of each component, focus order, focus return, and no keyboard traps.
Reflow at 320 CSS px
No horizontal page scrolling (WCAG 1.4.10); two-dimensional surfaces scroll in their own region.
Reduced motion and forced colours
Animations removed under reduced motion; boundaries, focus, and selection stay visible in Windows contrast themes.
Theme contrast
Every role-token pair of every shipped theme against WCAG 1.4.3 and 1.4.11.
Strict CSP
Every harness page runs with script-src self, no inline styles, and Trusted Types enforced.
Themes
Contrast by theme
Measured with the same engine the Theme Designer uses.
| Theme | Pairs | Result |
|---|---|---|
absolute-default | 84 | All pass |
absolute-dark | 84 | All pass |
absolute-high-contrast | 84 | All pass |
Scope and known limits
Automated tools detect only part of WCAG failures. No third-party manual audit has been performed yet, and screen-reader behaviour has not been manually verified with NVDA, JAWS, and VoiceOver. A VPAT/ACR is not yet available.
Accessibility also depends on how components are composed and labelled, on your content, and on manual testing with assistive technology. Each component page lists its keyboard contract, ARIA roles, and known caveats.