web-a11y-css

Reviews and writes CSS that preserves accessibility across contrast, focus, motion, and zoom.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/pedropenha/project-skills --skill web-a11y-css-pedropenha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-a11y-css
Source: https://github.com/pedropenha/project-skills/tree/main/.agents/skills/web-a11y-css
Command: npx skills add https://github.com/pedropenha/project-skills --skill web-a11y-css-pedropenha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? CSS changes often break accessibility in subtle ways: removed focus outlines, color-only state indicators, motion that ignores user preferences, and layouts that fail under zoom or forced-colors mode. This Skill gives you concrete rules and a checklist to catch those regressions before they ship. ## Core Features & Use Cases - Accessibility CSS Rules: Enforces five core rules covering focus indicators, color independence, reduced motion, zoom/reflow resilience, and semantic integrity. - Risky CSS Checklist: Provides a review checklist for focus styles, contrast, target sizes, motion preferences, and properties like display, visibility, content-visibility, and pointer-events. - Structured Review Output: Reports preference modes tested, risky properties used, and semantic mitigations applied. - Use Case: When restyling a design-system button component, use this Skill to verify the new focus ring is visible, the disabled state is not conveyed by color alone, and the styles hold up in forced-colors mode and at 200% zoom. ## Quick Start Review my stylesheet changes for accessibility issues covering focus styles, contrast, reduced motion, and forced-colors mode.

Frequently Asked Questions about web-a11y-css

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make CSS focus styles accessible?▼

Never remove focus indicators without a visible replacement. Ensure focus styles are visible and high contrast against the component background, and verify they remain distinguishable in forced-colors mode and at high zoom levels.

How to respect reduced motion preferences in CSS?▼

Respect reduced motion by disabling or reducing animations when users request it via their system preference, and provide user control for moving content. Test that transitions and animations do not run for users who opt out.

Which CSS properties can break accessibility semantics?▼

Properties like display, visibility, content-visibility, and pointer-events can break semantics or operability when misused. Hidden labels, legends, captions, and referenced text must still name controls correctly for assistive technologies.

Does accessible CSS need to work in forced-colors mode?▼

Yes, usable styling must be preserved under forced-colors mode, zoom, reflow, and large text settings. Verify that states are not conveyed by color alone and that controls remain operable when the platform overrides your palette.

What should an accessibility CSS review report include?▼

A review should list the preference modes tested, the risky CSS properties used, and any semantic integrity mitigations applied. This makes it clear which accessibility scenarios were verified and which risks remain.