How-to · Apartment Website Accessibility

Alt Text for Apartment Photos, Floor Plans and Unit Maps: Accessible Media Patterns for Multifamily Websites

For web producers, content managers and agency teams who build and update multifamily property sites.

Brynson Research Team·Updated ·9 min read Sources checked
TL;DR

Write alt text for apartment photos that says what a renter would learn from the image, in one short sentence, with no "photo of" and no keyword lists. Mark purely decorative images alt="". Give every floor plan a text summary, every pricing grid a real data table, every interactive unit map a list view and every tour a transcript.

  • WebAIM's 2026 scan of one million home pages found missing alt text on 53.1% of them.
  • A floor plan is a complex image: a short alt plus a text summary of rooms, size and layout beside it.
  • Unit maps and galleries must work by keyboard and with a single tap or click, not only by dragging or swiping, so publish the same units as a list.
  • Alt text should name only amenities the property has, taken from the same source as the listing copy.

This guide is general information, not legal advice. Laws and regulator guidance change; check the current rules for your properties with your counsel before acting.

53.1%of home pages had images with missing alt textWebAIM Million, 2026
10.8%of images that had alt text used questionable or repetitive text such as "image" or a file nameWebAIM Million, 2026
~89%of communities described themselves differently across listing sitesBrynson analysis of 6,000 properties and 1.6M units

Why the media is where property sites fail

On a listing site the photos are the product. WebAIM's February 2026 scan of the top one million home pages counted 66.6 images per page on average; 16.2% of those images had no alternative text, and 10.8% of those that did used "questionable or repetitive" text such as alt="image" or a file name. Missing alt text appeared on 53.1% of home pages, second only to low contrast (WebAIM Million 2026).

The Department of Justice names missing alt text as a barrier: people who are blind "will not be able to understand the content and purpose of images" without it (DOJ web guidance, March 18, 2022). Which law reaches which surface: see the ADA website compliance pillar.

Alt text is listing copy

In Brynson's analysis of 6,000 properties and 1.6M units, about 89% of communities described themselves differently across listing sites. Alt text drifts the same way: if it says "saltwater pool" and the amenity list says "pool", or names a feature that was removed, a screen-reader user hears a different property. Write it from the same amenity source as the listing.

Alt text for 12 common apartment photos: weak, better, best

Each item shows the usual weak version, a better one and the version that tells a renter what they would learn from the picture. WebAIM says alt text should be "succinct" and calls "Image of..." redundant because it "describes the image as an image" (<a href="https://webaim.org/techniques/alttext/">WebAIM</a>). The examples describe a hypothetical property; describe only what yours has.

  1. 01

    Kitchen

    Weak: "kitchen" or "IMG_4471.jpg". Better: "Apartment kitchen." Best: "Kitchen with a seating island, stainless appliances and white quartz counters."

  2. 02

    Living room

    Weak: "living room luxury apartment downtown". Better: "Furnished living room." Best: "Living room with floor-to-ceiling windows and a door to the balcony."

  3. 03

    Bedroom

    Weak: "bedroom". Better: "Bedroom with a large window." Best: "Primary bedroom with a walk-in closet and carpet."

  4. 04

    Bathroom

    Weak: "bath". Better: "Bathroom with tub." Best: "Bathroom with a tub and shower combination and a single vanity." In an accessible unit, name the features: "roll-in shower with grab bars and a fold-down seat."

  5. 05

    In-unit laundry

    Weak: "amenities". Better: "Washer and dryer." Best: "Full-size stacked washer and dryer in a hall closet."

  6. 06

    Pool

    Weak: "pool pool apartments with pool". Better: "Community pool." Best: "Outdoor pool with lounge chairs and shaded cabanas." Google calls keyword lists in alt text a negative user experience that "may cause your site to be seen as spam" (Google Search Central).

  7. 07

    Fitness center

    Weak: "gym". Better: "Fitness center with equipment." Best: "Fitness center with treadmills, a free-weight area and a wall of mirrors."

  8. 08

    Resident lounge or clubhouse

    Weak: "clubhouse". Better: "Resident lounge." Best: "Resident lounge with a coffee bar, sofas and a shared work table."

  9. 09

    Building exterior

    Weak: "exterior". Better: "Apartment building exterior." Best: "Four-story brick building with a landscaped courtyard at the main entrance."

  10. 10

    Parking and garage

    Weak: "parking". Better: "Covered parking." Best: "Gated parking garage with an elevator to the residential floors."

  11. 11

    Pet amenities

    Weak: "pet friendly". Better: "Dog park." Best: "Fenced dog park with artificial turf and a pet wash station nearby."

  12. 12

    View from the unit

    Weak: "view". Better: "City view from balcony." Best: "View of the downtown skyline from an upper-floor balcony." If the view is from one unit or floor only, say "from an upper-floor unit" rather than implying every unit has it.

