docs-accessibilitylisted

# docs-accessibility — Accessibility Analysis (WCAG 2.1 AA) ## Workflow 1. **Gather the docs** — get the list of pages in scope and read their content. If a semantic/graph search tool over the markdown is available (self-hosted `markdown-lsp`, or a connected Docsbook workspace), prefer it — it's faster and cheaper than scanning files; otherwise read the files directly with `grep`/`find`. Prioritize Tier 1 pages (quick-start, pricing, auth, install) first. 2. **Apply checklist** — scan each page for the three big categories: alt text, heading hierarchy, and anchor text. Then cover lists, tables, code blocks, video, and text readability. 3. **Produce report** — return one JSON issue object per finding, sorted by severity. ## Guardrails - Contrast ratios and runtime keyboard behavior depend on the rendered theme — these require a live browser check and are out of scope for this skill. - This skill covers only what is detectable from markdown source. - Do not edit any documentation files — surface findings only. - Target WCAG 2.1 AA by default; ask before applying stricter AAA criteria. - Empty alt (`![]()`) is correct for decorative images — flag only when the surrounding context implies the image is informative. ## Inputs This skill needs two things, by whatever means are available: - **The list of pages in scope** — a docs folder, a sitemap, or a doc graph. - **The content of each page** — read on demand. > **Acceleration (optional).** Graph/semantic search over the doc