Web design

ADA and accessibility for commercial real estate websites

By Noah, founder of Endcap. Published August 8, 2026 · Updated October 10, 2026

A real estate website is accessible when people who use screen readers, keyboards, magnification, or voice control can find the same listings, facts, and forms as everyone else. In the United States the working technical standard is WCAG Level AA. This guide covers the legal picture as of September 2026, where brokerage, property, and property management sites fail, and a pass an owner can run this week. It is general information, not legal advice; for a specific site or demand letter, talk to a lawyer.

What the rules are

Three separate things get blurred together, and separating them makes the subject manageable. The first is the technical standard. WCAG, the Web Content Accessibility Guidelines, is published by the W3C, and Level AA is the conformance level people mean when they say a site should be accessible. Version 2.1 is the one written into the federal rule for public entities. Version 2.2 became a W3C Recommendation on October 5, 2023 and adds nine success criteria. W3C describes the 2.0 and 2.1 criteria as essentially unchanged in 2.2, except that 4.1.1 Parsing was removed as obsolete, so a site built to 2.2 AA covers nearly all of 2.1 AA (W3C, What’s New in WCAG 2.2).

The second is federal law. Title III of the ADA covers businesses open to the public and does not name websites. The Department of Justice’s March 18, 2022 guidance says the ADA’s requirements apply to the goods and services such businesses offer online, and it leaves them flexibility in how they comply rather than adopting a technical standard (ADA.gov web guidance). Title II, which covers state and local governments, has a specific rule. The DOJ’s April 2024 final rule adopts WCAG 2.1 Level AA for public entities. An interim final rule effective April 20, 2026 moved the compliance dates to April 26, 2027 for entities serving 50,000 people or more and to April 26, 2028 for smaller entities and special districts, without changing the standard (ADA.gov Title II fact sheet). The Title II rule applies to public entities, not to private brokerages or landlords.

The third is state law, and in California it carries direct financial exposure. Civil Code section 51(f) makes a violation of the ADA a violation of the Unruh Civil Rights Act (Civ. Code § 51). Section 52(a) sets damages for each offense at no less than $4,000, plus attorney’s fees (Civ. Code § 52). Whether and how those provisions apply to a particular website is a legal question for counsel.

Lawsuit and failure-rate figures for 2025 and 2026

Two trackers count web accessibility lawsuits in different ways. Seyfarth Shaw counts federal filings only. UsableNet counts federal and state filings together, which matters in California, where Seyfarth found only four new federal website cases in 2025.

Web accessibility lawsuits and home-page failure rates

Measure	Figure	Source and date
Federal website accessibility lawsuits, 2025	3,117, up 27% from 2,452 in 2024	Seyfarth Shaw, March 25, 2026
Share of all federal ADA Title III lawsuits, 2025	36% (3,117 of 8,667)	Seyfarth Shaw, March 25, 2026
New federal website lawsuits in California, 2025	4	Seyfarth Shaw, March 25, 2026
Digital accessibility lawsuits, federal and state, 2025	More than 5,000	UsableNet, January 8, 2026
State-court cases in New York and California combined, 2025	Nearly 2,000	UsableNet, January 8, 2026
Top million home pages with detected WCAG 2 failures	95.9% in 2026, up from 94.8% in 2025	WebAIM Million, 2026
Most common detected failures, 2026	Low-contrast text 83.9%; missing image alt text 53.1%; missing form input labels 51%	WebAIM Million, 2026

WebAIM’s scan is automated and catches only part of the WCAG criteria, so the share of pages with some failure is likely higher. The useful part is that six kinds of error account for most of what it detects, so a focused pass fixes most of the common problems.

Where real estate sites fail

Real estate sites are built from components other industries rarely use: site plans, availability tables, drone film, flyers, and property search filters. The table lists the failures we see most often, where they appear, and the fix, with the related WCAG success criterion.

Common accessibility issues on real estate websites

