web-design-guidelines

To audit HTML and CSS for accessibility and UI guideline compliance, provide your frontend files to the Skill. It fetches the latest Web Interface Guidelines, evaluates the code for accessibility gaps and visual inconsistencies, and reports issues in a terse file:line format.

The best way to check frontend JavaScript for UX inconsistencies is a guideline-driven review against official UI standards. The Skill evaluates your JavaScript code to identify interaction violations and visual inconsistencies, outputting specific file and line numbers for remediation.

Yes, you can audit a design-system page for visual and interaction consistency. By providing your UI files or patterns, the Skill compares them against the latest UI guidelines to verify compliance and identify any accessibility or UX gaps before release.

Yes, the UI audit checks keyboard navigation and semantic HTML issues. It systematically evaluates your frontend code to identify contrast problems, semantic violations, and keyboard-navigation gaps to improve inclusive design across components and pages.

No, you do not need to manually provide the Web Interface Guidelines for the code review. The Skill automatically fetches the latest guidelines from the official source and compares them against your target HTML, CSS, and JavaScript files to report compliance issues.

The tool reports UI code violations and accessibility gaps in a terse file:line format. After fetching the latest guidelines and comparing them against your target files, it outputs specific file and line references for quick remediation of visual and interaction inconsistencies.