Compliance & accessibility

What AccessiFlow helps with

The widget gives visitors a browser-side control panel for 14 common accessibility adjustments: text size, line-height, letter-spacing, dyslexia-friendly font, contrast modes, color-blindness filters, reading guide / mask, text-to-speech, animation pause, focus indicator, and a structure outline. Each adjustment is a user choice, applied locally in their browser, cleared when they leave.

For many visitors this removes friction that the site’s default styling would otherwise leave in place — especially on sites built before the team prioritised accessibility.

What AccessiFlow does not do

The widget cannot

• Fix semantic HTML. If your headings skip levels, your buttons are styled <div>s, or your form inputs have no labels, a widget can’t rewrite your markup.
• Add meaningful alt text. Images without alt stay without alt.
• Make custom components keyboard-accessible. A carousel that only responds to drag gestures still only responds to drag gestures.
• Guarantee WCAG or ADA compliance. Compliance is a property of your whole site’s code, content, and workflows, audited by humans — not something a widget can certify.

The US DOJ, the European Commission, and multiple court rulings have been explicit: accessibility overlays do not by themselves bring a site into compliance. Several overlay vendors have been named in lawsuits for claiming otherwise. AccessiFlow doesn’t.

How we align with WCAG 2.1

The widget’s own UI targets WCAG 2.1 AA. That means the panel you see — not your underlying site — aims to be operable by keyboard, meet contrast ratios, expose ARIA roles, and work with screen readers.

Specifically:

• Everything is keyboard-reachable. Tab order is logical,Esc closes the panel, toggles are real input type="checkbox"s.
• Colour contrast on panel text meets AA (4.5:1) or better, including the pressed-state pills.
• Focus indicators are always visible on panel controls.
• The launcher has a descriptive aria-label in the visitor’s locale.
• Shadow-DOM isolation means the panel’s accessibility tree is clean regardless of how cluttered the host page is.

EAA (EU) and ADA (US) context

The European Accessibility Act (EAA) comes into effect 28 June 2025 for most consumer digital products in the EU — including e-commerce, banking, travel booking, and ebooks. The Americans with Disabilities Act has been interpreted by US courts to extend to websites of “places of public accommodation” since at least 2017.

Neither regime is satisfied by installing a widget. Both require that the underlying product be usable by people with disabilities, with documented conformance (usually WCAG 2.1 AA). AccessiFlow is a useful supplement for the friction that remains after that work — not a shortcut around it.

Privacy & the CCPA / GDPR

The widget sets no cookies. It stores per-visitor preferences in localStorage under the visitor’s origin and sends one anonymised beacon per session containing only a hashed session id, a coarse country code, and the site key. No PII, no IP, no cross-site tracking.

That means enabling AccessiFlow does not add to your GDPR or CCPA obligations — there is no identifiable personal data being collected through the widget. See our privacy policy for the full breakdown.

What you should do alongside the widget

1. Commission a WCAG 2.1 AA audit of your site with a qualified auditor (Deque, Scottish Accessible, Level Access — or a local equivalent).
2. Run axe DevTools, WAVE, or Lighthouse Accessibility as part of your CI.
3. Publish an accessibility statement that tells visitors how to reach you when something doesn’t work for them.
4. Then ship AccessiFlow. The widget takes care of the common friction points your audit won’t catch.

Questions? Email hello@accessiflowfiji.com and we’ll be honest.