The Complete Credit Union Website ADA Compliance and WCAG 2.2 Accessibility Playbook: A Strategic Guide to Digital Accessibility Audits, Remediation Prioritization, and Ongoing Compliance for Credit Union Websites in 2026-2027

Introduction: The Accessibility Imperative for Credit Unions

In October 2026, digital accessibility is no longer a compliance checkbox for credit unions. It is a fundamental member experience requirement, a significant legal liability, and a powerful competitive differentiator. The number of ADA Title III website accessibility lawsuits filed against financial institutions has risen dramatically over the past five years, and credit unions are increasingly named in demand letters and federal complaints alleging that their digital banking platforms, websites, and mobile applications discriminate against individuals with disabilities.

The stakes could not be higher. Credit union websites serve as the primary point of digital engagement for millions of members. From checking account balances and viewing statements to applying for loans and opening new accounts, virtually every member interaction now begins online. When these digital touchpoints are inaccessible to individuals who are blind, low-vision, deaf, hard of hearing, or have motor or cognitive disabilities, credit unions are not only violating federal law but also excluding a significant and growing member demographic.

According to the World Health Organization and the CDC, an estimated 1 in 4 American adults has some form of disability. This represents approximately 61 million Americans, with an estimated aggregate disposable income of over $490 billion annually, a figure that the American Institutes for Research projects will continue to grow as the population ages. For credit unions, this is not just a compliance obligation but a substantial market opportunity. Credit unions that prioritize accessibility unlock a loyal, underserved member segment while simultaneously reducing legal risk and improving the digital experience for all members through universal design principles.

The Web Content Accessibility Guidelines (WCAG) version 2.2, published as a W3C Recommendation in October 2023, represents the current international standard for digital accessibility. WCAG 2.2 added nine new success criteria while building on the WCAG 2.1 framework. For credit unions that already achieved or were working toward WCAG 2.1 Level AA compliance, the transition to WCAG 2.2 introduces new requirements for accessible authentication, focus visibility, consistent help mechanisms, and draggable motion controls. For credit unions that have not yet begun their accessibility journey, the gap is wider than ever.

This comprehensive playbook provides credit unions of all sizes with a strategic framework for achieving and maintaining WCAG 2.2 Level AA compliance. We cover the legal landscape, audit methodology, remediation prioritization, VPAT creation, accessibility statement compliance, vendor management, staff training, and ongoing governance. Whether your credit union has $50 million or $5 billion in assets, the principles and frameworks described here are designed to be scalable, actionable, and measurable.

The Legal Landscape: ADA Website Lawsuits and Credit Unions

Understanding the legal environment is the essential starting point for any credit union accessibility initiative. Since 2017, when the Department of Justice under the Trump administration withdrew its Advance Notice of Proposed Rulemaking on website accessibility under Title III of the ADA, plaintiffs have aggressively pursued litigation under the theory that websites are places of public accommodation. The courts have been divided on this question, but the majority of federal circuit courts that have addressed the issue have sided with plaintiffs, finding that the ADA applies to websites and mobile applications.

The legal activity has been relentless. Seyfarth Shaw, a law firm that closely tracks ADA Title III litigation, reported that plaintiffs filed over 4,600 website accessibility lawsuits in 2024 alone, with numbers continuing to climb in 2025 and 2026. Financial services websites, including credit union and bank websites, are among the most frequently targeted industries, alongside retail, hospitality, and healthcare. The plaintiffs' bar has developed sophisticated web-crawling technology that systematically scans financial services websites for WCAG violations, generates automated demand letters, and files lawsuits in plaintiff-friendly jurisdictions, particularly New York, California, and Florida.

For credit unions, the legal exposure is compounded by several factors. First, the ADA provides for injunctive relief and attorneys' fees but does not cap damages, leaving credit unions exposed to potentially significant litigation costs even in cases that settle. Second, credit unions are considered public accommodations under Title III, and courts have consistently held that insurance offices, banks, and similar service establishments are covered entities. Third, the plaintiff's bar has become increasingly sophisticated about identifying credit union websites with high-impact violations such as missing alt text on loan application buttons, inaccessible PDF statements, and forms that cannot be completed with a keyboard alone.

