test-a-cookie-banner

# test-a-cookie-banner Verify actual storage and network behavior, not only button labels. This is not legal advice. ## When to use - Use across relevant regions, devices, consent states, and authenticated journeys. - Do not assume one consent model satisfies every jurisdiction; obtain qualified review. ## Procedure 1. Define region, locale, browser, device, user state, consent categories, lawful configuration, and expected tags. 2. Start with clean cookies and storage, then record pre-choice requests, cookies, pixels, and local state. 3. Test accept all, reject all, category selection, close, no action, and necessary-only behavior. 4. Verify equal access, keyboard operation, focus, screen-reader labels, readable content, and no manipulative obstruction. 5. Confirm stored consent contains version, timestamp, region, categories, and expiry without unnecessary identity. 6. Revisit, change, and withdraw preferences; verify tags, cookies, and downstream signals respond. 7. Test localization, policy links, cross-subdomain behavior, login transitions, expiry, and policy-version changes. ## Done - A consent test report records region, choice, interface, storage, requests, tags, policy version, and observed discrepancies - Clean-state, reject, granular, withdrawal, accessibility, locale, expiry, and return-visit checks verify behavior