Accessibility (affaan-m) vs Accessibility (jezweb)
Two different Claude skills are both called Accessibility. Accessibility (affaan-m) and Accessibility (jezweb) install under the same name and do different jobs, which is exactly how the wrong one ends up running.
Accessibility
affaan-m/ecc
This tool inspects user interfaces against WCAG 2.2 Level AA and gives concrete checks and fixes for keyboard navigation, color contrast, and screen‑reader behavior. Unlike general accessibility guides, editor extensions, or chat-based assistants, it’s built for hands-on, change‑level audits and implementation guidance targeted specifically at WCAG 2.2 AA criteria rather than broad training or IDE integration.
1 scenario 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 answer to it
What is the difference between Accessibility (affaan-m) and Accessibility (jezweb)?
- Accessibility (affaan-m)
- This tool inspects user interfaces against WCAG 2.2 Level AA and gives concrete checks and fixes for keyboard navigation, color contrast, and screen‑reader behavior. Unlike general accessibility guides, editor extensions, or chat-based assistants, it’s built for hands-on, change‑level audits and implementation guidance targeted specifically at WCAG 2.2 AA criteria rather than broad training or IDE integration.
- 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 (affaan-m) 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 (affaan-m) when
My client insists the site must meet a formal, narrowly defined set of accessibility success criteria from their audit; I need a hands‑on inspection that lists which specific criterion each failure maps to and gives concrete, implementation‑level fixes so engineers can close the exact compliance tickets.
accessibility-affaan-m is the right choice because it is built to inspect against a formal set of success criteria and produce hands‑on, criterion‑mapped checks with concrete fixes developers can apply to meet that audited standard. The most tempting wrong choice is accessibility-addyosmani — it also explains failures and gives step‑by‑step, code‑level remediation, but it’s focused on teaching remediation rather than acting as a strict, criterion‑mapped auditor or compliance checklist tool. accessibility-jezweb is tempting for clear, example‑based fixes, but it focuses on short pattern reviews and refuses to act as a full compliance scorer; accessibility-microsoft is irrelevant here because it targets accessibility of the development app/UI itself rather than auditing site content against a formal checklist.
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