Configured axe rule · link-name
Baseline count: 1 serious violation
The controlled baseline fixture contains the intentionally introduced accessible-name failure.
Controlled proof · product-card link name
One fixture. One narrow claim.
This case study records a controlled Dawn-style fixture with an intentionally introduced product-card link-name issue, a minimal diff and the retained configured checks.
Retained observations
Baseline, patch and browser checks.
Configured axe rule · link-name
Patched count: 0 violations
The same configured axe check reports zero violations after the minimal fixture patch.
Browser observations
Name and focus
The patched fixture exposes one named image link and shows real first-Tab focus.
Minimal diff
What changed in the fixture.
The patch gives the product-card image link an accessible name while leaving the controlled scenario otherwise unchanged. The retained result is limited to the configured link-name check and the two browser observations above.
Reproduce locally
Download the bounded proof.
The archive contains the lockfile, test, controlled before/after snippets, minimal patch, raw evidence, focus screenshot and honest scope documentation. It excludes node_modules, browser binaries and merchant code.
After extracting the archive, enter its directory and run:
npm ci --ignore-scripts
npm test
Requires Node.js 20+, npm and Google Chrome at /usr/bin/google-chrome. Installation uses the pinned lockfile and requires npm registry access; the test itself runs against the local controlled fixture.
This is not evidence of a Dawn defect, not a merchant deployment and not proof of full accessibility. It records only the controlled fixture and retained checks described on this page.