CookieChimp Accessibility Conformance Report
Edition B · Original assessment date: 12 July 2026 · Remediation review: 14 September 2026 · Prepared by: CookieChimp Engineering
Accessibility assessment of visitor-facing consent components against WCAG 2.2 Level A and AA.
1. Scope and release status
This report covers the consent banner, its preferences modal (including its cross-origin iframe), and the privacy portal/vendor-list embed used by visitors to customer websites. It assesses the proposed widget 1.0.67 changes. Publication of these source changes is separate from production deployment and edge-cache synchronization.
The administration application, authentication, billing configuration and general marketing website are outside this assessment. The public accessibility statement describes this same scope.
Overall status: Supports all applicable WCAG 2.2 Level A and AA criteria for the assessed banner/preferences surface and privacy portal. Ratings cover built-in themes and controls in the assessed configurations; arbitrary customer-selected palettes are outside this assessment.
2. Evaluation method and ratings
The evaluation combines engineering review, automated regression testing, keyboard interaction, browser accessibility-tree inspection, visual checks and axe-core scans. It covers the consent banner, embedded preferences and privacy portal using representative content and configurations, including light and dark themes and cross-origin embedding.
CookieChimp confirms completed human verification of the assessed behavior. Ratings reflect this verification and the evaluation methods and configurations described here. Customer branding, content, languages and the surrounding website form part of the deployment review; this component assessment does not establish whole-site conformance.
- Supports: the reviewed component implementation provides the relevant behavior, within the scope above.
- Not applicable: the assessed component has no feature triggering the criterion; this does not describe the customer's wider website.
3. WCAG 2.2 Level A and AA assessment
| Criterion | Rating | Component evidence or limitation |
|---|---|---|
| 1.1.1 Non-text Content | Supports | Storage-type and description icons have textual equivalents; decorative SVGs are hidden. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 1.2.2 Captions (Prerecorded) | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 1.2.3 Audio Description or Media Alternative | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 1.3.1 Info and Relationships | Supports | Native fieldsets, labels, tables and description lists expose relationships. ARIA references use unique whitespace-safe identifiers. |
| 1.3.2 Meaningful Sequence | Supports | DOM order follows the visual grouping. Script-aware direction does not reverse reading order. |
| 1.3.3 Sensory Characteristics | Supports | Instructions identify preferences controls by their visible labels rather than position, shape or colour alone. |
| 1.4.1 Use of Color | Supports | Switch state is exposed programmatically and by thumb position, not colour alone. |
| 1.4.2 Audio Control | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 2.1.1 Keyboard | Supports | Native disclosure buttons and switches support keyboard operation. Explicit messages bridge Tab, Shift+Tab and Escape across the iframe. |
| 2.1.2 No Keyboard Trap | Supports | A reject action is supplied for configurations with no usable banner exit. Preferences retain their close action. |
| 2.1.4 Character Key Shortcuts | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 2.2.1 Timing Adjustable | Supports | There is no time limit for submitting consent choices. |
| 2.2.2 Pause, Stop, Hide | Supports | Consent controls use short transitions; reduced-motion styles disable them. |
| 2.3.1 Three Flashes or Below Threshold | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 2.4.1 Bypass Blocks | Supports | Embedded preferences and the portal provide main landmarks; neither repeats site navigation. |
| 2.4.2 Page Titled | Supports | Preferences and portal documents have descriptive interface titles. |
| 2.4.3 Focus Order | Supports | Dialog and iframe traversal is coordinated; closing restores the invoking control when it remains available. |
| 2.4.4 Link Purpose (In Context) | Supports | Policy links have descriptive text. Customer-supplied links require review. |
| 2.5.1 Pointer Gestures | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 2.5.2 Pointer Cancellation | Supports | Native controls activate on click/up-event. |
| 2.5.3 Label in Name | Supports | Switch and disclosure names reference the visible label, including multiword and Unicode service names. |
| 2.5.4 Motion Actuation | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 3.1.1 Language of Page | Supports | The preferences document declares the actual configured content language. The portal declares the selected interface locale. |
| 3.2.1 On Focus | Supports | Focusing a control does not navigate or submit a choice. Tooltips reveal supplemental content. |
| 3.2.2 On Input | Supports | Changing an optional preference updates draft choices; explicit footer actions submit them. |
| 3.2.6 Consistent Help | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 3.3.1 Error Identification | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 3.3.2 Labels or Instructions | Supports | Categories and services name their switches; necessary categories are marked Always enabled. |
| 3.3.7 Redundant Entry | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 4.1.2 Name, Role, Value | Supports | Named dialogs, labelled switches and disclosures, state updates and titled frames are implemented. CookieChimp confirms human verification of the assessed behavior. |
| 1.2.4 Captions (Live) | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 1.2.5 Audio Description (Prerecorded) | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 1.3.4 Orientation | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 1.3.5 Identify Input Purpose | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 1.4.3 Contrast (Minimum) | Supports | Built-in themes support text contrast requirements in the assessed configurations. Customer-selected palettes are outside this assessment. |
| 1.4.4 Resize Text | Supports | Human verification confirms text enlargement preserves content and functionality in the assessed consent surfaces. |
| 1.4.5 Images of Text | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 1.4.10 Reflow | Supports | Consent content and cookie tables reflow at 320 CSS pixels. Human verification confirms the assessed layouts remain usable with expanded and long content. |
| 1.4.11 Non-text Contrast | Supports | Built-in controls, switch boundaries and two-tone focus indicators support non-text contrast requirements in the assessed configurations. |
| 1.4.12 Text Spacing | Supports | Human verification confirms text-spacing changes preserve content and functionality in the assessed consent surfaces. |
| 1.4.13 Content on Hover or Focus | Supports | Consent tooltips accept keyboard focus, remain hoverable and support Escape dismissal. |
| 2.4.5 Multiple Ways | Supports | The assessment covers embedded consent controls rather than a collection of navigable website pages. |
| 2.4.6 Headings and Labels | Supports | Names use visible category/service labels; blank titles and logos retain a programmatic dialog name. |
| 2.4.7 Focus Visible | Supports | Two-tone focus styling covers preferences, banner controls and the floating reopen button. |
| 2.4.11 Focus Not Obscured (Minimum) | Supports | Focused controls remain visible in the assessed scrolling and embedded layouts. |
| 2.5.7 Dragging Movements | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 2.5.8 Target Size (Minimum) | Supports | Assessed targets meet minimum size or an applicable exception, including spacing and inline links. |
| 3.1.2 Language of Parts | Supports | Content, interface fragments and tooltips declare their rendered language, including translation fallbacks. |
| 3.2.3 Consistent Navigation | Supports | The assessed components have no repeated site navigation. |
| 3.2.4 Consistent Identification | Supports | Built-in controls performing the same function have consistent visible labels and accessible names. |
| 3.3.3 Error Suggestion | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Supports | Visitors can reopen preferences and revise saved choices through the floating button or an accessible replacement; the assessed flow is human-verified. |
| 3.3.8 Accessible Authentication (Minimum) | Not applicable | The assessed consent components do not include a feature that triggers this criterion. |
| 4.1.3 Status Messages | Supports | Consent saving does not present a status message. No unsupported live-region requirement is inferred from that absence. |
| 4.1.1 Parsing (WCAG 2.1 / EN 301 549 clause 9.4.1.1) | Supports | Legacy parsing review covers unique identifiers, non-nested interactive controls, valid fieldset legends and dt/dd relationships. This criterion was removed from WCAG 2.2. |
4. Customer configuration requirements
- Check configured text and background contrast (4.5:1 normal text; 3:1 large text), controls and focus in every theme.
- Write clear headings and labels. Use the same wording for controls that open the same preferences dialog. Review translations and mark mixed-language passages in customer content.
- Keep an accessible route back to preferences. If the floating control is disabled, provide an accessible replacement labelled "Manage cookie preferences" using the documented preferences trigger.
- Test the integrated page at 320 CSS pixels, 200% zoom, and with text-spacing overrides. Check fixed headers/footers and other overlays for obscured focus.
- Repeat keyboard, screen-reader and contrast checks after branding, content or integration changes.
5. Standards and regulatory scope
The criterion assessment above targets WCAG 2.2 A and AA. Legacy 4.1.1 Parsing is recorded separately because older WCAG-based procurement requirements may retain it. This component report does not establish compliance with EN 301 549, Revised Section 508, the European Accessibility Act or a customer's legal obligations as a whole. Full pages, complete processes and service-specific requirements require a separate assessment.
Primary technical references: WCAG 2.2, WAI modal dialog pattern, Content on Hover or Focus, and Non-text Contrast.
6. Contact and review
Report barriers to [email protected] with the affected page, browser, assistive technology and reproduction steps. Engineering owns review after material consent-surface changes and before 12 July 2027.
7. Assessment timeline
| Date | Milestone | Details |
|---|---|---|
| 12 July 2026 | Original assessment | Accessibility assessment of the visitor-facing consent components. |
| 14 September 2026 | Remediation review | Consolidated improvements and confirmed human verification for this customer edition. |