Use inclusive language
SkillMediaInclusive-language is a skill for AI agents that reviews web pages and UI designs for inclusive wording. It checks rendered HTML, interactive components, and design-system patterns so content avoids biased or exclusionary terms. The review starts with native semantics, then looks at keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an AI agent that can load skills.
Then ask your AI: use the Use inclusive language skill
What your AI can do with it
- Reviews rendered HTML for inclusive wording
- Checks interactive components for biased or exclusionary terms
- Reviews design-system patterns for inclusive language
- Checks native semantics first, then keyboard behavior and focus flow
- Inspects accessible names and screen-reader output where relevant
Getting started
- Have an AI agent that can load skills.
- Add the inclusive-language skill to the agent's available skills.
- Ask the agent to review a rendered HTML page, interactive component, or design-system pattern.
- The agent applies the skill, checking semantics, keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/inclusive-language/SKILL.md and read by ahel’s review.
Language shapes experience—ableist, gendered, or exclusionary terminology creates unwelcoming experiences and reinforces harmful stereotypes, even unintentionally.
Quick Reference
- Replace ableist terms (crazy, lame, blind to) with neutral alternatives
- Use gender-neutral language (they, users, people) by default
- Write error messages that guide rather than blame users
- Avoid idioms and cultural references that don't translate globally
Check
Review content for ableist language (crazy, lame, blind to), gendered assumptions (he/she defaults), cultural bias, and exclusionary terminology. Verify error messages and instructions are respectful and constructive.
Fix
Replace ableist terms with neutral alternatives. Use gender-neutral language (they, users, people). Avoid idioms that may not translate across cultures. Write error messages that guide rather than blame.
Explain
Explain how language shapes experience and can unintentionally exclude or harm users, and why inclusive language creates welcoming digital spaces for everyone.
Code Review
Review the rendered markup and interactive states that affect Use inclusive 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/inclusive-language
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- What does the skill check first?
- It checks native semantics first, then inspects keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
- What kinds of content can it review?
- Rendered HTML, interactive components, and design-system patterns related to inclusive language.
- Does it work on any web page?
- It is meant for reviewing rendered HTML, interactive components, and design-system patterns; the description does not list other content types.
Advanced
- Item type
- skill
- Key
inclusive-language- Source
- github.com/thedaviddias/front-end-checklist