playwright-accessibility-testing
Playwright Accessibility Testing
Use When
- Playwright accessibility testing
- Axe scans with
@axe-core/playwright - Accessibility violations or failing axe output
- WCAG checks with axe tags
- ARIA testing and accessible-name coverage
- Automated a11y tests for critical flows
- Page accessibility audits
Do Not Use When
- Manual keyboard, focus, or screen-reader behavior is the only concern
- Visual-only review is needed without automated checks
- Testing third-party pages the team does not control
Workflow
More from flpbalada/fb-skills
progressive-disclosure
Reduce complexity by revealing information progressively. Use when designing
10discuss-task
Clarify ambiguous tasks before action. Use when goal, scope, success criteria, constraints, or risks are unclear.
7react-useeffect-avoid
Guides when NOT to use useEffect and suggests better alternatives. Use when reviewing React code, troubleshooting performance, or considering useEffect for derived state or form resets.
6discuss-code
Critically discuss code issues with compact findings. Use when code needs review for logic, simplicity, structure, naming, or maintainability.
6react-key-prop
Guides proper usage of the key prop in React lists. Use this skill when rendering lists, mapping arrays to components, or troubleshooting list-related state bugs.
5cognitive-fluency-psychology
Apply cognitive fluency principles to improve clarity, trust, and conversion.
5