Staging acceptance pending after resolved automated axe regression #3

Reproducible release blocker on main (2026-10-14)

• Current inspected main f3ff20ebf5945071c3bf0b4c1d95e146d06716b9 moved the existing reflow CSS to theme.json. Exact main WordPress runtime smoke 38637227488 still ends failure on WordPress latest / PHP 8.3 matrix.
• Browser/long-content 320px reflow passes now. Next blocker: tests/runtime/axe_audit.py sees six axe automated WCAG-rule violations on six synthetic routes; no manual WCAG pass may be claimed. Original CI printed aggregate count only.
• Diagnostic-only PR #2 adds bounded synthetic route/rule ID/impact/count logging while retaining the existing failing assertion. PR #1 was closed as unmerged overlap with separately committed main reflow change (no double CSS).

Release / correction checklist

• Record exact axe rule IDs and affected synthetic routes from PR qa: print bounded axe rule IDs to diagnose 1.0.4 runtime failure #2 CI, without customer content or DOM details in public logs.
• Identify existing theme/Core/WooCommerce ownership and fix each genuine violation with minimal WordPress-native change; don't weaken the failing assertion to make CI green.
• Run exact source validation and all 4 WordPress/PHP/WooCommerce disposable runtime smoke profiles green, including 320px/375px reflow, editor interactions, backup/restore; verify exact theme ZIP hash.
• Independently assess staging keyboard/screenreader/real-site WCAG coverage with Website QA owner before any production-ready claim.
• Merge only passing, reviewed correction to main and verify post-merge main CI, hashes and rollback. No client/site deploy authorized.

No release GO while any required runtime check is red or pending.

Follow-up verificatie 2026-10-14

• De oorspronkelijke synthetische axe-list-regressie is op main hersteld in commit f7dc335.
• Starter source checks en WordPress runtime smoke op exact deze commit zijn geslaagd; 5/5 runtimejobs groen, inclusief reflow en geautomatiseerde axe-checks.
• Diagnose PR qa: print bounded axe rule IDs to diagnose 1.0.4 runtime failure #2 is aantoonbaar overbodig geworden en zonder merge gesloten; er is geen dubbele CSS-fix geïntroduceerd.
• Onafhankelijke stagingacceptatie met echte schermlezers/toegankelijkheid en gevraagde installatie-/rollbackcontrole moet nog plaatsvinden. Dit blijft geen productie- of WCAG-vrijgave.

Bij deze issue is de automatische bug opgelost; alleen de expliciet genoemde release-/human-acceptatiepoort staat nog open.

Current main verification — 17 October 2026

The newer theme 1.0.5 passed Starter source checks and WordPress runtime smoke at exact commit ce8c7b9de73fbc07317a71b54cefc242327dd4fe. The earlier synthetic axe regression is therefore not the current CI blocker.

Still open: independent staging review, actual assistive-technology checks, target WooCommerce/provider compatibility, and real environment restore/rollback acceptance. Do not treat this issue as production or full WCAG approval.