Share an accessibility report
Accessibility testing has an unusual property: the tool runs in engineering, and most of the fixes don't belong to engineering. Alt text is a content decision. Link wording is a content decision. Contrast and focus order are design decisions. Heading structure is usually both.
So the report lands in a CI artifact zip, which is the one place none of those people can reach, and the ticket that comes out of it says "fix a11y issues" with a screenshot attached.
Publish the report instead
npx pa11y-ci --reporter pa11y-ci-reporter-html || true
curl -fsS -X PATCH \
"https://commareports.com/api/v1/reports/$COMMA_REPORT_ID" \
-H "Authorization: Bearer $COMMA_API_TOKEN" \
-H "Content-Type: application/json" \
-d "$(jq -n --rawfile html pa11y-ci-report/index.html \
--arg title "Accessibility — $(date +%F)" \
'{title: $title, html: $html}')"
For @axe-core/cli, run it with --save results.json and render with
axe-html-reporter; for Lighthouse, --output html already writes a
self-contained file. All three publish with the same curl. Use a
scoped token with reports:write.