Sample accessibility report

This is an example for a fictional store, example-store.com, so you can see what a report looks like. Scan your own store free.

Results for example-store.com

4 pages scanned on Nov 7, 2026 · WCAG 2.2 A and AA automated checks

Estimated risk indicator

97/ 100

High estimated risk

Based on the number and severity of automated findings, weighted toward issue types commonly cited in accessibility lawsuits. This is an estimated risk indicator, not a legal assessment.

Issues found

42

across 8 issue types

Critical
26
Serious
16
Moderate
0
Minor
0

This report is not legal advice.

Automated checks catch a portion of WCAG issues; manual review is still recommended.

Fix these first

The issues with the most weight in your estimated risk indicator.

CriticalImages21 instances on 2 pages

Images without alt text

Screen readers announce these images with no description, so blind shoppers can't tell what the product or banner shows.

How to fix it

Add an alt attribute that describes the image (for products, the product and its key detail). Use alt="" only for purely decorative images. In Shopify, set alt text in the product media editor or in the theme section settings.

Where we found it

  • Page: /products/linen-shirt

    Element: .product__media img

    <img src="//example-store.com/cdn/shop/files/linen-shirt-front.jpg" width="1200" loading="lazy">
  • Page: /collections/all

    Element: .card__media img

    <img src="//example-store.com/cdn/shop/files/linen-shirt.jpg" class="motion-reduce">

Technical reference for this rule (opens in a new tab)

SeriousColor contrast9 instances on 2 pages

Text with low color contrast

This text is hard to read for people with low vision or color blindness, and on phones in bright light.

How to fix it

Raise the contrast to at least 4.5:1 for normal text and 3:1 for large text. Usually this means a darker text color or a lighter background in the theme settings or CSS.

Where we found it

  • Page: Home page

    Element: .announcement-bar__message

    <p class="announcement-bar__message">Free shipping on orders over $75</p>
  • Page: /products/linen-shirt

    Element: .price__compare

    <s class="price__compare">$68.00</s>

Technical reference for this rule (opens in a new tab)

CriticalButtons3 instances on 1 page

Buttons without an accessible name

Screen readers announce these as just "button", so shoppers can't tell if it opens the cart, a menu or closes a popup.

How to fix it

Add visible text to the button, or an aria-label for icon-only buttons (for example aria-label="Open cart").

Where we found it

  • Page: Home page

    Element: header .cart-toggle

    <button class="cart-toggle" type="button"><svg class="icon icon-cart">…</svg></button>

Technical reference for this rule (opens in a new tab)

All issues by severity

Critical (2)

Form fields without labelsForms · 1 instance
CriticalForms1 instance on 1 page

Form fields without labels

Shoppers using a screen reader hear an unlabeled field and don't know what to type, for example in search, newsletter or checkout-related forms.

How to fix it

Connect a visible <label for="..."> to each field. If the design hides the label, use a visually hidden label or aria-label instead of placeholder text alone.

Where we found it

  • Page: Home page

    Element: #NewsletterForm-email

    <input id="NewsletterForm-email" type="email" name="contact[email]" placeholder="Email">

Technical reference for this rule (opens in a new tab)

Dropdowns without labelsForms · 1 instance
CriticalForms1 instance on 1 page

Dropdowns without labels

Variant or quantity dropdowns have no name, so shoppers using assistive technology don't know what they're choosing.

How to fix it

Add a <label> connected to the <select>, or an aria-label such as "Size".

Where we found it

  • Page: /products/linen-shirt

    Element: #Option-size

    <select id="Option-size" name="options[Size]">…</select>

Technical reference for this rule (opens in a new tab)

Serious (3)

Links without an accessible nameLinks · 4 instances
SeriousLinks4 instances on 1 page

Links without an accessible name

Screen readers can't say where these links go, which is common with icon links like social media or the logo.

How to fix it

Add link text, or an aria-label on icon-only links. If the link wraps an image, give the image alt text that names the destination.

Where we found it

  • Page: Home page

    Element: footer .social-links a

    <a href="https://instagram.com/examplestore" class="social-link"><svg>…</svg></a>

Technical reference for this rule (opens in a new tab)

ARIA hidden element must not be focusable or contain focusable elementsARIA · 2 instances
SeriousARIA2 instances on 1 page

ARIA hidden element must not be focusable or contain focusable elements

ARIA attributes here are missing or used incorrectly, so assistive technology may announce the element wrongly or not at all.

How to fix it

Use native HTML elements where possible, and make sure ARIA roles, states and references are valid. Remove ARIA you don't need.

Where we found it

  • Page: /cart

    Element: .drawer[aria-hidden=true] a

    <a href="/checkout" class="drawer__checkout">Check out</a>

Technical reference for this rule (opens in a new tab)

Lists with the wrong structurePage structure · 1 instance
SeriousPage structure1 instance on 1 page

Lists with the wrong structure

A list contains elements that aren't list items, so screen readers announce the wrong number of items.

How to fix it

Make sure <ul> and <ol> only contain <li> elements (or script/template).

Where we found it

  • Page: /collections/all

    Element: .facets__list

    <ul class="facets__list"><div class="facet">…</div></ul>

Technical reference for this rule (opens in a new tab)

Get these fixed automatically: reserve your Founding plan

Our Shopify app will apply real code fixes to your theme, no overlay widget. Reserve today for $49, credited toward your first months of the $79/month plan. Full refund if automatic fixes don't launch within 60 days.