Accessibility snapshot report · projection
@accesslint/jest actually change?
Every team ships some share of features with accessibility
issues. Without a pre-merge guardrail, those regressions compound. The chart
below projects a team's trajectory over two years, with
@accesslint/jest adopted at the six-month mark.
The red dashed line is the counterfactual — the same team's projected path
without ever turning the ratchet on. Adjust the sliders to see where the
two lines diverge.
Tolerated violations in the baseline at adoption.
Share of new features shipping with accessibility issues.
New violations the team would ship at this leakage rate.
Projected open after 2 years if the ratchet is never turned on.
Projected open after 2 years, with adoption at the 6-month mark.
Net violations kept out of the codebase over the 2 years.
@accesslint/jest is introduced and the ratchet
engages. Slide the leakage rate and proactive fix rate below to
change both.
At 40% leakage, the team introduces
32 new violations per quarter, while closing
24 proactively. Without the ratchet, those
compete — net −8 per quarter. With
@accesslint/jest, new violations fail CI before merge,
so the net stays at +24 per quarter.