web-design-guidelines

To audit frontend source files for accessibility and UX anti-patterns, review the component code for missing aria-labels, unlabeled form controls, absent alt text, and semantic HTML misuse to surface usability and compliance issues before release.

Web design guidelines for interaction rules validate focus-visible states, keyboard handlers, and reduced-motion support. Checking these guidelines ensures your interface meets animation best practices and remains accessible to keyboard users.

Yes, you can review a pull request for frontend performance anti-patterns. The audit flags missing image dimensions, suggests lazy-loading, identifies virtualization needs, and checks for hydration risks to optimize web interface performance.

The best way to report UI review findings for a component library is producing a terse file:line formatted report. This format directly maps accessibility, form label, and animation violations to their exact location in the frontend source files.

Yes, this accessibility audit checks for localized content and form label issues. It identifies unlabeled form controls, validates semantic elements, and surfaces localization problems alongside standard a11y compliance violations in frontend projects.