Write in plain language

SkillMedia

The plain language skill is an accessibility review skill for AI agents. When reviewing rendered HTML, interactive components, or design-system patterns related to writing in plain language, it checks native semantics first, then keyboard behavior, focus flow, accessible names, and screen-reader output. It helps an agent flag jargon, complex sentences, and unclear instructions, and suggest concrete fixes.

Available today. Use it from your connected AI after setup.

Have an agent that can load skills and access the content or markup to review.

Then ask your AI: use the Write in plain language skill

What your AI can do with it

  • Review rendered markup and interactive states affecting plain language
  • Check native semantics first, then keyboard behavior and focus flow
  • Verify accessible names and screen-reader output where relevant
  • Flag exact elements, roles, labels, or keyboard interactions that violate the rule
  • Suggest fixes: short sentences, active voice, defined terms, bullet points
  • Explain how plain language benefits users with cognitive disabilities

Getting started

  1. Have an agent that can load skills and access the content or markup to review.
  2. Add the plain-language skill to the agent's available skills.
  3. Ask the agent to review a page, component, or design-system pattern for plain language.
  4. Optionally verify flagged issues with browser accessibility tooling or assistive tech; full details are in the skill's references/rule.md.

What this skill tells your AI

The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/plain-language/SKILL.md and read by ahel’s review.

Plain language helps users with cognitive disabilities, learning differences, attention disorders, non-native speakers, and anyone reading quickly or under stress.

Quick Reference

  • Use short sentences and common words
  • Define technical terms when first used
  • Write in active voice, not passive
  • Target reading level appropriate for your audience (often 8th grade)

Check

Review content for jargon, complex sentences, and unnecessary technical terms. Verify reading level is appropriate for the audience. Check that instructions are clear and actions are obvious.

Fix

Simplify complex sentences. Define technical terms when first used. Use short paragraphs and bullet points. Write in active voice. Target a reading level appropriate for your broadest audience.

Explain

Explain how plain language benefits users with cognitive disabilities, learning differences, attention disorders, non-native speakers, and anyone in a hurry or under stress.

Code Review

Review the rendered markup and interactive states that affect Write in plain language. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/accessibility/plain-language

Signals

GitHub stars
74k
Forks
7k
Last commit
Aug 2026

Questions

When should this skill be used?
When reviewing rendered HTML, interactive components, or design-system patterns related to Write in plain language.
What does the review check?
Native semantics first, then keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
What reading level should content target?
A level appropriate for the audience, often 8th grade, targeting the broadest audience.
Advanced
Item type
skill
Key
plain-language-thedaviddias
Source
github.com/thedaviddias/front-end-checklist