Illustrative client report · 17 October 2026

Small storefront: accessibility review

Field & Form · fieldandform.example

Fictional demonstration. All clients, domains, findings, and evidence are illustrative. These reports show the deliverable structure; they are not scans of real sites or proof of product results.

Choose plan

Executive summary

Clarify product imagery and quantity controls before handing this report to the shop team. Both affect the product-to-cart journey. Then correct the skipped heading level to make the catalog easier to navigate.

Pages reviewed: 3
Finding types: 3
Critical: 2
Moderate: 1

Counts represent distinct finding types in this fictional example, not the number of affected elements. Severity indicates review priority, not a compliance verdict.

Scope and method

Client journey: Browse products → choose quantity → review the cart.

Example pages: //products/stoneware-mug/cart

Method represented: automated axe checks of each loaded public page. This sample does not cover signed-in areas, every interaction state, keyboard use, screen reader behavior, or a full WCAG evaluation. Findings require human confirmation.

This report identifies automated accessibility findings. It does not establish legal compliance; manual evaluation is still needed.

Accessibility rules & eligibility

Prioritized findings

Priority	Finding	Page / rule	Next step
Critical	Product image is missing an alternative	`/products/stoneware-mug` `image-alt`	Describe the product information shown in the image.
Critical	Quantity buttons have no accessible names	`/cart` `button-name`	Name each quantity action and identify its product.
Moderate	Catalog heading skips a level	`/` `heading-order`	Use a consistent heading hierarchy for catalog sections.

Evidence and remediation

Two findings are expanded below to show how a report supports an implementation handoff.

Finding 1 · Critical

Product image is missing an alternative

Affected element: .product-gallery img:first-child on /products/stoneware-mug

Why it matters: Customers who cannot see the photograph still need the product details it communicates. Alternative text should describe useful visual information without repeating every nearby word.

1 · Illustrative evidence schematic. Recreated interface fragment, not a screenshot or a live scan. Illustrative product markup has no alt attribute. The photograph is the only place where the mug’s glaze and handle shape are described.

Suggested fix

Add concise alternative text that conveys the meaningful product details. Review each gallery image individually; avoid repeating the same description for every view.

Before · illustrative HTML

<img src="/mug.jpg" width="480" height="480">

After · suggested HTML

<img src="/mug.jpg" width="480" height="480"
  alt="Speckled cream stoneware mug with a wide loop handle">

Verify the fix: Re-run the image-alt rule. Read the product page with a screen reader and confirm the description is useful alongside the product name, price, and any additional gallery views.

Finding 2 · Critical

Quantity buttons have no accessible names

Affected element: .cart-item .quantity button on /cart

Why it matters: Customers need to distinguish increase from decrease, especially when more than one product is in the cart. The visible icon may not supply a meaningful control name.

1 · Illustrative evidence schematic. Recreated interface fragment, not a screenshot or a live scan. Illustrative quantity buttons contain decorative minus and plus SVGs without accessible names. This finding groups two affected buttons under one rule.

Suggested fix

Give each button an action and product name. Announce quantity changes without moving focus, and communicate the minimum quantity through the control state.

Before · illustrative HTML

<button><svg aria-hidden="true">…</svg></button>
<span>1</span>
<button><svg aria-hidden="true">…</svg></button>

After · suggested HTML

<button aria-label="Decrease Stoneware mug quantity">−</button>
<output aria-live="polite">1</output>
<button aria-label="Increase Stoneware mug quantity">+</button>

Verify the fix: Re-run the button-name rule. Adjust quantity with the keyboard and screen reader; confirm the action names, announced value, cart total update, and behavior at the minimum quantity.

Recommended handoff

Confirm findings in the live interface and agree on owners and scope.
Resolve the critical findings first; review each suggested change in context.
Test the client journey with a keyboard and assistive technology.
Re-scan the same pages, record remaining manual review work, and share the changes with the client.