When a property image should be alt=""

WCAG 1.1.1 exempts decoration only when it "is implemented in a way that it can be ignored by assistive technology" (WCAG 2.2). In HTML that means alt="", not a missing attribute: "Every image should have an alt attribute, even if it's alt=""" (WebAIM). W3C's decision tree says to use an empty alt when an image is purely decorative or when its text or content is already in nearby text (W3C alt decision tree).

Common property-site images and the right treatment
ImageTreatmentWhy
Gallery photo of the unit, amenity or buildingDescriptive altIt is the content
Hero image behind a headline that already names the amenityalt="" or a short alt that adds something newDo not repeat the headline
Texture or stock image with no property informationalt=""Decorative
Photo inside a link ("View the Juniper floor plan")Alt names the destinationW3C: communicate the destination
Specials banner with the offer as image textPut the offer in real text; alt repeats it if the image staysWCAG 1.4.5 Images of Text (AA)

Galleries and carousels: pause, keyboard, announce

W3C's carousel tutorial sets four requirements: users must be able to pause movement, "all functionality, including navigating between carousel items, must be operable by keyboard", changes must be announced to screen-reader users, and focus must be managed "in a reasonable and comprehensible fashion" (W3C carousels tutorial). Under WCAG 2.2.2 (A), anything that moves automatically for more than five seconds alongside other content needs a way to pause, stop or hide it. A gallery that only swipes needs previous and next buttons that do the same job with a single tap: a flick that must follow a straight path is a path-based gesture under 2.5.1 Pointer Gestures (A), and a free drag falls under 2.5.7 Dragging Movements (AA). W3C's passing example for both is a carousel with forward and backward buttons (W3C Understanding 2.5.1, 2.5.7). The dragging rule is explained in the WCAG 2.2 guide.

Gallery test (five minutes)

  • Tab to the gallery: the previous, next and pause controls receive visible focus and have names ("Next photo", not "button").
  • Press Enter on next: the photo changes and a screen reader announces it, ideally with a position such as "photo 3 of 24".
  • Open the lightbox: focus moves into it, Escape closes it, and focus returns to the thumbnail you came from. Focus that jumps elsewhere on the page can fail 2.4.3 Focus Order (A), which requires an order that "preserves meaning and operability".

Floor plans and pricing grids: image plus text, data as a table

A floor plan is a complex image. W3C's guidance for diagrams and maps is a two-part alternative: a short alt that identifies the image and says where the long description is, and the long description itself in adjacent text, a figure caption or a linked page (W3C complex images tutorial). What is usually missing is the layout sequence.

Illustrative example

Alt: "Floor plan of The Juniper, one bedroom. Layout described below."

Text summary: "The Juniper: 1 bed, 1 bath, 712 sq ft. The front door opens to an entry closet and the kitchen, which has an island facing the living room. A short hall off the living room has the laundry closet, the bathroom and the bedroom with a walk-in closet."

Pricing and availability are data, so WCAG 1.3.1 Info and Relationships applies: information and relationships "conveyed through presentation can be programmatically determined or are available in text" (WCAG 2.2). Build the grid as an HTML table: th for header cells, td for data, scope where needed and a caption (W3C tables tutorial).

Illustrative example
Available one-bedroom homes at a sample property
UnitPlanSq ftBase rentAvailable
214The Juniper712$1,840Now
318The Juniper712$1,875Dec 1
402The Aspen790$1,990Jan 15

Mandatory fees belong in text beside the grid too; see fees in advertised rent.

Interactive unit and site maps: give the same units as a list

WCAG 2.1.1 (A) requires that "all functionality of the content is operable through a keyboard interface", and under 4.1.2 Name, Role, Value (A) each hotspot needs a name that "can be programmatically determined", so a screen reader announces "Unit 214, one bedroom" rather than "button". One of the examples in W3C technique H37 is a building floor plan built as an image map, each room a clickable area, with the alt "The building's floor plan. Select a room for more information about the purpose or content of the room" (W3C H37).