The Americans with Disabilities Act is not the only legal framework governing digital accessibility for credit unions. Section 504 of the Rehabilitation Act of 1973 applies to credit unions that receive federal financial assistance. Section 508 of the same act establishes accessibility requirements for federal electronic and information technology, and while it primarily governs federal agencies, its standards have become a de facto benchmark for private-sector accessibility audits. Additionally, several states, including California, New York, and Texas, have their own accessibility laws that may impose obligations beyond the federal ADA. The California Unruh Civil Rights Act, for example, provides for statutory damages of $4,000 per violation, creating an even more aggressive plaintiff incentive in that state.

The Department of Justice has not issued formal website accessibility regulations under the ADA, although it has consistently taken the position that the ADA applies to websites and has entered into numerous consent decrees with public accommodations requiring WCAG 2.0 Level AA compliance. In the absence of formal regulations, the DOJ's consent decrees and the courts' reliance on WCAG as the applicable standard have effectively made WCAG 2.2 Level AA the de facto legal benchmark for credit union website accessibility compliance.

The cost of non-compliance can be substantial. Settlements in credit union website accessibility cases typically range from $10,000 to $100,000, with higher figures when the case involves named plaintiffs with significant harm or multi-year non-compliance. Attorneys' fees add to the expense, and the reputational damage to a credit union's brand when it is publicly named in an accessibility lawsuit can be severe. A Farleigh Dickinson University study found that 83% of consumers prefer to do business with companies that demonstrate a commitment to accessibility, and nearly half said they would stop doing business with a company that was sued for accessibility violations.

WCAG 2.2: What Changed and Why It Matters for Credit Unions

WCAG 2.2 builds on WCAG 2.1 by adding nine new success criteria focused on improving the accessibility experience for users with cognitive disabilities, users with low vision, and users who rely on keyboard or touch-screen interaction. For credit unions, these new criteria have direct implications for the most common digital banking workflows: authentication, form completion, navigation, and mobile interaction.

The nine new success criteria in WCAG 2.2, organized by conformance level, are as follows:

Level A (Minimum) New Criteria:

• 2.4.11 Focus Not Obscured (Minimum) (AA in 2.1 raised to A in 2.2): When a keyboard focus indicator is present, it must be fully visible and not hidden by other content such as sticky headers, cookie banners, or floating action buttons. For credit union websites, this means that sticky navigation bars must not obscure the focused element on loan applications or account opening forms.
• 2.4.12 Focus Not Obscured (Enhanced) (AAA): The entire focus indicator must be visible with no portion obscured by author-created content. This stricter version applies to AAA-level conformance.
• 2.4.13 Focus Appearance (AAA): The focus indicator must have a contrast ratio of at least 3:1 between its focused and unfocused states and must be at least as large as a 2 CSS pixel thick outline or 4 CSS pixel thick perimeter of the element.
• 2.5.7 Dragging Movements (AA): When an operation requires dragging (sliding a toggle, dragging a slider, reordering elements), an alternative input method must be available that does not require dragging. This is critical for credit union applications that use slider controls for loan amounts, reorderable check images, or drag-and-drop document upload interfaces.
• 2.5.8 Target Size (Minimum) (AA): The target area for pointer inputs must be at least 24 CSS pixels by 24 CSS pixels, with limited exceptions for inline links, essential targets, and legal or regulatory requirements. This has direct implications for mobile banking interfaces where account tiles, transaction buttons, and navigation elements must meet minimum tap target sizes.
• 3.2.6 Consistent Help (A): When a Web page contains help mechanisms (contact information, chat functionality, FAQ links, help center access), they must be located in the same relative order across pages in the set. For credit union websites, this means that the "Contact Us" link, live chat button, and help center access must be consistently placed across all pages of the site.
• 3.3.7 Accessible Authentication (Minimum) (A): Cognitive function tests, such as memorizing passwords, transcribing characters, or solving puzzles, are not required for authentication unless they provide an alternative method, a mechanism to bypass the cognitive test, or the test is object recognition or a non-text-based alternative. This directly impacts credit union online banking login pages that use image-based CAPTCHAs, security question verification, or character transcription.
• 3.3.8 Accessible Authentication (Enhanced) (AAA): Extends the same protection to object recognition tasks, meaning any cognitive function test is prohibited as the sole authentication method at AAA level.
• 3.3.9 Redundant Entry (A): Information that was previously entered by the user in the same process must be auto-populated or available for the user to select, not requiring re-entry. For credit union loan applications and account opening forms, this means that when a member enters their name, address, and contact information on one screen, it must be automatically carried forward to subsequent screens in the same multi-step flow.

