Havara: Accessibility Statement

Effective October 6, 2026

Havara is used by people who did not choose it. A resident joins because their homeowners' association adopted it, and the notices, dues records and violation cases they receive through it are not optional reading. That is the reason this page exists: when the software is the only door to something a person has to deal with, the door has to open for them.

What we aim for

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA on the Havara mobile app, the board console, and this website.

We say "aim to conform" deliberately. We do not claim to be compliant, we do not claim to be certified, and no third party has audited us. Anyone who tells you a piece of software is fully accessible is describing an intention, not a measurement. What we can tell you is what we test, what we found, and what is still open.

What we actually test

• Contrast. Every text colour against the surface it lands on, measured with a WCAG relative-luminance calculation at 1440px and 375px, not judged by eye. The mobile app carries this as an automated test that fails the build.
• Names on controls. Every button, link and form field is checked for a name a screen reader can announce. A placeholder is not a label, and we do not count it as one.
• Keyboard. The console is walked with the keyboard alone, with a visible focus indicator required at every stop.
• Text size. The mobile app respects the text size set on your phone. The website and console reflow to 375px without a horizontal scrollbar.
• Headings and structure. Page heading order, so navigating by heading produces a real outline.

Known limitations, honestly

This list is the point of the page. It is what we know is not right yet.

• Your community's own documents. Governing documents (CC&Rs, bylaws, minutes) are uploaded by your association, not written by us. Many are scans with no text layer. We run optical character recognition so the AI "Ask" feature can read them, but the original PDF you download is the file your board provided, and we cannot make an inaccessible scan accessible.
• Generated answers. The "Ask" feature returns generated text with citations. It is a reading aid, never a legal answer, and it inherits whatever the source document's structure is.
• Photographs uploaded by members. Violation-case photos, avatars and message attachments are added by residents and boards. We do not require alternative text on them today, so a screen-reader user may reach an image with no description. We are treating this as an open item rather than pretending it is solved.
• Third-party payment pages. Community subscription checkout is handled by Stripe on Stripe's own pages. We do not control their markup.
• No formal audit. Our testing is automated checks plus our own manual passes. It is not an independent evaluation, and automated tools find roughly a third of accessibility problems on their own.

If something blocks you

Tell us, and we will treat it as a defect rather than a request.

Write to support@havara.app and say what you were trying to do, what got in the way, and what you use to browse if you know it (VoiceOver, TalkBack, a screen magnifier, keyboard only). You do not need to know the technical name for the problem. "I cannot tell which field is wrong" is a complete report.

If a barrier stops you from something with a deadline, such as acknowledging a notice or responding to a violation case, say so and we will give you another route to it while we fix the underlying problem.

Technical notes

• Standard: WCAG 2.2, Level AA (aim, not a claim of conformance).
• Surfaces covered: the Havara apps for iOS and Android, the board console at app.havara.app, and this website.
• Approach: automated contrast and accessible-name checks in our build, plus manual keyboard and screen-reader passes.
• This statement was last reviewed: 2026-10-02.