November 5, 2026
by Maryam Zulfiqar

Credit Union Website Accessibility: Complete 2026 Guide

Credit union website accessibility is the practice of making online banking, loan forms, calculators and documents usable by members with disabilities. This guide shows marketing, IT and compliance teams what WCAG 2.2 AA means in practice, where credit union sites commonly fail, and how to sequence fixes over 90 days. It is general information, not legal advice.

Why Credit Union Website Accessibility Draws ADA Demand Letters

Credit unions draw ADA demand letters because members rely on websites for essential services, and the Department of Justice has held since 1996 that the ADA applies to web content. Its guidance lists banks as businesses open to the public. Whether a specific credit union is covered is a legal question for counsel.

According to the DOJ web accessibility guidance, an inaccessible website can exclude people just as steps at an entrance can. The page names barriers such as poor color contrast, inaccessible online forms and mouse-only navigation. Credit unions are form-heavy by nature: logins, applications, calculators and statements all depend on those basics.

The same guidance says the Department has no regulation setting detailed web standards, and that businesses have flexibility in how they comply. They must still make online goods and services accessible. In practice, many teams adopt WCAG as the working yardstick, and our bank website ADA compliance guide covers the closest comparison.

This article does not cite specific lawsuits. For background on how website claims tend to arise, read our ADA website lawsuits explainer. Note that the DOJ page is dated March 18, 2022, and describes itself as informal guidance without the force of law.

Compliance manager reviewing credit union website accessibility findings at her desk

What WCAG 2.2 AA Means for Portals, Loans and Mobile

The W3C defines three conformance levels: A, AA and AAA. Level AA requires meeting all Level A and AA success criteria, and the W3C does not recommend requiring AAA as a general policy. Here is how AA maps to common credit union assets, per the official WCAG 2.2 specification.

  • Member portal login: 3.3.8 Accessible Authentication (Minimum) says a step cannot require a cognitive function test, such as remembering a password, unless an alternative or assisting mechanism exists. The W3C notes password manager support and copy and paste as examples. Under 2.2.1, session timeouts need a warning and at least 20 seconds to extend.
  • Loan applications: 3.3.2 requires labels or instructions, 3.3.1 requires text error descriptions, and 3.3.7 Redundant Entry says information already provided in the same process must be auto-populated or selectable. For financial transactions, 3.3.4 requires submissions to be reversible, checked or confirmed.
  • Calculators: 4.1.3 requires status messages, such as results, to be exposed to assistive technology without moving focus. 2.5.7 requires a non-dragging option for sliders, and 2.5.8 sets a 24 by 24 CSS pixel minimum target size, with exceptions.
  • PDFs: the W3C says success criteria are not technology-specific, so statements, rate sheets and forms still need text alternatives, structure and readable contrast.
  • Mobile: WCAG covers web content on mobile devices, including 1.3.4 Orientation and 1.4.10 Reflow at 320 CSS pixels. Native apps are outside the references used here, so ask your vendor for their own documentation and test with a screen reader.

The W3C’s How to Meet WCAG 2.2 quick reference lets your developers filter criteria by level and technology.

If your team is still on WCAG 2.1, our post on WCAG 2.2 updates for website owners explains what changed.

Common Failures on Credit Union Sites

These patterns match barriers named in the DOJ guidance and WCAG 2.2 success criteria:

  • Light gray text on white, below the 4.5:1 contrast ratio in 1.4.3.
  • Required fields marked by red color alone, which the DOJ guidance flags.
  • Form fields without labels, or errors that screen readers never announce.
  • Menus and pop-ups that cannot be used with a keyboard, or that trap focus (2.1.2).
  • Login pages that block password managers or paste, against the intent of 3.3.8.
  • Chat widgets or cookie banners that hide the focused element (2.4.11).
  • Calculator results that change silently, with no status message.
  • Videos without captions, and scanned PDFs that are only images of text.
Blind tester using a screen reader and keyboard to test an online loan form

A 30-60-90 Day Remediation Plan

Treat credit union website accessibility as a program with owners and dates, not a one-off project. This sequence is a practical suggestion, not a legal requirement or a guaranteed timeline.

Days 1 to 30: find and triage

List your key member journeys: login, loan application, payments, calculators, contact and top PDFs. Run an automated scan, then test each journey by hand with a keyboard and a screen reader. The DOJ guidance warns that a clean automated report does not necessarily mean everything is accessible, so manual checks are essential.

Days 31 to 60: fix the highest-risk paths

Fix blockers first: unlabeled fields, keyboard traps, missing error messages, contrast and timeouts. Tools such as Accessify, an AI-powered widget with automated remediation, can help with many common issues on content you control. Complex portals still need fixes in code and by your vendors.