For credit unions, the most impactful new criteria are likely Focus Not Obscured (2.4.11), Dragging Movements (2.5.7), Target Size (2.5.8), Consistent Help (3.2.6), Accessible Authentication (3.3.7), and Redundant Entry (3.3.9). These criteria directly affect the core digital banking interactions that members perform daily: logging in, applying for products, navigating the site, and accessing help.

The transition from WCAG 2.1 to 2.2 is less disruptive than the transition from 2.0 to 2.1 was. Most credit unions that have already achieved WCAG 2.1 Level AA compliance will find that the new criteria address known pain points for their accessibility-sensitive members. However, the Accessible Authentication criterion (3.3.7) may require significant reengineering for credit unions whose online banking platforms rely on knowledge-based authentication, security image verification, or CAPTCHA challenges.

The Comprehensive Accessibility Audit Methodology

An effective accessibility audit is the foundation of any WCAG compliance initiative. Without a thorough understanding of your credit union website's current state, remediation efforts are unfocused, budgets are misaligned, and legal exposure remains unquantified. A comprehensive audit should cover all of your credit union's digital properties, including the public-facing website, the online banking platform, the mobile banking application, document portals, and any third-party embedded services such as loan origination systems or account opening platforms.

Phase 1: Scope Definition and Inventory

Begin by creating a complete inventory of all digital assets managed by your credit union. This inventory should include all URLs, page templates, content management system components, forms, interactive tools, and downloadable documents. For credit unions using a CMS such as WordPress, Drupal, or Sitecore, the audit should include every template and component type, not just every page, since remediating a template fixes all pages using that template. For credit unions with custom-built digital banking platforms, each screen and workflow step must be documented.

Phase 2: Automated Scanning

Automated accessibility testing tools provide a critical first pass at identifying violations. Tools such as WAVE, axe DevTools, Siteimprove Accessibility, and Lighthouse can scan thousands of pages and identify a significant subset of WCAG violations, typically covering 30-40% of all possible success criteria. Automated scans are particularly effective at detecting missing alt text, insufficient color contrast, missing form labels, duplicate IDs, and broken ARIA attributes. However, automated tools cannot detect approximately 60-70% of accessibility issues, including logical reading order, meaningful alternative text, keyboard trap detection, and screen reader interaction quality.

Phase 3: Manual Expert Review

Following automated scanning, a manual expert review by a qualified accessibility specialist is essential. The manual review evaluates the issues that automated tools cannot detect. A WCAG-trained accessibility expert will navigate your credit union website using only a keyboard to verify that all interactive elements are reachable and operable; evaluate screen reader output and verify that the semantic structure communicates the page content correctly; assess the logical reading order of content and the appropriateness of heading hierarchy; evaluate the quality and usefulness of alternative text beyond simple presence detection; and test forms for accessible validation, error identification, and error suggestion.

Phase 4: User Testing with People with Disabilities

The gold standard for accessibility auditing is user testing with individuals who have disabilities and who rely on assistive technologies in their daily lives. User testing reveals issues that even expert manual reviews can miss, particularly around real-world workflow complexity, assistive technology compatibility, and user satisfaction. For credit union websites, user testing should cover key member journeys: logging in to online banking, viewing and paying bills, applying for a loan, opening an account, finding a branch or ATM, and contacting member service.

Phase 5: Assistive Technology Compatibility Testing

Comprehensive testing must include the most commonly used assistive technology combinations: desktop screen readers (JAWS with Chrome and Firefox, NVDA with Firefox, VoiceOver with Safari), mobile screen readers (VoiceOver on iOS, TalkBack on Android), screen magnification software (ZoomText, built-in OS zoom), speech recognition software (Dragon NaturallySpeaking, Windows Speech Recognition, MacOS Voice Control), and alternative input devices (switch control, eye gaze, sip-and-puff).

Phase 6: Reporting and Documentation

The final output of the audit should be a comprehensive report organized by WCAG success criterion, prioritized by severity and impact, and actionable for your development team. Each finding should include the specific location (URL, component, or template), the applicable WCAG criterion, the current behavior, the expected behavior, a suggested remediation approach, and a severity rating. The report should also include a summary dashboard showing the percentage of criteria passed at Levels A, AA, and AAA, along with an overall accessibility score that can be tracked over time.

