Fair Housing & Accessibility
Which WCAG Level Fits Apartment Sites?
Every few months a client calls me after getting a demand letter over their apartment website. The complaint almost always […]
I’ve rebuilt enough leasing websites to know that most Fair Housing violations online aren’t intentional. They come from a photo caption nobody reviewed, a chatbot script written two years ago, or a floor plan page that uses the word “exclusive” without thinking twice about it. The law hasn’t changed much in decades, but where it applies has expanded fast. In 2026, your website, your chatbot, and your text messages all carry the same legal weight as a printed brochure.
This isn’t a repeat of the operational checklist we’ve published before. That post walks through a step-by-step audit. Here, I want to explain the legal reasoning behind the rules — why HUD and the courts treat digital platforms the way they do, and where I see operators misjudge their own risk.
The Fair Housing Act prohibits discrimination based on race, color, national origin, religion, sex, familial status, and disability in any advertisement or statement related to housing. That requirement applies regardless of medium, which means your website, chatbot, text campaigns, and social ads are all treated the same as a printed ad under HUD’s Fair Housing and Equal Opportunity guidance. Practically, this means three things: your written content and photos can’t signal a preference for or against any protected class, your site needs to be usable by people with disabilities under accessibility standards, and any automated communication tool — chatbot, AI assistant, or texting system — has to give every prospect the same information regardless of who’s asking. Operators often assume Fair Housing is about avoiding bad language. It’s really about avoiding inconsistent treatment, documented or not.
The classic violations are well known by now: phrases like “perfect for young professionals” or “walking distance to churches” that signal a preference tied to familial status or religion. What I see more often in 2026 is subtler. Amenity pages that only show photos of one demographic. Neighborhood descriptions that lean on coded language about “safe” areas. Floor plan names like “The Bachelor” that imply a target renter. None of these are automatically violations, but they create a pattern that a fair housing tester or plaintiff’s attorney can point to. I tell clients to read every page as if a HUD investigator will read it next week, because eventually, one might.
This is the part operators underestimate most. If your leasing team wouldn’t say it on the phone, your AI assistant shouldn’t say it in a chat window either. The risk isn’t theoretical — automated tools scale a bad answer to every visitor who asks a similar question, which turns one bad judgment call into a pattern across hundreds of conversations. We built LeaseSitePro AI to stick to approved, property-specific information and decline to answer questions that veer into protected-class territory, like “is this a family building” or “what’s the neighborhood like.” Instead, it redirects to a human. That’s not a feature we added for compliance theater — it’s because a scripted, consistent answer protects both the renter and the operator. If you’re evaluating any AI leasing tool, ask the vendor directly how it handles discriminatory or steering-adjacent questions, and ask to see it in a live demo before you trust it with real inquiries. For more on how these assistants are supposed to function day to day, see what an AI leasing assistant really does.
The ADA doesn’t contain a specific web accessibility standard, but the Department of Justice and most courts point to the W3C’s WCAG guidelines, currently at version 2.2, as the practical benchmark. Level AA conformance is the standard most multifamily sites are measured against, and I’ve watched this become a bigger liability category than copy violations in the last two years. Serial ADA plaintiffs target multifamily websites specifically because so many run on outdated templates with no alt text, no keyboard navigation, and video backgrounds that trap screen readers.
Here’s where I’ll push back on a popular shortcut: accessibility overlay widgets — the little scripts that claim to fix your site with one line of code — don’t hold up under real scrutiny. They paper over problems instead of fixing the underlying code, and several have become the subject of lawsuits themselves. If you want to understand the difference between a real fix and an overlay, Real ADA Compliance — Not an Overlay breaks down what actual remediation looks like versus a cosmetic patch. For what we do on our own platform, our accessibility statement lays out our conformance approach and how we handle feedback.
Fair Housing isn’t the only law touching your site. The moment you text a prospect, you’re under the Telephone Consumer Protection Act, enforced by the Federal Communications Commission. TCPA requires prior express written consent before sending automated or marketing texts, and that consent has to be captured clearly — not buried in a privacy policy nobody reads. I’ve seen operators treat a contact form submission as blanket consent to text, which is a mistake. The consent language needs to specifically disclose that the prospect may receive automated texts and that consent isn’t a condition of renting. Get this wrong and you’re looking at statutory damages per text message, which add up fast across a leasing season. This is a place where I always tell clients: don’t guess, get your attorney to review the exact consent language on your forms before you turn on any texting feature.
The mistake I see most is treating fair housing review as a one-time launch task. A site gets built, reviewed, approved, and then nobody looks at it again until renewal. But copy changes, new floor plans get added with new photos, a leasing agent updates the chatbot script to answer a question faster, and nobody runs it past the original standard. Fair Housing risk accumulates through small, well-intentioned edits more than through one bad decision. The National Apartment Association and National Multifamily Housing Council both publish ongoing fair housing resources for exactly this reason — it’s not a box you check once.
If you want the step-by-step audit version of this, our Fair Housing Online Checklist For Operators walks through specific items to review across advertising language, chatbot scripts, accessibility, and consent forms.
Pull up your own website this week and read every page like a tester would. Check your chatbot’s answers to a handful of edge-case questions about neighborhoods, schools, and families. Confirm your text consent language has been reviewed by counsel in the last year, not just at launch. And if your site runs on an old template or an accessibility overlay, get a real evaluation — Acute SEO Services and Real ADA Compliance are both worth a look if you want outside eyes on where your site actually stands.
At LeaseSitePro, we build and manage apartment websites with this exact framework baked into the structure, copy templates, and AI assistant behavior from day one — not bolted on after a complaint. You can see examples across our live portfolio of apartment websites, compare plans, or talk to our team about auditing what you’re running now.
Written by Derrick Tulali — Founder, LeaseSitePro.
Content Note: This article was created with AI assistance. Our team reviews all content for accuracy.
Tell us how many communities you operate and we will show you the platform on one of them.