web-design-guidelines

To audit web UI code for accessibility and best practices, provide a file path or glob pattern to review. The tool fetches the latest Web Interface Guidelines, applies all rules to your specified files, and returns compliance issues in a concise file:line format for quick fixes.

A UI compliance review checks your frontend files against an authoritative set of Web Interface Guidelines. It locates accessibility, design, and UX best practice issues by reading your code and applying fetched rules, returning findings in a terse file:line format.

Yes, you can target specific frontend files or patterns for a UX audit. Provide a file path or glob pattern, such as src/components/**/*.tsx, to focus the compliance review and receive actionable findings only for the specified files.

Yes, the accessibility review always uses the latest web interface guidelines. It fetches the most current guideline rules from the official source URL before analyzing your code to ensure all compliance checks reflect up-to-date standards.

Code review findings for design compliance issues use a terse file:line format. This concise output identifies exactly where accessibility and UX best practice violations occur in your web UI files so you can quickly locate and fix them.

You should run a web UI accessibility audit when preparing a release or verifying that key UI components meet design best practices. It confirms your frontend files comply with authoritative Web Interface Guidelines before deployment.