ibm-a11y-route-scan
Skill8 starsChanged 3 months agoMITView on GitHub
Batch-scan Langflow frontend routes for accessibility issues using the Python IBM Equal Access scanner (scripts/a11y/a11y_scan.py) and produce JSON/Markdown/HTML reports. Scans the default-loaded state of each route only (use explicit state files for modals). Use when asked to scan one or more routes, produce an accessibility report for pages, or batch-check static routes. Reports findings only — does not fix code, run Playwright/axe tests, or perform a formal Level 1 audit; see ibm-a11y-testing-guide, ibm-a11y-level1-audit, and ibm-a11y-pr-remediation for those.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- langflow-ai/langflowword for word, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 1
- langflow-ai/langflow★ 157k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/docs_development.mdcCursor rule
- backend-code-reviewSkill
- component-refactoringSkill
- e2e-testingSkill
- frontend-code-reviewSkill
- frontend-i18nSkill
- frontend-query-mutationSkill
- frontend-testingSkill
- ibm-a11y-level1-auditSkill
- ibm-a11y-pr-remediationSkill
- ibm-a11y-testing-guideSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill when asked to scan Langflow frontend pages for accessibility issues with the local Python scanner.
- Distinctive: line 12
Use the Python script:
- Very specific: line 43
Use scripts/a11y/a11y_routes.json as the source of truth for route selection.
- Distinctive: line 157
Use JSON for exact data. Use Markdown for PR comments or issues.
- Distinctive: line 169
Use report fields directly:
- Distinctive: line 182
Use only scanner output for findings.
- Very specific: line 183
Do not invent route names.
- Distinctive: line 184
Do not auto-click arbitrary buttons to find modals.
- Distinctive: line 185
Avoid destructive modal actions unless the user explicitly asks and data is safe.
- Distinctive: line 186
If a route has zero API requests, mention that scan quality may be limited.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
IBM Route Scanner
Use this skill when asked to scan Langflow frontend pages for accessibility issues with the local Python scanner. This skill only reports — it does not modify code. For test-writing guidance, formal audits, or PR-wide fixes, see ibm-a11y-testing-guide, ibm-a11y-level1-audit, and ibm-a11y-pr-remediation.
Scanner
Use the Python script:
uv run python scripts/a11y/a11y_scan.py \
--url http://localhost:3000 \
--routes-file scripts/a11y/a11y_routes.json \
--route-group static \
--out /tmp/langflow-a11y-report.json \
--markdown /tmp/langflow-a11y-report.md \
--html /tmp/langflow-a11y-report.html \
--timeout-ms 45000Script options:
--url: base app URL, usuallyhttp://localhost:3000.--routes-file: route manifest JSON file. Preferscripts/a11y/a11y_routes.json.--route-group: manifest group to scan. Default:static.--routes: comma-separated route paths to scan.--route: one route path; can be repeated instead of--routes.--levels: comma-separated issue levels. Default:violation.--out: JSON report path.--markdown: optional Markdown report path.--html: optional self-contained HTML report path.--timeout-ms: per-route timeout.--quiet-ms: network quiet window before scanning. Default:1000.--states-file: JSON file with explicit modal/state actions.--headed: show browser while scanning.
Route Selection
Use scripts/a11y/a11y_routes.json as the source of truth for route selection.
The normal CI/local batch is the manifest static group. Prefer that unless the user asks for custom, dynamic, or gated routes.
Common manifest-backed command:
uv run python scripts/a11y/a11y_scan.py \
--url http://localhost:3000 \
--routes-file scripts/a11y/a11y_routes.json \
--route-group static \
--out /tmp/langflow-a11y-static.json \
--markdown /tmp/langflow-a11y-static.md \
--html /tmp/langflow-a11y-static.htmlDynamic routes need real IDs before scanning:
/flow/:id//flow/:id/view/playground/:id//assets/knowledge-bases/:sourceId/chunks
For dynamic routes, get IDs from the loaded app, API responses, or existing test data before replacing placeholders.
Examples
Scan one route:
uv run python scripts/a11y/a11y_scan.py \
--url http://localhost:3000 \
--route /flows \
--out /tmp/langflow-a11y-flows.jsonScan multiple routes:
uv run python scripts/a11y/a11y_scan.py \
--url http://localhost:3000 \
--routes-file scripts/a11y/a11y_routes.json \
--route-group static \
--out /tmp/langflow-a11y-report.json \
--markdown /tmp/langflow-a11y-report.md \
--html /tmp/langflow-a11y-report.htmlScan more than violations:
uv run python scripts/a11y/a11y_scan.py \
--url http://localhost:3000 \
--routes-file scripts/a11y/a11y_routes.json \
--route-group static \
--levels violation,potentialviolation,recommendation \
--out /tmp/langflow-a11y-expanded.jsonScan route plus modal states:
uv run python scripts/a11y/a11y_scan.py \
--url http://localhost:3000 \
--states-file /tmp/langflow-a11y-states.json \
--out /tmp/langflow-a11y-modal-report.json \
--markdown /tmp/langflow-a11y-modal-report.md \
--html /tmp/langflow-a11y-modal-report.html \
--timeout-ms 45000State file shape:
[
{
"route": "/settings/global-variables",
"states": [
{
"name": "new-global-variable-modal",
"open": [
{ "click": "[data-testid='api-key-button-store']" },
{ "waitFor": "[role='dialog']" }
],
"close": [
{ "press": "Escape" },
{ "waitForHidden": "[role='dialog']" }
]
}
]
}
]Supported state actions:
{ "click": "<css selector>" }{ "clickText": "<visible text>" }{ "clickRole": { "role": "button", "name": "Create" } }{ "fill": { "selector": "<css selector>", "value": "text" } }{ "press": "Escape" }{ "press": { "selector": "<css selector>", "key": "Enter" } }{ "waitFor": "<css selector>" }{ "waitForHidden": "<css selector>" }{ "waitForText": "<visible text>" }{ "wait": 500 }{ "scroll": { "selector": "<css selector>", "to": "bottom" } }—toistoporbottom; use"by": <pixels>for a relative scroll, and omitselectorto scroll the page. Needed for virtualised grids whose tabbable rows only disappear after scrolling.
Report
The scanner always writes JSON. It can also write Markdown and HTML for presentation.
Use JSON for exact data. Use Markdown for PR comments or issues. Use HTML when the user wants a browsable report.
Summarize:
- report path
- Markdown/HTML report paths, when generated
- total issue count
- per-route issue count
- per-route API request count
- per-route request failure count
- top rule IDs
Use report fields directly:
totalIssuesresults[].routeresults[].stateresults[].phaseresults[].apiRequestsresults[].requestFailuresresults[].diagnosticsresults[].issues[].ruleId
Rules
- Use only scanner output for findings.
- Do not invent route names. Read
routes.tsx. - Do not auto-click arbitrary buttons to find modals. Use explicit state actions.
- Avoid destructive modal actions unless the user explicitly asks and data is safe.
- If a route has zero API requests, mention that scan quality may be limited.
- This skill reports only; do not edit files. If the user also wants fixes applied, hand off to
ibm-a11y-pr-remediationoribm-a11y-level1-audit.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