Issue	Where it appears	Fix
Site plan information only in shapes	Interactive center site plans, stacking plans, clickable suite maps	Publish the same availability as text beside the plan: suite, area, status, and rate or “on request” (1.1.1, 1.3.1)
Low-contrast text over photos	Hero images and drone stills with white headline type	Put the type on a scrim or solid panel and check 4.5:1 for normal text and 3:1 for large text (1.4.3)
Autoplaying film without controls	Aerial and flyover video on property pages	Provide pause or stop for moving content that plays automatically for more than five seconds (2.2.2)
Unlabeled form fields	Inquiry, tour-request, and contact forms that use placeholder text as the label	Use visible labels, text error messages, and a visible focus outline (3.3.2, 3.3.1, 2.4.7)
Status shown by color alone	Green and gray suites on availability maps and tables	Add the word “Available” or “Leased” next to the color (1.4.1)
Missing or empty alt text	Property photography, logos, and linked images	Describe what a prospect would learn from the image; mark decorative images as decorative (1.1.1)
Third-party embeds	Maps, virtual tours, scheduling widgets	Publish the address and key layout facts as text so the embed is never the only source (1.1.1)
Small tap targets	Map pins, gallery arrows, filter chips on phones	Make targets at least 24 by 24 CSS pixels or space them apart (2.5.8, WCAG 2.2)
Focus hidden behind sticky bars	Sticky headers, cookie banners, and chat widgets	Keep the focused element visible when a keyboard user tabs to it (2.4.11, WCAG 2.2)
Untagged PDFs	Flyers, OMs, community rules, applications, certificate of insurance requirements	Publish key facts as HTML, or produce tagged PDFs with a defined reading order and real form fields

Property management websites

Property management sites serve current residents and tenants as well as prospects, so they add search tools, logins, service requests, and document libraries. Those features are where the failures in the table above are most likely to block someone from completing a task.

• Property and unit search filters. Filters for city, property type, size, rent, and availability should be real form controls with labels, operable by keyboard. When results update without a page reload, announce the change, for example “12 properties found,” so a screen reader user knows the filter worked (4.1.3 Status Messages). Every property in the results should have a text link, not only a map pin.
• Contact and service-request forms. Label every field, explain required formats before submission, and describe errors in text next to the field. Do not ask the user to re-enter information already provided in the same process (3.3.7 Redundant Entry, WCAG 2.2). If photos can be attached to a maintenance request, the upload control needs a label and a keyboard path.
• Resident and tenant logins. WCAG 2.2 adds 3.3.8 Accessible Authentication: a login step should not depend on a memory or puzzle test unless an alternative exists, and password managers and paste should work. Many portals are third-party software, so ask the vendor for its accessibility conformance report.
• PDFs for residents and vendors. Community rules, move-in packets, lease applications, parking policies, and certificate of insurance (COI) requirements for vendors and commercial tenants are often posted only as scanned PDFs. Publish the key requirements as HTML on the page, such as the coverage types, limits, and additional-insured wording the manager requires, and keep a tagged PDF for download. A scanned image of a form cannot be read by a screen reader or completed without printing.
• Consistent help. Put the office phone, email, and emergency maintenance contact in the same place on every page (3.2.6 Consistent Help, WCAG 2.2).

Endcap’s property management website guide covers the rest of what these sites need, and the property management websites service describes how we scope them.

Flyers and other PDFs

Commercial real estate moves on PDFs. The flyer gets emailed, attached to portal listings, and printed for tours, and many leasing flyers are flattened design exports with no tag structure, reading order, or text layer. A screen reader opens one and finds a picture of a document.

Our own work shows the tension. The seven-page flyer we produced for the 5801 Lincoln listing, a 2,660 square foot corner suite in Buena Park, is flattened so it scrolls smoothly in a browser. Flattening helps the reader in a browser tab and hurts the reader using assistive technology. Our answer is to make sure the listing page carries every fact the flyer does as real HTML text: suite facts, traffic counts with sources, demographics, and contacts. Nobody should have to open a PDF to learn how big the space is or who to call. A fully accessible flyer is a tagged PDF with a defined reading order, produced deliberately, and it is worth requesting when a public agency is on the other side of the deal. Otherwise the web page is the accessible version of record. See our flyer design guide and the Lincoln case study.

