Skip to content

Skill

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.

3 other skills are also called Accessibility

Same name, different author, different job. If more than one is installed, the one that runs is whichever the agent matches first.

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.
Accessibility. 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.

Skills it gets confused with

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

Every comparison with Accessibility

Knowing what Accessibility does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

Accessibility is part of microsoft/vscode. Licence: MIT. The description above was written for this game, not taken from the skill.