From 20dd06ced50bd707005e203d35ead216dd253a87 Mon Sep 17 00:00:00 2001 From: rivassec Date: Fri, 23 Oct 2026 23:28:19 -0700 Subject: [PATCH] ci: make pa11y blocking All 36 pages pass since #107 (main run on f5ecf97). Drop continue-on-error so a new accessibility error turns the check red. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/a11y-check.yml | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/.github/workflows/a11y-check.yml b/.github/workflows/a11y-check.yml index 15df7c13..a30c260e 100644 --- a/.github/workflows/a11y-check.yml +++ b/.github/workflows/a11y-check.yml @@ -62,13 +62,11 @@ jobs: done - name: Run pa11y-ci - # Still non-blocking. The 2026-06-12 contrast "errors" were axe - # needs-review results (the hero gradient overlay hides the - # background; measured worst case is 5.5:1, above AA), which pa11y 6 - # reported as errors. levelCapWhenNeedsReview now keeps them as - # warnings. Every page in the sitemap is scanned. Flip to blocking - # in its own PR once the run is clean. - continue-on-error: true + # Blocking since 2026-10-23 (36/36 pages clean). The 2026-06-12 + # contrast "errors" were axe needs-review results (the hero gradient + # overlay hides the background; measured worst case is 5.5:1, above + # AA), which pa11y 6 reported as errors. levelCapWhenNeedsReview keeps + # them as warnings. Every page in the sitemap is scanned. run: >- pa11y-ci --config .pa11yci.json --sitemap http://127.0.0.1:8000/sitemap.xml