What accessibility checks belong in CI for headless commerce?

CI should run component checks plus browser tests for navigation, product selection, cart, forms, dialogs, and errors. Fail builds on newly introduced critical rules, but keep a reviewed baseline for known issues so noise does not disable the gate. Add manual testing before major releases because automation cannot judge every focus, announcement, and task-completion problem.

Build a useful gate

Test representative routes with stable fixtures, save the exact rule and selector, and fail only on regressions the team can act on. Flaky tests and unexplained scores teach developers to ignore accessibility.

Continue after deployment

Production differs through content, flags, apps, and live data. Rescan after release, compare with CI, and open a dated issue when a production-only defect appears. Close it only after a live passing retest.