web-design-guidelines

Audits frontend views for WCAG 2.1 AA accessibility, semantic HTML, and keyboard navigation.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill web-design-guidelines-tarunteja44
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-design-guidelines
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/web-design-guidelines
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill web-design-guidelines-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Frontend code often ships with hidden accessibility defects, broken keyboard navigation, poor semantic structure, and contrast failures that exclude users and hurt SEO. This Skill provides a systematic post-build audit pipeline to catch and fix these issues before release. ## Core Features & Use Cases - Accessibility Auditing: Runs a WCAG 2.1 AA checklist covering keyboard navigation, focus management, ARIA attributes, and screen reader compatibility. - Semantic HTML & SEO Validation: Verifies heading hierarchy, HTML5 landmark structure, meta tags, OpenGraph data, and layout shift prevention. - Responsive & Visual Polish Checks: Tests layouts at mobile, tablet, desktop, and wide viewports, plus contrast ratios and focus ring visibility. - Use Case: After building a React dashboard, run this audit to discover that icon buttons lack aria-labels, the modal does not trap focus, and body text fails the 4.5:1 contrast ratio, then apply the provided remediation patterns. ## Quick Start Audit the frontend view I just built for accessibility, semantic HTML, keyboard navigation, and responsive issues.

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 website for WCAG 2.1 AA accessibility?

Run a systematic checklist covering keyboard navigation, ARIA attributes, contrast ratios, and screen reader compatibility. Verify every interactive element is reachable via Tab, icon buttons have aria-labels, and body text meets the 4.5:1 contrast minimum.

How to test keyboard navigation in a web application?

Tab through the page checking that focus follows visual order, Enter and Space activate controls, Escape closes modals, and arrow keys work in radio groups and tab lists. Modals must trap focus until dismissed.

What contrast ratio is required for WCAG AA compliance?

WCAG 2.1 AA requires 4.5:1 for regular body text, 3.0:1 for large headings at 18pt or 14pt bold, and 3.0:1 for input borders and graphical icons. Focus outlines must remain distinct from both element and background colors.

Why is using div onClick bad for accessibility?

A div with onClick is not focusable, cannot be activated with Enter or Space, and is invisible to screen readers. Use native button or anchor elements instead, which provide keyboard interaction and semantic meaning for free.

Does semantic HTML structure affect SEO?

Yes, proper HTML5 landmarks like header, nav, main, and footer help search engines understand page structure. Combine them with a single h1, logical heading hierarchy, meta descriptions, and OpenGraph tags for best results.