Accessibility (jezweb) vs Accessibility (microsoft)
Two different Claude skills are both called Accessibility. Accessibility (jezweb) and Accessibility (microsoft) install under the same name and do different jobs, which is exactly how the wrong one ends up running.
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
Accessibility
microsoft/vscode
Offers tools inside the code editor to inspect and adjust the editor’s own accessibility behavior — things like toggling screen‑reader mode, examining the accessibility tree of editor UI, and checking keyboard focus and navigation in the IDE and its extensions. Unlike the WCAG/audit tools, it targets the editor’s UI and developer workflow rather than scanning websites for WCAG compliance or producing remediation for site content.
1 scenario in the bank answer to it
What is the difference between Accessibility (jezweb) and Accessibility (microsoft)?
- 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.
- Accessibility (microsoft)
- Offers tools inside the code editor to inspect and adjust the editor’s own accessibility behavior — things like toggling screen‑reader mode, examining the accessibility tree of editor UI, and checking keyboard focus and navigation in the IDE and its extensions. Unlike the WCAG/audit tools, it targets the editor’s UI and developer workflow rather than scanning websites for WCAG compliance or producing remediation for site content.
Should I use Accessibility (jezweb) or Accessibility (microsoft)?
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 (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.
Reach for Accessibility (microsoft) when
We shipped a VS Code extension and a blind developer says he cannot reach our sidebar panel with a keyboard at all. Nothing is wrong with our website; the problem is inside the editor.
Three of these audit web pages against WCAG; only one looks at the editor itself. accessibility (microsoft/vscode) inspects the editor's own accessibility tree, screen-reader mode and keyboard focus, which is exactly where an extension's sidebar lives. The affaan-m option is the tempting one because it is the thorough WCAG 2.2 AA auditor — but a WCAG audit of your website says nothing about whether your extension panel is reachable inside VS Code.
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