The most robust pattern is a list or table view of the same units, from the same data feed, reachable by a visible "View as list" toggle before the map. It is also the fallback when the map vendor's code is out of your hands. For panning, W3C's own example of a passing map has up, down, left and right buttons as well as dragging (W3C Understanding 2.5.7); the 24 by 24 CSS pixel target-size rule for small unit hotspots is explained in the WCAG 2.2 guide.

Virtual tours and video: which WCAG 1.2 criterion applies

It depends on sound: a silent walkthrough is "video-only", a narrated tour is "synchronized media". Criteria from WCAG 2.2.

Property media and the text alternative each needs
MediaCriterionWhat to publish
Silent drone or walkthrough video1.2.1 (A): "an alternative for time-based media or an audio track"A text description of what the video shows, in order
Narrated tour or leasing video1.2.2 Captions (A); 1.2.3 (A) and 1.2.5 Audio Description (AA)Accurate captions, and narration that describes what is on screen, or a described version
Background hero video that autoplays2.2.2 Pause, Stop, Hide (A) if it runs over five secondsA visible pause control; alt="" treatment if decorative
360 or self-guided 3D tourNo tour-specific criterion. Brynson's reading: 2.1.1 Keyboard (A) for the controls, 1.1.1 for the contentKeyboard controls, plus a room-by-room text description or a narrated, captioned guided video

W3C defines a full text alternative as "correctly sequenced text descriptions of time-based visual and auditory information" (W3C Understanding 1.2.3).

Chat widgets over galleries, and describing accessible units

