web-design-guidelines

Auditing frontend code for accessibility involves reading your HTML, CSS, and JS files and checking them against Web Interface Guidelines to identify performance and UX gaps. Findings are reported in a file:line format.

Checking HTML, CSS, and JS against web interface guidelines is best done by fetching fresh rules and applying them to your target files. This process identifies accessibility and usability gaps, reporting findings in a terse file:line format.

Yes, you can use this tool to review your UI project for performance gaps. It reads your specified frontend files, applies all rules from fetched guidelines, and outputs accessibility and usability findings in a file:line format.

A UI audit identifies accessibility gaps in frontend projects by fetching the latest web interface guidelines, reading your target files, and applying all rules to pinpoint specific issues. Results are delivered in a file:line format.

You need to specify files for a design review, or the tool will prompt you for files and patterns. It then reads those exact frontend files to check against all rules in the fetched guidelines and report findings.