web-design-guidelines

Accessibility auditing evaluates your UI code against the latest Web Interface Guidelines to detect semantic HTML, color contrast, keyboard navigation, and ARIA issues, outputting findings in a concise file:line format for review.

Checking color contrast and responsive behavior applies the latest web guidelines to your UI files, generating precise file:line findings that pinpoint exactly where your frontend components fail visual compliance checks.

Automating accessibility checks during a frontend code review requires fetching up-to-date web interface guidelines and applying them to your codebase, producing standardized file:line outputs that highlight semantic and ARIA failures for review.

Yes, you can verify ARIA usage and semantic HTML across your components. The Skill reads target UI files, evaluates them against fetched web guidelines, and returns a detailed file:line format critique of your accessibility implementation.

No, you do not need to provide your own accessibility rules to audit design assets. The Skill fetches the latest Web Interface Guidelines directly from its specified source to evaluate your UI codebase automatically.

A limitation of automated web design guideline audits is that while the Skill outputs precise file:line findings for semantic HTML and color contrast, complex keyboard navigation flows may still require manual verification.