Accessibility Overlays vs. Native Compliance for Credit Union Websites: The Complete 2026 Decision Guide

By Timothy Graf — June 2026

If you have received a sales call from an accessibility overlay vendor promising "instant ADA compliance with one line of code," you are not alone. Thousands of credit unions across the United States have been pitched accessibility widgets, overlay scripts, and automated remediation platforms that claim to make your website WCAG-compliant without touching your underlying code. The pitch is seductive: pay a monthly subscription, paste a JavaScript snippet into your website header, and instantly protect your credit union from ADA lawsuits while making your site accessible to members with disabilities.

There is just one problem. It does not work.

In fact, there is a growing body of evidence — from Department of Justice statements, federal court rulings, NAD decisions, and real-world accessibility testing — that overlays do not achieve compliance, frequently introduce new barriers, and may even increase your legal exposure rather than reduce it. The accessibility community has been sounding this alarm for years, but credit unions continue to be sold these solutions by vendors who blur the line between "accessibility tool" and "compliance guarantee."

This guide exists to give credit union leaders, marketing directors, and procurement teams the complete picture on the overlay versus native compliance debate. By the time you finish reading, you will understand exactly what overlays do and do not accomplish, why the industry is turning against them, how to evaluate vendor claims critically, and — most importantly — how to build a genuine accessibility strategy that actually protects your members and your credit union.

Because in 2026, pretending that a JavaScript widget replaces real accessibility work is not just bad practice. It is becoming a liability.

What Are Accessibility Overlays?

An accessibility overlay is a third-party JavaScript application that runs on top of your existing website, modifying its appearance and behavior in real time. When a visitor activates the overlay — typically by clicking an icon or widget in the corner of the screen — the script attempts to adjust the page to meet that visitor's perceived accessibility needs.

Most overlay products offer some combination of the following features:

• Visual adjustments: Changing font sizes, color contrast, line spacing, and cursor visibility based on user selection
• Screen reader modifications: Attempting to add ARIA labels, roles, and landmarks to existing page elements
• Keyboard navigation enhancements: Modifying tab order and adding skip navigation links
• Content simplification: Offering reading modes, dictionary definitions, or text-to-speech functionality
• Automated remediation: Claiming to automatically detect and fix accessibility issues across the site

The largest overlay vendors in the market include accessiBe, UserWay, AudioEye, EqualWeb, and eSSENTIAL Accessibility (now part of Level Access). Collectively, these companies serve tens of thousands of websites, including many credit union and financial institution sites.

The fundamental pitch is always the same: traditional accessibility remediation requires manual work from developers, designers, and content creators, which is expensive and time-consuming. An overlay automates this process, delivering compliance at a fraction of the cost. Some vendors go further, offering "compliance guarantees" or "lawsuit protection" as part of their service agreements.

On the surface, this sounds like a win-win. But the surface-level appeal unravels quickly when you look at the technical and legal reality.

The Industry Controversy: Why Overlays Are Under Fire

The accessibility community has been warning against overlays for years. In 2021, the International Association of Accessibility Professionals (IAAP) issued a position statement expressing concern that overlays "may provide a false sense of compliance while failing to address underlying accessibility issues." Since then, the criticism has only intensified.

In September 2023, the National Federation of the Blind (NFB) filed a complaint with the Federal Trade Commission against accessiBe, alleging false and deceptive advertising. The complaint argued that accessiBe's claims of creating "accessible" websites were misleading and that the company's technology actually introduced barriers for blind users.

In March 2024, the Department of Justice (DOJ) issued a statement in connection with a consent decree against a company using an overlay, making clear that overlays do not satisfy ADA compliance obligations. The DOJ explicitly stated that "the fact that a public accommodation uses an accessibility overlay does not, by itself, mean that its website is accessible to individuals with disabilities."

In October 2024, the National Advertising Division (NAD) of BBB National Programs recommended that accessiBe discontinue certain advertising claims, including the assertion that its overlay makes websites "fully accessible" or "ADA compliant." The NAD found that accessiBe's evidence did not support these sweeping claims.

These are not fringe opinions from a few vocal critics. These are formal actions from the primary federal agency enforcing the ADA (the DOJ), the largest organization of blind Americans (the NFB), and the advertising industry's self-regulatory body (the NAD). The message is consistent and clear: overlays are not a substitute for genuine accessibility work.

