lighthouserc.json's collect.url list only audits three routes — http://localhost:3000/, /marketplace, /commitments — under a hard categories:accessibility: ["error", { "minScore": 0.9 }] assertion (i.e. this is a blocking CI gate, not just a warning). The create-commitment wizard at /create is not included, despite design/accessibility-audit/findings/02-create-wizard.md documenting it as "the highest-density flow in the audit, with five Critical/High findings" (including two Critical-severity issues: the Continue button being removed from the tab order, and step 1 rendering outside the <main> skip-link target). /settings and a representative /commitments/[id] detail page are also absent from the list. As configured, the CI accessibility gate can stay green indefinitely while the flow with the worst known accessibility state — the one most likely to actually regress a Lighthouse score — is never measured. Acceptance criteria: add /create, /settings, and a representative /commitments/[id] URL to lighthouserc.json's collect.url list, and confirm the accessibility assertion actually fails against /create's current, unremediated state (proving the gate is now meaningful) before the audit findings are fixed.
lighthouserc.json's
collect.urllist only audits three routes —http://localhost:3000/,/marketplace,/commitments— under a hardcategories:accessibility: ["error", { "minScore": 0.9 }]assertion (i.e. this is a blocking CI gate, not just a warning). The create-commitment wizard at/createis not included, despite design/accessibility-audit/findings/02-create-wizard.md documenting it as "the highest-density flow in the audit, with five Critical/High findings" (including two Critical-severity issues: the Continue button being removed from the tab order, and step 1 rendering outside the<main>skip-link target)./settingsand a representative/commitments/[id]detail page are also absent from the list. As configured, the CI accessibility gate can stay green indefinitely while the flow with the worst known accessibility state — the one most likely to actually regress a Lighthouse score — is never measured. Acceptance criteria: add/create,/settings, and a representative/commitments/[id]URL tolighthouserc.json'scollect.urllist, and confirm the accessibility assertion actually fails against/create's current, unremediated state (proving the gate is now meaningful) before the audit findings are fixed.