Legal

Accessibility

Last updated: 13 May 2026. Our commitment to making Hartanahub usable for everyone.

Our commitment

Hartanahub aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. We treat accessibility as a feature, not a checkbox — the same level of care that goes into our data accuracy goes into making sure every screen reader, keyboard user, and low-vision user can use the product.

What we've built in

  • Keyboard navigation — every interactive element is reachable via Tab/Shift-Tab, with a visible focus ring. Modals trap focus and restore it on close.
  • Screen-reader labels — every icon-only button has an aria-label; every form field is programmatically associated with its label via a shared FormField wrapper.
  • Skip-to-main link — the first interactive element on every page jumps past the navigation.
  • Colour contrast — both the polished blue app theme and the cinematic-warm marketing theme target a 4.5:1 ratio for body text and 3:1 for large text, in both light and dark mode.
  • Status badges use icons alongside colour so colour-blind users can distinguish Upcoming / Past / Sold / Unsold.
  • Reduced motion — scroll-reveal animations respect prefers-reduced-motion.
  • Mobile inputs are sized at 16px so iOS Safari doesn't auto-zoom on focus, and tap targets are at least 44×44px.
  • Forms show inline error messages tied to the field via aria-describedby and aria-invalid.
  • Themed dialogs — we use a shared modal wrapper, never window.confirm() (unstyled and unreliable in iOS PWA).

Known gaps we're working on

  • Map markers on /near-me rely heavily on visual scanning. A list-view fallback for the same data is a planned addition.
  • Some chart visualisations (e.g. price trend) currently lack a tabular fallback.
  • Bahasa Malaysia translations are not yet available; the interface is English-only at launch.

Tools used in testing

We test with VoiceOver (macOS, iOS), TalkBack (Android), keyboard-only navigation in Chrome and Safari, and the Lighthouse + axe DevTools accessibility audits in CI before each deploy.

Reporting an issue

If you encounter a barrier using Hartanahub — with a screen reader, keyboard, magnifier, or any assistive tool — please tell us. The fastest path is the in-app Report a bug form (category: Accessibility), or email hello@hartanahub.com. We aim to acknowledge within two business days and to ship a fix or a documented workaround within 30 days, depending on complexity.

Standards reference

WCAG 2.2 quick reference · WAI-ARIA Authoring Practices.