AUTOMATED FINDINGS FOR SHOPIFY STOREFRONTS

Know what your accessibility scan found—and where to start.

A focused report of automated findings on agreed public Shopify pages, with documented locations and next checks for your developer to consider.

Automated checking and reporting. Fixes and comprehensive manual testing are outside this offer.

CONTROLLED DEMONSTRATION

Product card · initial loaded state

A button without an accessible name.

Observed element

#item-information

Tool observation: axe-core returned button-name for one button without discernible text or a label.

Why investigate: some assistive-technology users may not be able to identify its purpose. No user or screen-reader test was performed.

READ THE EVIDENCE

A finding needs more than a number.

The sample traces one detected rule from the page state to the element and a suggested investigation. Its HTML and PDF versions describe the same controlled run.

A short demonstration of report structure. The paid engagement covers the URLs and deliverables agreed in writing.

  1. See what was examined.

    One original product card, in its loaded state. No menus, cart drawers or checkout interactions were tested.

  2. Locate what the tool found.

    Read the rule, affected element, example markup and tool explanation. Counts describe returned instances, not unique store problems.

  3. Know what still needs checking.

    Confirm the button’s purpose and inspect its accessible name. A suggested investigation is not a verified fix.

IS THIS THE RIGHT NEXT STEP?

A bounded starting point.

For a defined set of public pages

A scoped report gives you a record of what automation found and where to investigate. It can support a conversation with the developer responsible for your store.

When you need deeper evaluation

Questions about keyboard use, screen-reader journeys, content meaning or completing a purchase need qualified manual evaluation. This report does not answer those questions or establish compliance.

SCOPE & PRICE

Agree the pages.
Define the work.

Page coverage and deliverables shape the written scope. Agree the final price and timing before work begins.

Public URLs, named in advance
For example: home, collection, product or cart pages. A URL does not include every interactive state.
Failures remain visible
Blocked pages and incomplete checks are recorded. An unchecked page is not a clean result.
Your developer handles changes
Code fixes, manual testing, rechecks and ongoing monitoring are outside the current offer.

Read the methods and responsibilities

SCOPED AUTOMATED REPORT

$499–$999

One-time · USD · final scope agreed in writing

The reporting includes

  • Automated checking of agreed public URLs in their loaded state
  • Documented rules, tool impact labels and example element locations
  • A coverage and findings record, with report formats agreed before work

The sample demonstrates HTML and PDF reporting. Neither format makes this a comprehensive audit or a verified remediation plan.

Request a written scope

Timing and any clarification arrangements are part of that agreement. No fixed page allowance or guaranteed turnaround.

HOW THE WORK IS DEFINED

From scope to documented findings.

Agree the scope

Identify public URLs, page types, deliverables, price and timing. Record the boundaries in writing.

Examine agreed pages

Run automated checks in the recorded browser state. Keep tool findings, incomplete checks and page failures distinct.

Deliver the record

Provide the agreed report and coverage record. Your developer investigates the findings and decides on changes.

YOUR CONTACT

I’m Ari.

Founder and operator, Access Risk Report

I founded Access Risk Report and I’m the contact for agreeing the scope of your report. It is a founder-led service that uses browser automation and axe-core to document findings on public storefront pages.

It is a scoped reporting service. Expert manual testing, accessibility certification and implementation are not included.

Contact me about your store

PRACTICAL QUESTIONS

Before you enquire.

Do you need access to my Shopify admin?

No admin credentials are needed for the current offer. Checking is limited to agreed public pages. Password-protected stores, account areas and authenticated checkout are outside the current method.

Does a page check include its cart drawer or menus?

No. The current checks examine the loaded page without opening drawers, choosing variants or completing a purchase. A page URL and an interaction state are different parts of coverage.

What do the impact labels and counts mean?

Impact labels come from axe-core. Counts are returned finding instances across checked pages, including repeated components. They are not legal-risk scores, business priorities or a complete count of accessibility barriers.

When will I receive the report?

Timing is agreed in writing after the page coverage and deliverables are defined. There is no published turnaround guarantee.

Who fixes the findings, and what happens afterward?

Your developer or another provider investigates and implements changes. Agree clarification arrangements before work starts. Additional checks, fixes and ongoing support are not included by default.

Can this confirm that my store is compliant?

No. Automated checks detect only some accessibility issues and do not replace comprehensive manual testing. The report provides technical observations, not legal advice, ADA compliance determinations, WCAG certification or lawsuit protection.

START WITH YOUR STORE URL

Let’s define the scope.

Email your store URL and, if you like, the concern that brought you here. Page coverage, deliverables, timing and price are agreed before work.

[email protected]

Opens your email app. Using webmail? Select and copy the address above into a new message.