Use this ADA ecommerce remediation plan template to turn a scan into work. Without it, you have a list of problems. With it, you have ownership, dates, and proof.

What the template should track

At minimum, every entry should include:

  • store or project name
  • page or template URL
  • issue summary
  • WCAG criterion
  • severity
  • owner
  • fix plan
  • evidence link
  • due date
  • status

Copy and paste template

Remediation item

  • Store:
  • URL or template:
  • Issue:
  • WCAG criterion:
  • Severity:
  • Owner:
  • Fix:
  • Evidence:
  • Due date:
  • Status:
  • Notes:

Example

  • Store: AmazingPlugins demo shop
  • URL or template: /products/silk-shirt/
  • Issue: Add to cart button has no accessible name in sticky mobile bar
  • WCAG criterion: 4.1.2 Name, Role, Value
  • Severity: High
  • Owner: Theme developer
  • Fix: Add visible text or an aria-label
  • Evidence: Screen reader output after deploy
  • Due date: 2026-05-28
  • Status: In progress
  • Notes: App embed also needs a re-check after the theme patch

How to prioritize the plan

Start with anything that blocks checkout or keyboard use.

  1. Keyboard traps
  2. Missing form labels
  3. Missing button names
  4. Focus visibility issues
  5. Alt text gaps on important product images
  6. Contrast failures on controls and text
  7. App embed conflicts

That order is not fancy, but it saves time.

How to keep the plan useful

  • Update it when the app or theme changes
  • Mark items closed only after you verify the live page
  • Keep screenshots or screen reader notes next to the entry
  • Split big problems into smaller tickets
  • Re-run the scan after each batch of fixes

What not to do

  • Do not store this in a one-time doc nobody opens
  • Do not leave owners blank
  • Do not use “misc” as a status
  • Do not close items before the live check passes

Quick FAQs

What fields should every remediation item include?

At minimum, capture the page or template, issue summary, WCAG criterion, severity, owner, fix plan, evidence, due date, and status.

Is this the same as a remediation log?

Close, but not identical. A remediation plan is the work queue. A remediation log is the record of what was actually fixed.

How often should I update the plan?

Update it whenever you finish a fix, discover a new issue, or re-scan after a theme or app change.

Bottom line

A remediation plan is not paperwork for its own sake. It is how you stop accessibility work from turning into a pile of half-finished fixes.