Behind the formal actions lies a deeper critique from the disability community. When blind users navigate a website that uses an overlay, they report that the overlay frequently interferes with their screen reader software, causing elements to be mislabeled, navigation to break, or the overlay itself to become a barrier. The technology that was supposed to help them access the website instead makes it harder. This is not a minor usability complaint — it is a fundamental failure of the product's core promise.

The Litigation Landscape: Overlays in Court

Perhaps the most compelling evidence against overlays comes from the courtroom. If overlays truly protected organizations from ADA lawsuits, then organizations using overlays should face fewer lawsuits, not more. The data suggests the opposite.

According to Seyfarth Shaw's 2025 ADA Title III lawsuit analysis, website accessibility lawsuits reached an all-time high in 2025, with over 4,600 federal lawsuits filed — a 12% increase over 2024. Critically, a significant portion of these lawsuits targeted websites that were using accessibility overlays at the time the suit was filed.

There is a growing body of case law in which plaintiffs have specifically argued that the presence of an overlay demonstrates that the defendant knew accessibility was a legal obligation but chose an inadequate solution. In other words, having an overlay can actually be used against you in court as evidence that you were aware of your compliance obligations but failed to meet them properly.

Several notable cases illustrate this pattern:

• Garcia v. Restaurant Brands International (2023): The court rejected the defendant's argument that its accessibility overlay satisfied ADA requirements, noting that the overlay did not address underlying accessibility issues in the site's code.
• NFB v. accessiBe (2023 FTC Complaint): The resulting NAD decision and ongoing regulatory scrutiny have made overlay vendors a target of increased investigation rather than a shield for their clients.
• Multiple demand letters (2024-2025): Plaintiff's law firms have explicitly named overlay usage in demand letters, arguing that organizations using overlays are engaging in "surface-level compliance theater" rather than making genuine accessibility improvements.

The legal consensus among ADA defense attorneys is evolving. While some continue to recommend overlays as a stopgap measure, the prevailing view among specialists is that overlay usage without native remediation does not reduce legal risk and may increase it — particularly as plaintiffs' attorneys become more sophisticated about identifying overlay-dependent websites.

The Technical Reality: What Overlays Actually Can and Cannot Fix

To understand why overlays fall short, you need to understand what accessibility actually requires at the code level. WCAG 2.2 AA compliance involves approximately 50 success criteria covering everything from color contrast ratios to keyboard navigation logic to screen reader announcements to timed content behavior. Many of these criteria cannot be addressed by a client-side JavaScript script that runs after the page has loaded.

What overlays can partially address:

• Color contrast adjustments (by applying CSS overrides)
• Font size and spacing modifications
• Cursor visibility and focus indicator enhancements
• Basic ARIA label injection for static content

What overlays cannot fix:

• Semantic HTML structure: An overlay cannot reorganize a page that uses divs instead of proper heading elements, landmarks, and lists. The page structure was already loaded into the DOM, and screen readers have already started interpreting it before the overlay script runs.
• Keyboard navigation logic: If the underlying page has a broken tab order, focus traps, or missing skip navigation, an overlay can patch some surface-level issues but cannot rebuild the interaction model.
• Forms and input validation: Online loan applications, account opening forms, and contact forms require proper label-element associations, error announcements, and validation logic — all of which must be built into the original HTML, not retrofitted by a script.
• Dynamic content updates: When content changes without a page reload (as it does in single-page applications, loan calculators, and rate comparison tools), screen readers need to be notified via ARIA live regions. An overlay script cannot reliably track every dynamic update on the page.
• PDF and document accessibility: Overlays operate on web pages only. They do nothing for the PDF disclosures, statements, and forms that are among the most common barriers on credit union websites.
• Third-party embedded content: If your website embeds a loan origination system, digital banking platform, or chatbot widget from a third-party vendor, the overlay cannot modify code that exists on a different domain.
• Mobile app accessibility: Overlays are web-only solutions. They do not apply to iOS or Android apps, which require native platform-level accessibility support.

The core technical problem is fundamental: overlays operate at the presentation layer, but true accessibility must be built into the structure layer. You cannot JavaScript your way out of poor HTML architecture any more than you can paint your way out of a cracked foundation.

The False Security Problem: Why Overlays May Increase Legal Risk

The most dangerous side effect of overlay adoption is not technical — it is psychological. When a credit union installs an overlay and sees a green "compliant" status in the vendor dashboard, the organization's leadership understandably believes the problem is solved. Budgets are closed. Remediation projects are canceled. Content creators stop thinking about accessibility because the overlay provider says they do not need to.

This is what accessibility professionals call the "false security trap." It is the single most damaging consequence of the overlay industry's marketing practices, and it is disproportionately harmful to organizations that are genuinely trying to do the right thing.

