← Use cases

Accessibility for retail

Retail is the most-sued sector for web accessibility, and the barriers that matter sit on the four pages between a customer and a completed order.

Purchase journey5 steps · 12,400 pages
Checkout blocked
8,940
open findings
mostly product pages
11
on the order path
where it counts
$412k
revenue at risk
from 4 barriers
3
fixes clear 96%
shared components

Barriers by journey step

  • 340
    Homeattention
  • 2,100
    Categoryattention
  • 6,489
    Productattention
  • 8
    Cartblocking
  • 3
    Checkoutblocking

In retail, a barrier is a lost order.

Every other sector argues about the cost of accessibility. Retail can measure it, which cuts both ways.

The most-sued sector

Retail draws more web accessibility claims than any other industry. Demand letters cite the cart and checkout, because that is where exclusion is easiest to prove.

Scale hides the signal

Twelve thousand product pages generate thousands of low-consequence findings that bury the eleven on the order path. Counts point you at the wrong work.

Weekly campaign churn

Promo templates and seasonal pages ship constantly and are gone in weeks. Nothing gets a proper review, and each one can break the funnel.

01 · Priced, not counted

The barrier on checkout outranks 8,000 on product pages.

A missing alt attribute on a lifestyle image is not the same problem as an unlabelled card field, even though a scanner counts them the same way.

limena ranks by the traffic on the page and whether an alternative route exists. On checkout, there is none.

Fix these first8,940 open · ranked
01Card fields have no labels$310k
3 fields

Payment step of every order. No alternative route to pay.

02Cart quantity control unreachable$78k
8 instances

Keyboard users cannot change quantity or remove an item.

03Product images missing alt text$24k
6,489 images

High volume, but the product name sits in text alongside.

02 · A number, not a severity

Something a merchandising lead can act on.

"WCAG 3.3.2, serious" does not compete for sprint capacity. "$310k a year on the payment step" does.

limena turns each barrier into reach and revenue using your own session and order figures, then routes it to the squad that owns the component.

Fail

Card fields have no labels

Error

The payment fields use placeholder text instead of labels. A screen reader announces three unnamed inputs, and the placeholder disappears as soon as the customer starts typing.

How to fix

<label for="cc-num">Card number</label>

Business impact

On the payment step of every order. 1.4M sessions a year reach this page, and there is no alternative way to pay. Estimated revenue at risk: $310k a year.

JTJordan Tran, checkout squadOne component · clears 3 fields on every orderPR #412

03 · Through peak

Campaign pages ship faster than anyone can test them.

Seasonal templates, promo banners, and countdown timers go live weekly through Q4 and get retired in January. limena tests each release, so a campaign template does not quietly break the cart during your highest-traffic month.

Release check · holiday campaign

  • Contrast on add-to-cartVerified
  • Card field labelsVerified
  • Cart keyboard operationVerified
  • New: countdown timer traps focusBlocked

The countdown timer traps focus before the cart button. Caught in CI, two days before Black Friday traffic.

Accessibility that competes for sprint capacity.

  • Barriers priced in revenue, so accessibility competes for sprint capacity on the same terms as everything else.
  • The eleven findings on the order path separated from the eight thousand that can wait.
  • Component-level fixes, so one change clears thousands of instances across the catalogue.
  • Campaign templates verified before they ship, through the quarter when traffic is highest.

Start with your checkout.

Four pages, the ones every order passes through. We will tell you what is blocking them and what it is worth.