web-design-guidelines

Audit UI components for accessibility and responsive design standards.

27|9|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/sabahattink/antigravity-fullstack-hq --skill web-design-guidelines-sabahattink
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-design-guidelines
Source: https://github.com/sabahattink/antigravity-fullstack-hq/tree/main/skills/web-design-guidelines
Command: npx skills add https://github.com/sabahattink/antigravity-fullstack-hq --skill web-design-guidelines-sabahattink

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web teams wrestle with ensuring accessibility and responsive consistency across interfaces. This guide provides a concrete framework to audit UI components, enforce color contrast, semantic HTML, and keyboard navigation.

Core Features & Use Cases

  • Accessibility checks: color contrast, focus management, semantic markup, keyboard operability.
  • Responsive design guidance: mobile-first patterns, fluid typography, container queries.
  • Use Case: An engineer audits a dashboard for WCAG 2.1 AA compliance and updates components to meet guidelines.

Quick Start

Audit a UI component for accessibility and responsiveness using the guidelines.

Frequently Asked Questions about web-design-guidelines

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

FAQPage Schema
How do I audit a UI component for WCAG 2.1 AA compliance?

To audit a UI component for WCAG compliance, you review its color contrast, semantic HTML structure, focus management, and keyboard operability against documented best practices. This ensures the component meets accessibility standards for disabled users across devices.

What are the best practices for responsive design and mobile-first patterns?

Responsive design best practices involve applying mobile-first patterns, fluid typography, and container queries to adapt layouts. This approach ensures UI components scale correctly and maintain usability across various screen sizes.

Why does keyboard navigation fail in my dashboard layout?

Keyboard navigation fails when UI components lack semantic HTML and proper focus management. Auditing your dashboard against accessibility guidelines helps identify and fix missing focus states and operability issues for keyboard users.

Can I use these UI guidelines to check color contrast across different devices?

Yes, you can use these UI guidelines to check color contrast and responsive consistency across devices. The framework enforces documented accessibility standards to ensure UI components remain readable and operable on any screen size.

When do I need semantic HTML for accessibility audits?

You need semantic HTML for accessibility audits when evaluating how screen readers interpret UI components. It forms the baseline for color contrast, focus management, and keyboard operability checks required for compliance.