Accessibility Statement

Version: 1.0 Effective Date: June 2026 Last Reviewed: June 2026

HOUSBE is committed to ensuring digital accessibility for everyone, including people with disabilities. We believe that searching, buying, renting, selling, listing, and financing property should be a seamless experience for every user — regardless of ability, age, device, connection speed, or assistive technology. Accessibility is not a feature we bolt on at the end; it is a principle we design, build, test, and maintain around. This statement explains what we do, how we do it, the standards we follow, the limitations we are aware of, and how you can reach us for help or to report a barrier.

1. Our Commitment

Accessibility is a core part of how we design and build HOUSBE. We work to ensure that our public website, account dashboards, property search, listing tools, deal rooms, messaging, forms, and AI assistant can be perceived, operated, understood, and used by the widest possible audience — including users who rely on screen readers, keyboard-only navigation, screen magnification, voice control, switch devices, and other assistive technologies. We treat accessibility as a continuous, organization-wide responsibility rather than a one-time project, and we factor it into our design reviews, development practices, and release process.

2. Scope of This Statement

This statement applies to the HOUSBE platform accessible at our primary domain and its associated subdomains, including the marketing pages, authenticated member areas, and interactive tools. Where we embed or link to third-party services — such as map providers, payment processors, video hosts, or social platforms — those services are governed by their own accessibility practices, which we do not control but actively encourage and, where possible, supplement with accessible alternatives.

3. Standards & Conformance

HOUSBE aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C). These guidelines explain how to make web content more accessible to people with a wide range of disabilities — visual, auditory, motor, speech, cognitive, language, learning, and neurological. Where the newer WCAG 2.2 success criteria apply, we incorporate them as part of our continuous improvement process. We also design with the principles of the Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act in mind.

WCAG is organized around four principles, often referred to as POUR. Content must be:

  • Perceivable — information and interface components must be presentable in ways users can perceive (for example, text alternatives and sufficient contrast).
  • Operable — interface components and navigation must be operable by everyone, including with a keyboard alone.
  • Understandable — information and the operation of the interface must be clear, predictable, and consistent.
  • Robust — content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies.

The sections below describe how HOUSBE addresses each of these principles in practice.

4. Accessibility Features at a Glance

The following capabilities are built into the HOUSBE experience to support a wide range of users:

Keyboard Navigation

All primary navigation, menus, links, buttons, and forms can be operated using a keyboard alone, with a logical focus order and visible focus indicators.

Screen Reader Compatibility

Semantic HTML, descriptive labels, alternative text, and ARIA attributes help content work with screen readers such as NVDA, JAWS, VoiceOver, and TalkBack.

Color Contrast & Typography

We maintain sufficient contrast between text and backgrounds and use clear, readable typography. Meaning is never conveyed by color alone.

Responsive Design

The platform adapts fluidly across desktop, tablet, and mobile, so content reflows and stays usable at any screen size and orientation.

Zoom & Text Scaling

Pages support browser zoom and larger text up to at least 200% without loss of content or functionality.

Accessible Forms & Controls

Form fields have associated labels, clear instructions, and accessible error messages. Controls expose their name, role, and state.

Reduced Motion

We respect the operating system "reduce motion" setting and minimize non-essential animation for users who prefer less movement.

Generous Touch Targets

Interactive elements are sized and spaced to be easy to tap or click, reducing accidental activation on touch devices.

5. Perceivable — Text, Media & Contrast

We make information available to more than one sense so it can be perceived in different ways:

  • Text alternatives: Images that convey information include descriptive alternative text, while purely decorative graphics are hidden from assistive technology to reduce clutter.
  • Color contrast: We target a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text and meaningful interface components and icons.
  • Not color alone: Status, errors, and required fields are communicated with text, icons, or patterns in addition to color.
  • Readable typography: We use clear typefaces, comfortable line spacing, and sufficient text size, and we avoid presenting essential content as images of text.
  • Media: Where we publish video or audio, we work to provide captions, transcripts, or equivalent text so the content is available to everyone.

6. Operable — Keyboard, Focus & Navigation

The platform can be operated without a mouse and is designed to be easy to move through:

  • Full keyboard access: Use Tab to move forward, Shift + Tab to move backward, Enter or Space to activate buttons and links, the arrow keys within menus and grouped controls, and Esc to dismiss dialogs.
  • Visible focus: A clear focus indicator shows which element is currently selected as you navigate.
  • Logical order: Focus moves in a sensible, predictable sequence that follows the visual layout.
  • No keyboard traps: You can move into and out of every component, and dialogs and menus manage focus so it is not lost.
  • Bypass blocks: Headings and landmark regions let assistive-technology users jump quickly to the main content and major sections.
  • Pointer-friendly: Actions that respond to clicks or taps do not rely on complex gestures, and accidental actions can generally be reversed.