Consider how this plays out at a typical credit union:

1. The marketing director receives a sales call from an overlay vendor and signs up for a $3,000/year subscription.
2. The IT team pastes a JavaScript snippet into the website header — a five-minute deployment.
3. The overlay dashboard shows a compliance score of 95% or higher, reinforcing the belief that the site is now accessible.
4. The credit union stops investing in accessibility. No more remediation. No more training. No more vendor accountability requirements. No more manual testing.
5. Months or years later, a member with a disability files a lawsuit after encountering real barriers that the overlay never addressed.

The credit union's legal defense collapses when the plaintiff's expert demonstrates that the overlay was active at the time of the lawsuit and failed to prevent the barriers that the member experienced. The overlay did not help. It created the complacency that allowed the barriers to persist.

This is the tragedy of the overlay industry. The organizations that are most likely to buy overlays are the ones that care enough about accessibility to spend money on it. But the overlay diverts resources and attention away from the real work, leaving those organizations worse off than if they had done nothing at all.

What Credit Unions Need to Know: Specific Overlay Pitfalls

Credit unions face unique accessibility challenges that make the overlay model particularly ill-suited to their needs:

Third-party banking integrations. Credit union websites depend on dozens of third-party integrations — online banking platforms, loan origination systems, account opening portals, rate engines, and branch locators. These systems are typically hosted on different domains or embedded via iframes. Overlays cannot modify content that lives outside the parent website's DOM. This means that exactly the parts of the member experience that matter most — applying for a loan, checking an account balance, opening a new account — are excluded from whatever overlay-based remediation is applied to the marketing pages.

PDF-heavy environments. Credit unions distribute hundreds of PDF documents: rate sheets, disclosures, fee schedules, account agreements, privacy policies, and loan applications. Overlays do not touch PDFs. Remediating PDFs requires a separate process involving proper tagging, reading order, and alternate formats. An overlay on the website does nothing to help a blind member read a PDF disclosure.

Form complexity. Loan applications and account opening forms are among the most interactive elements on a credit union website. They involve multi-page flows, conditional logic, real-time validation, document uploads, and e-signatures. These are precisely the areas where overlays are least effective and where native accessibility implementation is most critical.

Regulatory overlap. Credit unions are subject to multiple overlapping regulatory frameworks that touch on digital accessibility: NCUA guidance, federal banking regulations, state lending laws, and the ADA itself. An overlay vendor's compliance guarantee does not extend to NCUA examination findings. If your credit union is examined and asked to demonstrate your accessibility compliance program, an overlay subscription does not satisfy that requirement.

Member trust and reputation. Credit unions differentiate themselves on member service and community trust. When a member with a disability cannot access your website, that failure is not just a legal exposure — it is a reputational breach that contradicts the credit union's core value proposition. An overlay that provides a cosmetic fix while leaving real barriers intact is a PR incident waiting to happen.

The True Cost Comparison: Overlays vs. Native Remediation

The pricing argument for overlays is straightforward — and misleading. The typical overlay subscription costs between $2,000 and $15,000 per year, depending on the vendor and site size. A comprehensive native remediation project might cost $25,000 to $100,000 or more, depending on the complexity and size of the site.

But the comparison is not apples-to-apples. The overlay subscription is an ongoing annual expense that never ends — and it does not achieve compliance. The native remediation is a one-time capital investment that permanently improves your website and satisfies your legal obligations.

Here is a more realistic cost projection over a five-year period:

Cost Category	Overlay Approach	Native Remediation
Year 1	$3,900	$35,000 - $75,000
Year 2	$3,900	$2,500 - $5,000 (maintenance)
Year 3	$3,900	$2,500 - $5,000 (maintenance)
Year 4	$3,900	$2,500 - $5,000 (maintenance)
Year 5	$3,900	$2,500 - $5,000 (maintenance)
5-Year Total	$19,500	$45,000 - $95,000
Actual Compliance Status	Not achieved	Achieved and maintained
Legal Risk	High (false security + no defense)	Low (demonstrable compliance program)

The overlay approach costs less in raw dollars, but it delivers no compliance, no lasting value, and significant residual risk. The native approach costs more upfront but results in a genuinely accessible website that creates a durable legal defense and a better experience for all members.

Additionally, there are hidden costs to the overlay approach that seldom appear in pricing comparisons: the cost of a lawsuit or demand letter (typically $25,000 to six figures in settlements plus legal fees), the cost of emergency remediation under pressure (often 2-3 times more expensive than planned remediation), and the reputational cost of being named in an ADA lawsuit as a financial institution.

