Legal
Accessibility
Last updated August 21, 2026.
The short version
- We build to WCAG 2.2 Level AA, and we check it with a real browser before a site goes live rather than trusting a plugin.
- We do not use an accessibility overlay widget, and we will explain why if you ask.
- Found a barrier? Email hello@luxeveo.com. We will reply within 5 business days and tell you what we are doing about it.
Our commitment
A real estate website that a person cannot use is a listing they cannot see. We treat accessibility as part of whether the site works, not as a compliance chore bolted on at the end.
This applies to luxeveo.com, to the client portal at app.luxeveo.com, and to every website we build for a client.
The standard we work to
We target Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. In practice that means, on every page we ship:
- Every interactive control is reachable and operable with a keyboard alone, and shows a visible focus state.
- Text meets the contrast ratios the standard requires, measured against the actual rendered colors rather than assumed from the palette.
- Images carry meaningful alternative text, and decorative images are marked as decorative so a screen reader skips them.
- Headings run in order and describe the structure, so the page can be navigated by heading.
- Forms have real labels, and an error says what is wrong and how to fix it.
- Text stays readable and layouts stay usable down to a 320 pixel wide screen, and when text is enlarged.
- Motion respects
prefers-reduced-motion, so animation stops for anyone who has asked their device to stop it.
How we check
We render the real page in a real browser and measure it. Automated tooling catches perhaps a third of what matters, so it is a first pass, never the verdict. Keyboard navigation and screen reader behavior are checked by a person.
Why we do not use an overlay
Accessibility overlay widgets, the kind that add a floating icon promising instant compliance, do not fix the underlying page. They are widely criticised by the disability community, they can interfere with the assistive technology someone already uses and has configured, and they have not prevented litigation. We fix the page instead.
Where we fall short
Two honest limits:
- Content you supply. If you send us a photograph without a description or a PDF that was scanned rather than typed, we cannot make it accessible without your help. We will tell you when we hit this.
- Third party content. Listing data comes from your MLS in the form the MLS publishes it. Where a field is missing or an image has no description at source, we surface what is there and do not invent it.
We are not going to claim this site is perfectly conformant. Any site that claims that has usually not looked hard.
Tell us about a barrier
If something on this site or on a site we built stopped you, please tell us. It is the fastest way for it to get fixed, and we would rather hear it than not.
- Email hello@luxeveo.com with the page address and what happened.
- We will acknowledge within 5 business days.
- We will tell you what we found, what we are changing, and when.
Write to us at Luxeveo LLC, 66 W Flagler Street, Suite 900, PMB 12763, Miami, FL 33130 if you would rather use post.