Is the Pipeline Shopify theme accessible?
3 different failures in Pipeline's own code, including on the product page (21 occurrences across three pages), checked against WCAG 2.1 Level A and AA.
Rank 40 of 49 in our Shopify theme accessibility ranking. Pipeline is a paid theme.
On the product page: a field labelled only by placeholder text. That is the page where a shopper chooses a size and adds to cart.
Every shop that runs Pipeline without changes to its code has the same failures, so the theme is the cheapest place to fix them.
What fails in Pipeline's own code
A field labelled only by placeholder text
The grey hint text is the only visible label, and it disappears as soon as someone starts typing. People with memory or attention difficulties lose track of what the field was for. This one is on the product page, where people decide to buy.
Example from the demo store's product page:
<input class="input-group-field" type="email" placeholder="your-email@example.com" id="mail-footer-newsletter" aria-label="your-email@example.com" autocorrect=…What the check found: The only visible cue is the placeholder "your-email@example.com". There is an accessible name for screen readers, but sighted users lose the cue once they start typing.
How to fix it: Show a real label next to or above the field. The placeholder can stay as an example of the format.
A control the keyboard reaches but screen readers are told to ignore
Something inside an aria-hidden="true" area can still take keyboard focus. A keyboard user lands on it and a screen reader announces nothing at all. Off-screen carousel slides are the usual cause.
Example from the demo store's home page:
<a href="https://www.self.com/" class="logo-bar__link" target="_blank" rel="noopener" title="https://www.self.com/">What the check found: This control is focusable but sits inside aria-hidden="true" (set on an ancestor <div>).
How to fix it: Content that is hidden from screen readers must be out of reach of the keyboard too. Add the inert attribute to the hidden area (it removes it from both at once), or stop hiding content people can reach.
A form field with no label
A screen reader user reaches the field and hears only its type ("edit text", "checkbox") with no idea what to enter or choose.
Example from the demo store's collection page:
<input type="checkbox" name="filter.p.m.my_fields.simple_color" value="black" id="filter-color-1">What the check found: No label, aria-label, aria-labelledby or title.
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.
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 Pipeline. They are worth knowing because the same mistakes are easy to make when you add your own content.
- 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
- Duplicate ids (home page (5×), 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 Pipeline compares
2 other paid themes had no confirmed failure in its own code: Halftone, Prestige.
Next to it in the ranking: Mono (rank 39, 3 failures) · Monk (rank 41, 3 failures).
All 49 themes, ranked, with the method and its limits.
How we tested
We opened three pages of the official Pipeline 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:
This is the developer's own demo store; no merchant's shop was measured. If you make Pipeline and have fixed something here, write to hello@limen.ae and we will re-test it.