web-design-guidelines

To audit frontend UI for accessibility and best practices, fetch the latest Web Interface Guidelines from the official source and apply rule-based checks to your targeted files. This validates accessibility, contrast, semantics, and performance in your UI assets.

A UI accessibility audit for frontend projects is a review process that checks web interfaces against published guidelines to verify compliance with accessibility, contrast, semantics, and performance rules, reporting any non-conformance found in the files.

Yes, you can audit specific file patterns like src/components/**/*.tsx for web design compliance. The audit operates on user-provided file patterns to produce focused findings on accessibility and best practice violations within those targeted UI assets.

You should run an accessibility and design review on your web interface during code reviews, feature deliveries, or pre-release checks before QA. This ensures your new UI components comply with the latest Web Interface Guidelines prior to release.

Yes, the web design guidelines audit requires fetching rules from the official guidelines source using WebFetch. This ensures the validation checks applied to your UI files always reflect the latest published accessibility and performance standards.

A limitation of automated rule-based checks for UI accessibility is that they validate code-level conformance against published guidelines, but may not capture the full user experience. The audit operates strictly on provided file patterns to identify non-conformance in frontend assets.