ADA Accessibility for Online Rental Applications: Fixing Barriers in the Apartment and Multifamily Leasing Flow

Why the application is the page that matters most

In April 2019 the Equal Rights Center published matched-pair tests of 25 Greater Washington, D.C. area housing websites, comparing a blind screen-reader user with a sighted tester. Of the 16 sites with online applications, 13 were inaccessible to screen readers (Equal Rights Center). That is one region, seven years ago: test your own flow.

ADA Title III bars denying a person with a disability the opportunity to "participate in or benefit from" an entity's services (42 U.S.C. 12182(b)(1)(A)(i)), and DOJ's regulation lists "other sales or rental establishment" as a place of public accommodation (28 CFR 36.104). DOJ's 2022 guidance applies the ADA to services "offered on the web" and names "inaccessible online forms" as a common barrier (ada.gov). The Fair Housing Act separately bars refusing "reasonable accommodations in rules, policies, practices, or services" (42 U.S.C. 3604(f)(3)(B)). How far each reaches a website is in the ADA website compliance pillar.

The vendor builds it; you answer for it

Most applications are a PMS or screening vendor's flow, with payment and e-signature in further third-party frames. Title III applies whether the entity acts "directly, or through contractual, licensing, or other arrangements" (12182(b)(1)(A)). Where you cannot change the code, you control the alternative route, the apply-page notice and the contract.

Eight steps of a typical apply flow, and the WCAG criterion each one fails

Each item gives the criterion most often failed and a check anyone can run without a tool. Criterion text is from <a href="https://www.w3.org/TR/WCAG22/">WCAG 2.2</a>.

1. 01

   Unit, move-in date and lease-term selection

   2.1.1 Keyboard (A) and 4.1.2 Name, Role, Value (A). Date pickers and unit cards are often mouse-only and silent to screen readers. Check: Tab to the move-in date and type a date without clicking. Each unit option should announce its name and whether it is selected.

2. 02

   Applicant details

   1.3.1 Info and Relationships (A), 3.3.2 Labels or Instructions (A) and 1.3.5 Identify Input Purpose (AA). Placeholder text that vanishes on typing is not a label. Check: click the visible label; the cursor should land in its field. Name, email, phone and address fields need autocomplete attributes.

3. 03

   Co-applicants, occupants and guarantors

   3.3.7 Redundant Entry (A, new in 2.2). Information "previously entered by or provided to the user that is required to be entered again in the same process" must be auto-populated or available to select, with narrow exceptions such as security. Check: add a co-applicant at the same address. If you must retype it, the step fails.

4. 04

   Income and document upload

   2.1.1 Keyboard (A), 2.5.7 Dragging Movements (AA) and 3.3.1 Error Identification (A). Drag-and-drop zones with no focusable "choose file" button lock out keyboard and single-pointer users. Check: upload a pay stub using only Tab and Enter, then try a rejected file type. The error must be "described to the user in text."

5. 05

   Sign-in, identity verification and CAPTCHA

   3.3.8 Accessible Authentication (Minimum) (AA, new in 2.2) and 1.1.1 Non-text Content (A). 3.3.8 covers signing back in, not creating the account; 1.1.1 covers any CAPTCHA. Check: save the application, sign back in with a password manager, paste any one-time code, and look for a puzzle. The section below sets out what passes.

6. 06

   Application fee payment

   4.1.2 Name, Role, Value (A) and 3.3.4 Error Prevention (Legal, Financial, Data) (AA). Processor payment frames often have unlabeled card fields and silent errors. A payment is a financial transaction, so 3.3.4 requires it be reversible, checked or confirmed. Check: reach a review screen showing the amount before the charge.

7. 07

   E-signature

   2.1.1 Keyboard (A) and 3.3.4 Error Prevention (AA). A lease signature is a legal commitment, so 3.3.4 requires review, checking or reversal. 2.1.1 excuses input that depends on the path of movement, but the function here is adopting a signature, not drawing one: turn on typed or click-to-adopt signing. Check: sign the whole packet without a mouse.

8. 08

   Session timeouts across the whole flow

   2.2.1 Timing Adjustable (A). A silent timeout costs the slowest applicants, often screen-reader and switch users, everything entered so far. Check: leave a step idle until it times out. You should get a warning and a simple way to extend; see the worked example below.

Sign-in, CAPTCHAs and identity checks under WCAG 3.3.8

