Skip to main content
WCAGrules
Quick navigation

Services · By industry

A Grocery Delivery Audit, Because an Order Should Not Go Silent

For the grocery or delivery service that wants a customer who cannot see the screen to fill a cart, approve a substitution, tip the driver, and know where the order is.

What We Keep Finding

A grocery order is a long conversation with an interface, and half of it happens after checkout. Your shopper swaps an item and the app updates a banner. If nothing announces that banner, a customer using a screen reader has just approved a substitution they never heard about. The order moves from picking to out for delivery and a status bar changes color. Silence again.

Live status is the signature failure in this sector and it is also the one no scanner can settle, for a mechanical reason worth knowing. A live region sits in the page whether or not it ever speaks. Finding the attribute is trivial. Finding out whether anything was announced means provoking the update and listening, which is a person's job. Our own free scan sees one state of each page and never triggers a substitution, so this is precisely the class of failure the free tier cannot reach.

There is a smaller defect underneath the big one that explains most silent counters. A region that announces only what changed will say "3" where a customer needed "3 items in cart", and the fix is telling the region to read itself whole rather than in pieces. W3C uses a cart count as its own worked example of this. Add unlabeled quantity steppers, a tip flow whose buttons all announce as "button", and filters that only answer a mouse, and the easiest errand of the week stops being easy.

What We Check

  • Fill a cart by screen reader, so search, filters, quantities, and swaps
  • Test substitution prompts for something a customer can actually hear
  • Follow live order status by ear, from checkout to the doorstep
  • Run the tip and rating flow with every control named by what it does
  • Verify delivery windows and fees are read out before the payment step

What You Get

Every service on this site runs the same three-pass engine: an automated scan, an expert review of all 55 WCAG 2.2 A and AA rules, and a hands-on session with a professional blind screen-reader user. You get one report with every finding screenshotted, ranked by user impact, and linked to its fix. Your team fixes, we verify: the re-audit is half price within 3 months.

The format is not a mystery either. Read the sample report before you spend anything.

The Honest Limit

One honest limit. The live parts need a live order, so we place or stage one with you and test tracking and substitutions in motion rather than describing them from the markup. Whatever cannot be staged gets named in the report instead of guessed at. One boundary inside that. Where a substitution prompt opens as a dialog that takes focus, it stops being a status-message question and becomes a focus-management one. The report files it under the rule it actually breaks rather than the one that sounds closest.

What It Costs

Rapid Audit: $499, up to 10 pages you pick, report in 5 business days. Standard Audit: $1,499, up to 25 pages in 10 business days. Flat rates, no discovery calls, and a real blind screen-reader user on every engagement. Pick your pages. We bring the humans.

Worth Reading Next

Related on this site

Guides, checklists, tools, and terms that go with this service.

More in By industry

Go somewhere useful

Find tools, resources and your workspace.

29 destinations