What we do on our builds

Our property sites are written in code rather than assembled in a drag-and-drop page builder, which matters because most accessibility problems are structural. Headings run in order and describe the section instead of being chosen for their font size. Interactive elements are real buttons or links, reachable by keyboard. Focus outlines stay. Alt text is written by whoever wrote the listing copy, because they know what the photo is meant to show.

On the Marbella Plaza site, a 66,124 square foot shopping center in San Juan Capistrano, the availability list is the source of truth and the interactive site plan is a visual index of it. Both carry the same information, and the list works without vision, a mouse, or JavaScript. The Marbella case study covers the rest of the build. We do not describe any site as certified compliant, because no official certification exists and conformance is a judgment about a specific site at a specific time. We can state what was checked, by whom, and against which criteria.

About overlay widgets

Overlay vendors sell a line of JavaScript and an icon in the corner as a compliance fix. Accessibility practitioners, many of them screen reader users, have objected publicly through the Overlay Fact Sheet. In January 2025 the Federal Trade Commission announced an order requiring overlay vendor accessiBe to pay $1 million over claims that its AI product could make any website WCAG compliant, and the Commission approved the order as final in April 2025 (FTC, January 2025). A widget is a script layered over the markup and does not change it. The page underneath still needs labeled fields and readable contrast.

A pass you can run this week

• Unplug the mouse. Tab through your busiest property page from the top. You should always see where you are, and you should be able to reach and submit the inquiry form. This test finds more than a scanner does.
• Run a free automated scan. WAVE from WebAIM and the axe DevTools extension flag contrast, missing alt text, and unlabeled inputs in seconds. They catch only part of the criteria, so a clean report is a starting point.
• Zoom to 200 percent. Text should reflow and stay readable without horizontal scrolling.
• Read one photo’s alt text out loud. If it tells you nothing a prospect would want to know, rewrite it.
• Open your own flyer and try to select a sentence. If nothing selects, confirm everything in it also exists on the page.
• Use a search filter with the keyboard on a property management site, then submit a test service request the same way.
• Turn on your phone’s screen reader for two minutes. VoiceOver on iOS or TalkBack on Android is awkward at first and shows problems a report will miss.

What to ask whoever builds it

• Which WCAG version and level are you building to, and how will you check it?
• Who writes the alt text, and is it in the content scope or added at launch?
• When availability changes, does the text version change with the graphic?
• Which third-party tools, such as portals, maps, or scheduling widgets, are embedded, and what do their vendors report about accessibility?

There is a longer list of vendor questions in how to choose a commercial real estate web design firm, and you can see how we scope the work in our services.

The legal exposure is what usually prompts owners to act, but accessible pages also help readers without a disability. A tenant rep reading on a phone in sunlight, an owner zooming into a rent roll, and a broker tabbing through a form on an unreliable trackpad all benefit from the same fixes.

Sources

• W3C, What’s New in WCAG 2.2. Accessed September 24, 2026.
• U.S. Department of Justice, Guidance on Web Accessibility and the ADA, March 18, 2022.
• U.S. Department of Justice, Fact Sheet: Title II rule on web and mobile app accessibility, updated for the interim final rule of April 20, 2026.
• California Civil Code § 51(f) and § 52(a). Accessed September 24, 2026.
• Seyfarth Shaw, Federal Court Website Accessibility Lawsuit Filings Bounce Back in 2025, March 25, 2026.
• UsableNet, ADA web lawsuit data from 2025 filings, January 8, 2026.
• WebAIM, The WebAIM Million, 2026 report.
• Federal Trade Commission, accessiBe order announcement, January 2025.

If you want this handled rather than explained: brokerage website design and single-property websites.