The short version: the hand-built Loopo components are built to be keyboard and screen-reader friendly, with the gaps listed below. The generated components, converted from Figma, give you the exact look but not the behaviour: you add buttons, roles and focus handling when you wire them up. Each component page says which kind it is and what to add.
Our target
We aim for WCAG 2.2 level AA in the components and on this site. We don’t claim conformance yet: the results below show where we are, and this page changes as we fix things.
What we test and how
- Automated check. axe-core 4.14.0 in headless Chrome. WCAG 2.0, 2.1 and 2.2 level A and AA rules, plus axe best practices. Page-level rules (landmarks, page heading, document title) are off for components.
- Generated components. A sample spread over all six systems and their categories (48 in the latest run), rendered from their published code exactly as the component pages show them.
- Hand-built components. All 26 interactive Loopo components, checked live on their pages.
- Keyboard. On the hand-built components, a scripted pass Tabs through each one, checks that focus is visible and the control has a name, and opens and closes the dialog, menu and select with the keyboard to check focus moves in and comes back. Tabs are checked with the arrow keys.
- Code review. Every published generated file (1,708) is scanned for native controls, roles and ARIA.
- Visual match. Separately, every generated component is compared pixel by pixel with its Figma original; that score is on each component page.
Not yet tested: screen readers by hand (VoiceOver, NVDA, JAWS), zoom to 400% and reflow, Windows high-contrast mode. The check is a script in our repository, and the date at the top of this page is its latest run.
Latest results (15 November 2026)
74 components checked; 26 had no WCAG A or AA issue that axe can detect. Automated tools find only part of real accessibility problems, so a clean result is a floor, not a pass.
| System | Checked | No A/AA issues |
|---|---|---|
| Loopo | 34 | 18 |
| Auton | 8 | 2 |
| MailPulse | 8 | 2 |
| Axon | 8 | 3 |
| Veriq | 8 | 1 |
| Vantage | 8 | 0 |
Top issues by number of components
Elements must meet minimum color contrast ratio thresholdsWCAG AA, serious
48 components, 218 elements. For example loopo-paypal-integration-card-18953638.
ARIA toggle fields must have an accessible nameWCAG A, serious
1 component, 6 elements. For example data-table.
Table header text should not be emptyBest practice, minor
1 component, 1 element. For example data-table.
Heading levels should only increase by oneBest practice, moderate
1 component, 1 element. For example empty-state.
Keyboard pass
40 of 40 Tab stops in the hand-built components had a visible focus change and an accessible name. select: opens from the keyboard with focus inside, Escape closes it, focus returns to the trigger. dropdown-menu: opens from the keyboard with focus inside, Escape closes it, focus returns to the trigger. dialog: opens from the keyboard with focus inside, Escape closes it, focus returns to the trigger, focus stays inside while open.
This website
We also ran axe on 6 pages of this site. It finds: elements must meet minimum color contrast ratio thresholds; all touch targets must be 24px large, or leave sufficient space. The contrast issues are the light grey section labels in the sidebar; the small targets are the footer links. Both are on our list.
Known gaps
- Generated components are visual only. Of 1,708 published files, 0 use a native button, 0 a native input, 0 an ARIA role and 0 an aria-label; icons are hidden from screen readers. They are a pixel-accurate skin: swap drawn controls for real ones (the free Loopo primitives show how) before you ship. axe can’t see this, because a picture of a button made of <div>s isn’t a broken button to a scanner.
- Colour contrast. The most common issue by far. Light grey secondary text and white text on some accent fills fall below 4.5:1 in every system, including the Loopo tokens (muted #747474 on the sunken grey, faint #a6a6a6 on white, white on the danger red). This comes from the Figma designs, so the fix is in the design tokens, not in single components.
- Focus styles that depend on this site. Tabs and the segmented control have no focus ring of their own. They pass our keyboard check because this site adds a global focus ring; in your app, add one.
- Charts. Hand-built charts have a label naming the chart but no values in their text alternative; generated charts have none. Each chart page says what to add.
- Smaller gaps in hand-built components. Delta chips don’t say “up” or “down” in text; the data table’s row checkboxes have no labels and the sort state isn’t exposed; the segmented control has no arrow-key support. They are listed on each component’s page.
- No dark mode or reduced-contrast themes yet. Dark mode is planned; follow it in the changelog.
An ACR/VPAT for procurement is planned for the core components, after these gaps are closed.
Report a problem
If a component or a page on this site doesn’t work for you, email support@ingotui.com with the page link and what happened (your browser and any assistive technology help). We reply by email and note fixes in the changelog.