Stats
Actions
Tags
From accessible-content
Audits and rewrites link text so that every link makes sense out of context for screen reader users. Use when reviewing CTAs, navigation labels, or ambiguous anchor text like "click here" or "read more."
How this skill is triggered — by the user, by Claude, or both
Slash command
/accessible-content:link-text-designThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write link text that tells users where they're going before they get
Write link text that tells users where they're going before they get there. Screen reader users often navigate by pulling up a list of all links on a page — if every link says "click here" or "read more", that list is useless.
Every link should make sense when read completely on its own, outside of any surrounding sentence or context.
These phrases mean nothing out of context:
If you find yourself writing these, ask: more about what? Here where? That answer is your link text.
If two links have the same text, they must go to the same place. Two different "Learn more" links going to different pages is confusing for everyone and disorienting for screen reader users.
If two links go to different places, their text must be different.
npx claudepluginhub owl-listener/inclusive-design-skills --plugin accessible-contentGuides creation of accessible user-facing content including labels, headings, error messages, alt text, links, and form instructions for screen reader compatibility and clarity.
Reviews content accessibility across cognitive and literacy levels. Checks structure, readability, images, links, tables, forms, and multimedia. Use when auditing existing content.
Writes button labels, error messages, placeholder text, empty states, and tooltips that are specific, actionable, and honest. Helps reduce user friction and support contacts.