A finding that dies inside a panel is not worth much. Real accessibility work has to move. It gets handed to engineers, QA, delivery people, clients, and sometimes auditors. If the evidence falls apart in that handoff, the tool has failed halfway through the job.
That is why A11Y Cat carries ticketing output, evidence bundles, local status handling, and packaging rules. The repo talks about ticket generation, evidence bundle contracts, artefact packaging, and release preparation. All of that exists because the life of a finding does not end when it is first spotted.
I wanted something that could support the messy reality of teams: open, needs review, false positive, accepted temporarily, fixed pending retest. Those states matter. Handoff matters. Reproduction matters. Context matters.
This part of the project probably says the most about how I think. I am not interested in tools that only perform at the moment of discovery. I care about whether the result survives contact with a real team.
Documentation trail
COMMAND_REFERENCE.mdRELEASE_CHECKLIST.mdTECHNICAL_GUIDE.md
