You don’t need to know anything about WCAG success criteria to find out whether your store has an obvious accessibility problem. You need about five minutes, your own keyboard, and a browser you already have open.
Quick answer: Run four quick checks on a product page and your checkout. Unplug your mouse and try to buy something using only Tab, Shift+Tab, and Enter. Zoom your browser to 200% and see if anything gets cut off. Check whether sale badges and buttons still make sense in plain black-and-white. And spend sixty seconds with your operating system’s built-in screen reader turned on. None of this replaces a real audit, but each check maps to a real WCAG 2.1 success criterion and catches problems that are genuinely common on e-commerce sites — and genuinely block real customers.
This is educational content about technical accessibility testing practice, not legal advice. Meeting WCAG 2.1 AA does not guarantee legal compliance with the ADA or any other law. Consult qualified counsel for legal risk questions specific to your business.
Why run this before hiring anyone
If you’re a store owner, not a developer, “accessibility” can feel like a black box — something you either pay someone to fix or hope you don’t get a demand letter about. You don’t have to take it on faith. A handful of checks, run yourself in under five minutes, tells you whether your site has the kind of obvious, common problems that show up on most sites that haven’t been reviewed — and gives you a concrete starting point before you talk to anyone about fixing it.
This isn’t a replacement for a full audit, which combines automated scanning with a systematic manual review against every applicable WCAG 2.1 AA success criterion. It’s a fast way to get oriented first.
Check 1: Unplug your mouse (keyboard navigation)
What to do: Put your mouse or trackpad aside. On your product page, press Tab repeatedly to move through every link, button, and form field (Shift+Tab moves backward, Enter/Space activates whatever’s focused). Try to actually complete a purchase this way, from product page through checkout.
What you’re checking for:
- Can you tell where you are? Every time you tab to something, there should be a visible outline or highlight showing what’s focused. If focus becomes invisible at any point, you’ve lost your place — and so has a real keyboard user.
- Does Tab ever get stuck — cycling inside a menu, a cart drawer, or a popup with no way out?
- Can you reach and activate “Add to Cart” and every checkout field without ever touching a mouse?
Why it matters: This maps directly to WCAG Success Criterion 2.1.1 (Keyboard), a Level A requirement — the baseline tier of WCAG conformance — that all functionality be operable through a keyboard. It’s not a niche edge case: people with motor disabilities who can’t use a mouse rely on a keyboard or a keyboard-emulating device for everything, and getting stuck partway through checkout means a lost sale, not just a compliance gap. Fixing a keyboard trap is usually a matter of correcting how one modal or menu manages focus — a developer fix, not a redesign.
Check 2: Zoom to 200%
What to do: In your browser, zoom to 200% (Ctrl/Cmd and +, or your browser’s zoom menu). Look at your product page and checkout again.
What you’re checking for:
- Does any text get cut off, overlap other text, or disappear behind another element?
- Do buttons and form fields stay usable, or do they overflow their containers?
- Can you still read prices, product names, and error messages without horizontal scrolling getting in the way?
Why it matters: WCAG Success Criterion 1.4.4 (Resize Text), Level AA — the tier most demand letters and the DOJ’s own guidance point to as the accepted benchmark — requires that text can be resized up to 200% without losing content or functionality. The W3C’s own reasoning for picking 200% specifically: it’s “a reasonable accommodation that can support a wide range of designs and layouts” and matches the minimum magnification level of older screen magnifiers. This check catches a real population of customers directly — anyone with low vision who increases browser zoom instead of using dedicated magnification software.
Check 3: Look at it in black and white
What to do: You don’t need a special tool for a rough version of this check — take a screenshot of your product page and desaturate it (most phones and image editors have a one-tap “black and white” or grayscale filter), or use your browser’s built-in color-vision simulation if it has one.
What you’re checking for:
- Is your “Sale” or “20% off” badge still noticeable, or does it disappear into the background without its color?
- Can you tell your primary “Add to Cart” button apart from a plain, disabled, or secondary button once color is removed?
- Is any information — an in-stock indicator, a size availability grid — communicated by color alone, with no text, icon, or pattern backing it up?
For a precise check, use the free WebAIM Contrast Checker — paste in your text and background colors (hex codes, pulled from your browser’s DevTools) and it returns the exact contrast ratio and pass/fail. WCAG 2.1 AA requires a ratio of at least 4.5:1 for normal text and 3:1 for large text and UI components.
Why it matters: Color-only signaling and low contrast are two of the most common, easily-spotted issues on real e-commerce sites, and both affect a wide range of visitors — not just people who are colorblind, but anyone viewing a screen in bright sunlight or with any degree of low vision. For the deeper version, including failure modes generic contrast advice misses (text over hero images, disabled-vs-muted buttons), see our full contrast guide.
Check 4: A sixty-second screen reader spot-check
What to do: Turn on the screen reader that’s already built into your computer — VoiceOver on Mac (Command+F5), or NVDA on Windows (free download, since Windows doesn’t ship a full-featured one by default). Close your eyes, or turn off your monitor, and try to identify one product on your page and tell what its price is, purely by listening.
What you’re checking for:
- Does the product name and price get read out in a way that makes sense, or as a jumble of unlabeled numbers?
- When you tab to “Add to Cart,” does it announce as “Add to Cart, button” — or just “button,” with no name?
Why it matters: A real screen-reader pass is worth doing properly, not just in one minute. But if this quick spot-check turns up an unlabeled button or a price read as noise, that’s a strong signal there’s more to find. We’ve written a dedicated, non-expert guide to running a real fifteen-to-twenty-minute pass, with the commands you need and what to check on a full checkout flow.
What a failed check actually means
Finding a problem doesn’t mean your site is broken or you’re facing imminent legal risk — plenty of reasonably well-built sites have one or two of these issues, often traced to a single component (a promo modal, a custom dropdown) rather than the whole site. What it does mean is you now have something concrete: not “is my site accessible,” which is hard to answer yourself, but “my Add to Cart button loses its outline when I tab to it” — specific and fixable, something you can hand to a developer or ask an auditor to confirm and prioritize.
What this self-check won’t catch
Five minutes surfaces some of the most common, visible problems — it doesn’t systematically check anything. It won’t catch subtler screen-reader issues (reading order that’s technically valid but confusing), it won’t check every page, and it can miss things a non-expert doesn’t know to listen or look for. Treat a clean result as “no obvious problems found in five minutes,” not a clean bill of health.
FAQ
Do I need any special software to run this check? No. Every check uses something already on your computer — your browser’s zoom, a screenshot tool, and your operating system’s built-in or free screen reader (VoiceOver on Mac, NVDA on Windows).
I found a problem — what now? If it’s isolated to one component, you can often describe it precisely enough for a developer to fix directly, referencing the WCAG success criterion above. If you found more than one, that’s what a full audit is for.
Is passing all four checks the same as being WCAG 2.1 AA compliant? No. WCAG 2.1 AA has dozens of success criteria; this samples four common failure points, not the full standard — a fast first look, not a conformance assessment.
Get a full review, not just a five-minute look
This checklist is deliberately narrow — a fast way to decide whether accessibility is worth prioritizing right now, not a substitute for a real review. A Quietramp audit pairs automated scanning with a full human-verified manual review against WCAG 2.1 AA, delivered as a prioritized, developer-actionable PDF report within 48 hours. See a real sample report or check pricing — $890 one-time, $99/month if you want ongoing rescans after fixes ship.
This is educational content about technical accessibility testing practice, not legal advice. Meeting WCAG 2.1 AA does not guarantee legal compliance with the ADA or any other law, and nothing here should be read as a compliance guarantee. Consult qualified counsel for legal risk questions.
This article was drafted by an AI content system as part of Quietramp’s AI-operated, human-reviewed content process, and is reviewed for accuracy before publication — the same disclosure we make about how our audits are produced.