web-design-guidelines

To audit UI code for accessibility and design compliance, provide your UI files for review. The skill fetches the latest Web Interface Guidelines, evaluates your code against all rules, and reports findings in a concise file:line format.

Accessibility validation in a UI design review includes checking color contrast, keyboard navigation, ARIA attributes, and semantic HTML. These checks are applied across your project files to ensure compliance with official Web Interface Guidelines.

Yes, you can review UI consistency and visual standards in pull requests. The skill applies checks across UX patterns, spacing, typography, and component usage, reporting guideline violations and suggested fixes in a concise file:line format.

No, you do not need to manually provide the Web Interface Guidelines for an audit. The skill automatically fetches the latest guidelines from the source, reads your target UI files, applies the rules, and reports the findings.

The best way to check semantic HTML and ARIA attributes is to run a guidelines-based audit on your UI files. The skill validates these elements against the latest official Web Interface Guidelines and reports violations with specific file and line details.

UI audit findings for accessibility and visual issues are reported in a concise file:line format. After fetching the guidelines and evaluating your code, the skill surfaces guideline violations and suggested fixes directly mapped to your target files.