agentleFS
sukirman1901sukirman1901/frontend-expert/skills/accessibility/SKILL.md

accessibility

Skill9 starsChanged 2 months agoMITView on GitHub

Enforce WCAG 2.2 AA by default (keyboard, ARIA, focus, contrast, semantics, target size, dragging alternatives, accessible authentication). Use for accessibility work, pre-ship UI checks, and as a light pass on every UI build or design review — including "a11y", "keyboard", "screen reader", or shipping user-facing changes.

123 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use author-contributions, tool-rename-deprecation and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    author-contributions

    Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

    Also in 7 projects that use this

  • gitpod-ioSkill

    tool-rename-deprecation

    Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.

    Also in 5 projects that use this

  • DepressionCenterSkill

    project-preferences

    Apply repository-specific preferences when planning, implementing, or reviewing changes in this project.

    Also in 6 projects that use this

  • MicrosoftSkill

    chat-perf

    Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

    Also in 5 projects that use this

  • DepressionCenterSkill

    create-media-pack

    Create a coordinated project branding and media pack with three accessible design options, approved vector artwork, image exports, a branding guide, and README integration. Use when asked for a repository media pack, brand kit, or complete project visual identity.

    Also in 5 projects that use this

  • +7 more from microsoft

The file

Files
SKILL.md

Accessibility

Overview

New user-facing UI targets WCAG 2.2 AA by default. Honor an explicit legal/project target such as 2.1, and record it. Do not claim a check that was not performed.

When to use

  • Light pass on every /ui build
  • /design audits and dedicated a11y fixes
  • Keyboard, screen reader, contrast, focus, or target-size issues

When to skip

  • Palette construction → design-color (this skill owns conformance of pairs)
  • Type wrapping/truncation → design-typography
  • Hit-area feel only, with no conformance claim → polish

MUST

RuleDetail
Name the targetWCAG 2.2 AA unless the project/legal pin is different
Keyboard pathNative controls first; visible :focus-visible; logical order
Focus not obscuredSticky/fixed UI must not hide focused items (2.4.11)
Names and statesVisible labels; icon-only buttons have aria-label; toggles expose state
Contrast measuredText 4.5:1 / large 3:1 / UI 3:1 — measure pairs, do not guess from lightness
Not color aloneState needs icon, text, or pattern as well as color
Target size2.5.8 minimum is 24×24 CSS px (with exceptions). 44×44 is a pack recommendation, not 2.5.8
Dragging alternativePointer-drag actions have a non-drag method (2.5.7)
Auth / redundant entryNo cognitive-function test without an alternative (3.3.8); don’t re-ask data the user already gave in the same process (3.3.7)
Honest verificationUntested screen-reader or zoom checks are Not verified

Workflow

  1. Target — record 2.2 AA or the project pin.
  2. Keyboard — tab the real UI; trap/restore in dialogs; skip link on long nav.
  3. Names — labels, landmarks, live regions for dynamic status.
  4. Perceive — measured contrast; color-blind-safe state; 200% zoom if claiming it.
  5. Operate — 2.2 target size, dragging alternative, focus not obscured.
  6. Report — pass/fail per check; Not verified for tools not run.

Cheapest valid fix: native element → correct name/role → then ARIA.

Boundaries

  • May decide: native <dialog> vs labeled custom modal; live-region politeness.
  • Must not: report 44px as WCAG 2.5.8; claim SR/axe results without running them; use ARIA to paper over unkeyboardable divs.

Checklist

  • Conformance target recorded (2.2 AA or project pin)
  • Keyboard path and visible focus; focus not obscured
  • Labels / aria-label / toggle states / live regions as relevant
  • Contrast measured for text and UI components
  • No color-only state
  • 2.5.8 target size (24px) distinguished from 44px recommendation
  • Dragging alternative and accessible authentication checked if in scope
  • Untested items marked Not verified

Depth

Full checklist and recipes: references/accessibility-checklist.md. Contrast context: references/design-color.md, references/ux-foundations.md. Evidence classes: references/evidence-policy.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.