Add axe scans to your existing tests, and pair them with manual review. Deque says axe-core finds on average 57% of WCAG issues automatically and marks uncertain results as "incomplete" for manual review; other estimates of automation's coverage are lower, around 30%, so treat a clean scan as a baseline, not a certificate. Playwright's docs show scanning whole pages or specific components with the axe package and recommend combining automated tests, manual assessments and inclusive user testing. Run scans at each new UI state (dialogs, menus, error states) and fail the build on new violations. Regulations such as the European Accessibility Act and US ADA and Section 508 rely on WCAG.

Sources: axe-core README, Playwright accessibility testing, Storybook docs, David Mello summary of coverage estimates