WCAG 2.2 says a "cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process" unless the step offers an alternative, a helping mechanism (a password manager, copy and paste), object recognition, or recognition of content the user supplied (WCAG 2.2, 3.3.8). W3C adds that it "does not cover creation of a username or initiation of an account" (W3C Understanding 3.3.8). It bites when an applicant signs back in to resume, check status or sign the lease. Any CAPTCHA also falls under 1.1.1 Non-text Content (A), which requires a version in another sensory mode.

Knowledge-based identity questions from credit history are not a sign-in step and W3C does not address them, but they are still a memory test: offer document or in-person verification.

Session timeouts and save-and-resume

For each time limit, WCAG 2.2.1 requires at least one of: the user can turn it off; the user can adjust it to at least ten times the default; or the user "is warned before time expires and given at least 20 seconds to extend the time limit with a simple action," at least ten times (W3C Understanding 2.2.1).

Save-and-resume is not required by 2.2.1, but it is the practical fix, and AAA criterion 2.2.5 asks for it: continuing "without loss of data after re-authenticating" (WCAG 2.2).

The alternative path: publish it, and do not lean on it

State on the apply page how to apply by phone, in person or with help, and how to request an accommodation. In the 2004 HUD and DOJ Joint Statement (Question 17, Example 3), an applicant with an obvious vision impairment asks the leasing agent for help completing the rental application, and the provider "may not require the applicant to document the existence of her vision impairment." Providers must consider requests made orally or outside their "preferred forms or procedures" (Joint Statement, May 17, 2004).

The alternative cannot replace an accessible flow. Title III bars a benefit that is "different or separate" unless that is necessary to provide one "as effective as that provided to others" (12182(b)(1)(A)(iii)). An office-hours phone line rarely matches a 24-hour online application, and whether an alternative channel alone satisfies the ADA for a website is unsettled. Plan on both.

What to publish next to "Apply now"

• A phone number and email that reach someone who can take an application or an accommodation request.
• A plain sentence that applicants can request a reasonable accommodation in any form, including by phone.
• Office hours for in-person help.

Keep it identical everywhere the property appears. In Brynson's analysis of 6,000 properties and 1.6 million units, about 89% of communities described themselves differently across listing sites (listing accuracy report); accommodation contacts drift the same way.

The 15-minute test script for leasing teams

Run it on one property's live application with test data, on a desktop with a screen reader (NVDA on Windows is free; VoiceOver is built into macOS). Write down the step and the screen for every place you get stuck.

Time needed: 15 minutes

1. 1

   Reach the application by keyboard (1 minute)

   From the property home page, press Tab until "Apply now" is focused and press Enter. If you cannot see where focus is, or the button is skipped, stop and log it.

2. 2

   Pick a unit and move-in date (2 minutes)

   Select a unit and type a move-in date without the mouse. Turn on the screen reader and confirm each option announces its name and selected state.

3. 3

   Fill the applicant form by label (2 minutes)

   Tab through each field and listen for its label. Click each visible label and check the cursor lands in the right field.

4. 4

   Trigger an error (2 minutes)

   Leave a required field empty and submit. The error must be announced or reachable, in text, next to the field, not only as a red border.

5. 5

   Upload a document (2 minutes)

   Upload a test file using only Tab and Enter, then try a rejected file type and confirm the error is described in text.

6. 6

   Sign back in with a password manager (2 minutes)

   Save the application, sign out, then sign back in letting the password manager fill the password and pasting any one-time code. Note any CAPTCHA, puzzle, blocked paste or memory question.

7. 7

   Wait out the session (2 minutes of attention)

   Leave a step idle until the session warning should appear. Confirm you get a warning and can extend it with one simple action.

8. 8

   Reach payment and signature review (2 minutes)

   Advance to payment and e-signature with the keyboard only, and confirm there is a review screen before any charge or signature. Do not submit real payment details.

Questions to send your application vendor

Ask for an Accessibility Conformance Report (ACR), a completed VPAT. The current version is VPAT 2.5Rev (April 2025); its WCAG edition covers WCAG 2.0, 2.1 and 2.2, and rates each criterion supports, partially supports, does not support or not applicable (ITI).

1. Send your current ACR on the VPAT 2.5 WCAG edition for the exact application, payment and e-signature components we use, with its date and evaluation method.
2. Which criteria are rated "partially supports" or "does not support," and what is the fix date for each?
3. Is there a timeout warning, and can a session be extended or saved?
4. Does sign-in use a text CAPTCHA, block paste or reject a pasted one-time code? Does identity verification ask knowledge-based questions, and what is the alternative?
5. Who do we contact when an applicant reports a barrier, and what is the fix window?

Keep reports and dated test notes (evidence retention), and if a letter has arrived, see responding to an ADA demand letter.

Frequently asked questions