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.

A situation 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 (addyosmani). 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.

5 scenarios in the bank answer to accessibility (addyosmani). The rest are in the game.

Skills it gets confused with

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

Knowing what accessibility (addyosmani) does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

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

← All skills