When Third-Party Systems Fail Your Accessibility Goals: A Practical Guide
Every accessibility professional hits this wall eventually. You’ve worked hard to make your website WCAG compliant—testing, fixing, retesting. Your team has bought into accessibility as a core value. Then someone says, “We need to use this donation platform,” or “The event registration system is already chosen,” and you realize the third-party tool you’re required to use has accessibility issues you can’t fix.
You’re stuck between genuine commitment to accessibility and operational necessity. This isn’t about making excuses—it’s about doing the best you can with the constraints you face while maintaining your integrity and legal compliance.
Understanding the Real-World Constraint
Most organizations don’t have unlimited resources or the leverage to demand that every vendor meets perfect accessibility standards. Government agencies must work within procurement contracts. Nonprofits rely on donor platforms that offer favorable fee structures. Small organizations can’t build custom systems from scratch.
The Americans with Disabilities Act and Section 508 require accessible digital experiences, but they also recognize that “undue burden” exists. Courts understand that organizations must sometimes use third-party systems, but they expect you to minimize barriers and provide alternatives.
First Step: Document Everything
Before implementing any third-party system, conduct an accessibility evaluation and document the findings. Use automated scanning tools like Insi to identify technical issues, then conduct manual testing with keyboard navigation and screen readers.
Create a written accessibility evaluation that includes:
- Specific WCAG violations identified
- Severity of each issue (critical vs. minor)
- Which user groups are most affected
- Remediation attempts made with the vendor
- Business justification for using the system despite limitations
This documentation serves three purposes: it demonstrates due diligence for legal compliance, provides a roadmap for improvement efforts, and gives you leverage when advocating for vendor improvements.
Negotiate with Vendors First
Many third-party platform providers are more responsive to accessibility concerns than you might expect, especially when facing questions from multiple clients. Before accepting a system’s limitations, push back.
Send the vendor your accessibility evaluation with specific WCAG violations. Frame accessibility as a business requirement, not just a nice-to-have feature. Reference legal requirements like the ADA, Section 508, or AODA that your organization must meet.
Ask for a remediation timeline. Even if immediate fixes aren’t possible, getting vendor commitment to future improvements helps you plan alternatives and shows good-faith effort if compliance questions arise.
If the vendor won’t address issues, that information belongs in your documentation. Courts and regulators view vendor responsiveness differently than organizational neglect.
Provide Accessible Alternatives
When a third-party system has accessibility barriers you can’t eliminate, your obligation shifts to providing equivalent access through alternative methods.
For donation platforms with keyboard navigation issues, provide a phone number staffed during business hours where people can make donations with human assistance. For event registration systems that don’t work with screen readers, offer email or phone registration with the same pricing and access to the same information.
The alternative path must provide truly equivalent service—not a lesser experience that makes users feel like second-class participants. Process alternative submissions with the same speed and efficiency as online submissions. Don’t make people justify their need for accommodation.
Document these alternatives prominently on the page where you link to the third-party system. Place alternative contact information immediately visible, not buried in footer text or FAQ pages.
Write Honest Accessibility Statements
Your website’s accessibility statement should acknowledge third-party system limitations honestly while explaining your accommodation approach.
Include language like: “We are committed to providing accessible digital experiences. While we strive to meet WCAG 2.1 Level AA standards, some third-party systems we use have accessibility limitations we cannot directly control. We are actively working with these vendors to improve accessibility and provide alternative access methods for affected users.”
List specific third-party systems with known issues and provide contact information for users who need alternative access. Update this statement as you make progress with vendors or implement new workarounds.
Honesty demonstrates good faith and helps users understand that you take accessibility seriously even when facing constraints. It’s significantly better than pretending barriers don’t exist or discovering them only when users complain.
Implement Technical Workarounds Where Possible
Sometimes you can’t fix a third-party system, but you can reduce its accessibility impact through how you implement it.
Use clear link text before directing users to third-party systems: “Register for our event through Eventbrite (note: some accessibility issues present, phone registration available at 555-0123).” This gives users information to make informed choices about how to proceed.
If embedding third-party content in iframes, ensure your site’s surrounding context is fully accessible. Provide descriptive labels and instructions before the iframe. Make your alternative contact information immediately adjacent to the embedded system.
For systems with color contrast issues, provide browser extension recommendations that can override vendor styling. For keyboard navigation problems, document the specific keyboard sequences that do work.
These workarounds don’t solve everything, but they demonstrate active problem-solving rather than passive acceptance of barriers.
Set Internal Improvement Timelines
Third-party system constraints shouldn’t become permanent excuses. Set internal timelines for vendor improvement, alternative system evaluation, or workaround enhancement.
Review vendor accessibility quarterly. If a vendor consistently ignores accessibility concerns over 12-18 months, that’s a signal to begin evaluating alternatives even if switching involves cost or operational disruption.
Track user feedback about accessibility barriers in third-party systems. If you receive multiple complaints about a specific system, prioritize finding a more accessible alternative.
Some systems will improve over time as accessibility becomes standard practice. Others won’t. Your job is distinguishing between temporary constraints and permanent obstacles, then acting accordingly.
Communicate Proactively with Users
Don’t wait for users to discover accessibility barriers and contact you frustrated. Proactive communication about limitations and alternatives demonstrates respect and reduces negative experiences.
When linking to third-party systems, provide context: “The registration platform we use has some accessibility limitations. We offer phone registration at [number] or email registration at [address] as fully accessible alternatives.”
For systems used repeatedly (weekly event registration, monthly giving, etc.), reach out to users who have used alternative access methods to understand their experience. Ask what would make the process easier. Implement their suggestions where possible.
This ongoing dialogue helps you understand real-world impact and shows users their feedback matters. It also generates documentation of your accessibility efforts.
Know When to Walk Away
Sometimes a third-party system’s accessibility barriers are so severe that continuing to use it creates unacceptable risk and user experience problems. Critical barriers include:
- Complete inability to access core functionality with keyboard or screen reader
- Vendor refusal to address WCAG violations or provide remediation timeline
- User complaints indicating the alternative access methods aren’t working
- Legal opinions suggesting exposure to ADA complaints
If a system meets these criteria, advocate strongly for switching even if that involves cost, contract termination fees, or operational disruption. Some barriers can’t be worked around acceptably.
Document your advocacy efforts. If leadership decides to continue with an inaccessible system despite your recommendation to switch, ensure that decision is documented with clear acknowledgment of the risks.
Moving Forward with Integrity
Using third-party systems with accessibility limitations doesn’t make you a bad actor—it makes you human and resource-constrained like most organizations. What matters is how you respond: with documentation, vendor pressure, alternatives, honesty, workarounds, improvement timelines, and proactive communication.
Accessibility is a journey requiring ongoing effort, not a binary pass/fail destination. Organizations demonstrating good-faith effort to minimize barriers and provide alternatives are in a fundamentally different position than those ignoring accessibility entirely.
Keep pushing vendors for improvements. Keep evaluating alternatives. Keep listening to users. Keep documenting your efforts. That combination of persistence and transparency is what responsible accessibility looks like in real-world situations with real-world constraints.