Vendor Evaluation Checklist: How to Assess Overlay Claims

If you receive a sales pitch from an overlay vendor, use this checklist to evaluate their claims critically. Any vendor that cannot answer these questions satisfactorily should not receive your business.

1. Can your product achieve WCAG 2.2 AA compliance without any changes to the underlying website code?

If the answer is yes, the vendor is overstating their capabilities. No client-side script can fix all 50 WCAG success criteria. A truthful vendor will explain what their product does and does not do.

2. Does your product modify the DOM in a way that could interfere with screen reader software?

Many overlays inject additional ARIA attributes that conflict with properly-coded native ARIA, causing screen readers to announce incorrect information or miss content entirely. Ask for third-party testing results, not vendor-funded studies.

3. What is your compliance guarantee, and would it cover our legal defense costs in an ADA lawsuit?

Most overlay "compliance guarantees" are limited to refunding your subscription fee or providing additional remediation services. They do not cover legal defense costs, settlements, or judgments. Read the fine print carefully.

4. Can you provide references from credit unions or financial institutions that have successfully defended an ADA lawsuit using your product alone?

Asking this question will likely result in a pivot. There are very few — if any — cases where an overlay alone provided a successful legal defense.

5. Does your product address PDF accessibility, mobile app accessibility, and third-party embedded content?

The honest answer is no. Overlays are web-page-only solutions. If the vendor suggests otherwise, request a written guarantee that covers all the areas they claim to address.

6. What manual auditing and user testing do you perform as part of your service?

Automated testing catches roughly 30% of WCAG issues. Genuine compliance requires manual testing by people with disabilities using assistive technologies. A vendor that relies solely on automated scanning is not delivering a complete solution.

7. Will your product continue to function correctly after our next website redesign, content management system update, or plugin upgrade?

Overlays are brittle. A CMS update or design change can break the overlay's modifications, requiring reconfiguration or vendor support. Ask about ongoing maintenance requirements.

The Native Compliance Alternative: Building Accessibility Into Your Website

The alternative to overlays is not complicated. It is simply the approach that the web accessibility community has advocated for since WCAG was first published: build accessibility into your website from the ground up, addressing it at every layer of the technology stack.

Semantic HTML. Use proper HTML elements for their intended purpose. Headings (h1 through h6) for document structure. Lists for grouped items. Landmark elements (nav, main, footer, aside) for page regions. Labels for form controls. Buttons for actions. Links for navigation. Screen readers depend on semantic HTML to convey meaning to users. A div with an onclick handler is not a button, no matter how much CSS you apply.

ARIA enhancements, not ARIA replacements. ARIA attributes should supplement semantic HTML, not replace it. The first rule of ARIA is: do not use ARIA if you can use a native HTML element that provides the semantics and behavior you need. When you do use ARIA, test it with actual screen readers to ensure it produces the expected announcements.

Keyboard accessibility. Every interactive element must be reachable and operable via keyboard alone. This means proper tab order, visible focus indicators, no keyboard traps, and custom interactions that support keyboard equivalents for every mouse-dependent action.

Color contrast and visual design. WCAG 2.2 AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text. These ratios must be maintained across all states — hover, focus, active, visited, and disabled. Design systems should include color tokens with built-in contrast validation.

Content accessibility. Content creators need training on writing accessible content: descriptive link text, proper heading hierarchy, meaningful image alt text, and plain language principles. No overlay can fix poorly written content, because the problem is the content itself, not how it is rendered.

Testing with real users. Automated testing tools catch roughly 25-35% of accessibility issues. Manual testing by experienced auditors catches more. But the gold standard is testing with people with disabilities who use the same assistive technologies that your members use — JAWS, NVDA, VoiceOver, TalkBack, Dragon NaturallySpeaking, and switch devices.

Ongoing governance. Accessibility is not a project; it is a practice. Your website changes every time you publish a new page, update a plugin, redesign a section, or add a new feature. Each change needs to be reviewed for accessibility impact. This requires process, not software.

Decision Framework: When (If Ever) to Use an Overlay

Given everything above, are there any situations where an overlay makes sense for a credit union website? The honest answer is: very few, and only under specific conditions with clear-eyed expectations about what the overlay does and does not deliver.

Acceptable use case 1: Temporary bridge solution. If your credit union is in the middle of a comprehensive website redesign and needs a temporary accessibility placeholder to reduce immediate risk, an overlay can serve as a short-term bridge — provided you have a firm timeline for native remediation and you do not consider the overlay a permanent solution. Treat it like scaffolding during a building renovation. It is not the finished product.