Days 61 to 90: verify and govern

Retest every fixed journey, publish a way for members to report accessibility problems (a practice the DOJ guidance recommends), and add accessibility checks to your release and procurement process. Record what you tested and when.

Examples: Community and Regional Credit Unions

Small community credit union (illustrative scenario). One webmaster manages a WordPress marketing site, while online banking comes from a vendor. The 90-day focus is the ten most-visited pages, rate and fee PDFs, and the forms on the marketing site. The team also asks the banking provider for accessibility documentation and tests login by keyboard.

Larger regional credit union (illustrative scenario). Separate teams own the public site, mortgage portal, card services and a mobile app. A central owner sets WCAG 2.2 AA as the target, adds accessibility language to procurement, and schedules recurring manual tests of every journey. Each vendor product gets its own tracked remediation list.

Credit union IT, marketing and compliance team planning a 90-day accessibility remediation roadmap

Working With Core and Online Banking Vendors

The W3C says conformance applies to full pages, and when pages form a process, such as a multi-step loan application, every page in it must conform. A single inaccessible vendor step can therefore break the whole journey. Ask each provider for:

  • A conformance statement naming the WCAG version, level, pages covered and technologies relied upon, which are the elements the W3C lists for a conformance claim.
  • A dated list of known issues and a fix schedule.
  • A contact route for reporting barriers.
  • Clarity on third-party content they do not control, which the W3C addresses through statements of partial conformance.

Put these asks into contracts and renewals, and verify claims with your own testing.

How Accessify and Other Vendors Compare

The reference sources do not document financial-sector features for any vendor, so this list covers only what they support. Verify details on each vendor’s own pages, and check the vendor’s site for current pricing.

  • Accessify: AI-powered widget with automated remediation, a 2-minute install on Shopify, WordPress and other platforms, and plans from $19/month. It suits small and mid-size sites needing fast fixes, and complex portals still need manual testing.
  • UserWay: [INSERT: one verified strength from UserWay’s public page]
  • accessiBe: [INSERT: one verified strength from accessiBe’s public page]
  • AudioEye: [INSERT: one verified strength from AudioEye’s public page]
  • Level Access: staff are listed among participants in the W3C Accessibility Guidelines Working Group in the WCAG 2.2 acknowledgements, showing involvement in the standard itself.

A larger regional credit union with complex portals should weigh a manual audit or managed service alongside any widget.

Credit Union Accessibility Checklist

Use this list to keep credit union website accessibility work on track:

  • Name an owner and set WCAG 2.2 AA as the target.
  • List key journeys and PDFs.
  • Test each journey with keyboard and screen reader.
  • Fix labels, errors, contrast, focus and timeouts first.
  • Check login against 3.3.8 and loan forms against 3.3.7.
  • Request conformance documentation from vendors.
  • Publish a way to report barriers.
  • Retest after every release.

Frequently Asked Questions

What does WCAG 2.2 AA mean for a credit union?

It means your pages meet every Level A and Level AA success criterion in the W3C standard, including newer ones such as Accessible Authentication (Minimum) and Target Size (Minimum). The W3C says conformance applies to full pages, and every page in a multi-step process, such as a loan application, must conform.

How long does it take to make a credit union site accessible?

It depends on site size, how many vendor products you use and how many issues testing finds, so no honest fixed timeline exists. A 30-60-90 day plan gives you a sequence: audit and triage first, fix key journeys next, then verify and document. Larger portals may continue beyond 90 days.

Is an accessibility widget enough for a credit union?

No. A widget and automated remediation can help with many common issues, but the DOJ guidance says a clean automated report does not necessarily mean a site is accessible, and it recommends pairing automated checkers with manual checks. Complex portals and forms also need assistive technology testing and code-level fixes.

Do credit unions have to follow the ADA online?

The DOJ’s guidance says the ADA applies to the web content of businesses open to the public and lists banks as an example. Whether a particular credit union falls under Title III is a legal question, so ask qualified counsel. This article is general information, not legal advice.

What should a credit union fix first?

Start with the journeys members depend on most: login, loan application, payments and contact. Test each with only a keyboard and a screen reader, then fix blockers first, such as unlabeled fields, keyboard traps and missing error messages. Move to marketing pages, PDFs and calculators afterward.

What changed in WCAG 2.2 compared with WCAG 2.1?

WCAG 2.2 adds new success criteria at Level A and AA, including Focus Not Obscured (Minimum), Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry and Accessible Authentication (Minimum), and removes 4.1.1 Parsing. The W3C says content that conforms to 2.2 also conforms to 2.1 and 2.0.

Ready to start? Accessify installs in 2 minutes on Shopify, WordPress and other platforms and adds automated remediation alongside the manual testing described above.

Related Articles