The Phased Accessibility Redesign: A Practical Path When Full Redesigns Aren’t Possible
After decades of building WordPress sites, I’ve had countless conversations that start the same way: “We know our site isn’t accessible, but we can’t afford to rebuild everything right now.”
It’s a legitimate concern. A complete website redesign can easily run $50,000-$150,000+ for organizations with substantial content. When you’re a nonprofit operating on tight budgets, a government agency with procurement constraints, or a small business with limited resources, that price tag can make accessibility feel impossible.
But here’s what I’ve learned: accessibility doesn’t have to be an all-or-nothing proposition.
The Reality of Budget and Time Constraints
Let’s be honest about the challenges organizations face:
Budget realities mean many organizations simply cannot allocate six figures to a complete redesign, even when they understand the legal and ethical importance of accessibility. The money isn’t there, and no amount of explaining ADA compliance requirements will make it materialize.
Organizational capacity matters too. Even when budget exists, many teams lack the bandwidth to manage a full redesign project. Marketing departments are stretched thin, IT resources are limited, and the prospect of migrating hundreds or thousands of pages feels overwhelming.
Business continuity concerns are real. A full redesign means months of disruption, content migration challenges, potential SEO impacts, and the risk that comes with any major change to a business-critical asset.
The traditional response from accessibility consultants has been: “You need a complete redesign on an accessible foundation.” While technically correct, this advice isn’t helpful for organizations facing real-world constraints.
There’s a better way.
The Phased Redesign Methodology
A phased accessibility redesign starts with an accessible foundation but approaches the transition strategically, prioritizing impact while managing cost and complexity.
Here’s how it works:
Phase 1: Build the Accessible Core
Start by creating a new WordPress site using a genuinely accessible theme (not just one that claims accessibility). Your core pages include:
- Homepage
- Primary service/product pages (typically 3-8 pages)
- About page
- Contact page
- Key conversion paths
These pages are built from scratch following WCAG 2.2 AA standards. They establish your accessible design system – your color contrast ratios, heading structures, navigation patterns, form designs, and interactive elements all meet accessibility requirements from day one.
This initial phase typically costs $8,000-$25,000 depending on complexity – far more manageable than a full redesign while creating immediate value.
Phase 2: Import Legacy Content
Here’s where the methodology gets interesting. Rather than rebuilding everything, you import your remaining content into the new site in a “legacy” state.
These imported pages maintain their existing design and functionality. They’re clearly identified (often with a subtle banner or designation) as legacy content that doesn’t yet meet your new accessibility standards. This transparency is crucial – you’re being honest about where you are in the journey.
Critical technical considerations:
Your accessibility statement must explicitly address this mixed state. Something like: “We are actively working to improve accessibility across our entire website. Pages marked ‘Updated’ meet WCAG 2.2 AA standards. Legacy pages are being systematically improved and will be updated by [timeline].”
URL structure requires careful planning. Ideally, maintain existing URLs to preserve SEO equity. If URLs must change, implement 301 redirects with a comprehensive redirect map. Use Google Search Console to monitor any ranking impacts and address issues quickly.
Site architecture needs clear distinction between compliant and legacy sections. This might mean different templates, CSS namespacing, or even subdomains depending on your technical setup.
Phase 3: Systematic Legacy Remediation
Now comes the steady improvement process. You prioritize which legacy sections to rebuild based on:
Traffic data – High-traffic pages get priority since they impact the most users
Conversion importance – Pages critical to your business objectives move up the queue
Complaint history – If users have reported specific accessibility barriers, address those sections first
Logical grouping – Tackle related pages together to maintain consistency and efficiency
Each quarter (or month, depending on resources), you rebuild 10-20 legacy pages using your established accessible design system. Because the design patterns are established, this work is faster and more cost-effective than the initial core page development.
The goal is complete transition within 12-24 months for most organizations.
Managing the Process: Essential Strategies
Create a Detailed Accessibility Statement
Your accessibility statement becomes your roadmap and your commitment. It should include:
- Current WCAG conformance level and goal
- Specific pages or sections that are fully compliant
- Known limitations in legacy sections
- Timeline for improvements
- Clear contact information for accessibility concerns
- Testing methodology and tools used
Update this statement each time you complete a phase of legacy remediation. This demonstrates progress and shows good faith compliance efforts.
Implement Rigorous Testing Protocols
Testing becomes more complex with mixed compliance states:
Test new pages thoroughly before launch using both automated tools and manual testing. The standard should be: if it’s new, it’s compliant. No exceptions.
Document legacy issues systematically. Run accessibility scans (like Insi’s virtual browser scanning) to identify and prioritize problems in legacy content. This documentation serves both as a remediation roadmap and as evidence of due diligence should accessibility complaints arise.
Retest after migration. Content that worked fine standalone sometimes breaks when imported. URL structures, asset paths, and JavaScript functionality all need verification post-migration.
Create a testing schedule. Monthly scans of legacy sections help identify any new issues introduced through content updates or plugin changes.
Manage SEO Implications Carefully
Accessibility improvements often boost SEO, but the transition process requires attention:
Preserve URL equity through careful redirect mapping when URLs must change. A comprehensive 301 redirect strategy prevents the traffic losses that can occur during major redesigns.
Improve as you go. New accessible pages typically have better semantic HTML structure, clearer heading hierarchies, and better alt text – all of which benefit SEO. Make this an explicit part of your redesign criteria.
Monitor search performance using Google Search Console and analytics throughout the transition. Quick identification of ranking drops allows for rapid response.
Update XML sitemaps to reflect your new structure and ensure search engines discover your improved pages quickly.
Establish Clear Project Governance
A phased approach requires discipline:
Designate an accessibility lead responsible for maintaining standards and overseeing the transition roadmap.
Create page templates and component libraries that embed accessibility patterns, making it easier for team members to build compliant pages without deep accessibility expertise.
Develop content migration checklists covering the specific items that need review when moving legacy content: image alt text, heading structure, link text, form labels, table headers, etc.
Implement approval workflows ensuring new and rebuilt pages meet your accessibility criteria before going live.
Communicate progress to stakeholders with regular updates on pages completed, timeline adherence, and any adjustments to the roadmap.
Additional Critical Considerations
Legal and Compliance Perspective
A phased approach doesn’t eliminate legal risk, but it demonstrates several important factors:
Good faith effort – You’re actively working toward compliance rather than ignoring the issue
Resource allocation – You’re dedicating budget and time to accessibility improvements
Clear timeline – Your accessibility statement provides a realistic roadmap
Prioritization logic – You’re addressing high-traffic and critical pages first
Many accessibility attorneys view phased approaches favorably when they’re genuine, well-documented efforts rather than indefinite deferrals.
Technical Architecture Decisions
Your WordPress setup needs to support this dual state:
Theme selection matters immensely. Start with a genuinely accessible theme like Neve, Astra, or Kadence (properly configured) rather than retrofitting an inaccessible theme.
Plugin audit is essential. Many WordPress plugins introduce accessibility barriers. Your new site should use only accessibility-tested plugins, while legacy imports may include problematic plugins that need gradual replacement.
CSS namespacing can help maintain clear separation between legacy and new styling, preventing conflicts and making it obvious which code supports which sections.
Content Migration Workflow
The actual process of moving content requires structure:
- Export legacy content with complete metadata, taxonomies, and media assets
- Catalog issues through automated scanning before migration
- Import with clear categorization marking pages as legacy
- Test functionality ensuring forms, searches, and dynamic elements still work
- Update internal links to reflect new site structure
- Verify redirects from old URLs if changed
- Update accessibility statement to reflect the transition state
Weighing the Pros and Cons
Advantages of the Phased Approach
Financial feasibility – Organizations can start with $8K-$25K instead of needing $50K-$150K upfront
Faster time to value – Your most important pages become accessible within weeks or months rather than waiting for a complete rebuild
Reduced project risk – Smaller phases mean less complexity, easier testing, and fewer moving parts to coordinate
Business continuity – The website remains functional throughout, with minimal disruption to operations or user experience
Learning curve management – Teams build accessibility expertise gradually rather than facing an overwhelming knowledge gap all at once
Demonstrable progress – Stakeholders see tangible improvements each phase rather than waiting months for a big reveal
Disadvantages and Challenges
Mixed user experience – Visitors encounter inconsistent design and accessibility across different sections, which can be confusing
Extended timeline – Full accessibility takes 12-24 months rather than the 3-6 months of a complete redesign
Ongoing management overhead – Coordinating between legacy and new sections requires consistent attention and clear processes
Potential for scope creep – Without discipline, “temporary” legacy sections can become permanent as new priorities emerge
Testing complexity – You’re essentially maintaining and testing two sites simultaneously during the transition period
Explanation burden – Your accessibility statement needs clear, honest communication about the mixed state, and you may face questions from users or auditors
When This Approach Makes Sense
The phased methodology works best for:
- Organizations with 50-500 pages of content (too much for quick rebuild, manageable for phased approach)
- Teams with limited technical resources who need to build capacity gradually
- Nonprofits and government agencies facing budget constraints but compliance requirements
- Businesses where full-site disruption would significantly impact operations
- Organizations with content that varies widely in importance and traffic
This approach is less ideal for:
- Very small sites (10-20 pages) where complete rebuild is nearly as fast
- Organizations facing immediate legal action requiring rapid full compliance
- Sites with deeply integrated accessibility barriers throughout the technical architecture
- Teams unable to commit to the sustained effort required for systematic remediation
Moving Forward
If you’re facing the “we can’t afford a full redesign” challenge, the phased approach offers a viable path. It’s not perfect – you’ll live with inconsistency for a year or two, and it requires sustained commitment.
But it’s real. It acknowledges the constraints organizations actually face while creating a credible roadmap to full accessibility.
The key is treating it as a genuine commitment, not an excuse for indefinite delay. Set clear phase timelines, maintain rigorous tracking, update your accessibility statement honestly, and hold yourself accountable to the roadmap.
Accessibility is the right thing to do, but it also has to be possible within your actual organizational reality. The phased redesign makes it possible.
What’s your experience with accessibility redesigns? Have you found ways to make accessibility improvements manageable within budget constraints? I’d be interested to hear what’s worked (or hasn’t) for your organization.
About Accessibility Testing: If you’re planning a phased redesign, starting with clear baseline data is essential. Insi’s virtual browser scanning tests how users with disabilities actually interact with your site, helping you prioritize which legacy sections need attention first. Try a free scan to understand your starting point and track progress through your transition.
