Do this today
A Real Estate Website Accessibility Checklist You Can Run Yourself
Ten checks you can complete in an afternoon, without buying anything or hiring anyone.
Part of the Real Estate Website Accessibility guide · Last reviewed 2026-08-09
You can find most of your website's accessibility problems yourself, today, without buying anything. WebAIM tested one million home pages in February 2026 and found that six error types account for 96% of all detected failures: low contrast text, missing image alt text, missing form labels, empty links, empty buttons, and missing document language. Every one of those is findable with a free scanner or by pressing Tab. This page is those checks in the order worth doing them, with the real estate specifics that generic checklists miss, and an honest note on where self-testing stops being enough.
Key takeaways
- Six error types account for 96% of all accessibility failures WebAIM detected across one million home pages in February 2026.
- A free scanner such as WAVE finds most contrast, alt text, and label problems in minutes, on any page you point it at.
- Automated tools detect only a portion of issues and cannot judge whether alt text is meaningful, so a clean scan is a floor rather than a certificate.
- The keyboard test needs no tools: press Tab through your contact page and try to submit the form without touching the mouse.
- Fix the contact form first, because it is where an inaccessible site costs you an enquiry directly.
- Content fixes work on any platform. Structural problems in template markup are the point where self-testing hands off to a developer or a rebuild.
Check 1: Run a free scanner on three pages
Start with WAVE, the free web accessibility evaluation tool published by WebAIM at Utah State University. Enter a URL and it marks up the page with icons showing errors and warnings.
Scan three pages rather than one, because they fail differently: your home page, one listing or property detail page, and your contact page. The home page carries your design decisions, the listing page carries your IDX component, and the contact page carries your forms.
Look at the errors first and ignore the warnings on this pass. Errors are things WAVE is confident are wrong, such as an image with no alt attribute or a form input with no label. Warnings need human judgment and will drown you if you start there.
Understand the ceiling on this result before you take comfort from it. Automated tools detect a portion of accessibility problems, and they check whether alt text exists rather than whether it makes sense. A photo of a kitchen with alt text reading image1.jpg passes the automated check and tells a blind visitor nothing.
Check 2: Press Tab through your contact page
This one needs no tools at all and finds problems no scanner will. Open your contact page, put your mouse somewhere you cannot reach, and press the Tab key repeatedly.
You are watching for three things. Can you see where you are, as a visible outline moving from link to link? Can you reach every field, the message box, and the submit button? Can you actually submit the form using only the keyboard, pressing Enter or Space on the button?
If the focus outline is invisible, that is a real barrier and usually a deliberate one, because a stylesheet somewhere removed it for looking untidy. If Tab skips your submit button, a keyboard user cannot send you a message. If the focus jumps somewhere unexpected, the reading order does not match the visual order.
Repeat the same test on your property search filters, which is where custom controls commonly fail. A filter built from styled div elements rather than real buttons looks identical and cannot be operated by keyboard at all.
Check 3: Fix your form labels
WebAIM found missing form input labels on 51% of the home pages it tested. On an agent site this is the highest-cost failure in the whole list, because the form is how a visitor becomes a lead.
The usual cause is a design that looks clean: placeholder text inside the box saying Your name, with no label above it. A screen reader may announce nothing but an edit box, and the placeholder vanishes as soon as the visitor starts typing, which also hurts people with memory or attention difficulties.
The fix is a real label element tied to the input, which most website builders expose as a field label setting. Visible labels help everyone, so this is not a change that only serves screen reader users.
Check every form on the site, not just the contact page. The valuation request, the newsletter signup, the property search box, and the showing request form all count, and the ones embedded from third-party tools are the ones most often missed.
Check 4: Write alt text that says something
Missing alt text appeared on 53.1% of pages WebAIM tested. Alt text is the description a screen reader reads in place of an image, and on a real estate site it is unusually important, because photographs carry much of the information.
Three rules cover almost every case on an agent website:
- Describe what is in the photograph, not the file name and not the address. A kitchen with white cabinets and an island is useful. IMG_4471 is not, and 123 Main Street repeated on twelve photos is not either.
- Mark purely decorative images as decorative, with an empty alt attribute, so a screen reader skips them instead of announcing a background texture.
- Give your headshot a description with your name in it, since it is often also a link to your about page.
Check 5: Test your colour contrast
Low contrast text was the single most common failure WebAIM found, on 83.9% of pages. It is also the easiest to fix, because it is a colour value.
WCAG 2.1 sets the numbers precisely under success criterion 1.4.3, Contrast (Minimum), at Level AA: normal text needs a contrast ratio of at least 4.5 to 1 against its background, and large text needs at least 3 to 1. WebAIM's free contrast checker computes the ratio when you enter two colour values.
On agent websites the offenders are predictable. Light grey body text, which a designer chose because black felt harsh. White text over a photograph, where contrast changes across the image and fails wherever the photo is bright. Brand-coloured buttons where the label is a slightly different shade of the same colour.
This one also has a business case beyond compliance. Everybody reads low contrast text worse, particularly on a phone screen outdoors, which is exactly how buyers browse listings.
Check 6: Look at your headings and page language
Screen reader users navigate long pages by jumping between headings, the same way a sighted visitor scans. That only works when headings describe structure rather than being chosen for their size.
The common failure is using a large heading tag because the text needed to look big, or skipping from a top-level heading straight to a third-level one. Each page should have one main heading naming what the page is, with section headings nested under it in order.
While you are in the markup, check that the page declares its language. WebAIM found this missing on 13.5% of pages. It is a single attribute on the html element, and without it a screen reader may read English content with the wrong pronunciation rules. Most website builders expose it as a site language setting.
Check 7: Confront the IDX component
Run your scanner on a listing page and the results will often look worse than your home page. This is usually not your fault, and it is also the part you can least fix yourself.
IDX property search is embedded from your board or a third-party provider, renders through JavaScript after the page loads, and generally cannot be edited by you. Automated scanners may report little on it precisely because they cannot see inside it, which reads as a pass and is not one.
The right action here is a vendor question rather than a code change. Ask your IDX provider what accessibility testing their component has had and whether they publish a conformance report, and get the answer in writing. If they have one, you have documentation. If they have nothing, you have learned something important about a component sitting on your most valuable pages, and the dedicated IDX page in this hub covers what to do next.
Check 8: Publish an accessibility statement
This is the cheapest item here and the only one that helps a visitor who hits a barrier you have not fixed yet.
The National Association of REALTORS recommends that members post a clear accessibility statement offering direct assistance to anyone unable to take advantage of services offered on their website, including home search. Keep it short and honest: say you are working to make the site usable for everyone, and give a phone number and an email address that reach a real person.
Do not claim conformance you have not verified. A statement asserting the site fully meets WCAG 2.1 AA, published on a site that has never been audited, is a false claim on the record. Saying you are working toward it is accurate and costs you nothing.
Where self-testing stops
Everything above is genuinely doable in an afternoon and will resolve most of what an automated scan finds. Being clear about the limits matters more than selling you the checklist.
Automated testing catches a portion of accessibility issues. It cannot tell you whether your alt text is meaningful, whether your reading order makes sense, or whether a custom control announces its state correctly. Only testing with an actual screen reader, ideally by someone who uses one daily, answers those.
The other boundary is structural. Contrast, alt text, labels, and an accessibility statement are content edits available on almost any platform. Headings baked into a template, custom controls built from div elements, and content that only exists after JavaScript runs are decisions inside the markup. On a platform that does not let you edit markup, there is no content-level fix, and that is the point where this becomes a developer conversation or a rebuild rather than an afternoon.
| # | Check | Tool needed | Time | Fixable yourself? |
|---|---|---|---|---|
| 1 | Scan three pages | WAVE (free) | 10 minutes | Finding, yes |
| 2 | Keyboard test the contact page | None | 5 minutes | Sometimes |
| 3 | Fix form labels | Site editor | 30 minutes | Usually |
| 4 | Write real alt text | Site editor | 1 to 2 hours | Yes |
| 5 | Check colour contrast | WebAIM contrast checker (free) | 20 minutes | Usually |
| 6 | Check headings and page language | Site editor | 20 minutes | Sometimes |
| 7 | Question the IDX vendor | 10 minutes | No, vendor task | |
| 8 | Publish an accessibility statement | Site editor | 20 minutes | Yes |
Failure rates behind checks 3 to 6 come from WebAIM's Million report, February 2026. Times are the order of magnitude for a typical agent site, not a measured average.
Frequently asked questions
What is the fastest way to check if my real estate website is accessible?
Run the free WAVE tool from WebAIM on three pages: your home page, a listing page, and your contact page. It takes about ten minutes and flags most missing alt text, unlabelled form fields, and contrast failures. Then press Tab through your contact page without using the mouse. Those two checks find the majority of what automated testing can detect, at no cost.
Are free accessibility scanners good enough on their own?
They are a good starting point and not a certificate. Automated tools detect a portion of accessibility problems and cannot judge meaning, so an image with alt text reading photo1.jpg passes the automated check while telling a blind visitor nothing. Use a scanner to find the mechanical failures, then test with a keyboard yourself, and treat a clean scan as a floor rather than proof.
What contrast ratio does text on my website need?
WCAG 2.1 success criterion 1.4.3 at Level AA requires a contrast ratio of at least 4.5 to 1 between normal text and its background, and at least 3 to 1 for large text. WebAIM publishes a free contrast checker that computes the ratio from two colour values. Low contrast text was the most common failure in WebAIM's February 2026 study, appearing on 83.9% of the one million home pages tested.
What should alt text say on a real estate listing photo?
Describe what is visible in the photograph rather than repeating the address. A kitchen with white shaker cabinets and a marble island tells a blind visitor something useful, while 123 Main Street repeated across twelve images tells them nothing about any of them. Mark purely decorative images with an empty alt attribute so a screen reader skips them instead of announcing them.
How do I test my website with only a keyboard?
Open your contact page, move the mouse out of reach, and press Tab repeatedly. Watch for a visible outline showing where you are, check you can reach every field and the submit button, and confirm you can send the form by pressing Enter or Space. If the outline is invisible or Tab skips the button, you have found a real barrier that no automated scanner would have reported as clearly.
Why does my listing page score worse than my home page?
Because the listing page contains the IDX component you did not build. Property data arrives through a third-party feed that renders after the page loads, and its markup is usually outside your control. Scanners may also report little on it because they cannot see inside it, which looks like a pass. Ask your IDX provider in writing what accessibility testing the component has had.
Can I fix accessibility problems myself or do I need a developer?
It splits cleanly. Contrast values, alt text, form labels, page language, and an accessibility statement are content edits available in most website builders, so you can do those yourself. Headings baked into a template, custom controls built from div elements instead of real buttons, and JavaScript-only content live in markup you may not be able to edit, and those need a developer or a platform change.
How often should I re-check my website for accessibility?
Re-scan whenever you change the site's design or add a new template, since a new theme can reintroduce contrast and heading problems across every page at once. Beyond that, a check every six months is reasonable for a site where you are mainly adding listings and posts. Any new embedded tool, such as a chat widget or a booking form, deserves its own scan when it goes in.
Does an accessibility statement need to claim WCAG conformance?
No, and claiming conformance you have not verified is a mistake. Write that you are working to make the site usable for everyone and give a phone number and email that reach a person, which is what NAR recommends members provide. Asserting full WCAG 2.1 AA conformance on a site that has never been audited puts a false claim on the record about your own business.
Which fix should I make first if I only have an hour?
Fix your contact form labels. It is the page where an inaccessible site costs you a lead directly, missing form labels appeared on 51% of pages in WebAIM's February 2026 study, and the change is usually a field label setting in your site editor rather than code. Visible labels also help every visitor, so the benefit is not limited to screen reader users.
Related pages in this guide
Related reading
Sources
Every claim on this page that could be checked against a primary source is linked below. Where something is not publicly documented by a vendor, the page says so rather than filling the gap with an estimate.
- The WebAIM Million: An annual accessibility analysis of the top 1,000,000 home pages (WebAIM, Utah State University (published February 2026))
- WAVE Web Accessibility Evaluation Tool (WebAIM, Utah State University)
- How to Meet WCAG 2.1 (Quick Reference) (World Wide Web Consortium (W3C))
- WebAIM Contrast Checker (WebAIM, Utah State University)