Remediation Sprint
Track every fix from audit finding to verified
We remediate audit findings in your theme with documented changes, a tracker your team can watch, and rescans that prove the violation count actually dropped.
$8,000 to $20,000
Scope-dependent. You get a fixed-price quote from the audit findings, so the number is approved before any work starts.
Timeline: 1 to 8 weeks (depending on severity)
No black-box agency work
This is the live tracker from the client dashboard, loaded with the remediation plan for Tosche Station Outfitters. Filter it, expand an item, read the fix. Nothing here is a screenshot.
Every finding becomes a tracked item
Each audit finding turns into an item with a severity, a WCAG criterion, a scope (site-wide, template, or one page), and subtasks per URL. Items carry the fix write-up your developer actually needs, plus who made the change and who verified it. When a fix ships, we rescan the affected URLs and record the count before and after.
Try this
- Download the sample audit package. It is the same Excel workbook clients get.
- Click a status card to filter the list, then click it again to clear it.
- Filter by severity, scope, source, or WCAG criterion to narrow the list.
- Expand the alt text item to see a retest that went from 2 violations to 0.
- Expand the cart drawer item: manual testing found it, no scanner would.
- Expand the review widget item to see how a vendor-owned fix is handled.
- Scroll to the progress log at the bottom for the timestamped history.
Remediation plan
https://toschestation.example
In progress · 1 of 6 items verified · 1 fixed awaiting verify · 1 won't fix
Click a status to filter the task list. Click again to clear. Hover a card to read what the status means.
6
1
2
2
1
How remediation works
- Each audit finding becomes a tracked item with severity, WCAG criterion, scope, and fix guidance your developer can ship.
- Cascadia Marquee updates status as work progresses. Verified means an auditor confirmed the fix on a retest.
- Expand a task below for fix guidance, per-page checklist progress, retest counts, and who reported or verified the work.
- Add alt text to hero and product card images
Critical · Template · Automated · WCAG 1.1.1 · 8 occurrences · 2/2 pages
VerifiedMTFixed by Marcus T.DRVerified by Dana R.Eight images render with missing or empty alt across the homepage hero, featured collection, collection grid, and product gallery. The report points to Featured collection and Product information in Customize, plus Products admin media alt fields.Fix guidance
In Customize, open Image banner and Featured collection > product card image blocks and set Alt text. On the product template, set alt on Product information media. Backfill the same copy under Products admin > Media so merchandisers own it going forward.Pages
- Open page (Example URL, does not go anywhere)MTFixed by Marcus T.· Sep 30, 2026
- Open page (Example URL, does not go anywhere)MTFixed by Marcus T.· Oct 1, 2026
Retest improvement
https://toschestation.example/ (Example URL, does not go anywhere): 2 → 0 · improved
https://toschestation.example/ (Example URL, does not go anywhere)
- Label cart, search, and contact form fields
Critical · Template · Automated · WCAG 1.3.1 · 6 occurrences · 2/3 pages
FixedMTFixed by Marcus T.Six form controls across the cart, search, and contact templates rely on placeholder text instead of a real label. Assistive technology announces them as unlabeled, and the placeholder disappears once the customer starts typing.Fix guidance
Wire each input to a `<label for>` pair. Where the design has no room for a visible label, use a visually hidden label rather than `aria-label` so the text stays translatable. Give the cart quantity stepper a name that includes the product title.Pages
- Open page (Example URL, does not go anywhere)MTFixed by Marcus T.· Oct 4, 2026
- Open page (Example URL, does not go anywhere)MTFixed by Marcus T.· Oct 4, 2026
Retest improvement
https://toschestation.example/cart (Example URL, does not go anywhere): 3 → 0 · improved
https://toschestation.example/cart (Example URL, does not go anywhere)
- Raise text contrast on muted UI copy
Serious · Site · Automated · WCAG 1.4.3 · 20 occurrences · 1/3 pages
In progressMTFixed by Marcus T.Twenty text and button elements fail WCAG contrast, including a large cluster of white label text on the salmon Add to cart buttons (#cc967e) from the Tosche mockups. The visual contrast preview groups each pair with a suggested pass ratio before you edit Theme settings.Fix guidance
Use the visual contrast preview on the report to pick target hex values, then update Theme settings > Colors or section block colors (announcement bar rust, warm cream surfaces, primary buttons). Darken #cc967e button fills or use darker text until each pair clears 4.5:1.Pages
- MTFixed by Marcus T.· Oct 6, 2026
https://toschestation.example/products/dune-warden-jacket (Example URL, does not go anywhere)
- Fix cart drawer focus trap and focus return
Serious · Template · Manual · WCAG 2.4.3 · 0/2 pages
In progressDRReviewed by Dana R.Found during keyboard testing, not by the automated scan. Opening the cart drawer from a collection page leaves focus on the page behind the overlay, so keyboard users tab through hidden content. Closing the drawer does not return focus to the cart button.Fix guidance
Trap focus inside the drawer while it is open, set `aria-modal="true"`, and store the trigger element so focus returns to it on close. Add `inert` or `aria-hidden` to the background region while the drawer is open.https://toschestation.example/collections/outerwear (Example URL, does not go anywhere)
- Name icon-only buttons and the product tablist
Serious · Site · Manual verified · WCAG 4.1.2 · 4 occurrences · 0/3 pages
To doIcon-only controls in the header, hero carousel, and cart line items announce as "button" with no purpose. The product detail tablist has no accessible name, so screen reader users cannot tell what the tabs control.Fix guidance
Add visually hidden text inside each icon button (Search, Next slide, Remove item). Give the product tablist an `aria-label` such as "Product details". Keep the SVG marked `aria-hidden`.Pages
https://toschestation.example/products/dune-warden-jacket (Example URL, does not go anywhere)
- Review widget iframe has no title (vendor owned)
Moderate · Site · Automated · WCAG 4.1.2
Won't fixDRDecision by Dana R.The third-party review widget renders an iframe with no title attribute. The markup comes from the vendor bundle, so we cannot fix it in your theme.Fix guidance
We sent the vendor a written report with the failing selector and the WCAG criterion. Tracking here so it stays visible. If the vendor does not ship a fix, the fallback is to wrap the embed in a titled region.https://toschestation.example/products/dune-warden-jacket (Example URL, does not go anywhere)
Progress log
How a sprint runs
Fixed scope from the audit, shipped on a branch you approve before anything reaches production.
- Input
- The completed audit. Every failing criterion and every automated finding becomes a tracked item before work starts.
- Where we work
- A development branch or an unpublished theme. Your team reviews and merges. Nothing goes live without your approval.
- Approach
- Code fixes in Liquid, CSS, and JavaScript. We do not install overlay widgets, because they do not satisfy WCAG and often add new barriers.
- Proof of fix
- Each shipped fix triggers a rescan of the affected URLs. Violation counts before and after are recorded on the item.
- Manual re-verification
- Keyboard and screen reader findings are re-tested by hand, since a rescan cannot confirm focus behavior.
- Typical effort
- A storefront the size of the demo runs 16 to 24 developer hours, which is one sprint.
What this tier does not include
- Violations inside third-party app iframes. We report them to the vendor in writing and track the item, but the code is theirs.
- Shopify Checkout beyond the surfaces your plan exposes to customization.
- Content authored after the sprint. New pages and merchandising edits can introduce new violations, which is what Monitoring covers.
- Legal certification. We deliver technical conformance evidence, not a compliance guarantee.
What you receive
- All audit findings remediated in your theme
- Live remediation tracker with items, subtasks, and progress log
- Per-change documentation with the WCAG criterion addressed
- Before and after rescan counts on every shipped fix
- Manual re-verification of keyboard and screen reader findings
- Updated accessibility statement
- Conformance documentation suitable for legal review
Most requested path
Audit and remediation, as one engagement
One contract, one fixed quote after scoping, and one end date. You approve a single number instead of adding two ranges together. If you are answering a demand letter, an audit on its own documents the problems without resolving them, so most of these engagements run straight through both stages.
From $10,500
2 to 11 weeks to documented conformance
Common questions
No. We fix code in your theme and checkout flow. Overlays do not satisfy WCAG requirements, they are a common target in demand letters, and they frequently create new barriers for screen reader users.
Turn your audit into a fixed storefront
Sprint length tracks how severe your findings are, from 1 to 8 weeks. Start with a scoping call.