web-design-guidelines

To audit UI code for accessibility, the skill fetches Web Interface Guidelines, reads target HTML/JSX/TSX and CSS files, applies the rules, and reports violations in a file:line format. This surfaces focus management, ARIA, and semantic issues.

Automating checks for ARIA attributes and color contrast involves running a guideline-driven review against your component patterns. The skill compares target UI files against fetched rules and outputs conformance violations directly mapped to file and line numbers.

Yes, you can scan JSX and TSX component structures for UX conformance. The skill accepts target file patterns like components/**/*.tsx, applies Web Interface Guidelines, and reports accessibility and semantic HTML violations found within those files.

No dependencies or specific component libraries are required to perform an accessibility review. The skill operates independently by fetching guidelines from a remote source and analyzing your target UI files directly to identify design conformance violations.

To start a design audit for focus management issues, run the skill by providing target UI file patterns. It fetches the Web Interface Guidelines, scans the specified files, and reports any accessibility violations in a file:line format.

Limitations when scanning CSS and component files include relying on fetched Web Interface Guidelines for rule definitions and reporting violations only in a file:line format, without automatically fixing the identified accessibility or semantic HTML issues.