In development, not yet available to install

A banner everyone can use.

The ConsentAlly banner and preference centre are being built to meet WCAG 2.2 AA: every control works from the keyboard, focus is managed and is only trapped inside a modal while it is open, changes are announced to screen readers, every target is at least 44 by 44 pixels, above the 24 by 24 that AA asks for, and the layout holds at 200% zoom.

What that means in practice

• Tab will reach every control in a sensible order, and the focus indicator will always be visible.
• A reject-all control as prominent as accept-all will be on by default, with nothing hidden or styled to be missed.
• The banner will use correct ARIA roles and labels and announce state changes through live regions.
• Right-to-left languages will lay out correctly.

Isolated from the store's theme

The banner will render in a shadow root with its own stylesheets, so the store's CSS cannot break it and it cannot break the store. It will need no unsafe-inline for scripts or styles, so it can run under a strict Content Security Policy.

Respects the visitor's settings

Reduced motion will turn animations off, and the visitor's contrast and colour-scheme preferences will be followed.

Why it matters for a store

The banner is the first thing a visitor meets on the way to a purchase. If it cannot be used, the shop cannot be used.

Tested before launch

Keyboard and screen reader testing with NVDA and VoiceOver, and an audit by Inclusify, Magebit's accessibility product, are on the launch checklist.