web-design-guidelines

To audit UI code for accessibility, validate target files against Web Interface Guidelines by specifying path patterns like 'src/**/*.html'. The tool fetches current remote rules, reads matching files, and reports design conformity findings in a terse file:line format.

Yes, you can check web project accessibility using a specific file path. The tool accepts flexible targeting via specific paths like 'index.html' or broader patterns, scanning the target UI files and reporting any UX or accessibility guideline violations.

Web design guidelines stay current during a UI audit through a remote source fetch mechanism. The tool retrieves up-to-date guidelines from a remote source before validating your codebase, ensuring accessibility checks and UX audits apply the latest rules.

The best way to review UI code for UX consistency is using pattern-based file matching against centralized guidelines. By targeting patterns like 'src/**/*.html', the tool scans multiple files simultaneously and outputs concise file:line reports for every design conformity deviation.

The accessibility audit report uses a terse file:line format for code findings. This concise output style pinpoints exactly where UI code deviates from Web Interface Guidelines, enabling quick navigation to accessibility or UX issues within your project files.