Repository navigation
[accessibility-review] Cookie consent Customize control does not expose disclosure state #1458
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-10-11T08:39:09.554Z.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem
The cookie banner's Customize button shows and hides
#consent-details, but the button has noaria-expandedoraria-controls, and the script does not update any state attribute. Assistive-technology users cannot tell whether activating Customize opened the preferences panel. The hidden panel is also managed only with inlinedisplay, without an equivalent semantic disclosure state.WCAG 2.2
Evidence
EssentialCSharp.Web/wwwroot/js/consent-manager.js:108-115:showCustomizeOptions()togglesdetails.style.displaybut never updates ARIA state. Addaria-expanded="false" aria-controls="consent-details"to the button and updatearia-expandedwhenever the panel opens or closes. Prefer thehiddenattribute (or a matching semantic disclosure pattern) for the panel's collapsed state.Warning
Firewall blocked 7 domains
The following domains were blocked by the firewall during workflow execution:
accounts.google.comandroid.clients.google.comclients2.google.comupdate.googleapis.comwww.google.comwww.gstatic.comwww.microsoft.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
Add this agentic workflow to your repo
To install this agentic workflow, run
All reactions