ui-check

End-to-end UI checks for frontend quality orchestrate automated pipelines that validate design rules, execute lint gates, and perform accessibility verification to prevent regressions before deployment.

Automating frontend lint and a11y verification in a CI pipeline requires a multi-layer approach: running prevention checks, executing ESLint and Stylelint gates, and validating accessibility when a dev server is reachable, generating structured reports for actionable feedback.

Yes, you need a running dev server for accessibility validation because the a11y verification layer executes only when a dev server is reachable; otherwise, the accessibility check is skipped and the pipeline proceeds without it.

The frontend UI quality pipeline handles lint failures by blocking progress when the lint gate encounters errors, producing a structured report of the failures and halting the run to prevent deploying non-compliant code.

You can enforce design-system conformance checks for new UI components by running prevention checks for design documentation and shadcn readiness, which emit warnings without failing the run, alongside the standard lint and accessibility gates.

Automated UI check results are logged to a summary JSON file, specifically written to the ui-check-results/summary.json path after each run, providing an integrated log of all prevention, lint, and accessibility verification outcomes.