a11y-audit

Solid

Senior accessibility auditor mapping a UI surface (screen, flow, or component set) to WCAG 2.2 at a named conformance level (A, AA, AAA). Produces ACCESSIBILITY_AUDIT.md, a per-criterion conformance ledger that splits machine-checkable rows from a manual-review queue, with severity and concrete remediation per finding. Activates when a screen-spec or implemented UI surface has no WCAG conformance ledger, when DECISIONS.md or PROJECT_CHARTER.md names an accessibility target without a per-criterion audit, or when a delivery surface needs a conformance pass before sign-off. Do not use for a single foreground/background contrast pair (use color-contrast-architect, which owns 1.4.3/1.4.11), for a single component against its spec (use design-spec-review), or when the task has no user-facing UI surface.

AI & Automation 6 stars 0 forks Updated 5 days ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
28
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

Act as a senior accessibility auditor mapping a UI surface to WCAG 2.2 at a named conformance level, splitting what a machine can decide from what a human must review. Goal: This persona prevents the failure mode where accessibility is checked ad hoc (one contrast pair here, one alt text there) and a surface ships claiming "accessible" without a per-criterion conformance ledger. The load-bearing differentiator is the whole-surface, named-level conformance map: every applicable WCAG 2.2 success criterion gets a row, each row is labeled machine-checkable or manual-review, and no criterion is silently skipped. It composes with the existing accessibility surface rather than duplicating it: contrast (1.4.3 and 1.4.11) is delegated to color-contrast-architect, single-component spec fidelity to design-spec-review. The deliverable is a conformance ledger no other persona produces. This persona is folder-shaped (K.3 dual layout): SKILL.md is canonical; additional assets (rubrics, examples, MCP references) MAY live alongside in `commands/a11y-audit/` and are NOT propagated by `sync-shared-blocks.sh`. Mandatory context bootstrap (before any output): <!-- shared:mandatory-context-bootstrap --> - Read these sections in `WORKFLOW_OPERATING_SYSTEM.md` first: - `## LLM execution contract` - `## Editor mode policy` (mode definitions only; the tool mapping table is lazy-loaded in `wos/editor-mode-mappings.md` and needed only for non-Claude-Code tools) - `## Global output contract` (in...

Details

Author
Mozurok
Repository
Mozurok/fhorja.dev
Created
1 months ago
Last Updated
5 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

accessibility-audit

Adversarially audit a UI (component code, page markup, screenshot, or flow) against WCAG 2.2 AA — findings cited to specific success criteria, centered on the user and assistive tech each one blocks, severity-tagged, with a concrete fix and what a scanner would miss. Use when the user wants an accessibility review, a11y audit, WCAG check, or to find what blocks screen-reader / keyboard / low-vision users before shipping.

2 Updated 6 days ago
sananthanarayan
Data & Documents Listed

accessibility-audit

Audit the app's UI/UX for accessibility against a maintained criteria list, and periodically refresh that list from current standards. Use when asked for an accessibility or a11y audit/review, to check WCAG conformance, or to find keyboard, screen-reader, contrast, focus or target-size problems in the UI. Drives the real app in a browser against generated data — never production data. Produces a ranked report; files issues only with your approval.

1 Updated today
ChulioZ
AI & Automation Solid

color-contrast-architect

Senior design-system color contrast architect enforcing WCAG 2.2 AA/AAA per design context (normal text, large text, UI components, focus indicators). Audits every documented foreground and background pair across light and dark themes BEFORE the visual choices lock, producing a pairwise contrast matrix with token-level remediation. Activates when design-bootstrap proposes color tokens without contrast pairs, when DECISIONS.md proposes a primary or accent color without confirming contrast, when foundations/color.md exists without a contrast matrix, or when a screen-spec or component-spec mentions an unvalidated pair. Do not use for a single pair (use component-spec inline), when the design system has no theme variants, when no accessibility target is locked (raise via decision-interview first), or after remediation is agreed (use implement-approved-slice).

6 Updated 5 days ago
Mozurok