accessible-charts-and-dashboards
Skill8 starsChanged 2 months agoMITView on GitHub
1. Obtain the chart's purpose, underlying data, units, filters, and user tasks. If meaning or data is unavailable, document the gap rather than inventing a description. 2. Use the chart review guide to choose concise context and an appropriate detailed alternative, including interactive task equivalence. 3. Compare the visual representation and its alternative across filters, empty/loading/error states, and live updates. Test keyboard access to controls and information otherwise revealed only on hover. 4. Repair the shared data transformation or rendering…
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-auditSkill
- accessibility-regression-testSkill
- accessible-authenticationSkill
- accessible-combobox-and-autocompleteSkill
- accessible-component-reviewSkill
- accessible-data-tables-and-gridsSkill
- accessible-dynamic-updatesSkill
- accessible-formsSkill
- dialog-accessibilitySkill
- fix-accessibility-issueSkill
- keyboard-navigation-reviewSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
If meaning or data is unavailable, document the gap rather than inventing a description.
- Distinctive: line 20
Use the chart review guide to choose concise context and an appropriate detailed alternative, including interactive task equivalence.
≈ “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
Accessible charts and dashboards
Workflow
- Obtain the chart's purpose, underlying data, units, filters, and user tasks. If meaning or data is unavailable, document the gap rather than inventing a description.
- Use the chart review guide to choose concise context and an appropriate detailed alternative, including interactive task equivalence.
- Compare the visual representation and its alternative across filters, empty/loading/error states, and live updates. Test keyboard access to controls and information otherwise revealed only on hover.
- Repair the shared data transformation or rendering source. Add a regression that compares visual and alternative values after the same interaction.
- Perform the guide's manual interpretation, screen-reader, and low-vision checks; preserve unresolved meaning judgments for a human reviewer.
Boundaries
A data table is often useful but is not the only valid alternative. Do not invent trends, assert that an aria-label makes a chart accessible, expose thousands of unstructured SVG marks, or remove interactive analysis functionality to clear a scan.
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.

