Aurum Estate

Legal

Accessibility Statement

Our intended conformance target, the practices we follow, known limitations, and how to report a barrier.

Template document — requires review by qualified counsel before it is relied upon

This page sets out the structure and the positions Aurum Estate intends to take. It is a drafting starting point, not executed legal terms, and it is not legal advice. The effective date below is a placeholder until counsel signs off. Do not rely on it for a compliance decision.

Real estate is a marketplace everyone has to be able to use. Accessibility is treated as a product requirement rather than a remediation project, and this statement records what we target, what we test, and what we know is still incomplete.

01Conformance target

Our target is WCAG 2.2 Level AA for this website and for the tenant storefronts and transaction interfaces inside the platform. This statement is written against that target, and conformance is not claimed for surfaces that have not yet been tested — including some partner-configurable areas described below.

02Practices we follow

  • Semantic HTML landmarks and heading order that reflect the actual document structure.
  • Keyboard operability for navigation, filters, forms, and dialogs, with no keyboard traps.
  • Visible focus indicators on every interactive element.
  • Color contrast checked in both light and dark themes, with information never conveyed by color alone.
  • Form fields with programmatically associated labels, error text announced to assistive technology, and errors that do not rely on color.
  • Text alternatives for meaningful images and decorative images marked as such.
  • Motion-reduced preferences respected for animated transitions.

03White-label theming and accessibility

Partners can configure brand colors, which creates a real accessibility risk: a brand palette can produce insufficient contrast. The platform constrains tenant theming so that text and interactive elements maintain contrast regardless of the palette chosen, and unsafe combinations are rejected rather than permitted with a warning.

04Known limitations

  • Third-party embedded content and partner-supplied documents may not be authored to the same standard, and we cannot control how a partner's own files are produced.
  • Third-party mapped search widgets and document viewers may have gaps we can only work around, not fix outright.
  • Complex data tables in analytics views are being reworked to improve screen reader navigation.
  • This statement has not yet been validated by an independent third-party audit.

05Assistive technology tested

Testing is performed with current versions of the major screen readers paired with their reference browsers, keyboard-only navigation, and operating-system zoom up to 200%. A summary of the most recent test pass is available on request.

06Reporting a barrier

If you encounter a barrier on this website or inside a partner marketplace, contact us with the page, the assistive technology you were using, and what happened. We aim to acknowledge within five business days and to resolve or provide an alternative in a documented timeframe.

Where a barrier affects a partner's own marketplace content or documents, we route the report to the responsible partner and assist them with remediation.

07Ongoing commitment

Accessibility checks are part of the release process rather than an annual review, and this statement is updated when test coverage changes. It is a working record of our posture, not a certification.

Need the executed version?

Current MSA, DPA, and SLA templates are provided during onboarding and can be sent to your reviewer on request.