Maintain Compliance After Remediation
To maintain compliance after remediation, organizations treat accessibility as a continuous program rather than a one-time project. This means recurring scans to catch regressions, periodic (manual) audits to verify conformance at a deeper level, governance policies that route new content and code through accessibility review, and training for the teams that create and maintain digital assets. Remediation closes the issues present on the day of the audit. Ongoing work keeps them closed.
| Element | What It Covers |
|---|---|
| Recurring Scans | Automated checks on a scheduled cadence to flag regressions across HTML, CSS, and ARIA. |
| Periodic Audits | Deeper evaluations by accessibility professionals covering the 75% of issues scans cannot detect. |
| Governance | Policies, review gates, and documented processes for new content, design, and code. |
| Training | Role-based education for designers, developers, content editors, and QA teams. |
| Documentation | Accessibility statement, conformance records, and evidence of ongoing program activity. |
Why Compliance Erodes After Remediation
Websites are not static. New pages get published, templates get updated, third-party scripts get added, and content editors post new material every week. Each change is an opportunity for an accessibility issue to reappear or emerge for the first time.
A site that was fully conformant at the close of remediation can regress within weeks if no oversight exists. The work of maintaining compliance is the work of catching those changes before they accumulate.
Set a Recurring Scan Schedule
Automated scans evaluate HTML, CSS, and ARIA against WCAG success criteria. They identify approximately 25% of accessibility issues, and they do it quickly. Conducting scans on a schedule (daily, weekly, or monthly depending on how often the site changes) provides an early warning system.
Scans are most useful for catching regressions on pages that have already been remediated. When a new issue appears on a previously clean page, it almost always points to a recent change in content or code.
Schedule Periodic Manual Evaluations
Scans miss roughly 75% of WCAG issues. Keyboard operability, screen reader output, focus management, logical reading order, meaningful alternative text, and form error handling all require human evaluation. These are the same areas most often cited in demand letters.
Most organizations schedule a full (manual) audit annually, with targeted evaluations after major releases, redesigns, or platform migrations. Audits typically start at 1,000 dollars and range to 3,000 dollars depending on scope.
Build Governance Into the Workflow
Compliance holds when accessibility is embedded in the production process, not bolted on afterward. Governance practices that support this include:
- Design review: Accessibility checks during design, before development begins.
- Code review: Accessibility criteria included in pull request checklists.
- Content guidelines: Documented standards for editors covering headings, link text, images, and media.
- Third-party vetting: Review of vendor accessibility documentation (VPAT or ACR) before integration.
- Release gates: Accessibility sign-off required before major launches.
Train the Teams That Produce Content and Code
Remediation fixes the output. Training changes the input. Designers, developers, content editors, and QA staff each need role-appropriate education so their day-to-day work does not introduce new issues.
Training is where most organizations see the strongest long-term return. A developer who understands semantic HTML and ARIA produces accessible components by default. An editor who understands heading structure and descriptive link text writes compliant pages without rework.
Keep Documentation Current
An accessibility statement should reflect the current state of the program, including the conformance target (commonly WCAG 2.1 AA), the date of the most recent evaluation, and contact information for users who encounter issues. Internal records of scans, audits, remediation activity, and training complete the picture.
This documentation serves two purposes. It communicates the organization’s position to users, and it provides evidence of good-faith, ongoing effort if questions ever arise.
Respond to Major Changes With Targeted Evaluations
Certain events warrant evaluation outside the regular cadence. A redesign, a CMS migration, a new e-commerce platform, a major feature release, or the addition of a third-party component all change the accessibility profile of the site. Evaluating after these events catches issues while the context is fresh and fixes are easier to prioritize.
Ongoing accessibility monitoring connects these pieces into a program that survives staff changes, redesigns, and shifts in priorities. Compliance is a state an organization maintains, not a milestone it reaches.