PP-250 local accessibility CI fixture, observed October 1, 2026 UTC Historical record, labelled October 19, 2026: this earlier hands-on check was made on October 1, 2026, before Practical Picks adopted its research-only method on October 3, 2026. It is kept as dated, bounded evidence of what these versions did on one synthetic page. It is not current testing and did not decide the article's current Pick. Versions have changed since: Pa11y CI 5.0.0 and @axe-core/cli 4.14.0 were current on October 19, 2026; Lighthouse CI 0.15.1 was still the latest release. See the article for current findings. Scope: original bad.html and clean.html in research/PP-250/fixture. This file reports a two-page functional check, not WCAG conformance or a comparative detection-rate study. No account, private page, external deployment or paid service was used. Environment: Linux x86_64; Node 22.23.3; npm 10.9.9; Chrome for Testing 152.0.7977.54. pa11y-ci 4.1.1; @axe-core/cli 4.13.0 and axe-core 4.13.0; ChromeDriver 152.0.3; @lhci/cli 0.15.1 and Lighthouse 12.6.1. Isolated packages were under /home/graklink-ops/.cache/pp250-tools. All three URL tools used the same Chrome binary. Fixture server command: python3 -m http.server 4250 --bind 127.0.0.1 --directory /home/graklink-ops/practicalpicks.guide/research/PP-250/fixture Listener check: ss -ltnp '( sport = :4250 )' showed LISTEN 127.0.0.1:4250, python3 PID 769516. The server was stopped after testing. Bad page: unlabeled #email input; img without alt; ordinary p.hint text #aaa on white. Clean page: matching label, image alt and #222 text. Both contain lang, title and main landmark. /missing.html is a real 404 on this server; curl -fsS -o /dev/null http://127.0.0.1:4250/missing.html exited 22. Pa11y CI command from repository root: /home/graklink-ops/.cache/pp250-tools/node_modules/.bin/pa11y-ci -c research/PP-250/pa11yci.json The tested pa11yci.json contained: { "defaults": { "chromeLaunchConfig": { "executablePath": "/home/graklink-ops/.cache/puppeteer/chrome/linux-152.0.7977.54/chrome-linux64/chrome", "args": ["--no-sandbox"] } }, "urls": [ "http://127.0.0.1:4250/bad.html", "http://127.0.0.1:4250/clean.html" ] } Result: bad.html 3 errors: contrast 2.32:1 with #767676 suggested, img missing alt, emailinput missing accessible name. clean.html 0 errors. Summary 1/2 URLs passed; exit 2. Clean-only pa11yci-clean.json: 1/1 URLs passed; exit 0. Missing-path command with pa11yci-clean.json plus http://127.0.0.1:4250/missing.html: 0 errors on both URLs; 2/2 URLs passed; exit 0. This is a false pass for route delivery. For the clean-only control, pa11yci-clean.json kept the same defaults and set urls to ["http://127.0.0.1:4250/clean.html"]. The exact missing-path command from repository root was: /home/graklink-ops/.cache/pp250-tools/node_modules/.bin/pa11y-ci -c research/PP-250/pa11yci-clean.json http://127.0.0.1:4250/missing.html axe CLI command from repository root: /home/graklink-ops/.cache/pp250-tools/node_modules/.bin/axe http://127.0.0.1:4250/bad.html http://127.0.0.1:4250/clean.html --chrome-path /home/graklink-ops/.cache/puppeteer/chrome/linux-152.0.7977.54/chrome-linux64/chrome --chrome-options=no-sandbox --exit Result: bad.html had one occurrence each of color-contrast, image-alt and label; selectors p, img and #email; rule links printed. clean.html 0 violations. Combined exit 1; clean-only exit 0. First attempt exited 1 before scanning because chromedriver binary was absent after --ignore-scripts install; matching ChromeDriver install fixed it. Missing-path command exited 1 because the Python 404 response had landmark-one-main and region violations; this did not establish an HTTP-status gate. Exact missing-path axe command used the same flags and replaced the page arguments with http://127.0.0.1:4250/missing.html: /home/graklink-ops/.cache/pp250-tools/node_modules/.bin/axe http://127.0.0.1:4250/missing.html --chrome-path /home/graklink-ops/.cache/puppeteer/chrome/linux-152.0.7977.54/chrome-linux64/chrome --chrome-options=no-sandbox --exit Lighthouse CI commands from research/PP-250: /home/graklink-ops/.cache/pp250-tools/node_modules/.bin/lhci collect --config=lighthouserc.json /home/graklink-ops/.cache/pp250-tools/node_modules/.bin/lhci assert --config=lighthouserc.json The tested lighthouserc.json contained: { "ci": { "collect": { "url": [ "http://127.0.0.1:4250/bad.html", "http://127.0.0.1:4250/clean.html" ], "numberOfRuns": 1, "chromePath": "/home/graklink-ops/.cache/puppeteer/chrome/linux-152.0.7977.54/chrome-linux64/chrome", "settings": {"onlyCategories": ["accessibility"], "chromeFlags": "--no-sandbox"} }, "assert": { "assertions": { "categories:accessibility": ["error", {"minScore": 1}], "color-contrast": ["error", {"minScore": 1}], "image-alt": ["error", {"minScore": 1}], "label": ["error", {"minScore": 1}] } } } } Result: collect exited 0 for both URLs. bad.html accessibility score 0.72; report failed color-contrast (body > main > p.hint), image-alt (body > main > img), label (body > main > form > input#email). clean.html score 1.00 with no failed accessibility audit. Category-only assertion first exited 1 but printed only score 0.72. With category and three named audit assertions, terminal printed all three audit IDs, explanations and rule links; exit 1. A clean-only collect/assert run with lighthouserc-clean.json exited 0 for both commands. The local HTML/JSON report contains selectors; assertion terminal output does not. Missing-path Lighthouse CI command used lighthouserc-missing.json. collect exited 1 with runtimeError code ERRORED_DOCUMENT_REQUEST and message ending `(Status code: 404)`. It emitted a long diagnostic log. The first LHCI attempt used an incorrect relative config path and failed before collection; correction succeeded on the second attempt. The clean-only and missing-path Lighthouse configs kept the same Chrome and collection settings, replacing the url array with clean.html or missing.html respectively. Unlike the final two-page config above, both controls asserted only categories:accessibility at minScore 1. Their exact collect commands from research/PP-250 were: /home/graklink-ops/.cache/pp250-tools/node_modules/.bin/lhci collect --config=lighthouserc-clean.json /home/graklink-ops/.cache/pp250-tools/node_modules/.bin/lhci collect --config=lighthouserc-missing.json The clean-only assertion command was: /home/graklink-ops/.cache/pp250-tools/node_modules/.bin/lhci assert --config=lighthouserc-clean.json These are the observed commands and tested config values, not a claim that the absolute Chrome or package paths work on another machine. Replace those paths with local Chrome and package paths to reproduce. No config shown here was tested with a different browser. `--no-sandbox` was part of this isolated Linux test, not a recommended default for a developer machine. Source configs and fixture: research/PP-250/. Results are one run per tool, with targeted setup retry and clean/missing controls. We did not rank speed, test hosted CI, simulate assistive technology, or measure general false-positive/false-negative rates. W3C WAI guidance: https://www.w3.org/WAI/test-evaluate/tools/selecting/