Writing for accessibility
Skill Dragoon0x/everything-design-taste/skills/writing-for-accessibility
Accessible content writing including plain language, reading level, and cognitive accessibility in text.From its SKILL.md
npx -y skills add Dragoon0x/everything-design-taste --skill writing-for-accessibilityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.2 KB, 235 tokens by cl100k_base, as published. Nobody here has run it
Writing For Accessibility
Plain Language Rules
- Short sentences. Average 15-20 words.
- Common words. "Use" not "utilize." "Start" not "commence."
- Active voice. "We send your report" not "Your report will be sent."
- One idea per paragraph.
- Define jargon on first use.
Reading Level
- Target: 8th grade reading level for general audiences.
- Tools: Hemingway Editor, Flesch-Kincaid score.
- Medical/financial: provide plain-language summaries alongside technical content.
Structural Accessibility
- Descriptive headings (not clever ones).
- Lists for 3+ related items.
- Tables for comparative data (with proper headers).
- Alt text for meaningful images.
- Link text that makes sense out of context ("Download the report" not "Click here").
Cognitive Load
- Chunk information into small pieces.
- Use consistent terminology (don't switch between "workspace" and "project").
- Provide examples alongside instructions.
- Allow undo instead of requiring confirmation.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.