To manage remediation across multiple sites, treat the portfolio as a single program with shared standards, prioritized fixes, and centralized tracking. Each property gets its own audit and remediation plan, but the work is coordinated under one accessibility policy, one conformance target (typically WCAG 2.1 AA), and one process for identifying, fixing, and validating issues. Without that structure, teams duplicate effort, apply inconsistent fixes, and lose visibility into where each site stands.
| Element | What It Covers |
|---|---|
| Shared Standard | One conformance target across the portfolio, usually WCAG 2.1 AA. |
| Per-Site Audits | Each property receives its own audit since code, templates, and content differ. |
| Prioritization | Riskiest issues first across all sites, scored by user impact and legal exposure. |
| Centralized Tracking | One system records issues, owners, status, and validation for every site. |
| Ongoing Monitoring | Scheduled scans across all properties catch regressions between audits. |
Start with One Accessibility Policy
A portfolio program needs a single accessibility policy that applies to every site. The policy states the conformance target, the responsibilities of internal teams and vendors, the cadence of audits, and the process for addressing reported issues.
Without one policy, each site operates on its own assumptions. Some teams pursue 2.2 AA, others stop at partial 2.0 conformance, and a few rely only on automated scans. That inconsistency is the largest source of risk in a multi-site environment.
Audit Each Site Individually
Audits cannot be shared across sites. Each property has its own templates, components, third-party integrations, and content patterns. An audit identifies the specific issues on that specific site.
What can be shared is the methodology. The same auditor or team using the same evaluation process across every site produces consistent reports, consistent severity ratings, and consistent remediation guidance. That consistency is what makes portfolio-level management possible.
Prioritize Across the Portfolio, Not Within Each Site
The instinct is to fix one site at a time. The smarter approach is to prioritize across all sites at once. A high-impact issue on a heavily trafficked site outranks a moderate issue on a low-traffic property, even if the low-traffic site has more issues overall.
Prioritization should account for two factors: user impact (how much an issue affects people relying on assistive technology) and risk factor (how often the issue appears in demand letters and complaints). Sorting the combined issue list by these factors produces a remediation queue that reduces the most risk in the shortest time.
Centralize Issue Tracking
Tracking remediation in spreadsheets across multiple sites breaks down quickly. A centralized system, whether a compliance management platform or a structured project tool, gives you one view of every open issue, every owner, and every validation status.
Centralized tracking also makes reporting practical. Leadership can see portfolio-level progress, legal can see what has been documented, and procurement can see which sites are ready for VPAT or ACR issuance.
Standardize Component Fixes Where Possible
Many multi-site portfolios share components: the same CMS theme, the same checkout flow, the same form library. When an issue appears in a shared component, fixing it once should resolve it everywhere that component is used.
This requires coordination between development teams. A fix applied on one site but not propagated to the others wastes the efficiency that shared components offer. Component-level remediation is one of the few places where multi-site management produces real cost savings.
Train the People Doing the Work
Remediation quality depends on whether developers, designers, and content authors understand WCAG. Without training, fixes are guesses. Issues get marked resolved when they are not, and new issues appear faster than old ones get closed.
Training is the difference between a portfolio that steadily reaches conformance and one that runs in circles. Teams responsible for multiple sites need a working knowledge of the success criteria they are being asked to meet.
The WCAG Course at adacompliance.net covers the full set of WCAG 2.1 AA success criteria along with how to apply them in real remediation work, making it a practical foundation for teams managing accessibility across multiple sites.