Skip to content

Skill

Accessibility

addyosmani

Runs accessibility checks against WCAG 2.2 and returns developer-facing issues with concrete, code-level recommendations for ARIA, keyboard focus, contrast, and semantic HTML. Unlike similarly named validators or IDE extensions, it’s focused on teaching and step‑by‑step remediation - it explains failures and how to fix them instead of acting as a strict Level‑AA certifier or an auto‑patch tool.

3 other skills are also called Accessibility

Same name, different author, different job. If more than one is installed, the one that runs is whichever the agent matches first.

Situations it fits

During testing, a participant who uses assistive technology can't tell which inputs belong to which labels and tabbing skips the 'submit' control entirely.
Accessibility. accessibility-focused work finds and explains interface failures that prevent assistive tools and keyboard users from interacting: missing or incorrect labeling, improper focus order, and other practical defects, then gives concrete remediation steps. While layout tweaks or SEO changes won't fix invisible labels or broken keyboard flow, an accessibility review will identify the code-level fixes needed so those users can complete the form.
Users report that screen-reader users can't tell what buttons do, important icons have no descriptive text, and some interactive controls are unreachable by non-mouse visitors.
Accessibility. This skill is focused on finding and explaining code-level problems that stop people using a site with assistive tech (missing labels, non-announced errors, unreachable controls) and gives concrete remediation steps for developers. Other choices deal with layout across devices or search visibility and won’t produce the step-by-step fixes needed for assistive-technology failures.
A form on the site shows errors visually but screen-reader users get no explanation and keyboard users can’t reach the modal’s submit control.
Accessibility. This skill pinpoints and explains developer-level fixes for interaction and content that isn’t accessible - missing error announcements, focus and order problems, and unlabeled controls - and returns actionable steps for engineers. The other skills focus on layout, scaling, or search issues, not the assistive-technology failures described.

5 scenarios in the bank answer to Accessibility. The rest are in the game.

Skills it gets confused with

These share a family with Accessibility, which is another way of saying they are the ones you might reach for by mistake.

Every comparison with Accessibility

Knowing what Accessibility does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

Accessibility is part of addyosmani/web-quality-skills. Licence: MIT. The description above was written for this game, not taken from the skill.