Full ADA compliant rebuilds

Not every site needs a full rebuild. Many can be remediated through systematic fixes. But certain situations make rebuilding the more practical option.

The site is older than 3-5 years. Web development moves fast. Platforms evolve. If your site was built before WCAG 2.1 was the standard, the underlying code probably doesn't support modern accessibility requirements.

The content management system is end-of-life. If your CMS no longer receives security updates or doesn't support semantic HTML output, fixing individual pages is a losing battle.

You've been sued and the audit shows fundamental structural problems. When the accessibility issues aren't surface-level—when the heading hierarchy makes no sense, when the navigation relies on mouse-only interactions, when forms are built with divs instead of proper HTML—patching is like putting new tires on a car with a broken engine.

Your development team estimates that remediation will take longer than rebuild. This is the pragmatic test. If the time and cost to fix existing code exceeds the time and cost to build new code, rebuild wins.

You're planning a redesign anyway. If you were already going to update your brand, refresh your content, or change platforms, adding accessibility requirements to the scope costs marginally more than doing it later.

The legal trigger: DOJ deadlines

For state and local governments, the deadlines are fixed. April 24, 2026 for entities with 50,000 or more people. April 26, 2027 for smaller entities and special district governments .

These aren't suggestions. The Department of Justice adopted WCAG 2.1 Level AA as the technical standard for Title II entities in April 2024 . If your government website doesn't meet that standard by the deadline, you're out of compliance.

For private businesses, there's no federal regulation with a specific date. But the DOJ's position is clear: the ADA applies to websites, and WCAG 2.1 Level AA is the de facto standard courts use . The Fashion Nova case from February 2026 shows that the DOJ is actively monitoring whether settlements actually produce meaningful accessibility improvements .

What a rebuild actually requires

A full rebuild means starting with accessibility requirements in the design phase, not adding them during development.

Design phase: Your designer needs to know color contrast requirements from the start—4.5:1 for normal text, 3:1 for large text . They need to plan for visible focus indicators that don't ruin the aesthetic. They need to design with keyboard navigation in mind.

Development phase: Your developers need to use semantic HTML, not divs with click handlers. Forms need proper labels. Images need alt text frameworks. Heading structures need to follow logical hierarchy without skipping levels. Custom components need ARIA roles and keyboard handlers.

Content phase: Your content team needs to write alt text for every image. They need to structure documents with proper headings. They need to avoid PDFs that aren't accessible or provide HTML alternatives.

Testing phase: Manual testing with keyboard navigation. Screen reader testing with NVDA on Windows and VoiceOver on Mac. Automated scanning as a safety net, not the primary test .

The Awe Inspired example

Awe Inspired's experience with TestParty shows what a rebuild with accessibility baked in looks like in practice.

The company, a fast-growing direct-to-consumer jewelry brand on Shopify, knew their site had accessibility gaps but lacked the bandwidth to address them proactively. Like many scaling e-commerce companies, they moved fast—sometimes launching initiatives within days rather than weeks .

When they evaluated options, they rejected overlay widgets like AccessiBe and UserWay. Alison Noda, who leads site operations, explained why: "The overlays are just expensive for what they are. And it doesn't solve the problem. It's kind of just a band-aid approach" .

Instead, they chose a source code remediation approach that fixed problems at their root. As they underwent a complete site rebuild and retheme, accessibility became a baseline requirement. "We don't have to think about the accessibility part because it's already baked in," Noda said .

The result during budget planning: when leadership asked where to rank tools and requested 50 percent cuts, TestParty was immediately categorized as "non-negotiable." Noda told leadership, "We can't get rid of TestParty—that's not an option" .

The costs

Rebuilding costs money. There's no way around that.

The ADA Quick Scan FAQ provides ranges based on approach. Basic compliance scoring 70-90 on audits runs $5,000 to $20,000. Full compliance scoring 90-plus runs $15,000 to $50,000. Enterprise automated solutions run $500 to $2,000 per month .

Those numbers are for remediation. A full rebuild with accessibility baked in typically costs more on the front end but less on maintenance.

Meghna Deshraj, who consults on website projects, breaks down costs by site size :