7. Understandable — Clarity & Predictability

We aim to make HOUSBE easy to read, learn, and operate:

  • Plain language: We use clear wording and explain industry or technical terms where they appear.
  • Consistent navigation: Menus, controls, and layout patterns behave the same way across the platform so they are predictable.
  • Helpful guidance: Instructions, examples, and contextual hints accompany complex tasks such as creating listings, submitting leads, or completing a transaction.
  • Clear errors: When something goes wrong, we describe the problem in text, indicate the affected field, and suggest how to fix it.
  • Language: The page language is identified in the markup so assistive technology can pronounce content correctly.

8. Robust — Assistive Technology Compatibility

We build with standards-based, semantic HTML and apply ARIA roles, states, and properties only where native semantics are not enough. Interactive components expose their name, role, and value so assistive technologies can present and control them reliably. Dynamic updates — such as new messages, validation feedback, or status changes — are announced using appropriate live regions where relevant, so users are kept informed without losing their place.

9. Responsive Layouts & Touch Targets

HOUSBE is built with a responsive, mobile-first approach. Content, navigation, and controls reflow to fit the available space on phones, tablets, laptops, and large displays, and remain operable in both portrait and landscape orientations. Layouts are designed to work down to narrow widths (approximately 320 CSS pixels) without requiring horizontal scrolling for normal reading. Buttons, links, and form controls are given comfortable target sizes and spacing so they are easy to activate by touch, mouse, or stylus.

10. Zoom, Text Scaling & Visual Adjustments

You can adjust the presentation to suit your needs. Pages support browser zoom and increased text size up to at least 200% without loss of content or functionality, and content reflows rather than being clipped or overlapped. Because we use relative units for typography and spacing, the interface also responds to your browser's or operating system's default font-size preferences. The platform is compatible with operating-system level tools such as high-contrast modes, screen magnifiers, and custom cursor settings.

11. Motion, Animation & Visual Comfort

Some users experience discomfort, distraction, or motion sensitivity from animation. HOUSBE respects the "reduce motion" preference exposed by your operating system or browser (prefers-reduced-motion) and minimizes non-essential movement accordingly. Animations are used to support understanding rather than to convey essential information, and we avoid content that flashes in a way that could trigger seizures.

12. Forms, Errors & Interactive Controls

Forms are central to HOUSBE — from sign-up and login to leads, listings, and transactions. We design them to be accessible:

  • Labels: Every field has a visible, programmatically associated label; placeholder text is not used as the only label.
  • Instructions: Required fields, formats, and constraints are described in text before you submit.
  • Error handling: Validation messages identify the field in error, describe the issue, and are announced to assistive technology.
  • Grouping: Related controls (such as radio groups and multi-step flows) are grouped and labeled so their relationship is clear.
  • State: Custom controls (toggles, dropdowns, accordions, dialogs) expose their expanded, selected, or checked state to assistive technology.

13. Time Limits & Session Management

Where a process involves a time limit — for example, a security-related session timeout — we aim to warn you in advance and, where appropriate, allow you to extend the session, so you are not penalized for needing additional time to read or complete a task. We avoid unexpected changes of context and try to preserve your input where possible if a session needs to be re-established.

14. Accessibility Across HOUSBE Features

We apply our accessibility practices across the platform's key experiences, including:

  • Property search & listings: Search filters, results, and listing details are structured with headings and labels so they can be navigated and understood efficiently.
  • Dashboards: Account, agent, owner, and lender dashboards use consistent navigation, clear headings, and keyboard-operable controls.
  • Deal rooms & messaging: Conversations and document exchanges are designed to be operable by keyboard and screen reader, with status updates communicated in text.
  • Forms & lead submission: Buying, renting, selling, and lending request forms follow the form-accessibility practices described above.
  • Payments & wallet: Where payment is handled by a PCI-compliant third-party provider, we present accessible entry points and alternatives; the provider's own interface is governed by its accessibility practices.
  • AI assistant (Tiffany): Our conversational assistant is designed to be operable by keyboard, with text-based input and output that works with assistive technology, and is not the only way to complete essential tasks.

15. Supported Browsers & Assistive Technologies

