a11y-responsive

Implements and audits accessibility, responsive layouts, and cross-browser compatibility for web interfaces.

1|Updated Aug 18, 2026
One-click install
npx skills add https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent --skill a11y-responsive-scsm-unrestrict
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y-responsive
Source: https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent/tree/main/frontend-engineer/skills/a11y-responsive
Command: npx skills add https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent --skill a11y-responsive-scsm-unrestrict

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web interfaces often fail users on keyboards, screen readers, small screens, or older browsers because accessibility, responsive behavior, and compatibility checks are skipped during development. This Skill provides concrete checklists and rules to build and verify interfaces against WCAG AA, mobile-first breakpoints, and progressive enhancement. ## Core Features & Use Cases - Accessibility implementation: Semantic HTML landmarks, keyboard and focus management (focus traps, Esc handling, focus return), minimal ARIA usage, form labeling and error association, and 4.5:1 contrast verification. - Responsive layout guidance: Mobile-first CSS, content-driven breakpoints (640/768/1024/1280), fluid layouts with flex/grid, clamp() typography, srcset images, and 44px touch targets. - Cross-browser compatibility: Feature detection with @supports over UA sniffing, progressive enhancement, fallbacks for newer CSS features, and real-browser verification. - Use Case: When reviewing a modal dialog component, use this Skill to verify focus moves into the dialog on open, Tab cycles inside it, Esc closes it, and focus returns to the trigger button. ## Quick Start Audit this page's accessibility, responsive breakpoints, and keyboard navigation, then list issues with locations and suggested fixes.

Frequently Asked Questions about a11y-responsive

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

FAQPage Schema
How do I make a modal dialog accessible with keyboard navigation?

Move focus into the dialog when it opens, trap Tab cycling inside the container, close on Esc, and return focus to the trigger element on close. Use semantic HTML first and add ARIA attributes like aria-labelledby only where native semantics are insufficient.

What color contrast ratio is required for WCAG AA compliance?

WCAG AA requires at least 4.5:1 contrast for body text and 3:1 for large text and UI component boundaries. Verify values with a contrast checking tool rather than judging by eye, and never rely on color alone to convey state.

How do I choose responsive breakpoints for a website?

Use a mobile-first approach: write narrow-screen styles first, then add breakpoints where the layout actually breaks. Common reference points are 640, 768, 1024, and 1280 pixels, but content-driven breakpoints beat fixed device lists.

Should I use ARIA roles or semantic HTML elements?

Prefer semantic HTML over ARIA whenever possible. A real button element beats a div with role="button", and landmark elements like nav and main reduce the need for explicit roles. Add ARIA only for gaps semantics cannot cover.

How do I handle CSS features that older browsers do not support?

Use feature detection with @supports instead of UA sniffing, and apply progressive enhancement so baseline functionality works everywhere. Provide fallbacks such as flexbox before grid, and let build tools like autoprefixer handle vendor prefixes.