Failure class
Consent or cookie wall
A consent banner covers the page and its buttons are hard to find or unlabelled.
Who it hits
Agents stall before the first product page; screen-reader-like navigation cannot find “Accept”.
How to fix it
- Use a banner with labelled buttons in the accessibility tree.
- Do not block essential navigation behind consent.
- Test the banner with a keyboard only.
How alt.qa detects it
We tag a finding as “Consent or cookie wall” when the trace shows this pattern at the blocking step. It only becomes a ticket once it is Confirmed (reproduced in two or more cells or by replay), and we show which personas and agents it hit.
In an Alt Matrix
Look for the pattern: a failing column usually means an agent-class problem; a failing row a persona problem; the same step failing in three or more cells a product bug.
See where agents fail on your funnel.
Run one free cell on a property you own. No sales call, no card.