Comparison
Accessibility (addyosmani) vs Accessibility (jezweb)
Two different Claude skills are both called Accessibility. Accessibility (addyosmani) and Accessibility (jezweb) install under the same name and do different jobs, which is exactly how the wrong one ends up running.
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.
5 scenarios in the bank answer to it
Accessibility
jezweb
Helps developers understand and fix accessibility problems by reviewing short examples and giving concrete, code-level suggestions and plain-language explanations. It is aimed at teaching and pattern-based fixes, not at producing formal WCAG conformance reports or full audits - it compares code patterns to practical a11y best practices and refuses to act as a compliance scorer.
1 scenario in the bank answers to it
What is the difference between Accessibility (addyosmani) and Accessibility (jezweb)?
- 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.
- Accessibility (jezweb)
- Helps developers understand and fix accessibility problems by reviewing short examples and giving concrete, code-level suggestions and plain-language explanations. It is aimed at teaching and pattern-based fixes, not at producing formal WCAG conformance reports or full audits - it compares code patterns to practical a11y best practices and refuses to act as a compliance scorer.
Should I use Accessibility (addyosmani) or Accessibility (jezweb)?
The clearest answer is a situation each one is unambiguously right for. Both of these are drawn from the game's question bank.
Reach for Accessibility (addyosmani) when
A volunteer using a screen reader says the site uses images for navigation links with no textual labels and the tab order doesn’t follow the visual menu, so keyboard navigation is chaotic.This is an assistive-technology and semantic-markup problem: navigation needs proper textual labels and a logical focus order, and the skill provides code-level remediation to fix those issues. Responsive-design is a tempting distractor because menus can look wrong on some sizes, but the core failures here are missing labels and focus order for non-visual users - not purely layout breakpoints.
Reach for Accessibility (jezweb) when
You are learning as you go and want plain-language explanations with small before-and-after examples of why a pattern shuts people out and how to fix it - not a formal conformance audit, and not scored against a particular standard's checklist.accessibility-jezweb teaches through plain-language explanations and pattern examples and refuses to act as a compliance scorer. accessibility-affaan-m runs a strict WCAG 2.2 AA conformance audit; accessibility-addyosmani anchors its remediation to WCAG 2.2 checks; accessibility-microsoft fixes the editor's own UI. The tell is plain-language teaching with no standard's checklist.
What they have in common
Both are filed under Accessibility, the axis along which they collide. That shared ground is what makes an agent pick between them on description alone - and what makes it pick wrong.
Nearby comparisons
Reading the difference is not the same as spotting it at speed. That is the game.
Today's session