web-design-guidelines

To audit UI code for accessibility and UX, provide a file path or pattern like 'src/**/*.tsx' to the skill, which fetches official Web Interface Guidelines and applies them to generate a rule-based findings report.

A Web Interface Guidelines compliance review evaluates UI code against established accessibility and usability best practices, flagging contrast issues, keyboard navigation gaps, and ARIA usage flaws to reduce design debt.

Yes, you can check ARIA usage and keyboard navigation gaps by running a targeted review against your codebase, which applies fetched rules to specified files and returns actionable recommendations.

To verify design consistency for typography and spacing, audit your UI components against the latest Web Interface Guidelines, which assesses responsive behavior and visual uniformity across pages.

Yes, the accessibility audit works with web project files like HTML and TSX, requiring a specified path or pattern to read files and apply fetched Web Interface Guidelines rules to them.

A limitation of checking web design accessibility automatically is that the review relies on fetching the latest guidelines and reading specified static files, meaning dynamic runtime state may not be evaluated.