Compliance Maintenance Checklist
An accessibility compliance maintenance checklist defines the recurring activities that keep a website aligned with WCAG 2.1 AA after the initial audit and remediation work is complete. Maintenance covers scheduled scans, periodic (manual) evaluations, documentation updates, training refreshers, and a process for managing new content and code changes. Without these activities, conformance status reflects a single point in time and decays as the site evolves.
| Component | What It Covers |
|---|---|
| Scheduled Scans | Recurring automated checks that flag approximately 25% of WCAG issues across key pages and templates. |
| Periodic Evaluation | Human-led (manual) review covering screen reader, keyboard, and visual inspection on a defined cadence. |
| Change Review | Accessibility checks tied to new templates, features, content types, and third-party integrations. |
| Documentation | Accessibility statement, policy, audit reports, and remediation logs kept current. |
| Training | Role-specific refreshers for content authors, designers, and developers. |
Why Maintenance Matters After Remediation
A website that conforms to WCAG 2.1 AA today will not conform six months from now without active oversight. New blog posts, product pages, marketing campaigns, code releases, and third-party scripts all introduce potential issues. Maintenance is the difference between a one-time conformance status and an ongoing compliance posture.
For organizations operating under ADA Title II, where the rule references WCAG 2.1 AA as the technical standard, maintenance is how conformance is preserved between formal evaluations. For private organizations operating under ADA Title III, maintenance is a primary way to reduce legal risk over time.
Recurring Scan Activities
Scheduled scans run on a defined cadence, typically weekly or monthly, across the site’s most important pages and templates. Scans evaluate HTML, CSS, and ARIA attributes against WCAG success criteria and surface issues that automated detection can identify with high accuracy.
Scan coverage should include the homepage, primary template variations, key conversion paths, and any authenticated areas reachable through a logged-in session. Scan results need an owner. Without someone reviewing flagged issues and assigning remediation work, scan output becomes background noise.
Periodic (Manual) Evaluation
Because scans only flag approximately 25% of issues, the remaining 75% requires human evaluation. A maintenance program schedules periodic (manual) review on a cadence appropriate to the site’s rate of change. Quarterly reviews suit fast-moving sites. Annual reviews may be sufficient for static informational sites with strict change controls.
Periodic evaluation includes screen reader testing with NVDA, JAWS, and VoiceOver, keyboard testing across all interactive components, visual inspection at standard and zoomed magnifications, and code inspection where automated checks raise questions. The evaluation identifies issues that scans cannot detect, including focus order problems, ambiguous link text, missing form instructions, and inaccessible custom components.
Change Review Process
Most accessibility regression happens at the moment of change. A maintenance checklist includes a change review process tied to the development and content workflows.
- New templates and components: Evaluated against WCAG 2.1 AA before release.
- Content publishing: Authors verify alternative text, heading structure, and link text on every new page.
- Third-party integrations: Embeds and scripts reviewed for accessibility impact before deployment.
- Design system updates: Component changes reviewed for downstream effects on conformance.
- Major releases: Targeted evaluation before any release that touches navigation, forms, or interactive components.
Documentation Updates
Documentation reflects the current state of the program. The accessibility statement is reviewed at least annually and updated when conformance status changes. The accessibility policy stays aligned with the actual workflows in use. Audit reports and remediation logs are retained as evidence of an ongoing program, which matters if the organization receives a demand letter or complaint.
For sites maintaining a connection to a parent monitoring program, documentation also includes scan schedules, evaluation cadences, and the names or roles responsible for each activity.
Training Refreshers
Personnel turnover and platform changes erode institutional knowledge. A maintenance program schedules role-specific training refreshers for content authors, designers, developers, and quality reviewers. Training covers the WCAG criteria most relevant to each role, the organization’s accessibility policy, and the workflow for reporting and resolving issues.
Assigning Ownership
The most common point of breakdown in accessibility maintenance is unclear ownership. Each item on the checklist needs a named owner, a defined cadence, and a place where outcomes are recorded. Without ownership, scans run but no one acts, evaluations get postponed, and documentation drifts out of sync with the live site.
A maintenance checklist that lives in a shared system, with clear assignees and review dates, is what separates a real program from a binder on a shelf.