Audit, test, and maintain
Prioritize and prevent regressions
Rank barriers by user impact and reach, then add the cheapest reliable guard that stops recurrence.
9 minute lesson
An impossible registration path is fixed before a minor redundant announcement, and the label regression gains an automated test. That contrast gives us something useful to test instead of a rule to memorize.
Not every issue has equal severity, and a fix that is not protected can disappear in the next component refactor. The useful target is not encyclopedic coverage. Make one deliberate choice, observe its consequences, and know which requirement would make you revise it.
The happy path can hide a bad design: you can sort issues only by tool severity or fix count and still get one successful demo. Push past the demo. combine task blockage, affected users, frequency, workaround, and confidence, then add review or automation, then test the condition most likely to prove the choice wrong.
The module is moving toward one outcome: Turn the repaired page into a repeatable accessibility practice rather than a one-time cleanup. Save the before-and-after evidence now; it will make the final project review much more honest.
Triage the flawed page findings and defend the first three fixes plus their regression guard. Save the evidence, then explain which requirement would force you to choose a different design.
Lesson completed