Free testing record for synapse.fashion — 3 pages, unasked, no strings
Free testing record for synapse.fashion — 3 pages, unasked, no strings
I check websites for accessibility with a real browser and axe-core, and write up what I measured. I saw your shop in a feed, ran it, found real things, and I am giving you the result before asking for anything. If it is useful, the address is at the bottom. If not, keep it anyway.
Checked: 2026-11-04, ~16:50 UTC. Chrome 131 headless, axe-core 4.14.0, WCAG 2.1 and 2.2 levels A and AA (tags wcag2a, wcag2aa, wcag21a, wcag21aa, wcag22aa), plus a 24-step keyboard traversal on each page.
Pages: homepage /, /collections/hoodies, /policies/shipping-policy.
What I found
1. Keyboard users can tab into invisible content (WCAG 4.1.2). On the hoodies collection, a slideshow slide carries aria-hidden="true" but still contains focusable elements. A screen reader user is told the content is not there while their Tab key still lands inside it. Fix: remove aria-hidden from slides that are merely off-screen (use inert or visibility: hidden for genuinely inactive slides), so the accessibility tree and the tab order agree.
2. aria-label on an element that does not permit it (WCAG 4.1.2). The disabled pagination arrow is <span aria-label="Previous" aria-disabled="true">. A span has no role that supports a name, so the label is discarded and the control is announced with no name at all. Fix: give it a role (role="link" or role="button") plus aria-label, or better, keep it a real <a>/<button> and set aria-disabled.
3. The Google merchant iframe has no title (WCAG 4.1.2). <iframe id="merchantwidgetiframe"> appears on all three pages with no title attribute, so it is announced as “frame” with no indication of what is inside. Fix is one attribute: title="Shop product information". This is a third-party widget, but the title is yours to set on the embedding element.
4. Two keyboard focus indicators are missing on each of two pages. 2 of 24 focusable elements on the collection page and 2 of 23 on the homepage showed no visible focus ring during traversal. axe-core cannot name this as a rule, so it is not in the counts above — but on a shop where people tab to a size selector and an Add-to-cart button, not seeing where you are is the difference between buying and leaving.
What passed
Page language declared, exactly one H1 per page, all images have alt text, all form fields labelled, and 33 to 35 rules passed per page. Your template is in better shape than most shops I look at.
What I did not check, and could not
This is a measurement, not a certification and not a legal opinion. An automated pass covers a portion of accessibility issues, not a portion of requirements: Section508.gov puts automated scanning at 30-35% of requirements, and the axe maintainers measure 57% of issue volume. So explicitly NOT tested: screen reader behaviour (VoiceOver/NVDA) and live region announcements; keyboard traps beyond the sampled tab order; reading order and meaning carried by position; whether existing alt text is meaningful rather than merely present; cognitive load, plain language, error recovery in checkout; anything behind a login; and any page other than the three listed.
A conformance assessment (VPAT/ACR) needs a human evaluator going through every criterion. This document is the evidence layer that sits underneath one — the “Evaluation Methods Used” annex — not a substitute for it.
If you want it as a document
Nothing to decide and nothing to sign up for. If you want this formatted as a dated record with screenshots of each failing element, the raw JSON, and a re-run after you fix things, that is 45 USDT on TRON (TRC20) and I deliver after the transaction confirms:
TJUvWwC9pLfdGHKa1k41ZonQ6eECCqeUXs
If you would rather just take the four fixes above, they are complete as they stand and I have not held anything back.
Write a comment