Native semantics
- Real buttons and switches, never clickable divs
- Every icon button has an accessible name
- Active profiles expose selected state, not just colour
- Grouped controls announce their group
What the panel does, and what it doesn't.
Changes one visitor’s view, never your code.
Why we don't sell the panel as compliance
A widget doesn't fix the underlying site.
In 2025 the FTC ordered accessiBe to pay $1M1 over claims its widget made sites compliant. About 1 in 52 US accessibility lawsuits still targeted sites that already had a widget. And 83.9%3 of the top million home pages have low contrast text, which only a code fix removes.
1 in 5: EcomBack, 456 of 2,014 lawsuits. Figures current at publication.
Explore an illustrative comparison.
Example states only. Run an audit for measured findings.
Drag or use arrow keys. The score reflects code changes.
Illustrative sample scores · no scan is run by this slider
Accessibility in the panel itself.
Most overlays fail their own audit. Ours meets the standard we apply to you.
Keyboard and focus
- Focus is contained while the panel is open
- Escape closes it and focus returns to the trigger
- Targets are at least 44×44 CSS pixels
- Nothing depends on hover or a fine pointer
Held to it publicly
Designed for keyboards, assistive technology and display preferences. Complete journeys still need human testing.
Panel barriers get our highest priority.
The panel your visitors open
Profiles, Content, Color, and Orientation groups as they appear on a live site.
Questions worth asking first
About performance, settings and accessibility limits.
Does installing the panel make my site compliant?
No. The panel changes preferences, not markup or audit findings.
Will it interfere with screen readers or a visitor's own settings?
It respects system settings and stays dismissed once closed.
Will it slow my site down?
The script loads asynchronously, and the panel loads only when opened.
Does the panel itself pass an accessibility audit?
Yes: native controls, real labels, contained focus and 44px targets.
Can I match it to my brand?
Yes: position, colour, icon and language. We warn you if colours fail contrast.
What data does the panel collect?
Only their settings and total usage counts. No page content, no visitor profiles.
Is a widget enough for the European Accessibility Act?
No. The EAA judges the product itself, not an add on. Overlays don't make a site compliant.
Why ship a panel at all if it is not compliance?
Preferences help people today. Code fixes take a sprint. Both matter.