Automated Testing: Tools, Configurations, and Limitations

Automated accessibility testing tools are an indispensable part of any credit union's accessibility program, but they are often misunderstood. Credit union leaders sometimes ask, "Can we just run an automated tool and fix what it finds?" The answer is no. Automated tools can identify only a fraction of WCAG violations, typically around 30-40% of the success criteria. However, they excel at detecting the structural violations that are the most common source of ADA demand letters and lawsuits.

Leading Automated Accessibility Testing Tools

WAVE (Web Accessibility Evaluation Tool) by WebAIM is one of the most widely used automated tools in the credit union space. WAVE provides visual feedback on the page by overlaying icons and indicators that show accessibility issues, making it accessible to non-technical stakeholders. WAVE can be used as a browser extension, a standalone API, or a bulk testing tool. For credit union marketing teams that manage website content, WAVE's visual approach makes it particularly valuable for training content editors to identify and fix common issues.

axe DevTools by Deque Systems is the industry standard for developer-facing accessibility testing. It integrates directly into the browser developer tools and provides detailed, W3C-standardized issue descriptions with remediation guidance. axe can be integrated into CI/CD pipelines for automated regression testing, ensuring that new code deployments do not introduce new accessibility violations. For credit unions with internal development teams or agency partners, axe integration is a cornerstone of a sustainable accessibility program.

Siteimprove Accessibility offers a SaaS-based platform that continuously monitors websites for accessibility issues. It provides a compliance score, trend tracking, and automated PDF checking. Siteimprove is particularly valuable for credit unions that lack dedicated accessibility expertise, as its platform provides plain-language explanations of issues and suggested fixes.

Lighthouse is part of Chrome DevTools and provides a free, open-source audit for accessibility, performance, and best practices. While Lighthouse's accessibility checks are not as comprehensive as axe or WAVE, its integration into the Chrome developer workflow makes it an accessible starting point for credit union development teams.

Limitations of Automated Testing

Understanding what automated tools cannot detect is as important as understanding what they can. Automated tools cannot determine whether alternative text is meaningful rather than simply present. They cannot detect whether a keyboard focus indicator has sufficient contrast or is obscured. They cannot assess the logical reading order of content above the heading structure level. They cannot determine whether error messages are descriptive and actionable. They cannot evaluate the quality of a user's experience with assistive technology.

For these reasons, the industry standard is that automated testing should be combined with manual expert review and user testing. The automated scan identifies the low-hanging fruit, the manual review catches the complex issues, and user testing validates the real-world experience.

Recommended Automated Testing Configuration for Credit Unions

For most credit unions, we recommend the following automated testing configuration: weekly full-site scans using WAVE or Siteimprove for content-driven pages; CI/CD integration of axe DevTools for all code changes; monthly Lighthouse audits for performance and accessibility baseline; quarterly PDF accessibility scans for statement templates and disclosure documents; and annual mobile application automated testing using axe for Android and XCUITest Accessibility Inspector for iOS.

Manual Testing: Screen Reader Audits, Keyboard Navigation, and Human Evaluation

Manual accessibility testing is where the true quality assessment happens. While automated tools can flag missing labels or insufficient contrast, only manual testing can determine whether a blind member using JAWS can complete a loan application, whether a member with motor disabilities can navigate online banking using only a keyboard, and whether a member with cognitive disabilities can understand error messages and recover from mistakes.

Keyboard Navigation Testing

Keyboard navigation testing is the single most important manual accessibility check. Every interactive element on your credit union's website must be reachable and operable using only the keyboard, with no mouse or touch input. The testing protocol is straightforward but rigorous: tab through every focusable element on the page, ensure that the focus order matches the visual reading order, verify that all interactive elements receive a visible focus indicator, confirm that no element traps keyboard focus, and test all interactive features including dropdown menus, accordion panels, modal dialogs, date pickers, and carousels.

For credit union websites, the most common keyboard navigation failures occur in interactive components: loan calculators that cannot be operated with keyboard alone, date pickers that trap focus within the calendar widget, mobile hamburger menus that cannot be opened with the keyboard, modal dialogs that do not trap focus within the dialog, and carousels that automatically advance with no pause mechanism.

