Skip to content
Consent Experience

Ask clearly

Beta

A dialogue nobody can dismiss is not a choice.

The consent UI is tested for keyboard navigation, focus trapping and restoration, screen-reader labelling, contrast and reduced-motion behaviour — because it is a modal interruption on every first visit, which is the worst possible place for an inaccessible control.

Accessibility

  • Keyboard navigation
  • Focus trap & restore
  • Screen-reader labels
  • Contrast & reduced motion

How it helps

What you get with Accessibility

1

Keyboard first

Every control reachable and operable by keyboard, with focus returned where it started when the dialogue closes.

2

Announced properly

Roles and labels so a screen reader describes a consent choice as a consent choice.

3

No colour-only meaning

Allowed and blocked states carry words as well as colour, in the product and on this site.

Know what runs before you ask visitors to trust it.

Start with a scan of what your website loads today. The list is usually longer than the team expects, and that is the useful part.

No code to install for a scan Public pages only DotCensus runs on DotCensus