Start With Public Financial Tasks
Review the paths visitors use before they become authenticated customers: compare accounts, check rates, use calculators, find branches or ATMs, start a loan or account application, contact support, and read required disclosures.
Do not treat the homepage as the website. A public-page snapshot should be paired with manual review of forms, tables, calculators, PDFs, and vendor-owned widgets that affect financial decisions.
Forms, Tables, Calculators, And Disclosures
Financial sites often carry long forms, rate tables, eligibility questions, calculators, disclosures, PDF applications, statements, brochures, and policy files. Review labels, grouped controls, validation, instructions, focus order, headings, table structure, document titles, reading order, and support paths.
If a disclosure, fee schedule, rate sheet, or application is only available as a PDF, treat it as a document-accessibility workstream rather than a small content issue.
Online Banking And Vendor Handoffs
Public banking sites often hand visitors to online-banking platforms, loan-origination tools, appointment schedulers, chat systems, map providers, card tools, and document portals. List each vendor-owned surface, what your team controls, and how accessibility issues are escalated.
Do not submit credentials, account details, payment information, customer records, or private financial data through public lead forms. The first pass should use public URLs and scope context only.
Evidence And Responsible Claims
Keep an evidence folder with the public-page snapshot, form inventory, PDF and disclosure inventory, calculator notes, branch-locator notes, vendor list, remediation tickets, retest dates, and accessibility statement updates.
Avoid claiming the site is fully ADA compliant or that a provider has solved legal risk. Use the evidence to route manual review, remediation workflow, document accessibility, monitoring, or support resources.
Decision path
Use these links to move from research to evidence, then from evidence to a responsible remediation option.
Downloadable assets
Optional follow-up
Want help using these asset?
Direct downloads stay available above. Share a work email only if you want a tailored note on how to use the asset for your site, client, or article.
Frequently asked questions
Can a public scan check online banking accessibility?
No. Public scans can review public HTML signals only. Authenticated banking, account, loan, and payment workflows need privacy-safe manual review and vendor coordination.
What should financial institutions review first?
Start with public product pages, applications, branch and ATM locators, calculators, disclosures, PDF forms, support paths, login handoffs, and vendor-owned tools.
Does this checklist guarantee ADA compliance?
No. It is technical planning guidance for public website and workflow review. It does not replace counsel, compliance owners, vendor review, or a full WCAG audit.