Screen Reader Testing

Screen reader testing validates that your credit union's website communicates effectively to members who are blind or have low vision. Testing should be conducted with at least two screen reader combinations: JAWS with Chrome and NVDA with Firefox on Windows, and VoiceOver with Safari on MacOS. The testing protocol should verify that page structure is communicated correctly through heading hierarchy and landmarks; images have meaningful alternative text that communicates the function of the image; form controls have properly associated labels that are announced when the control receives focus; dynamic content changes are announced through live regions or ARIA alerts; tables have proper headers and relationships; and the overall flow of content makes logical sense when read linearly.

For credit union online banking portals, screen reader testing is particularly critical because these platforms often use custom JavaScript widgets and dynamic content loading that can break screen reader communication. Common failures include account balance amounts that are not announced when the page loads, transaction tables that lack proper header markup, pop-up alerts for suspicious activity that are not announced to screen readers, and multi-step forms that do not communicate progress or navigation instructions to assistive technology users.

Zoom and Magnification Testing

Credit union websites must be fully usable when the browser zoom is set to 200% and when screen magnification software is active. This testing verifies that content does not overlap, overflow, or become truncated; navigation menus remain accessible; forms remain completable; and text reflows without horizontal scrolling or content loss.

Contrast and Color Testing

Manual contrast testing goes beyond automated tools by considering the actual visual presentation in different viewing conditions. Testers should verify that text contrast meets the 4.5:1 ratio for normal text and 3:1 for large text; that non-text content including icons, chart elements, and form boundaries meets the 3:1 ratio against adjacent colors; that focus indicators provide sufficient contrast against the focused element's background; and that color is not the sole method of conveying information.

Remediation Prioritization: The Risk-Severity-Impact Framework

Once your credit union has completed a comprehensive accessibility audit, you will have a list of issues that may number in the hundreds or thousands, depending on the size and maturity of your digital properties. Not all accessibility issues are created equal. Some represent immediate legal exposure, while others are minor inconveniences for certain user groups. A systematic prioritization framework ensures that remediation resources are allocated to the highest-impact issues first.

The RSI (Risk-Severity-Impact) Framework

Legal Risk Rating: Each finding receives a legal risk rating based on whether the issue corresponds to a WCAG Level A or Level AA success criterion (Level A violations carry the highest legal risk), whether the issue affects a core member journey such as online banking access, loan application submission, or account opening completion, whether the issue has been the subject of recent ADA lawsuits against financial institutions, and whether the issue prevents equal access to essential banking services.

Severity Rating: The severity of each issue is rated based on whether the issue completely prevents a user with a disability from completing a task (Critical), makes a task extremely difficult or time-consuming (High), causes confusion or uncertainty during task completion (Medium), represents a minor inconvenience or unexpected behavior (Low), or is a best-practice recommendation without functional impact (Informational).

User Impact Rating: The impact on users with disabilities is assessed based on the estimated number of users affected by the issue, the frequency with which users encounter the issue, whether a workaround exists, the skill level required to bypass the issue, and the frustration or cognitive burden imposed.

Priority Matrix

Combine the three ratings to create a composite priority score. Issues rated Critical or High on both legal risk and severity should be remediated immediately, typically within 30 days. These include keyboard traps on online banking pages, missing form labels on loan applications, and CAPTCHA puzzles that prevent screen reader users from logging in. Medium-priority issues, such as insufficient color contrast on secondary elements or missing heading hierarchy on informational pages, should be remediated within 60-90 days. Low-priority issues and informational recommendations can be scheduled for the next planned website redesign cycle.

Common High-Priority Issues on Credit Union Websites

The most common high-priority accessibility issues found on credit union websites include keyboard traps or missing keyboard functionality on interactive widgets, missing or incorrect form labels on account opening and loan application forms, CAPTCHA or cognitive tests as the sole authentication method on the login page, non-descriptive link text such as "Click Here" or "Learn More" that prevents screen reader users from understanding the link destination, missing alternative text on images that convey important information such as check images, signature cards, or document previews, insufficient color contrast on primary navigation and call-to-action elements, and inaccessible PDF statements that cannot be read by screen readers.

The 10 Most Common WCAG Violations on Credit Union Websites