HOUSBE is designed to work with current versions of major browsers and assistive technologies. We aim to support recent versions of:

  • Browsers: Google Chrome, Mozilla Firefox, Microsoft Edge, and Apple Safari on desktop and mobile.
  • Screen readers: NVDA and JAWS (Windows), VoiceOver (macOS and iOS), and TalkBack (Android).
  • Other tools: Browser zoom, screen magnifiers, operating-system contrast and text-size settings, voice control, and keyboard-only navigation.

Accessibility can depend on your specific combination of browser, assistive technology, and their versions. If you encounter an issue with a particular setup, please tell us — the details help us reproduce and fix it.

16. How We Test & Evaluate

We use a combination of methods to evaluate and improve accessibility:

  • Automated checks integrated into our development workflow to catch common issues early.
  • Manual review against WCAG success criteria during design and development.
  • Keyboard and screen-reader testing of key flows using the assistive technologies listed above.
  • Responsive and zoom testing across a range of screen sizes and magnification levels.
  • User feedback from our community, which we treat as an important signal and act on.

17. Ongoing Improvements

Accessibility is an ongoing commitment. As we add new features and update existing ones, we review them against our accessibility standards, test with assistive technologies, and prioritize the remediation of any issues we discover. We periodically re-audit the platform and update our practices and this statement as the platform evolves. Newly identified barriers are logged, prioritized by impact, and scheduled for resolution.

18. Known Limitations

Despite our best efforts, some content or components may not yet be fully accessible. Known areas we are working to improve include:

  • Embedded maps: Interactive map components provided by third parties may have limited keyboard or screen-reader support; we aim to provide text-based location details as an alternative.
  • Third-party widgets: Payment forms, video players, and social embeds follow their providers' accessibility behavior, which we do not fully control.
  • User-generated content: Listings, images, and documents uploaded by users may not always include complete text alternatives or accessible formatting.

If you encounter a barrier that is not listed here, please let us know using the details below so we can address it and offer assistance in the meantime.

19. Third-Party Content

HOUSBE integrates services from third parties — including mapping, payment processing, analytics, and media hosting — to deliver a full experience. These services maintain their own accessibility practices, which we do not control. We choose partners with accessibility in mind where feasible, provide accessible entry points and alternatives where possible, and welcome reports about third-party barriers so we can advocate for fixes or offer another path to complete your task.

20. Alternative Formats & Reasonable Accommodations

If you need information from HOUSBE in an alternative format, or require a reasonable accommodation to use the platform or complete a task, we are here to help. This may include providing content in a different format, walking you through a process, or offering an alternative way to achieve the same outcome. Contact us using the details in the next sections and describe what would help — we will work with you in good faith to find a solution.

21. Feedback & Reporting an Issue

We welcome your feedback on the accessibility of HOUSBE. Your input helps us identify and fix barriers we may have missed. When reporting an issue, the following details help us respond quickly, though none are required:

  • The page or feature where you experienced the problem (a URL is ideal).
  • A description of the barrier and what you were trying to do.
  • The device, browser, and any assistive technology you were using (with versions if known).

Our response commitment: We aim to acknowledge accessibility feedback within 5 business days and to work with you toward a resolution or a suitable alternative as quickly as we reasonably can.

22. Contact Us

To report an accessibility issue, request assistance, or ask for content in an alternative format, please use any of the following:

Accessibility Support

Accessibility Team: accessibility@housbe.com

General Support: info@housbe.com

Help Center: Contact HOUSBE Support

Address: HOUSBE, L.L.C., 900 N Federal Hwy, Ste 306, Hallandale Beach, FL 33009.

This Accessibility Statement reflects our current practices and is reviewed and updated periodically. It is provided for informational purposes and describes our good-faith, ongoing efforts to make HOUSBE accessible to all users.

Talk to Tiffany
Tiffany
×
Enter Deal Room

Welcome to your

HOUSBE Deal Room

Enter the Deal Room Press Continue and Choose Your Role
HOUSBE
Real Estate Deal Marketplace

Start Your Deal Room

OR
Secure & Private HOUSBE uses bank-level encryption to keep your information and transactions secure.

Need help? Our team is ready to assist you. Contact Support

housbe.com
Looking up your account…
Tiffany

Choose 2+ listings, tap Compare

or tap COMPARE (top bar).

Tiffany AI highlights what truly matters most.

Offer Accepted

Update the status and add a note for your team.
Choose the current status of this offer.
This helps your team stay aligned on what’s happening next.
0 / 1000
Add important details, next steps or any updates for your team.
Moving Forward
Waiting on Something
Client Notified
Next Step Defined

Document Verification

×
Invite link copied to clipboard!