accessibility (microsoft/vscode)
- Accessibility
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.
A situation it fits
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.
Skills it gets confused with
These share a family with accessibility (microsoft/vscode), which is another way of saying they are the ones you might reach for by mistake.
- 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 (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.
- 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.
Knowing what accessibility (microsoft/vscode) does is the easy half. Telling it apart from the others under time pressure is the game.
Today's sessionaccessibility (microsoft/vscode) is part of microsoft/vscode. Licence: MIT. The description above was written for this game, not taken from the skill.