Based on analysis of hundreds of credit union website accessibility audits and an extensive review of ADA demand letters and lawsuits filed against financial institutions, the following ten violations appear most frequently and carry the highest legal risk.

1. Missing Alternative Text on Images (1.1.1 Non-text Content, Level A)

Credit union websites frequently use images of checks, documents, branch locations, and staff without providing alternative text that conveys the information presented by the image. This affects screen reader users who cannot perceive the image content. The most damaging examples include images of transaction records, signature cards, or identification documents that are the sole method of conveying essential information.

2. Missing Form Labels (1.3.1 Info and Relationships, 3.3.2 Labels or Instructions, Level A)

Form controls on loan applications, account opening forms, and contact pages frequently lack programmatically associated labels. Screen reader users cannot determine what information a form field requires when the label is only visual. This is the single most litigated accessibility issue across all industries, not just financial services.

3. Insufficient Color Contrast (1.4.3 Contrast Minimum, Level AA)

Credit union branding often uses lighter color palettes for a modern, friendly appearance, but these lighter colors frequently fail the 4.5:1 contrast ratio requirement for normal text. This issue is particularly common on call-to-action buttons, navigation text, and footers where the brand colors are applied to small text.

4. Missing Heading Structure (1.3.1 Info and Relationships, 2.4.6 Headings and Labels, Level A/AA)

Many credit union websites lack a proper hierarchical heading structure. Pages jump from an H1 to an H3 with no H2, or use visual styling instead of semantic headings. This prevents screen reader users from understanding the page structure and navigating efficiently through content sections.

5. Keyboard Trap (2.1.2 No Keyboard Trap, Level A)

Interactive components such as date pickers, loan calculators, chat widgets, and modal dialogs sometimes trap keyboard focus, preventing users from tabbing out of the component. This is a critical failure because it makes the entire page unusable for keyboard-only users.

6. Insufficient Focus Indicator (2.4.7 Focus Visible, Level AA)

Many credit union websites remove or obscure the default browser focus indicator in favor of custom styling that either hides the focus completely or provides insufficient visibility. Without a visible focus indicator, keyboard-only users cannot track their position on the page.

7. Link Text Ambiguity (2.4.4 Link Purpose in Context, Level A)

Credit union pages frequently use generic link text such as "Learn More," "Click Here," "Read More," or "Apply Now" that provides no context when read in isolation by a screen reader. When multiple links on the same page share identical text but link to different destinations, screen reader users cannot distinguish between them.

8. CAPTCHA and Cognitive Authentication (3.3.7 Accessible Authentication, Level A in WCAG 2.2)

Credit union online banking platforms frequently use image-based CAPTCHAs, security image verification, knowledge-based authentication questions, or text-transcription challenges that are inaccessible to users with cognitive disabilities, visual impairments, or learning disabilities. WCAG 2.2's new Accessible Authentication criterion directly addresses this issue.

9. Inaccessible PDF Documents (1.1.1, 1.3.1, 2.4.2, Level A/AA)

Monthly statements, disclosure documents, privacy policies, and loan agreements are frequently provided as untagged PDFs that are completely inaccessible to screen reader users. PDF accessibility requires proper tagging, reading order, heading structure, alternative text, and metadata.

10. Missing Error Identification and Suggestions (3.3.1 Error Identification, 3.3.3 Error Suggestion, Level A)

When a user makes an error on a credit union form, the website must identify the error and suggest a correction where possible. Common failures include form validation that only highlights the error field in red (relying solely on color), validation messages that appear and disappear too quickly, and error messages that say "Invalid entry" without specifying the correct format.

VPAT Creation and Accessibility Conformance Reports

A Voluntary Product Accessibility Template (VPAT) is a document that communicates how a product or service conforms to accessibility standards. For credit unions, VPATs serve two critical functions. First, when your credit union purchases third-party software platforms such as online banking portals, loan origination systems, or content management systems, the vendor should provide a current VPAT documenting the accessibility conformance of the product. Second, your credit union should maintain its own VPAT for its custom-developed digital properties, particularly if your credit union offers digital products or services to other credit unions.

The VPAT is structured according to the Information Technology Industry Council (ITI) VPAT format, which has evolved through several versions. The current VPAT 2.4 Rev was published in February 2023 and includes four tables: WCAG 2.2 (covering all Level A, AA, and AAA criteria), EN 301 549 (the European accessibility standard), Revised Section 508 standards (applicable to federal agencies and entities receiving federal funding), and the Accessibility for Ontarians with Disabilities Act (AODA).

