web-design-guidelines

To audit UI code for accessibility, fetch the latest web interface guidelines from a specified URL and evaluate your target UI files against those rules, outputting findings in a terse file:line format for direct integration into design reviews.

You can review frontend projects for a11y compliance by providing UI files or selection patterns; the system fetches up-to-date web guidelines at runtime via a WebFetch mechanism and applies all fetched rules to surface actionable usability issues.

The best way to integrate automated design reviews is to output accessibility and quality findings in a file:line format, allowing developers to directly pinpoint and resolve web guideline violations within their existing code review processes.

Yes, you need to provide the UI files you want reviewed or a pattern to select them so the system can read the targets and evaluate them against all fetched web guidelines to identify specific usability and accessibility issues.

Fetching up-to-date web guidelines works by using a WebFetch mechanism to retrieve the latest rules from a specified source URL at runtime, ensuring the accessibility and quality audit checks your UI code against current standards.

Evaluating UI patterns for web interface guidelines requires a valid guidelines source URL to fetch rules at runtime, and the output is limited to terse file:line findings, meaning you must manually interpret and apply the accessibility fixes.