Repository navigation
[accessibility-review] TOC filter control is mouse-only and its input is unlabeled #1460
Replies: 1 comment
|
This discussion was automatically closed because it expired on 2026-10-11T08:39:11.229Z.
|
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 Contents filter is implemented as a clickable
<i>element. It is not keyboard focusable, has no semantic button role, no accessible name, and does not expose whether the filter is open. Once opened, the text input has only a placeholder and no associated label. Keyboard and screen-reader users cannot discover or operate this feature reliably.WCAG 2.2
Evidence
EssentialCSharp.Web/src/components/SidebarPanel.vue:78-90:Replace the icon with a
<button type="button">labelled, for example,Filter contents, exposearia-expandedandaria-controls, and associate a visible or visually-hidden<label for="...">with the input.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