An outside check of the pages shoppers use most, for barriers that stop disabled people from buying and for security gaps an attacker could use.
Prepared for
Sample: W3C’s demo site
Prepared by
AccessFix
Date
26 October 2026
Pages checked
4
Standard
WCAG 2.2 A and AA
01
At a glance
We found 21 problems that can stop shoppers from finishing a purchase, and 83 more that make the store confusing or hard to use. The security check found no high- or medium-risk issues.
Please read: automated checks catch only part of accessibility problems. Things like keyboard use, screen-reader flow and how pop-ups behave need a person to test. This report is not a legal assessment and does not certify compliance with any law or standard. 4 further checks could not be decided automatically and need a human review.
02
Accessibility: fix these first
The problems that affect shoppers most, across every page we checked.
1
Blocks shoppers
Form fields have no label
11 elements · Survey · WCAG 4.1.2
What it means for shoppers
Screen-reader users do not know what to type into a field (email, search, quantity, address), so they cannot complete it.
How to fix
Connect a visible <label> to each field, or add aria-label when a visible label is not possible.
An outside look at the gaps an attacker could use, ranked by risk.
How this was checked: we only looked at what any visitor’s browser receives: response headers, page code, the site’s own scripts and the libraries they load. We did not try to break in, guess passwords or open hidden pages. A clean result does not mean a site cannot be hacked. Deeper testing needs the owner’s written permission.
No security problems were found by these outside checks.
Checks with no problems found
Plain http:// visits are redirected to https://.
Pages are served over HTTPS.
Browsers are told to always use a secure connection (HSTS).
The store cannot be framed inside another site (clickjacking protection).
Browsers will not guess file types (X-Content-Type-Options).
A Content Security Policy is set.
No known-vulnerable versions of common libraries were detected.
No secret keys were found in page code or the store’s own scripts.
Every file on the scanned pages loads over HTTPS.
Forms send their data over HTTPS.
04
Accessibility, page by page
Every problem on every page, for whoever makes the fixes.
Home
https://www.w3.org/WAI/demos/bad/before/home.html
Problems on the Home page
Problem
Priority
Elements
Links have no nameShow 7 affected elements for “Links have no name”