Accessibility audit

Skill TrevorEdris/fellowship-of-the-workflows/skills/accessibility-audit

WCAG 2.1/2.2 accessibility audit covering all POUR principles, keyboard navigation, screen reader strategy, color contrast, ARIA patterns, and semantic HTML. Triggered by: a11y audit, accessibility check, screen reader test, keyboard navigation, WCAG compliance, color contrast check, accessible, aria labels. Use when reviewing UI changes for accessibility compliance or conducting pre-release accessibility checks.From its SKILL.md

Install

npx -y skills add TrevorEdris/fellowship-of-the-workflows --skill accessibility-audit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.0 KB, as published. Nobody here has run it

Accessibility Audit

Audit the pending UI changes against WCAG 2.1/2.2.

Context

GIT STATUS:

!`git status`

PR METADATA:

!`gh pr view --json title,body,author,files,additions,deletions,headRefName,state 2>/dev/null || echo "No PR context - reviewing local branch"`

FILES MODIFIED:

!`gh pr diff --name-only 2>/dev/null || git diff --name-only origin/HEAD...`

DIFF CONTENT:

!`gh pr diff 2>/dev/null || git diff --merge-base origin/HEAD`

Prerequisites

Playwright MCP server connected
Live preview environment running (provide URL to agent)

Objective

Use the accessibility-audit agent to audit the UI changes above. Execute the 6-phase POUR review process with live browser testing. Your final reply must contain the complete markdown accessibility audit report with screenshots for visual findings.

The audit baseline is WCAG 2.1 Level AA. WCAG 2.2 criteria are assessed and labeled as enhancements where applicable. Severity levels follow the project taxonomy:

Critical — WCAG Level A failures (complete access barriers)
High — WCAG Level AA failures (significant barriers, fix before merge)
Medium — WCAG Level AAA or edge-case AA (fix in follow-up)
Low — Best practice enhancements (no WCAG criterion violated)

References

references/WCAG_CHECKLIST.md — Full WCAG 2.1/2.2 checklist organized by POUR principles
references/ARIA_PATTERNS.md — WAI-ARIA Authoring Practices 1.2 widget patterns and keyboard interactions
references/FALSE_POSITIVE_GUIDE.md — Exclusion list and confidence thresholds for avoiding false positives