You're facing a legacy system that can't meet WCAG 2.1 Level AA without a complete rebuild. Your client wants to claim undue burden. Before drafting that defense, know this: courts see "undue burden" as a narrow exception needing specific documentation, not a blanket excuse for inaccessible digital properties.
This guide walks you through evaluating, documenting, and defending an undue burden claim under ADA Title III and Section 508 of the Rehabilitation Act. Use it when your organization faces genuine technical or financial constraints that prevent immediate full conformance.
The Problem: When Undue Burden Claims Collapse
Most undue burden defenses fail because counsel confuses operational inconvenience with legal impossibility. A court won't accept "our CMS is old" or "remediation costs exceed our quarterly budget" as sufficient evidence. The statute requires proof that compliance would fundamentally alter your service or impose costs disproportionate to your organization's overall resources.
Without a documented compliance roadmap and interim accommodations, your undue burden claim appears as willful noncompliance. This distinction matters when a plaintiff's attorney reviews your accessibility statement during discovery.
What You Need Before Starting
Before drafting an undue burden defense, gather these materials:
Financial documentation: Three years of audited financial statements, IT budgets, and capital expenditure forecasts. Courts evaluate burden relative to total organizational resources, not just the digital team's allocation.
Technical assessment: A conformance report identifying which WCAG success criteria your system fails and why. Document whether barriers stem from third-party dependencies, legacy architecture, or custom code. Include vendor statements if applicable.
User impact analysis: Data showing how many users encounter barriers and which features are affected. Courts weigh burden claims against the scope of exclusion.
Alternative accommodation plan: Written procedures for providing equivalent access through non-digital channels. This is a statutory requirement when claiming undue burden.
Legal review of jurisdictional standards: Confirm which accessibility standards apply to your organization. Federal contractors must meet Section 508 requirements regardless of financial burden. State and local government entities fall under ADA Title II, which applies different burden analysis than Title III.
Step-by-Step Implementation
1. Conduct a Burden Threshold Analysis
Start by determining whether your situation meets the legal definition of undue burden. Under ADA Title III, you must demonstrate that compliance would result in significant difficulty or expense when considered in light of:
- Nature and cost of the needed action
- Overall financial resources of your facility or facilities involved
- Number of persons employed Assistive Technology the facility
- Effect on expenses and resources
- Legitimate safety requirements
- Impact on your organization's operations
Document each factor with specifics. "Significant expense" means different things for a regional nonprofit versus a multinational corporation. A $500,000 remediation project might constitute undue burden for an organization with $2 million in annual revenue; it won't for one with $200 million.
2. Map Critical User Journeys
Identify which digital functions are essential versus supplementary. Courts expect you to prioritize accessibility fixes for core services. If your e-commerce checkout fails WCAG 1.4.3 (Contrast Minimum) but your marketing blog also fails, fix checkout first.
Create a severity matrix:
- Critical: Functions required to access goods, services, or information (authentication, forms, checkout, account management)
- High: Features that significantly enhance usability but have workarounds
- Medium: Supplementary content with accessible alternatives available
- Low: Decorative or redundant elements
This matrix becomes your remediation roadmap and demonstrates good faith effort during litigation.
3. Document Your Remediation Roadmap
Draft a written accessibility plan that includes:
- Specific WCAG success criteria you're addressing
- Estimated timeline for each phase of remediation
- Budget allocated to accessibility work
- Personnel assigned to implementation
- Milestones for conformance testing
Update this document quarterly. If your burden claim rests on a multi-year modernization project, courts will expect evidence that you're making measurable progress. Stalled roadmaps undermine your defense.
4. Establish Interim Accommodations
While addressing technical barriers, you must provide equivalent access through alternative means. Document your accommodation procedures:
Phone-based assistance: Train staff to complete transactions on behalf of users who can't access your digital interface. Log these requests to demonstrate demand.
Email alternatives: Provide accessible document formats (PDF/UA, properly tagged Word documents) for forms and content that aren't web-accessible yet.
In-person services: If your physical locations are accessible, ensure staff can provide the same services available online.
Third-party accessible platforms: Consider whether you can temporarily offer services through an accessible vendor platform while remediating your primary system.
Post these accommodation options prominently on your accessibility statement. Include direct contact information, not just a generic support email.
5. Prepare Your Legal Documentation
If you're facing litigation or a demand letter, compile your burden defense package:
- Sworn affidavit from your CFO detailing financial constraints
- Technical expert report explaining why immediate conformance isn't feasible
- Your accessibility roadmap with documented progress
- Records of interim accommodations provided
- Communications with vendors about accessibility fixes
- Board meeting minutes discussing accessibility budget allocation
This package demonstrates you've conducted a thorough analysis, not just claimed burden as a delaying tactic.
Validation: How to Verify Your Defense Holds
Test your undue burden claim against these questions:
Can you explain why partial conformance isn't achievable? If you can fix some barriers within existing resources, courts expect you to do so while claiming burden for the remainder.
Have you provided meaningful interim accommodations? If users still can't access your services through any channel, your burden claim fails.
Does your timeline show concrete progress? A five-year roadmap with no completed milestones won't satisfy a court.
Have you explored less burdensome alternatives? If an overlay or third-party widget could address critical barriers Assistive Technology lower cost, you need documentation explaining why you rejected that option.
Run your documentation past outside counsel familiar with accessibility litigation. They'll identify gaps before opposing counsel does.
Maintenance: Ongoing Tasks
Undue burden isn't a permanent status. Review your claim quarterly:
Update financial analysis: If your organization's resources improve, your burden threshold changes. A defense that held two years ago might not hold today.
Track accommodation requests: Document every user who requests alternative access. This data proves your interim measures are functioning and demonstrates demand for full accessibility.
Audit remediation progress: Compare actual conformance improvements against your roadmap. Missed milestones weaken your defense.
Monitor regulatory changes: The DOJ Final Rule (2024) and updated Section 508 standards may affect your burden analysis. What constituted undue burden under older interpretations might not qualify under current enforcement priorities.
Reassess third-party dependencies: If a vendor releases an accessible version of a component you claimed Web Accessibility Specialist impossible to remediate, you can't continue claiming burden for that element.
Undue burden is a time-limited defense requiring active management. Treat it as a compliance bridge, not a destination. Your goal is to eliminate the burden claim by achieving conformance, not to extend it indefinitely through documentation alone.
