web-design-guidelines

To check web accessibility and UI conformance, this Skill fetches current Web Interface Guidelines, parses them, and analyzes your frontend files to identify non-compliant patterns. It reports findings in a file:line format so you can locate and fix issues quickly.

Running a UI review involves pointing the Skill at your project directory containing UI components and styles. The Skill fetches the latest rules from a specified source URL, applies them to your target files, and outputs a detailed report of design and accessibility violations.

The best way to ensure your web frontend matches up-to-date usability guidelines is to automate validation against a fetched source of current rules. This process reads your templates and styles to detect visual inconsistencies and accessibility gaps before release.

Yes, you can validate specific UI components and styles for a11y compliance. The Skill allows you to apply fetched guidelines to targeted file patterns within your project workspace, reporting conformance gaps only for the specified components rather than the entire repository.

No external dependencies are required to fetch web accessibility rules. The Skill operates independently to retrieve the latest guidelines from a specified URL, parse the content, and evaluate your codebase for UI compliance without needing additional packages.

Conformance gaps appear in your UI review report because the Skill compares your existing frontend code against newly fetched, up-to-date Web Interface Guidelines. It identifies outdated patterns, accessibility issues, and visual inconsistencies, outputting them in a file:line format for correction.