Skip to content

Accessibility statement

Accessibility

How the QFlow Design System meets WCAG 2.2 AA, how we test it, what teams using it must do, and how to reach us.

Our commitment

QFlow builds software for people who serve the public and for the public itself, so the QFlow Design System is built to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That target is stricter than both Section 508 of the Rehabilitation Act (WCAG 2.0 AA) and the ADA Title II rule for state and local governments (WCAG 2.1 AA, from 24 April 2027 for large public entities).

This statement covers the design system: its tokens, elements, templates and patterns, as published on this site. Products built with it need their own evaluation.

How we test

  • Every page of this site, including one page per element, runs through an automated gate in the light and the dark theme: static checks of the markup, CSS and scripts, and browser checks with Playwright and axe-core (contrast, keyboard operation, focus visibility and order, target size, reflow at 320 pixels, 200% zoom, text spacing, motion and ARIA state).
  • Known problems are tracked as debt. Debt never counts as passing.
  • An element shows WCAG 2.2 AA · Passed only when the gate finds nothing on its page, and Approved only after a named person has run its manual checklist (General, Zoom, Keyboard, Screen reader). The date last checked, the date last approved and the approver are shown with it.
  • Automated testing cannot establish conformance. A certified WCAG engineer makes the final determination manually; the chip and the conformance report are evidence for that review, not a substitute for it.

Current status: Test status (77 checked, awaiting approval · 1 contract not yet reviewed). Gate: run 358b316 on 2026-10-22.

What teams using the system must do

  • Follow each element’s Accessibility guidance: keyboard map, roles and names, focus.
  • Test your implementation too. Labels, reading order, announcements and content come from the screen that composes the elements, and need their own keyboard and screen reader check.
  • Keep the token pairings: a custom color or a literal value can break contrast in one theme.

Known limitations

Elements with findings are listed on Test status, with each finding’s check and theme. The conformance report states each WCAG 2.2 criterion’s level of support.

Feedback

If something in the design system is hard to use with your assistive technology, or you need this content in another format, email accessibility@qflow.com. Tell us the page, what you tried and what happened. We aim to reply within five business days.

This statement was last reviewed on 2026-10-20.