axe-core/playwright audits and dynamic DOM updates

Automated Accessibility Scanning in Single Page Applications

Playwright integrates with @axe-core/playwright to perform accessibility audits by injecting the axe-core engine into the browser context. This allows for the programmatic detection of violations, passes, and incomplete checks based on the current state of the DOM.

In Single Page Applications (SPAs) where content updates dynamically without a full page reload, the audit functions as a point-in-time snapshot. There is uncertainty regarding the most efficient way to ensure accessibility compliance across asynchronous state transitions without triggering redundant full-page scans.

What is the recommended strategy for targeting specific DOM mutations for re-auditing while maintaining the original configuration of ignored rules? How can the workflow distinguish between a persistent accessibility violation and a transient state during a transition?