Skip to content
SiteRecord

Accessibility Remediation Checklist: Find, Assign, Fix, Verify

This checklist turns accessibility remediation into a repeatable routine: find the issues, give them owners, fix them, verify the results, and keep the record. It is a working process for teams, not a compliance certification and not a legal test. Completing it does not prove a website is accessible or legally compliant; it produces organized work and an honest record of it.

1. Define the testing scope

  • List the user journeys people depend on most: sign-up, checkout, application, search, contact.
  • List the shared components that appear across the site: navigation, headers, footers, forms, embedded widgets.
  • Choose the pages to monitor, starting with the journeys and components above rather than every URL.
  • Write the scope down: which pages, which checks, and how often.

2. Run automated and manual checks

  • Run an automated scan across the monitored pages and record the date and coverage.
  • Review scan findings for false positives before they become work items.
  • Do a keyboard walkthrough of the main journeys: can every interactive element be reached and operated, and is focus visible?
  • Check the things automation cannot judge: meaningful alt text, sensible focus order, understandable error messages, reading order.
  • If expertise is available, run an assistive technology pass on the most important journeys.
  • Log every confirmed barrier as a finding with its page, element, and a plain-language description.

What Accessibility Scans Can and Cannot Tell You explains where each method applies.

3. Prioritize and assign ownership

  • Give every confirmed finding one named owner.
  • Rank by blocked tasks first: issues that stop someone from completing a journey.
  • Weight shared components: a fix in a shared template can clear the same barrier on many pages.
  • Consider recorded severity and affected-page count as inputs, not the whole ranking.
  • Record who was assigned and when, so ownership history is preserved.

How to Prioritize Accessibility Issues covers the tradeoffs in more detail.

4. Remediate and keep the supporting record

  • For each fix, record what actually changed: the code edit, content update, or design revision.
  • Attach supporting material where it helps: a screenshot of the corrected element or a link to the change.
  • Record the date the change shipped.
  • Do not mark work done before it is verified; a completed change and a verified fix are different things.

5. Verify fixes and track unresolved issues

  • Reproduce the original issue first so you know exactly what success looks like.
  • Check the deployed change with the right method: a rescan for mechanical issues, keyboard or assistive technology checks for interaction problems.
  • Check related pages and shared components for regressions.
  • Record who verified the fix, how, when, and with what result.
  • Keep unresolved and deferred findings visible with their reasons; a record of only closed work is not a complete record.

How to Verify an Accessibility Fix walks through a worked example.

6. Report and review on a cycle

  • Summarize the state of the work for whoever needs it: what was fixed, what is open, what is next.
  • Report what the record actually shows, including unresolved work.
  • Set the next automated scan on its recurring schedule.
  • Schedule the next manual pass, and trigger extra checks after releases, template updates, and third-party component changes.
  • Review recurring findings for shared causes worth fixing at the source.

Why Accessibility Needs Ongoing Monitoring covers how to keep this routine sustainable as the site changes.

Using this with SiteRecord

SiteRecord is built around this loop: monitored pages and scheduled scans, findings with one owner each, correction records with attachments, verification entries that note who checked and how, and reports drawn from the same record. The Free plan covers one website. Start a free account to run the checklist against a real site.