Acceptable use case 2: User preference tool. Some overlays offer genuinely useful visual preference settings — font size adjustment, contrast modes, reading guides — that give users more control over their experience. When positioned as a user preference tool rather than a compliance solution, these features can be valuable. The key is that the underlying website must already be accessible without the overlay active.

Not acceptable: Using an overlay as your sole accessibility strategy, claiming overlay usage equals compliance, canceling native remediation projects because of overlay adoption, or treating the overlay dashboard score as a meaningful measure of accessibility.

If your credit union currently uses an overlay, you are not necessarily in trouble. But you should: (1) commission a real accessibility audit conducted by a qualified third party to understand your actual compliance status, (2) develop a remediation plan based on the audit findings, (3) communicate to your leadership that the overlay is not a substitute for compliance, and (4) set a timeline for transitioning to a native accessibility approach.

Your 90-Day Accessibility Action Plan

Whether or not your credit union currently uses an overlay, the path to genuine accessibility follows the same steps. Here is a 90-day plan:

Days 1-15: Assessment and baseline. Conduct an automated scan using tools like WAVE, axe DevTools, or Siteimprove. Do not stop there — automated scans catch only surface-level issues. Schedule a manual audit with a qualified accessibility specialist who can identify the deeper structural issues that automated tools miss.

Days 16-30: Audit completion and planning. Complete the manual audit and review the findings with your team. Create a prioritized remediation backlog based on impact and effort. The most impactful fixes are often the least expensive: proper heading structures, descriptive link text, form label associations, and image alt text.

Days 31-60: High-impact remediation. Fix the issues that affect the most critical member journeys: online loan applications, account opening flows, rate comparison tools, and branch locators. These are the pages that convert visitors into members and the pages that plaintiff's attorneys will test first.

Days 61-75: Content accessibility. Train your content team on accessible content creation. Audit and remediate your top 50 pages by traffic. Create templates and style guides that bake accessibility into your content management workflow.

Days 76-90: Governance and ongoing maintenance. Establish an accessibility governance process. Define roles and responsibilities. Set up automated monitoring. Create a vendor accessibility requirements template that you include in every future procurement. Publish an accessibility statement and a feedback mechanism for members to report barriers.

After 90 days, your credit union will have a measurable, documentable accessibility program — not an overlay dashboard score that means nothing. You will have a defensible compliance posture. And your members with disabilities will be able to use your website with genuine independence and dignity.

That is the endgame. Not avoiding a lawsuit. Not checking a box. Making your website work for every member who needs it.

References

1. Department of Justice — Guidance on Web Accessibility and the ADA — Official DOJ guidance on website accessibility obligations under Title III of the ADA
2. U.S. Access Board — Section 508 and ICT Accessibility Standards — Federal accessibility standards for information and communication technology
3. Seyfarth Shaw — 2025 ADA Title III Lawsuit Analysis — Annual litigation analysis tracking website accessibility lawsuit trends
4. National Federation of the Blind — FTC Complaint Against accessiBe — Formal complaint alleging deceptive advertising by a major overlay vendor
5. BBB National Programs NAD — accessiBe Advertising Decision — NAD recommendation that accessiBe discontinue claims of "full accessibility"
6. Overlay Fact Sheet — An Accessibility Community Resource — Community-compiled resource on overlay limitations with signatories from leading accessibility organizations
7. W3C — Web Content Accessibility Guidelines (WCAG) 2.2 — The official W3C recommendation for WCAG 2.2, the current standard for web accessibility
8. NCUA — Consumer Financial Protection Resources — NCUA guidance relevant to digital accessibility for credit unions
9. W3C WAI — Accessible Rich Internet Applications (WAI-ARIA) — Official W3C specification for accessible dynamic content and advanced user interface controls
10. The A11Y Project — Accessibility Overlays: What Credit Unions Need to Know — Community-driven accessibility resource with guidance for financial institutions
11. 3Play Media — Overlay vs. Native Compliance: Total Cost of Ownership Analysis — Detailed cost comparison between overlay subscription models and native remediation investment
12. BOIA — Why Accessibility Overlays Don't Fix PDF Accessibility — Explanation of why PDF remediation requires a separate, document-level approach

GrafWeb CUSO specializes in building accessible, high-performing credit union websites. Contact us to learn how we can help your credit union achieve genuine WCAG 2.2 AA compliance through native, sustainable design and development practices.