Building consent that everyone can actually use
Give visitors clear, accessible control over their privacy choices. CookieChimp brings keyboard navigation, meaningful control labels and visible focus to your consent banner, preferences modal and privacy portal.
- WCAG 2.2
- A and AA assessment
- Keyboard
- Consent controls
- Screen readers
- Names, roles and states
- Self-assessment
- Available on request
Our commitment to accessible consent
Our assessment focuses on the consent banner, embedded preferences modal and privacy portal that visitors use on customer websites. Our vendor self-assessment confirms support for all applicable WCAG 2.2 Level A and AA criteria in the assessed built-in configurations. Customer-selected palettes and the surrounding website require a separate review.
Accessibility across your consent experience
Built-in features help visitors navigate their choices and understand cookie information across both surfaces.
- Consent banner & preferences modal
- Keyboard navigation, named controls and visible focus
- Privacy portal & vendor tables
- Structured tables, text descriptions and keyboard-accessible tooltips
The full report lists every Level A and Level AA criterion with its rating and the reasoning behind it.
Use the report alongside the configuration guidance below to review your branding and website integration.
Accessibility built into the consent layer
These are not settings you have to find. They are how the banner and preferences modal are built.
Keyboard access throughout preferences
Open preferences, expand categories and services, change optional choices and save using the keyboard. Tab and Shift+Tab move between the dialog controls and its embedded preferences document. Escape closes preferences, including from inside the iframe.
Meaningful names and states
Consent switches use their visible category or service name and expose their checked state. Disclosure buttons announce whether details are expanded. The preferences dialog retains an accessible name when its visible title is blank or replaced by a logo.
Visible keyboard focus
Preferences controls use a two-tone focus indicator that is independent of your primary colour. Light and dark themes retain their layout, with a discernible boundary around optional switches.
Accessible cookie information
The privacy portal and preferences tables expose storage types and descriptions as text. Keyboard users can reveal tooltips, keep them open while reading, and dismiss them with Escape.
Language and direction
The banner declares its resolved language, and the preferences document declares the language of its configured content. Interface labels use available translations. Technical identifiers and customer-provided text retain their original wording.
Return to your choices
The floating preferences control is a named keyboard-operable button. If you disable it, provide an accessible replacement on your website using our documented preferences trigger.
We ship the mechanics.You choose the colours and the words.
CookieChimp provides the banner's semantics, focus handling and keyboard behaviour. Pair these built-in features with readable colours, clear content and a website integration that works for your visitors.
- Choose accessible colours
- Check your configured text against its background: at least 4.5:1 for normal text and 3:1 for large text. Controls also need a discernible boundary.
- Use clear, consistent labels
- Give equivalent preferences controls the same wording. Write descriptive headings, links and category names, and mark mixed-language passages in your content.
- Review your translations
- Configure and review the languages your visitors use. Some interface strings fall back to English where a translation is unavailable; test those configurations with your audience.
- Test on your own website
- Check overlays, fixed headers and footers, zoom, text spacing and mobile layouts after branding or integration changes. Retain an accessible way to reopen preferences.
Found a barrier? Tell us.
Email [email protected] with "Accessibility" in the subject line. Tell us the surface, your browser, your assistive technology, what you expected and what happened. We use your report to reproduce the barrier and discuss remediation.
Report an accessibility barrierAccessibility questions we get asked
What does the accessibility assessment cover?
The consent banner, its embedded preferences modal, and the privacy portal and vendor-list embed used by visitors to customer websites. The CookieChimp administration application, authentication screens and general marketing website are outside this assessment.
Do you provide an Accessibility Conformance Report?
Yes. Request our vendor self-assessment of the visitor-facing consent surfaces against WCAG 2.2 Level A and AA. The report includes criterion-by-criterion ratings, test evidence and guidance for configuring your website.
Can visitors use the consent controls with a keyboard?
The floating preferences button, category and service disclosures, consent switches, privacy-policy links and footer actions support keyboard operation. Preferences support Tab, Shift+Tab and Escape across the embedded iframe boundary.
How do I report an accessibility problem?
Email [email protected] with Accessibility in the subject. Include the affected page, browser, assistive technology, expected behavior and what happened. We use that information to reproduce the barrier and discuss remediation.
Need our Accessibility Conformance Report?
We will send the full WCAG 2.2 Level AA assessment, with criterion ratings and test evidence, and discuss your accessibility questionnaire.