Limen
Back to Limen

Is the Palo Alto Shopify theme accessible?

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

2 different failures in Palo Alto's own code, including on the product page (6 occurrences across three pages), checked against WCAG 2.1 Level A and AA.

Rank 26 of 49 in our Shopify theme accessibility ranking. Palo Alto is a paid theme.

On the product page: a control the keyboard reaches but screen readers are told to ignore. That is the page where a shopper chooses a size and adds to cart.

Every shop that runs Palo Alto without changes to its code has the same failures, so the theme is the cheapest place to fix them.

What fails in Palo Alto's own code

A control the keyboard reaches but screen readers are told to ignore

WCAG 4.1.2, Level A · Found on the product page (1×)

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. This one is on the product page, where people decide to buy.

Example from the demo store's product page:

<div class="tabs__contents" data-tabs-contents="" tabindex="0">

What the check found: This control is focusable but sits inside aria-hidden="true" (set on an ancestor <drawer-element>).

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.

Headings that skip a level

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

Screen reader users move around a page by its headings. A jump from a level-2 heading to a level-4 one suggests a missing section and makes the page harder to scan.

Example from the demo store's product page:

<h3 class="countdown-timer__title font-heading">

What the check found: Jumps from <h1> to <h3>, skipping 1 level(s).

How to fix it: Change the heading tags so levels go down one step at a time, and keep the look with CSS. Pick heading levels for the page's structure, not for their size.

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 Palo Alto. They are worth knowing because the same mistakes are easy to make when you add your own content.

What this does not tell you

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 Palo Alto compares

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

Next to it in the ranking: Sleek (rank 25, 2 failures) · Broadcast (rank 27, 2 failures).

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

How we tested

We opened three pages of the official Palo Alto 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 Palo Alto and have fixed something here, write to hello@limen.ae and we will re-test it.