web-design-guidelines

To audit UI code for accessibility and design consistency, review HTML, CSS, and component files against Web Interface Guidelines. This process checks for semantic HTML, ARIA, contrast, spacing, and design-token violations, outputting findings in a file:line format.

Yes, you can check React components for design system and accessibility compliance. The review applies rule-based checks to component files, scanning for semantic HTML, ARIA usage, and design-token inconsistencies, returning actionable violations in a file:line format.

Automate web interface guideline checks by fetching authoritative rules from a remote URL before each run, then applying rule checks against specified files or patterns. This surfaces accessibility and UX consistency issues across pages and components for developer triage.

Auditing HTML and CSS for web interface guidelines finds contrast problems, semantic HTML errors, ARIA misuse, spacing inconsistencies, and design-token violations. Results are reported in a terse file:line format ready for developer triage or CI integration.

Yes, the UI code review fetches authoritative rules from a specified remote guidelines URL before each run. This ensures all accessibility, UX consistency, and design-token checks use the latest available guidance during the audit.

Accessibility audit results use a terse file:line format for CI integration. This format directly maps rule violations from HTML, CSS, and component files to their exact locations, making them ready for automated developer triage.