Chat bubbles, tour schedulers and cookie banners float over photos and floor plans. WCAG 2.4.11 Focus Not Obscured (Minimum), new in 2.2 at AA, requires that a focused component "is not entirely hidden due to author-created content" (W3C, What's new in WCAG 2.2). Tab through the gallery with the widget open and closed.

For accessible units, a label such as "ADA unit" tells a renter less than the features do. Describe what is physically there, in listing copy, alt text and floor plan summary alike: "roll-in shower with grab bars", "step-free entry from the garage". Take the wording from the unit specifications and keep it identical on the website and every ILS.

Build an alt-text style guide for your photo library

One style guide, applied by whoever uploads photos, keeps alt text consistent across a portfolio and makes it reviewable.

Time needed: 2 hours

  1. 1

    Pick the source of truth

    Decide which system holds the amenity and unit feature names, usually the PMS or the marketing amenity list. Alt text uses those names and nothing else.

  2. 2

    Set the pattern

    Write the rule as space, then two or three distinguishing features, in one sentence, with no "photo of", no property name and no keyword list. Add a soft length limit, such as one line in your CMS field.

  3. 3

    Define decorative images

    List the image types that get alt="" (textures, icons beside labels, hero images that repeat a headline) so uploaders stop guessing.

  4. 4

    Add the complex-image rule

    Require a text summary beside every floor plan and site map, and a list view for every interactive map. Store the floor plan summary with the plan so it syndicates with it.

  5. 5

    Add the media rule

    Require captions on every narrated video, a text description for every silent video, and a room-by-room description for every 360 tour before it goes live.

  6. 6

    Fix the existing library

    Export image file names and current alt values, sort by empty, file-name and duplicate alt, and rewrite those first. Gallery images on the floor plan and amenity pages come before blog images.

  7. 7

    Review on a schedule

    Re-check alt text whenever an amenity changes, a photo is replaced or a renovation finishes, and sample a few properties each quarter. Record who checked and when.

Where Compliance360 fits

Compliance360 Web Accessibility scans each property's key pages nightly against WCAG 2.1 AA by default (or 2.2 AA) and flags images with no text alternative, with the location and the fix. Whether existing alt text is meaningful is a judgement a person makes, so it sits in the manual review checklist your team signs off. FrameCheck keeps the photo itself honest: it registers each image against the original in your archive and shows what changed, then a person decides. It does not write alt text. See the full Compliance360 suite.

Explore Compliance360 Web Accessibility
Compliance360 Web Accessibility report for a property website with issues by severity and WCAG level

Frequently asked questions

Describe what a renter would learn from the photo in one short sentence: the space and two or three features that set it apart, such as "Kitchen with a seating island and stainless appliances." Skip "photo of", the property name and keyword lists. Use your listing's amenity names.

Both. A floor plan is a complex image, so W3C recommends a short alt that identifies it and points to a longer description, plus that description as text nearby. Give beds, baths, size and the room order from the front door.

Every unit hotspot must be reachable and selectable by keyboard and announce its name, and panning needs a single-click alternative to dragging, such as arrow buttons. The most dependable fix is a "View as list" option that shows the same units from the same data feed as a table.

WCAG has no criterion written for 360 tours, but a tour embedded on the site is site content. Brynson's reading is that its controls fall under 2.1.1 Keyboard and its visual content under 1.1.1 Non-text Content. Publish a room-by-room text description or a narrated, captioned guided video next to the tour.

Only the words that describe the image. Google's own guidance warns that filling alt attributes with keywords is a poor user experience and may cause a site to be seen as spam. A precise description already carries the terms renters search for.

How we checked this

Written by the Brynson Research Team and checked against the primary sources below. Each source shows the date we last read it.

  1. Web Content Accessibility Guidelines (WCAG) 2.2, W3C. Accessed 2026-10-22.
  2. Guidance on Web Accessibility and the ADA, U.S. Department of Justice, Civil Rights Division, 2022-03-18. Accessed 2026-10-22.
  3. H37: Using alt attributes on img elements, W3C. Accessed 2026-10-22.
  4. An alt Decision Tree, W3C Web Accessibility Initiative. Accessed 2026-10-22.
  5. Complex Images tutorial, W3C Web Accessibility Initiative. Accessed 2026-10-22.
  6. Tables tutorial, W3C Web Accessibility Initiative. Accessed 2026-10-22.
  7. Carousels tutorial, W3C Web Accessibility Initiative. Accessed 2026-10-22.
  8. What's New in WCAG 2.2, W3C Web Accessibility Initiative. Accessed 2026-10-22.
  9. Understanding SC 2.5.7: Dragging Movements, W3C. Accessed 2026-10-22.
  10. Understanding SC 2.5.1: Pointer Gestures, W3C. Accessed 2026-10-22.
  11. Understanding SC 1.2.1: Audio-only and Video-only (Prerecorded), W3C. Accessed 2026-10-22.
  12. Understanding SC 1.2.3: Audio Description or Media Alternative (Prerecorded), W3C. Accessed 2026-10-22.
  13. The WebAIM Million: The 2026 report on the accessibility of the top 1,000,000 home pages, WebAIM, 2026. Accessed 2026-10-22.
  14. Alternative Text, WebAIM. Accessed 2026-10-22.
  15. Google image SEO best practices, Google Search Central. Accessed 2026-10-22.

This guide is general information, not legal advice. Laws and regulator guidance change; check the current rules for your properties with your counsel before acting.

Keep reading

Related guides

ExplainerAccessibility12 min readADA Website Compliance for Apartment and Multifamily Websites: What the Law Requires in 2026Yes, in practice. The Justice Department treats a rental office as a public accommodation under ADA Title III, and courts apply Title III to websites that connect renters to that office. No federal rule sets a technical standard for private housing sites, so WCAG 2.1 Level AA is the working benchmark, and 2.2 AA is the safer build target.Read the guide ChecklistAccessibility12 min readApartment Website Accessibility Checklist: WCAG 2.1 AA for Every Multifamily Page TypeCheck an apartment website page type by page type against WCAG 2.1 AA: gallery photos and floor plans need text alternatives, unit maps, tour schedulers and chat must work by keyboard, application fields need labels and readable errors, and text needs 4.5:1 contrast. Automated tools catch only part of WCAG, so mark which items a person must verify.Read the guide Reference tableAccessibility12 min readWCAG 2.2 for Apartment and Multifamily Websites: The New Criteria Mapped to Maps, Floor Plans and ApplicationsWCAG 2.2, published by W3C on October 5, 2023, keeps every WCAG 2.1 criterion except the obsolete 4.1.1 Parsing and adds nine new ones, six at Level A or AA. On apartment websites they hit sticky tour bars and chat bubbles that hide focus, draggable maps and sliders, small gallery controls, repeated application fields and portal logins.Read the guide ChecklistListing accuracy9 min readVirtual Staging and Listing Photo Policy Template for Apartment and Multifamily CommunitiesA virtual staging policy for an apartment community sorts every edit into three tiers: allowed without a label (lighting, color, cropping), allowed with a label and the original nearby (staging, added or removed furniture), and prohibited (features the unit lacks). It also covers model units, renderings, originals, refresh dates and who signs off.Read the guide
Compliance360 Web Accessibility

Find every property photo with no text alternative

Compliance360 Web Accessibility scans your property sites nightly, shows each image and control that fails, where it is and how to fix it, and gives your team a checklist for the judgement calls.