web-design-guidelines

UI design guideline compliance is checked by fetching up-to-date rules and comparing your web app, component library, or site files against them. It detects accessibility, usability, and consistency issues, emitting results in a terse file:line format.

The best way to check a component library for usability and consistency is to read target files or patterns and apply all Web Interface Guidelines checks. It emits a compliance report in a terse file:line format to catch issues early.

You cannot review UI code for compliance without specifying targets; if omitted, you will be prompted for files or patterns. The review then reads these files to apply all checks from the fetched Web Interface Guidelines.

Yes, the accessibility audit applies to web apps, component libraries, and sites where accessibility, usability, and consistency are priorities. It fetches fresh guidelines, reads target files, and applies all checks to emit results.

A compliance report in a file:line format is generated by fetching fresh Web Interface Guidelines, applying all checks to your web design files, and emitting the findings. This terse output helps locate and fix accessibility and usability issues.

Automated guideline checks fetch up-to-date Web Interface Guidelines and apply all rules to your project files, catching accessibility and usability issues early. This ensures comprehensive compliance reporting in a terse file:line format.