Commitment
We design and test major public pages with accessibility in mind, guided by the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA principles: perceivable, operable, understandable, and robust. We improve issues iteratively as we ship product changes rather than treating accessibility as a one-time audit.
What we work toward
- Semantic headings, landmarks, and labels on core templates (search, listing detail, account shell, tools)
- Keyboard reachability for primary navigation, search, listing tabs, and account flows
- Visible
:focus-visiblestates and adequate colour contrast on key UI - Text alternatives for meaningful images where we control the asset
- Support for zoom, responsive layouts, and mobile safe areas on phones and tablets
- Respect for
prefers-reduced-motionwhere animations are non-essential - ARIA patterns for composite widgets (for example listing detail tabs with roving tabindex)
Listing detail & tools
Property detail pages use a sticky tab list (Overview, Details, Area, Visit, Finance, Tools) so related content is grouped without forcing a single endless scroll. Tabs follow the WAI-ARIA tabs pattern where implemented: arrow keys move between tabs, Tab moves into the active panel, and only the selected tab stays in the page tab order. Calculators and inquiry forms are separate destinations with standard labels and buttons.
Known limitations
Some experiences are harder to fully equalize and may still present barriers:
- Interactive maps — pin-dense map search can be difficult with screen readers or fine motor constraints; list and filter views are the parallel path.
- Third-party embeds — media players, virtual tours, or widgets from partners may not meet the same standard as our first-party UI.
- User-generated content — agent and builder photos, PDFs, and free-text descriptions vary in quality and alt text.
- Dense calculators — multi-field mortgage and tax tools are improved over time; feedback on specific fields helps prioritization.
- Live chat or experimental widgets — if introduced, they may lag the accessibility level of core templates until hardened.
Assistive technology
We test major flows with current versions of common browsers plus screen readers such as VoiceOver and NVDA on a sampling basis. Compatibility can still differ by OS, browser, and AT version. If a flow works in one combination and not another, include those details in your report.
Request assistance or report a barrier
If you encounter a barrier, tell us:
- The page URL
- What you were trying to do
- The assistive technology, browser, and device you use
- Whether the issue blocks a core task (search, contact, sign-in, booking)
We will respond as promptly as we can and prioritize fixes that block core tasks.
Formal feedback
This statement is informational and does not create additional legal rights beyond applicable law. We review it when we make material accessibility-related product changes. Related pages: Platform security, Privacy Policy.