Small business website (10-20 pages, simple structure)

• Initial audit: $2,000-$3,000
• Remediation: $3,000-$8,000
• Total: $5,000-$11,000

Mid-size website (50-100 pages, moderate complexity)

• Initial audit: $4,000-$7,000
• Remediation: $10,000-$20,000
• Total: $14,000-$27,000

Large website (200-plus pages, complex functionality)

• Initial audit: $8,000-$15,000
• Remediation: $25,000-$50,000+
• Total: $33,000-$65,000+

E-commerce site (product catalog, transaction flows)

• Initial audit: $6,000-$12,000
• Remediation: $15,000-$35,000
• Total: $21,000-$47,000

These ranges assume starting from a typical website with moderate accessibility debt. Sites built with accessibility in mind from the start can achieve compliance for 20 to 30 percent less .

The cost of doing nothing is higher. A single lawsuit typically costs $92,000 to $316,000 when you include settlement, legal fees, and remediation .

The timeline

A full rebuild with accessibility requires realistic timelines.

The ADA Quick Scan FAQ gives ranges :

• Automated overlay: 2-5 days to implement
• Manual fixes in-house: 3-6 months
• Consultant or agency: 6-12 weeks
• Complete redesign: 6-12 months
• Critical pages only: 2-4 weeks

Meghna Deshraj's 60-day plan for remediation provides a more detailed breakdown :

Weeks 1-2: Assessment. Automated scans, manual review, keyboard testing, screen reader testing. Output: comprehensive audit report with prioritized remediation list. Investment: 12-20 hours internal, or $2,000-$5,000 for professional audit.

Weeks 3-4: Critical fixes. Keyboard navigation, missing alt text on critical images, severe color contrast issues, form labels, skip navigation links. Investment: 30-50 development hours, or $3,000-$7,500 if outsourcing.

Weeks 5-6: Comprehensive remediation. Complete alt text, remaining contrast issues, heading hierarchy, link descriptiveness, video captions, ARIA landmarks. Investment: 40-60 development hours, or $4,000-$9,000 if outsourcing.

Week 7: Testing and QA. Comprehensive keyboard testing, screen reader testing, automated verification, user testing if budget allows. Investment: 12-20 hours, or $1,500-$3,000.

Week 8: Documentation and processes. Accessibility statement, internal guidelines, quarterly audit schedule, content workflow checkpoints. Investment: 8-12 hours, or $1,000-$1,500.

A full rebuild extends these timelines because you're building from scratch, not fixing existing code. The 6-12 month range for complete redesign accounts for design, development, content migration, and testing.

The overlay problem

Accessibility widgets and overlays have become a massive industry. Companies sell JavaScript tools that claim to make any site accessible with one line of code.

The data says they don't work.

Nearly 25 percent of lawsuits in 2025 targeted websites that used accessibility widgets . The Federal Trade Commission fined AccessiBe $1 million for making false claims about ensuring ADA compliance.

The Overlay Fact Sheet, signed by more than 700 accessibility professionals including experts from Google, Microsoft, Apple, and Shopify, states plainly that overlays don't fix underlying code problems. They attempt to patch issues on the fly, often introducing new barriers in the process.

Alison Noda's assessment from Awe Inspired matches this industry consensus: overlays are "a band-aid approach" that doesn't solve the problem .

If you're doing a full rebuild, don't plan to rely on an overlay. Build accessibility into the code from the start.

What WCAG 2.1 Level AA requires

The technical standard is WCAG 2.1 Level AA, adopted by the DOJ for Title II entities and used by courts for Title III cases .

The guidelines are organized around four principles: perceivable, operable, understandable, robust .

Perceivable means information must be presentable in ways users can perceive. Provide text alternatives for all images. Add captions for videos. Ensure sufficient color contrast.

Operable means interface components must be operable. All functionality must be available from a keyboard. Users need enough time to complete tasks. Content shouldn't cause seizures.

Understandable means information must be understandable. Text should be readable. Behavior should be predictable. Forms should help users avoid and correct mistakes.

