Sample report — identifying details removed. This is a real automated snapshot we prepared for a real store; the store's name, URLs, and store-specific identifiers have been withheld.
Accessibility audit — sample report
Automated snapshot prepared by AuditorSignal. Pages checked:
Homepage and one collection page of a 7-figure fine-jewelry Shopify store (name withheld).
15
critical0
serious5
moderate8
minor28 accessibility issues were detected on the pages we scanned
(15 critical or serious). Issues like these are exactly what plaintiff firms' automated scanners
flag before sending ADA demand letters — and e-commerce is their #1 target. Below are real examples
pulled directly from the audited store.
Fix it now with AuditorSignal
$497
vs.
One ADA demand letter typically settles for
$10,000–$75,000
Acting before the lawyers do saves you up to $74,503 — before legal fees,
rushed remediation under a court deadline, and the sales lost from shoppers who couldn't check out.
The audit pays for itself the moment it prevents a single letter.
Real examples from this store
critical
aria-required-parent
10 element(s) · WCAG 2AWhat a shopper experiencesA menu/list role is used without its required parent, so screen readers announce it as broken and shoppers can't navigate it.
Found on the store · a[aria-label="FINE JEWELRY"]
<a class="Heading u-h6 main-links" style="color: #000000;" role="tab" aria-label="FINE JEWELRY" aria-expanded="false" tabindex="0"> FINE JEWELRY <span class="Header__LinkSpacer">FINE JEWELRY</span></a>How to fix: Nest the role inside its required parent element.
critical
button-name
4 element(s) · WCAG 2AWhat a shopper experiencesThis button is announced with no name — a screen-reader shopper can't tell it's “Add to cart”, so they can't buy.
Found on the store · .boost-pfs-filter-option.boost-pfs-filter-option-skeleton.boost-pfs-filter-option-collapsed:nth-child(1) > .boost-pfs-fi
<button class="boost-pfs-filter-button boost-pfs-filter-option-title-heading" tabindex="0"><span></span></button>How to fix: Add visible text or an aria-label to the button.
critical
image-alt
1 element(s) · WCAG 2AWhat a shopper experiencesA shopper using a screen reader hears nothing where the product photo is — they can't tell what the item looks like or even that it exists.
Found on the store · #desktopVideo-template--XXXXXXXXXXXXXX__hp_banner > video > img
<img src="//[store-domain]/cdn/shop/files/preview_images/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.thumbnail.0000000000_1920x.jpg?v=0000000000">How to fix: Add descriptive alt text to every product and content image.
moderate
meta-viewport
2 element(s) · WCAG 2AAWhat a shopper experiencesThe page blocks pinch-to-zoom, so shoppers who need bigger text simply can't enlarge it.
Found on the store · meta[name="viewport"]
<meta name="viewport" content="width=device-width, initial-scale=1.0, height=device-height, minimum-scale=1.0, user-scalable=0">How to fix: Remove user-scalable=no / maximum-scale from the viewport tag.
moderate
region
2 element(s)What a shopper experiencesContent sits outside landmarks, so a screen-reader shopper can't skip the menu and jump to products — every visit means wading through navigation.
Found on the store · .international-carousel > .flickity-viewport
<div class="flickity-viewport" style="height: 40px; touch-action: pan-y;">How to fix: Wrap content in <main>/<nav> landmarks.
moderate
landmark-unique
1 element(s)What a shopper experiencesRepeated unnamed landmarks confuse screen-reader navigation.
Found on the store · .reviews-carousel-section-desktop
<section class="reviews-carousel-section-desktop" aria-labelledby="reviews-carousel-heading-desktop-template--XXXXXXXXXXXXXX__reviews_carousel" aria-hidden="false">How to fix: Give each landmark a unique accessible name.
Want a report like this for your store?
This sample is a limited snapshot. The full audit ($497) covers every template — home, collection, product, cart and checkout — with a prioritized, developer-ready fix list and a free re-scan after your fixes.
Request your full audit — $497