Each criterion in the VPAT is assigned one of five conformance statuses: Supports, Supports with Exceptions, Does Not Support, Not Applicable, and Not Evaluated. For credit unions, the VPAT should clearly document which WCAG criteria are fully supported and which require remediation, along with a timeline for addressing identified gaps.

Best Practices for Credit Union VPAT Creation

A credible VPAT is based on a thorough accessibility audit, not on a desktop review or product documentation alone. The VPAT should include detailed remarks and explanations for each criterion that is not fully supported. The VPAT should be reviewed and updated at least annually or whenever significant functionality changes are made to the digital platform. The VPAT should be available on the credit union's website, either publicly or through an accessibility request process, depending on the credit union's risk tolerance and accessibility maturity.

Credit unions should be aware that a VPAT is a legal document that can be used in ADA litigation. An inaccurate or inflated VPAT that claims compliance when significant violations exist can be used against the credit union as an admission that the known issues should have been fixed. Conversely, an honest VPAT that documents a remediation plan can demonstrate good-faith efforts toward compliance.

Crafting Your Credit Union Website Accessibility Statement

An accessibility statement is a public commitment to accessibility that appears on your credit union's website. While not explicitly required by WCAG or the ADA, an accessibility statement is strongly recommended by the W3C Web Accessibility Initiative (WAI) and may be considered as evidence of good-faith efforts in the event of a lawsuit. An effective accessibility statement serves multiple purposes: it communicates the credit union's commitment to digital inclusion, provides members with a mechanism to report accessibility barriers, demonstrates good-faith compliance efforts to regulators and plaintiffs, and educates staff and members about accessibility.

Required Elements of a WCAG-Conformant Accessibility Statement

The W3C WAI provides a recommended template for accessibility statements. Key elements that every credit union's statement should include are a clear commitment statement affirming the credit union's dedication to digital accessibility for all members and the public; the conformance standard being targeted, typically WCAG 2.2 Level AA; the date of the most recent conformance evaluation; the evaluation method used, including the automated tools, manual testing protocols, and user testing conducted; known limitations and ongoing remediation efforts, with transparency about areas where full compliance has not yet been achieved; contact information for reporting accessibility barriers, including at least an email address and telephone number, and ideally a dedicated web form; an alternative access mechanism for members who cannot access content through the standard interface; and a formal complaint process and expected resolution timeline.

Placement and Visibility

The accessibility statement should be linked from the footer of every page on the credit union website. It should also be accessible from the site map, help center, and any page that discusses credit union policies or member rights. The statement itself should be written in plain language at no more than an 8th-grade reading level, and an accessible version should be available in alternative formats upon request.

Sample Accessibility Statement Structure for Credit Unions

We recommend that credit union accessibility statements follow this structure: an opening commitment paragraph that affirms the credit union's dedication to accessibility as part of its cooperative values; a conformance status section that states the targeted standard (WCAG 2.2 Level AA) and the current evaluation date; a known limitations section that honestly documents areas where full conformance has not yet been achieved, with a remediation timeline; a feedback mechanism section that provides the email address, phone number, and web form for reporting issues; an alternative access section that describes how members can obtain information in alternative formats; a complaint process section that outlines the steps for filing a formal accessibility complaint; and a review and update section that documents the statement's revision history and next review date.

ARIA Landmarks and Semantic HTML: The Foundation of Screen Reader Accessibility

Accessible Rich Internet Applications (ARIA) is a W3C specification that defines ways to make web content and web applications more accessible to people with disabilities. ARIA attributes supplement HTML with additional semantics that are communicated to assistive technologies, allowing screen readers to understand the structure, state, and behavior of web page elements.

For credit union websites, ARIA landmarks are the single most impactful accessibility improvement that can be made. Landmark regions such as role="banner" for the page header, role="navigation" for navigation menus, role="main" for the primary content area, role="search" for the search function, role="form" for forms, role="complementary" for sidebars and supplementary content, and role="contentinfo" for the footer allow screen reader users to quickly navigate between regions of the page without having to read through all the content.

The first rule of ARIA is: do not use ARIA if you can use a native HTML element that provides the semantics you need. Native HTML semantic elements such as

,