ADA Title III website complaints against community banks and credit unions have settled into a recognizable pattern. This post is descriptive, not legal advice — work with FI compliance counsel for specifics — but the technical patterns and regulatory context are public record.

The complaint pattern in 2026

A serial-plaintiff firm runs an automated WCAG scan against community FI websites (often via the FDIC institution directory or NCUA credit-union list), filters to institutions in friendly jurisdictions, sends demand letters. The cited issues are nearly always the same: color contrast on rate tables, unlabeled form fields on loan-application landing pages, focus-indicator failures on navigation, missing alt text on hero imagery, inaccessible disclosure PDFs.

Settlement amounts cluster in the low five figures plus remediation. The plaintiff firms running these are sophisticated about the FI niche — they know the procurement cycle, the examiner pressure, and the reputational sensitivity, and price the demand accordingly.

What regulators are watching

Beyond the lawsuit dimension, three regulatory signals matter:

  1. OCC has issued guidance on digital access for federally chartered institutions, with explicit reference to WCAG conformance for public websites.
  2. CFPB has signaled increased attention to digital experience as a fair-access concern, especially for credit applications.
  3. State financial regulators vary widely; some (NY DFS, Massachusetts Division of Banks) have explicit digital-accessibility expectations in examination guides.

Examiners increasingly ask "show us your accessibility monitoring program." A documented continuous-scanning program with audit logs is the artifact they want to see.

Why credit unions specifically face exposure

Credit unions have three structural factors that compound:

  1. Visibility through league directories. Credit Union Leagues publish member directories that serial-plaintiff scanners harvest.
  2. Limited marketing budgets. Most credit unions don't have a dedicated accessibility specialist; the marketing function manages the website with limited compliance oversight.
  3. Compliance posture. Credit unions are accustomed to compliance work and tend to settle quickly rather than litigate, which makes them attractive targets.

The same factors that make CUs attractive to serial plaintiffs also make documented monitoring programs especially valuable: the upside in settlement posture is significant relative to the program cost.

What community banks face

Community banks face the same lawsuit pattern with somewhat different examiner pressure. State-chartered banks face state regulator attention; nationally chartered banks face OCC attention; both face FDIC examination on consumer-facing risk. Banks with multiple charters face all of the above.

The difference from credit unions: community banks are more likely to have agency-of-record handling the website, which means the monitoring program needs to either live with the agency or include the agency in the workflow.

What's typically cited in demand letters

The pattern is consistent across complaints we've seen referenced in public filings:

  • Color contrast on rate tables, calls-to-action, and disclosure text. The thin-gray-on-white pattern many banking sites use for "fine print" reliably fails 4.5:1.
  • Unlabeled form fields on loan-application landing pages and contact forms.
  • Focus indicator removed in custom CSS (outline: none) without replacement.
  • Inaccessible PDFs — disclosure documents, rate sheets, application forms.
  • Inaccessible third-party widgets — branch locators, mortgage calculators, online appointment booking.
  • Missing alt text on imagery.

Most of these are mechanically detectable and are what an automated scanning program would surface continuously.

The minimum reasonable program for an FI

Three components, in order:

  1. Continuous automated scanning of the public site (homepage, branch locator, loan applications, rate disclosures, calculators) with weekly review.
  2. Annual or biannual manual audit by an accessibility specialist. Catches what scanning can't.
  3. Documented remediation workflow — when an issue is found, who fixes it, on what timeline, where it gets logged.

SEO Score API's financial services vertical is built specifically for component 1. Audit logs are timestamped and exportable in formats examiners expect.

What does an examiner actually want to see?

When an examiner asks about your accessibility program, they typically want:

  • Policy document: a written accessibility policy stating your standard (WCAG 2.1 AA), your monitoring cadence, your remediation timelines.
  • Monitoring evidence: scan reports, audit logs, the actual artifacts of the program.
  • Remediation log: what was found, what was fixed, when.
  • Manual audit records: copies of any specialist audits.

The policy is the easy part. Most FIs lack the monitoring evidence and remediation log because they don't have continuous scanning in place.

Is overlay technology a defense?

No. Overlay widgets (accessiBe, UserWay, AudioEye) have themselves been the subject of ADA litigation, and several courts have held that an overlay does not satisfy ADA Title III. Plaintiff firms now routinely cite overlay presence in complaints rather than treating them as protective.

The defensible posture is genuine remediation — accessible code, accessible content, documented monitoring — not an overlay layer.

What about agency-of-record relationships?

Many community banks and credit unions outsource website management to a digital agency. The bank is still legally responsible for ADA compliance regardless of who built or hosts the site. The right pattern: the bank (or credit union) owns the monitoring program and the audit log; the agency is responsible for remediation. Make the responsibilities explicit in the agency contract.

How do batch scans help multi-branch FIs?

A 25-branch institution often has 25 near-identical branch microsites. Issues at the template level replicate everywhere. Batch scanning all 25 in one pass surfaces template-level vs. location-specific issues separately, so you fix each pattern once. Our /audit/batch endpoint supports this directly.

What's the realistic budget?

A tiered estimate:

  • Basic continuous monitoring: $15–$99/month with our service depending on scan volume.
  • Annual manual audit: $5,000–$25,000 for a typical community FI site.
  • Remediation labor: highly variable. Budget for 40–80 hours of dev work in the first remediation pass for a typical 50-page bank site, then 10–20 hours per quarter for ongoing fixes.

The total program cost is meaningfully less than a single demand letter settlement.

Run a free scan of your institution's homepage → — start the audit log today.