Robust means content must work with assistive technologies. HTML should be valid. Accessibility APIs should be properly used.

The North Carolina Department of Information Technology's checklist identifies specific success criteria that require manual testing because automated tools can't catch everything .

These include meaningful image alt text, proper data table coding, correct heading hierarchy, meaningful sequence when navigated linearly with a screen reader, and content functionality at 400 percent zoom without two-dimensional scrolling.

The vendor responsibility trap

If you hire someone to build your rebuild, you're still responsible for accessibility.

The DOJ's small entity compliance guide makes this explicit: if you have a contract, license, or other arrangement with another entity to provide public services, you still need to make sure those services comply . This includes web content or mobile apps the other entity provides.

For governments, this means working with vendors to help ensure they understand the requirements or seeking out vendors with such knowledge. If a town hires an outside web developer to design and build the town's website, the town needs to make sure the web developer's design complies .

For private businesses, the same principle applies. Your vendor agreement should require WCAG 2.1 AA compliance. Your acceptance testing should verify it before you pay.

The trade-offs

A full rebuild costs more upfront than patching. That's the main trade-off.

But there are others.

Speed vs. thoroughness. A rebuild takes longer. If you're facing an imminent lawsuit deadline, a rebuild might not be feasible. You may need to fix critical pages first and plan the rebuild for later.

Design flexibility vs. constraints. Designing within WCAG requirements means some aesthetic choices are off the table. Light gray text on white backgrounds doesn't work. Custom interactive components require more development time. Some designers chafe at these constraints.

Maintenance vs. one-time fix. A rebuild isn't a one-time solution. Content changes. Features get added. New developers make mistakes. Maintaining accessibility requires ongoing attention, not just a launch checklist .

User experience vs. legal compliance. Some accessibility requirements improve experience for everyone. Keyboard navigation helps power users. Good contrast helps in bright sunlight. Clear form labels help everyone avoid mistakes. But some requirements feel like pure compliance overhead.

What to test for

The enhanced Chromium checklist from October 2025 provides specific testing protocols for each WCAG success criterion .

For images, test that every meaningful image has descriptive alt text. Decorative images should have empty alt attributes or role="presentation". Use DevTools to inspect each img element and the accessibility tree to verify computed names .

For contrast, test normal text at 4.5:1 minimum and large text (18pt or 14pt bold) at 3:1 minimum. Use DevTools color picker to see contrast ratios automatically calculated. Check hover, focus, and disabled states .

For keyboard navigation, test using only Tab, Shift+Tab, Enter, Space, and arrow keys. Every interactive element must be reachable and usable. Watch for visible focus indicators .

For forms, test that every input has an associated label. Placeholder text is not a label. Error messages must be clear and programmatically associated with the field .

For headings, test that they follow a logical hierarchy without skipping levels. One H1 per page, then H2s for major sections, H3s for subsections .

For zoom, test at 400 percent. Content should reflow without requiring two-dimensional scrolling or losing functionality .

The bottom line

A full ADA compliant rebuild means building from scratch with accessibility as a baseline requirement, not an afterthought. It costs more upfront than remediation—typically $15,000 to $50,000 depending on site size and complexity—but avoids the endless cycle of patching problems that should have been fixed at the foundation.

The DOJ's Title II deadlines are fixed. April 2026 for large entities. April 2027 for smaller ones. Private businesses face the same standards through lawsuits, with over 3,900 cases filed in 2025 and a 37 percent increase in the first half of the year.

The Awe Inspired example shows what a rebuild with accessibility baked in looks like: a site that doesn't require thinking about accessibility because it's already part of the foundation, categorized as "non-negotiable" during budget cuts, and positioned to avoid the lawsuit cycle that catches most e-commerce brands.

If you're facing a major redesign, if your site is older than three to five years, if your audit shows fundamental structural problems, or if you've been sued and need to actually fix things—a full rebuild is worth considering.

Get an audit first. Know what you're dealing with. Then decide whether patching or rebuilding makes more sense for your timeline, your budget, and your risk tolerance.

The money you spend on a rebuild is less than the money you'll spend on one lawsuit. And your site will actually work for everyone who tries to use it.