Mortgage brokers and lenders sit at one of the highest-stakes transactions a consumer will ever complete online, and almost the entire funnel now runs through the website: a rate table and mortgage calculator, a pre-qualification or affordability form, a full loan application (often a lengthy 1003), income and asset document uploads, credit authorization, disclosures, and electronic signature. Every one of these steps is a frequent accessibility failure point, and the consequences of an inaccessible one are severe because a home loan is complex, legally binding, and financially irreversible. The borrowers most affected include older adults refinancing or buying later in life, veterans using VA loans, and people with low vision, motor impairments, or cognitive disabilities who cannot afford to mis-enter an interest rate, misread a monthly payment, or accidentally submit a wrong figure on a legal document. A blind applicant who cannot operate a slider-only calculator, a keyboard user who cannot upload a pay stub, or a low-vision borrower who cannot read an APR shown only in a faint colored box is shut out of a life-changing financial product. Lender sites also depend heavily on third-party point-of-sale, calculator, and e-sign widgets that are rarely tested for accessibility, and because lending is a protected activity under fair-lending law, an inaccessible application is not just an ADA problem, it can be a discrimination problem. This guide covers the legal requirements, the most common failures, and a practical compliance checklist for mortgage brokers and lenders.

Legal Requirements

Key Accessibility Issues in Mortgage Brokers & Lenders

Mortgage Calculators and Rate Sliders That Are Mouse-Only or Unannounced

The entry point to most lender sites is a payment or affordability calculator, frequently built on drag-only sliders for loan amount, rate, and term. These sliders are often not keyboard operable, expose no current value or range to screen readers, and update the resulting monthly payment and APR silently. A blind, low-vision, or keyboard-only borrower cannot set the inputs or learn the result, so the primary decision-making tool on the site is closed to them.

How to fix:

Make every calculator input keyboard operable, with sliders that respond to arrow keys and expose current value, min, and max (WCAG 2.2 4.1.2 Name, Role, Value), and always provide a typeable number field as an alternative. Announce recalculated monthly payment, APR, and totals through an accessible live region, and present results as real text, never color or a chart alone.

Long Loan Applications With Placeholder Labels, Poor Structure, and Silent Errors

A full mortgage application collects income, employment, assets, debts, and property details across many pages, and lender point-of-sale forms commonly use placeholder-only labels, ungrouped radio and checkbox sets, timeouts that wipe progress, and validation errors shown only in red with no announcement. A screen reader user, a keyboard-only user, or an applicant with a cognitive disability cannot accurately complete a form this long and consequential when fields are unlabeled, structure is missing, and mistakes are never announced.

How to fix:

Give every field a persistent, associated label, group related questions with fieldset and legend, and expose a clear, announced multi-step progress indicator. Announce validation errors, link each to its field, and move focus to the first error (WCAG 2.2 3.3.1, 3.3.3). Warn before session timeouts and preserve entered data (2.2.1 Timing Adjustable), and let applicants review and correct every value before submission (3.3.4).

Document Upload and Credit-Authorization Steps That Fail With Assistive Technology

Applicants must upload pay stubs, W-2s, bank statements, and identity documents and then authorize a credit pull. Custom drag-and-drop uploaders are routinely mouse-only, unlabeled, and silent about success or failure, while credit-authorization checkboxes and consents may be unlabeled or presented in inaccessible modals. A keyboard user who cannot trigger the file picker, or a screen reader user who cannot confirm which documents uploaded or what they are consenting to, cannot advance and may unknowingly authorize a hard credit inquiry.

How to fix:

Pair drag-and-drop with a keyboard-operable, clearly labeled file-input button, and announce each upload's progress, success, and errors and list the accepted files as text (WCAG 2.2 4.1.3). Label every consent and authorization control explicitly, present authorization language as readable text, and require an accessible, explicit confirmation before any credit inquiry.

Disclosures, Loan Estimates, and E-Sign Delivered as Inaccessible PDFs or Modals

Federally required disclosures such as the Loan Estimate and Closing Disclosure, along with e-sign packages, are often delivered as scanned or untagged PDFs, or inside e-sign tools whose signature fields and controls are not keyboard operable or screen-reader labeled. A blind or low-vision borrower who cannot read a Loan Estimate, or cannot reach and activate the signature fields, is asked to legally commit to terms they were never able to review, a direct 3.3.4 and fair-lending failure.

How to fix:

Deliver all disclosures as tagged, readable PDFs or accessible HTML with a proper reading order and real text, not scanned images, and choose an e-sign platform whose fields and controls are keyboard operable and screen-reader labeled. Ensure the applicant can review the full document, understand what they are signing, and correct or decline before completing a binding signature.

Rate Tables, Comparisons, and Adverse-Action Notices Conveyed Only Visually

Lenders present rate and product comparisons in tables and highlight recommended options or status with color, and decisions such as approvals or adverse-action (denial) notices may be shown through color-coded badges or delivered in inaccessible formats. When APRs, fees, and loan status are conveyed only by color, an unlabeled table, or an image, a screen reader or color-blind borrower cannot compare products or understand a credit decision, including the reasons a denial requires.

How to fix:

Mark up rate and comparison tables with proper header cells and scope so screen readers can navigate them, and convey highlighted or recommended options and loan status with text, not color alone (WCAG 2.2 1.4.1). Deliver approvals and adverse-action notices as accessible text that states the outcome and, where required, the specific reasons, so every applicant can read and act on the decision.

Compliance Checklist

  • Mortgage and affordability calculators are keyboard operable, expose slider values to assistive technology, and offer typeable number inputs
  • Recalculated payments, APR, and totals are announced through a live region and presented as real text, not color or chart alone
  • Loan application fields use persistent labels, grouped questions (fieldset/legend), and a clear announced step indicator
  • Application errors are announced, linked to their fields, and focus moves to the first error; timeouts warn users and preserve entered data
  • Applicants can review and correct all income, rate, and identity data before any binding submission or credit pull (WCAG 2.2 3.3.4)
  • Document upload offers a keyboard-operable, labeled file-input alternative and announces upload success, errors, and accepted files
  • Credit-authorization and consent controls are explicitly labeled, presented as readable text, and require accessible confirmation before any inquiry
  • Disclosures and Loan Estimates are delivered as tagged accessible PDFs or HTML with real text, never scanned images
  • E-sign fields and controls are keyboard operable and screen-reader labeled, with full document review before a binding signature
  • Rate tables use proper header cells, and recommended options, loan status, and adverse-action notices are conveyed as text, not color alone

Further Reading

Other Industry Guides