Every finding, anchored to evidence.Nothing sold on the back of it.

• Evidence-anchored findings, filed against criteria

  Each failure names the page, the element selector, the computed value we measured, and a screenshot of the element in place — filed under the WCAG 2.2 success criterion it fails, with its severity and instance count.

  Read more

  A finding that says "low contrast on buttons" is not actionable. A finding that says "button.btn--primary on /collections/new renders #8FA8A0 on #FFFFFF, a measured ratio of 2.54 : 1, against a 4.5 : 1 requirement for 16px text under 1.4.3" is. Every entry is the second kind, re-checkable by your developer in about thirty seconds, and grouped by root cause — "14 failures across 4 templates, 9 of them a single repeated component" is what you plan a sprint against, so the report leads with the components rather than the instance count.

• Manual keyboard review

  A human moves through your storefront using only Tab, Shift+Tab, Enter, Space, and the arrow keys, and records where that breaks down.

  Read more

  Focus order, focus visibility, keyboard traps, skip mechanisms, the cart drawer, the mobile menu, and the filter controls. This is where storefront themes usually fail, and it is not something a scanner can decide for you.

• Screen-reader review

  Key flows are walked with a screen reader so the audit reports what a customer actually hears, not what the markup implies.

  Read more

  Product page, collection page, search results, and cart. We record the announced name, role, and state of each control that matters to buying something, and note where the announced text and the visible text disagree.

• A remediation brief you can hand to anyone

  For each finding, what the correct end state looks like — written for whoever does the work, whether that is your agency, your theme vendor, or your own developer.

  Read more

  We describe the required outcome and the criterion it satisfies. We do not ship you a patch, because we do not implement, and because a fix written by the party who also grades the fix is not an independent result. The brief is deliberately vendor-neutral.

1. Snapshot — free

   Our crawler loads up to 5 public pages on your storefront, waits at least one second between requests, honors robots.txt, and never touches your checkout. You get a short document listing what an automated scan alone could see. It is free, there is no obligation, and it is not an audit — automated testing detects only a portion of accessibility barriers, and the Snapshot says so on its own first page.

   How the crawler works and how to stop it

2. Audit

   Everything listed above, run across your key templates and written up as one dated document against WCAG 2.2 Level AA. One fixed price, agreed before we start. You own the report and can hand it to anyone.

3. Re-audit

   After your team ships fixes, a verification re-audit re-tests the same scope and reports what cleared and what did not. If you want the storefront checked on a standing basis as your theme and apps change, an annual re-audit is also available.

• Snapshot

  Free

  one-off

  Automated scan of up to 5 public pages. Delivered by email. Not an audit.

• Audit

  $1,800

  one-time

  Automated coverage, manual keyboard pass, screen-reader pass, full evidence-anchored report against WCAG 2.2 Level AA.

• Verification re-audit

  $700

  typically ~6 months later

  Re-tests the same scope and reports which findings cleared.

• Annual re-audit

  $1,400

  per year

  A full re-audit once a year, for storefronts that keep changing.

Prices are in US dollars and cover a single storefront. Scope is fixed in writing before any work starts; if a storefront is materially larger than a standard Shopify apparel build, we say so and quote before beginning, never after.