accesslint-diff

Accessibility diffing against a baseline compares current page violations with stored data to identify new issues. It reads a live target, manages baseline storage, and reports only the changes, using stash-based diffing by default.

Yes, you can compare accessibility issues against a named branch by using the branch mode. This mode guides rebuild or wait-for gating during branch diffs to ensure the live target accurately reflects the branch state before reading violations.

The best way to identify new accessibility issues is to diff the live page against a stored baseline. This method reports only what changed, allowing you to quickly verify fixes and spot newly introduced violations without reviewing the entire page.

Stash-based accessibility diffing works by comparing the live target's current accessibility violations against a baseline captured before changes were applied. It isolates only the new issues introduced by the stashed code changes for focused testing.

Yes, when using branch mode, you often need to rebuild or wait for the application to reflect the branch state. The tool provides guidance for rebuild gating and waits to ensure the live target matches the named branch before diffing.

If your accessibility diff shows unchanged violations, the baseline may not be properly stored or the live target may not reflect the correct branch state. Ensure baseline storage is handled correctly and use rebuild gating to verify the target.