nickcrew/accessibility-audit
skills/accessibility-audit/SKILL.md
Fast, high-signal accessibility triage for pages, components, or PRs targeting WCAG 2.2 AA compliance.
$ install --global
skillsauthnpx skillsauth add nickcrew/claude-cortex accessibility-auditInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 7, 2026, 8:28 PM10.2s1 file scanned
SKILL.md
- name:
- accessibility-audit
- description:
- Fast, high-signal accessibility triage for pages, components, or PRs targeting WCAG 2.2 AA compliance.
Accessibility Audit Skill
Fast, high-signal accessibility triage for pages, components, or PRs. This is a lightweight check, not a full compliance audit.
When to Use This Skill
- Quick accessibility triage before releases
- Component-level a11y verification
- PR review for accessibility regressions
- Smoke checks for WCAG compliance
- Validating keyboard navigation on new features
Quick Audit Checklist
1. Automated Snapshot (Recommended)
Run one of these automated tools first:
npx @axe-core/cli <url>- Quick axe-core scannpx pa11y <url> --standard WCAG2AA- Pa11y audit- Lighthouse Accessibility score (Chrome DevTools > Lighthouse > Accessibility)
2. Keyboard Basics
| Check | Expected | |-------|----------| | All interactive elements reachable via Tab | Yes | | Focus indicator always visible | Yes | | No keyboard traps | Yes | | Logical tab order | Yes | | Skip link works for long pages | Yes |
3. Semantics and Labels
| Check | Expected | |-------|----------| | Single, descriptive H1 | Yes | | Logical heading order (no large jumps) | Yes | | Form inputs have visible labels or aria-label | Yes | | Buttons and links have clear names | Yes | | Images have meaningful alt text (or empty for decorative) | Yes |
4. Visual Contrast
| Element | Minimum Ratio | |---------|---------------| | Normal text | 4.5:1 | | Large text (18pt+ or 14pt bold+) | 3:1 | | UI components (inputs, buttons, focus rings) | 3:1 |
5. Motion and Updates
| Check | Expected |
|-------|----------|
| Respects prefers-reduced-motion | Yes |
| Dynamic updates announced (aria-live) | Yes |
Output Format
After running the audit, report findings as:
## Accessibility Audit: [Component/Page Name]
### Result: [Pass | Needs Fixes | Escalate to Full Audit]
### Findings
| Severity | Issue | Location | Fix Guidance |
|----------|-------|----------|--------------|
| Critical | [Description] | [Selector/Line] | [How to fix] |
| Major | [Description] | [Selector/Line] | [How to fix] |
| Minor | [Description] | [Selector/Line] | [How to fix] |
### Escalation Recommendation
[If applicable, explain why a full audit is needed]
Escalate to Full Audit When
- New or changed navigation structure
- Complex forms or authentication flows
- Custom widgets or advanced interactions (modals, accordions, tabs)
- Public releases or compliance requirements
- Significant page structure changes
- Failed automated scans with multiple critical issues
Notes
- This smoke check targets WCAG 2.2 AA by default
- If a different compliance level is required, state it explicitly
- Automated tools catch ~30-40% of issues; manual testing is essential
- Test with actual screen readers (VoiceOver, NVDA) for comprehensive coverage
Related Skills
nickcrew/product-strategy
development
VerifiedTrustedCommunity
Product vision, roadmap development, and go-to-market execution with structured prioritization frameworks. Use when evaluating features, planning product direction, or assessing market fit.
15SKILL.mdUpdated Apr 7, 2026
nickcrew/agent-loops
development
VerifiedTrustedCommunity
Complete operational workflow for implementer agents (Codex, Gemini, etc.) making code changes and writing tests. Drives all work through atomic commits — each loop operates on the smallest complete, reviewable change. Defines the Code Change Loop, Test Writing Loop, Lint Gate, and Issue Filing process with circuit breakers, severity levels, and escalation rules. Requires `cortex git commit` for all commits. Includes bundled provider-aware review scripts that keep same-model shell-outs as the last resort, plus a fresh-context Codex fallback for code review and test audit. Use this skill when starting any implementation task.
15SKILL.mdUpdated Apr 7, 2026
nickcrew/product-manager
development
VerifiedTrustedCommunity
Use this skill when writing product requirements documents, prioritizing features, creating user stories, defining acceptance criteria, or setting product metrics. Trigger phrases: 'write a PRD for', 'prioritize this feature backlog', 'write user stories for', 'help me define acceptance criteria', 'what metrics should we track for'. Not for writing code, designing UI mockups, or conducting user research interviews.
13SKILL.mdUpdated Apr 7, 2026
nickcrew/playwright-cli
tools
VerifiedTrustedCommunity
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
13SKILL.mdUpdated Apr 7, 2026