Is the Mono Shopify theme accessible?

Updated 10 October 2026 · Tested on the theme's official demo store

What fails in Mono's own code

A form field with no label

WCAG 1.3.1, 4.1.2, Level A · Found on the home page (2×), collection page (3×), product page (1×)

A screen reader user reaches the field and hears only its type ("edit text", "checkbox") with no idea what to enter or choose. This one is on the product page, where people decide to buy.

Example from the demo store's product page:

<input id="NewsletterForm--sections--20332339429620__footer" type="email" name="contact[email]" class="field__input" value="" aria-required="true" autocorrect=…

What the check found: No label, aria-label, aria-labelledby or title. It has a placeholder ("Email") but a placeholder is not a label — it disappears the moment the user types.

How to fix it: Give every field a label element tied to it with for and id. It can be visually hidden if the design has no room for it, but it has to be there.

A link with no name

WCAG 2.4.4, 4.1.2, Level A · Found on the home page (4×), collection page (2×)

A screen reader announces "link" and nothing else, or reads out the web address, so a blind shopper cannot tell where it goes. It is usually an icon link or a logo image with an empty description.

Example from the demo store's collection page:

<a href="/products/mustard-yellow-cape?variant=43324828352756" class="color-swatch color-swatch--small color-swatch--yellow full-unstyled-link active" data-var…

What the check found: Link contains no text, no aria-label, and no image with alt text. It appears to be an icon-only link. A screen reader will announce the destination URL instead.

How to fix it: Give the link text a screen reader can read: visible text, a description (alt text) on the image inside it, or an aria-label on the link. For a logo, your shop's name is the right text.

A label pointing at a field that is not there

WCAG 1.3.1, Level A · Found on the collection page (2×)

The label's for attribute names an id that no field has, so the field it was meant for ends up with no name.

Example from the demo store's collection page:

<label class="field__label hidden" for="Filter-Price-LTE">

What the check found: Label references id "Filter-Price-LTE", but no element on the page has that id.

How to fix it: Make the label's for value match the field's id exactly. It usually breaks when a section is duplicated and the ids are made unique but the labels are not.

Found in the demo's content, which yours replaces

These come from the images and words the theme's developer put in the demo store, not from the theme's code, so they do not count against Mono. They are worth knowing because the same mistakes are easy to make when you add your own content.

• Video or slides that play by themselves (home page (4×)). Moving content that starts on its own and cannot be paused distracts people with attention difficulties. Turn autoplay off in the section settings, or make sure a pause control shows.
• An embedded frame with no title (home page (1×)). A video or map embed with no title is announced as "frame". Give the embed a title that says what it is.
• Images with no description (home page (8×), product page (1×)). When you add your own images, write a short description for each one in the Shopify admin (open the image, then "Add alt text"). Decorative images can stay empty.
• Image descriptions that are file names (home page (4×), collection page (1×), product page (1×)). Descriptions like "IMG_2041.jpg" or "banner-final" tell a screen reader user nothing. Replace them with a few words about what the image shows.
• Links that do not say where they go (home page (1×)). "Shop now" and "Read more" mean nothing when a screen reader lists the links on a page. In the section settings, write link text that names the destination ("Shop the linen range").

Checked, not counted

• Text contrast (home page (1×), product page (4×)). Some text measured below the 4.5:1 contrast WCAG asks for. Contrast over photos and gradients needs the actual pixels, which a markup check cannot see, so it is not counted. Check your own colour settings, which replace the demo's.
• Duplicate ids (home page (6×), collection page (2×), product page (2×)). Two elements share an id. WCAG 2.2 removed this criterion, and it only harms when a label or an ARIA reference points at the duplicated id, so it is not counted. Most come from hidden copies of menus and drawers.

What this does not tell you

• Automated checks find roughly a third of accessibility barriers. A clean result here still needs a keyboard and screen-reader test of your checkout. A failure here is certain.
• We tested what loads first. Menus, the cart drawer and pop-ups that open on a click were not opened, so the real totals can only be higher.
• Your shop is not the demo. Apps, sections, settings and your own content change the result, in both directions.
• Themes get updated. These results are for the version the demo store ran on 10 October 2026.

Check your own shop

Run the free check on your shop's pages. It needs no account and lists every confirmed failure with its WCAG criterion, including the ones your apps and content add. If you want every occurrence with the exact Shopify code to fix it, that is what the Fix Pack is for: $99, once.

How Mono compares

2 other paid themes had no confirmed failure in its own code: Halftone, Prestige.

Next to it in the ranking: Wonder (rank 38, 3 failures) · Pipeline (rank 40, 3 failures).

All 49 themes, ranked, with the method and its limits.

How we tested

We opened three pages of the official Mono demo store in Chromium and let its scripts run. Anything the browser did not show was removed, so the theme is never marked down for something no visitor meets. Then each page went through the same engine as our free check. The pages tested:

• Home page
• Collection page
• Product page

This is the developer's own demo store; no merchant's shop was measured. If you make Mono and have fixed something here, write to hello@limen.ae and we will re-test it.