Accessibility conformance report
GoConsent 1.0.115, free and Pro. Tested against WCAG 2.2 levels A and AA on November 2, 2026.
This is a self-assessment by RoxxiStudios, the makers of GoConsent, not a certification. An independent audit by an accessibility specialist is planned. It covers what GoConsent adds to your site, not your theme or content.
Summary
- Criteria checked
- 55
- Supports
- 38
- Partially supports
- 0
- Not applicable
- 17
“Not applicable” means GoConsent has nothing the criterion is about (it plays no audio or video, for example).
What was tested
Everything GoConsent shows your visitors:
- Consent banner (bottom center, bottom left and full-width bar; opt-in, opt-out and notice modes; Global Privacy Control message)
- Your Privacy Choices dialog (category switches and details, cookie lists, Consent ID receipt, Do Not Sell or Share request form)
- Cookie Policy dialog
- Privacy button (shield) and the "Your Privacy Choices" footer link
- Click-to-load placeholders for maps, videos and booking or chat widgets
- Legal links (block, shortcode and automatic footer row)
- "Policy changed" notice (Pro)
- Age gate, yes/no and date of birth (Pro)
- Generated policy page markup (headings and tables) and the printable proof-of-consent receipt (Pro)
How it was tested
An automated test suite runs on every release, for both the free and Pro builds, in a real browser:
- axe-core 4.10 with the WCAG 2.0, 2.1 and 2.2 A and AA rule sets, run inside the banner's shadow root: 0 violations
- Banner positions: bottom center, bottom left, full-width bar
- Widths: 320 px and 390 px (phones), 640 px (200% zoom), 1280 px (desktop); 320 x 256 px (400% zoom)
- Light and dark pages; button colors #ffff00, #00ff00, #777777, #000000, #ffffff, #ff0000, #0000ff, #ff69b4 and the default green
- Right-to-left (dir="rtl"), Windows high contrast (forced colors), reduced motion, WCAG text spacing
- All 13 bundled locales: English (US), German, Spanish (Spain, Mexico), French (France, Canada), Italian, Japanese, Dutch, Polish, Portuguese (Brazil, Portugal), Swedish
- Banner modes: opt-in (EU visitor), analytics before consent, Global Privacy Control, US opt-out (no banner), after a choice (privacy button)
- Scripted keyboard tests (Playwright, Chromium): Tab and Shift+Tab, Enter, Space, Escape; focus into and out of dialogs; no trap; focus ring width and contrast; focus not obscured; switches and accordions; status messages
- Accessibility tree (Chrome DevTools Protocol): roles, names, states, modal dialog, headings, live region
WCAG 2.2 A and AA criteria
Principle 1: Perceivable
| Criterion | Level | Conformance | Remarks | How tested |
|---|---|---|---|---|
| 1.1.1 Non-text Content | A | Supports | The privacy button (shield icon) has the accessible name "Your Privacy Choices". The California opt-out icon has alt text in links and is marked decorative next to the dialog heading. Chevrons and logo shapes are hidden from screen readers; the "Powered by" logo link is named "GoConsent (opens in a new tab)". | axe-core, Accessibility tree |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | Not applicable | GoConsent shows no audio or video of its own. Click-to-load placeholders hold the site's own videos, which are the site owner's content. | Review |
| 1.2.2 Captions (Prerecorded) | A | Not applicable | No GoConsent media. | Review |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | Not applicable | No GoConsent media. | Review |
| 1.2.4 Captions (Live) | AA | Not applicable | No GoConsent media. | Review |
| 1.2.5 Audio Description (Prerecorded) | AA | Not applicable | No GoConsent media. | Review |
| 1.3.1 Info and Relationships | A | Supports | The banner is a region named "Cookie consent"; category switches sit in a named group; dialogs use headings (each category toggle is a heading, as in the WAI-ARIA accordion pattern); cookie tables have captions and column headers; form fields have labels and fieldsets; click-to-load placeholders are named groups. Policy-page and receipt tables mark column headers. | axe-core, Accessibility tree, Review |
| 1.3.2 Meaningful Sequence | A | Supports | The open banner comes first in the page's reading order (it stays where it is on screen). The Pro age gate makes the page behind it inert, so screen readers read only the gate. | Keyboard, Accessibility tree |
| 1.3.3 Sensory Characteristics | A | Supports | Instructions refer to buttons by name, never by shape, position or color. | Review |
| 1.3.4 Orientation | AA | Supports | Works in portrait and landscape; nothing locks the orientation. | Measured |
| 1.3.5 Identify Input Purpose | AA | Supports | The request form uses autocomplete="email" and "name"; the Pro date-of-birth gate uses bday-month, bday-day and bday-year. | Review |
| 1.4.1 Use of Color | A | Supports | Switches show on and off by the thumb position and expose aria-checked; links are underlined; errors are stated in text. | Measured, Accessibility tree |
| 1.4.2 Audio Control | A | Not applicable | GoConsent plays no audio. | Review |
| 1.4.3 Contrast (Minimum) | AA | Supports | All text is 4.5:1 or more. The button color setting adjusts automatically: white, near-black or (for mid-tones such as #777777) black text on the button, and a darkened accent for links and outline buttons. Measured with #ffff00, #00ff00, #777777, #000000, #ffffff, #ff0000, #0000ff, #ff69b4 and the default green. Footer and legal links use the theme's own text color. | axe-core, Measured |
| 1.4.4 Resize Text | AA | Supports | Text resizes to 200% without loss of content or function (tested at 640 CSS px wide, the 200% zoom equivalent of a 1280 px screen). | axe-core, Measured |
| 1.4.5 Images of Text | AA | Supports | All text is real text. The only image of text is the GoConsent logotype in the optional "Powered by" credit, which is allowed. | Review |
| 1.4.10 Reflow | AA | Supports | At 320 CSS px (400% zoom), and at 320 x 256 px, the banner and dialogs fit without horizontal scrolling. The banner scrolls inside itself and covers at most three quarters of the screen; the dialog header stops sticking on short screens. Cookie tables scroll sideways inside their own focusable box, as data tables may. | axe-core, Measured |
| 1.4.11 Non-text Contrast | AA | Supports | Switch tracks, the switch thumb, input borders, radio buttons and focus rings are 3:1 or more against their background with any button color. In Windows high contrast (forced colors), switches keep a visible track, thumb and on/off state, and the banner, dialogs and privacy button keep their outlines. | axe-core, Measured |
| 1.4.12 Text Spacing | AA | Supports | With line height 1.5, paragraph spacing 2em, letter spacing 0.12em and word spacing 0.16em, nothing is cut off or overlaps (English and German, 320 and 1280 px). Long button labels wrap instead of being clipped. | Measured |
| 1.4.13 Content on Hover or Focus | AA | Not applicable | GoConsent shows no custom tooltips or hover pop-ups. The privacy button's title tooltip is the browser's own. | Review |
Principle 2: Operable
| Criterion | Level | Conformance | Remarks | How tested |
|---|---|---|---|---|
| 2.1.1 Keyboard | A | Supports | Everything works with the keyboard: Tab and Shift+Tab, Enter and Space on buttons and switches, Escape to close dialogs. The footer "Your Privacy Choices" link (a link that acts as a button) also answers the Space key. | Keyboard |
| 2.1.2 No Keyboard Trap | A | Supports | The banner is not modal and never traps focus: Tab moves on to the page after its last control. Modal dialogs keep focus inside until closed with Escape or a button. The Pro age gate keeps focus inside by design until the visitor answers, and every answer works by keyboard. | Keyboard |
| 2.1.4 Character Key Shortcuts | A | Not applicable | No single-key shortcuts. | Review |
| 2.2.1 Timing Adjustable | A | Not applicable | No time limits. The banner waits as long as the visitor needs. | Review |
| 2.2.2 Pause, Stop, Hide | A | Not applicable | No moving, blinking or auto-updating content. The banner's quarter-second slide-in is skipped with reduced motion. | Measured |
| 2.3.1 Three Flashes or Below Threshold | A | Supports | Nothing flashes. | Review |
| 2.4.1 Bypass Blocks | A | Supports | The banner is a short named region that screen reader users can skip as a landmark, and it disappears once the visitor chooses. Skip links for the page itself are the theme's. | Accessibility tree, Review |
| 2.4.2 Page Titled | A | Supports | GoConsent's own page (the Pro proof-of-consent receipt) has a descriptive title. Other page titles are set by the site. | Review |
| 2.4.3 Focus Order | A | Supports | The open banner is first in the tab order. Dialogs take focus when opened and give it back to whatever opened them. After Accept All, Reject All or Save, focus moves to the privacy button instead of the top of the page. After "Load video" or "Load map", focus moves to the loaded embed. | Keyboard |
| 2.4.4 Link Purpose (In Context) | A | Supports | Link text says where it goes (Privacy Policy, Notice at Collection, Cookie Policy). Links that open a new tab say so to screen readers. | axe-core, Accessibility tree |
| 2.4.5 Multiple Ways | AA | Not applicable | Applies to sets of pages; site navigation is the theme's. | Review |
| 2.4.6 Headings and Labels | AA | Supports | Dialogs have descriptive headings; every field and switch has a label; each "Load" button is described by its placeholder's notice. | Accessibility tree |
| 2.4.7 Focus Visible | AA | Supports | Every control shows a focus ring of 2-3 px with 3:1 or more contrast: dark rings on the white banner and dialogs, white rings on dark click-to-load cards, a white-backed ring on the privacy button for dark pages, and the page's own text color for footer and legal links. | Keyboard, Measured |
| 2.4.11 Focus Not Obscured (Minimum) | AA | Supports | Page links that get focus while the banner is open are scrolled clear of it, right to the end of the page (a spacer the banner's height is added only while it is open). Focused dialog controls stay clear of the dialog's sticky header. The privacy button and the "policy changed" notice step aside while a page element under them has focus. | Keyboard |
| 2.5.1 Pointer Gestures | A | Not applicable | No path-based or multipoint gestures. | Review |
| 2.5.2 Pointer Cancellation | A | Supports | Actions run on click (pointer up) through native buttons. | Review |
| 2.5.3 Label in Name | A | Supports | Accessible names start with the visible text (for example "Your Privacy Choices" plus the icon's alt text). | Accessibility tree |
| 2.5.4 Motion Actuation | A | Not applicable | Nothing responds to device motion. | Review |
| 2.5.7 Dragging Movements | AA | Not applicable | No dragging. | Review |
| 2.5.8 Target Size (Minimum) | AA | Supports | Every target is at least 24 x 24 px (buttons 38-52 px high, switches 44 x 26 px, the privacy button 48 px), except links inside sentences, which the criterion allows. | Measured |
Principle 3: Understandable
| Criterion | Level | Conformance | Remarks | How tested |
|---|---|---|---|---|
| 3.1.1 Language of Page | A | Supports | GoConsent's own page (the Pro receipt) declares its language. Other pages are the site's. | Review |
| 3.1.2 Language of Parts | AA | Supports | The banner, dialogs, footer link, click-to-load placeholders and the Pro age gate carry a lang attribute, which changes when they are shown in the visitor's browser language instead of the page's. Tested in all 13 bundled locales. | Measured |
| 3.2.1 On Focus | A | Supports | Focus never changes the context. | Keyboard |
| 3.2.2 On Input | A | Supports | Switches change nothing until the visitor presses a button to save. | Keyboard |
| 3.2.3 Consistent Navigation | AA | Supports | The privacy button and the "Your Privacy Choices" link sit in the same place on every page. | Review |
| 3.2.4 Consistent Identification | AA | Supports | The same functions have the same names everywhere (Reject All, Accept All, Your Privacy Choices). | Review |
| 3.2.6 Consistent Help | A | Not applicable | GoConsent adds no help mechanism to pages. | Review |
| 3.3.1 Error Identification | A | Supports | Request form and date-of-birth errors are described in text, the fields are marked aria-invalid and linked to the message, and focus moves to the field. | Keyboard, axe-core |
| 3.3.2 Labels or Instructions | A | Supports | Every field has a visible label; optional fields say so. | axe-core |
| 3.3.3 Error Suggestion | AA | Supports | Errors say how to fix them ("Enter a valid email address.", "Please enter a valid date."). | Keyboard |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Supports | A privacy request is a request, not an instant change: the visitor gets an email confirmation, and copies or deletions may need them to confirm it's them. | Review |
| 3.3.7 Redundant Entry | A | Not applicable | No multi-step processes. | Review |
| 3.3.8 Accessible Authentication (Minimum) | AA | Not applicable | No sign-in. The Pro age gate asks for a date of birth, which is not authentication. | Review |
Principle 4: Robust
| Criterion | Level | Conformance | Remarks | How tested |
|---|---|---|---|---|
| 4.1.2 Name, Role, Value | A | Supports | Switches are buttons with role="switch" and aria-checked; category toggles expose aria-expanded; dialogs are modal with a name and a description; loaded frames have titles. Checked in the browser's accessibility tree. | axe-core, Accessibility tree |
| 4.1.3 Status Messages | AA | Supports | "Your privacy choices have been saved." and "Copied" are announced through a polite live region; request-form results use role="status". | Keyboard, Accessibility tree |
4.1.1 Parsing was removed in WCAG 2.2 and is not listed. How tested: axe-core = automated rules; Keyboard = scripted keyboard test; Accessibility tree = roles, names and states read from the browser; Measured = contrast, size and layout measured in the browser; Review = code review.
48 issues found and fixed in 1.0.115
The audit found these problems. All are fixed, in both the free and Pro builds.
- 1.4.10 Reflow (4): Banner taller than the screen at 400% zoom and on short screens (3 positions), now scrolls inside itself and covers at most 75%; dialog heading cut off at 320 px.
- 1.4.4 / 1.4.12 Resize text, Text spacing (2): Buttons with long German and Dutch labels clipped at 320 px and with text spacing (labels could not wrap); dialog heading could not wrap.
- 1.4.3 Contrast (3): Mid-tone button colors (#777777) gave 4.48:1 button text; the Pro age gate used white text on any color (1.07:1 on yellow) and the raw color for its outline button text.
- 1.4.11 Non-text contrast / 2.4.7 Focus visible (6): Dark focus ring on dark click-to-load cards; privacy button ring invisible on dark pages; footer and legal link rings fixed to near-black on dark footers; "policy changed" notice and age gate rings used the raw button color; request-form radio buttons used the raw button color.
- Forced colors (Windows high contrast) (4): Switch track, thumb and on/off state disappeared; banner and dialogs lost their edges; privacy button shield stayed dark on dark.
- 2.4.3 Focus order (5): Banner was last in the tab order (after all page content); focus fell to the top of the page after Accept All, Reject All or Save; and after loading a video, map or widget; dialog close had no fallback when its opener was gone.
- 2.4.11 Focus not obscured (3): Links at the end of the page stayed under the open banner on phones; dialog controls could scroll under the sticky header; the privacy button and notice could cover a small corner link.
- 2.5.8 Target size (5): Footer "Your Privacy Choices" link (17 px), legal links (18 px), banner policy links and "Cookie details" (22.5 px), "Open in Google Maps" (21.75 px) and age gate links.
- 4.1.3 Status messages (2): Nothing was announced after saving a choice; "Copied" was not announced.
- 4.1.2 Name, role, value / 2.1.1 Keyboard (4): Loaded embed frames could lack a title; the footer link with role="button" ignored Space; dialogs did not state aria-modal; age gate background stayed readable by screen readers and reachable by keyboard.
- 1.3.1 Info and relationships / 2.4.6 Headings and labels (5): Your Privacy Choices had no description; categories were not headings; click-to-load placeholders were unnamed and their "Load" buttons undescribed; policy-page and receipt tables lacked column-header scope.
- 3.1.2 Language of parts (1): Click-to-load placeholders shown in the visitor's language had no lang attribute.
- 3.3.1 Error identification (1): Age gate date-of-birth errors were not tied to the fields (aria-invalid, aria-describedby).
- Admin (secondary pass) (3): Toasts announced twice (live container plus role on each toast); error toasts vanished after 8 seconds; tab lists had no arrow-key support.
Known limits
- This is a self-assessment by RoxxiStudios, not a certification. An independent audit by an accessibility specialist, including testing with NVDA, JAWS, VoiceOver and TalkBack by people who use them, is planned.
- Automated tests ran in Chromium. Firefox and Safari use the same standard HTML (buttons, dialog, ARIA) but were not part of this round.
- Your theme, page content, page builder and other plugins are outside what GoConsent can test. Footer links, legal links and policy pages take your theme's fonts and colors.
- Embedded videos, maps and widgets are made by other companies. GoConsent makes the placeholder accessible; the loaded embed is the provider's.
- Very old browsers without the HTML dialog element (before 2022) get the dialogs as a plain panel without focus management.
Feedback
Found a barrier in the GoConsent banner or dialogs? Tell us and we’ll fix it. For a barrier on a website that uses GoConsent, contact that website’s owner.
See What visitors see for how the banner works.