HOA Notes should be usable by everyone who needs it.

We target conformance with WCAG 2.1 Level AA across every public page of hoanotes.com, including the marketing site, the order form, the brokerage seat-license intake form, the policy pages (Privacy, Terms, Security, Subprocessors), and the brief-delivery experience at briefs.hoanotes.com. Level AA is the standard most US public-accommodation and procurement frameworks reference, and it is the standard we hold ourselves to.

Accessibility is treated as a release-gating concern, not an afterthought. New pages and form fields are reviewed against this target before they ship, and changes that would introduce a known barrier are not shipped without a fix.

The site is built from the ground up around the practices below. These are the load-bearing measures; the list is not exhaustive.

• Semantic HTML. Pages use real headings, lists, landmarks (header, nav, main, footer), and form controls rather than styled div soup. Screen readers and browser reader modes can map the structure of every page.
• One h1 per page. Each page has exactly one top-level heading describing what the page is, and subsequent headings nest in order without skipping levels. The order form's heading hierarchy mirrors its fieldset structure.
• Sufficient color contrast. Body text, headings, link text, and form labels meet WCAG 2.1 Level AA contrast ratios (4.5:1 for normal text, 3:1 for large text and non-text UI components) against the page background. Focus indicators are visible on every interactive element.
• Keyboard navigation. Every interactive element - navigation links, the order form's fields and file picker, the click-wrap acceptance checkboxes, the submit button - is reachable and operable with a keyboard alone. Tab order follows the visible reading order.
• Skip link. Each page exposes a "Skip to main content" link as the first focusable element so keyboard users can bypass the site header and primary navigation on every page.
• Alt text on meaningful images. Images that convey information have descriptive alt attributes. Decorative graphics (wordmark glyphs, divider rules) are marked aria-hidden="true" so they are not announced.
• Form labels and help text. Every input has a visible, programmatically associated label. Help text is wired up with aria-describedby so assistive technologies announce it alongside the field. Required fields are marked with aria-required="true" in addition to the visible asterisk.
• Respect for user preferences. We honor prefers-color-scheme and prefers-reduced-motion. We do not use auto-playing animation, blinking content, or content that scrolls without user input.
• Language attribute. Every page declares lang="en" so screen readers pronounce content correctly.

No known significant issues. As of the last review date below, we are not aware of any open WCAG 2.1 Level AA conformance gaps on hoanotes.com or in the order-form flow.

That said, accessibility is a moving target: browser behavior changes, assistive-technology behavior changes, and small content edits can introduce regressions we have not caught. If you encounter a barrier - an unlabeled control, a focus trap, a low-contrast element, a screen reader that announces something nonsensically, anything - please tell us. We treat these reports as defects, not as feature requests.

One scoping note: the buyer-facing brief PDF delivered at briefs.hoanotes.com is a generated document. We tag headings, include text-extractable content (not scanned images), and aim for the same conformance target, but PDF rendering across screen readers is less uniform than HTML. If you need an HTML or plain-text rendering of a brief for accessibility reasons, contact us and we will provide one at no additional cost.

The canonical reporting channel is our contact form at /contact?subject=accessibility. Use the subject "accessibility" so the report routes correctly. Please include, where you can:

• The page URL where you encountered the issue.
• What you were trying to do (for example, "submit the order form," "read the pricing section").
• The barrier you hit (what you expected to happen, what actually happened).
• Your browser, operating system, and any assistive technology you were using (screen reader name and version, magnification, voice control, etc.).

If you would rather not use the contact form and you are an active buyer who has already started or completed an order, you can also reply to any email we have sent you about your order - that reaches the same inbox. The contact form is the canonical channel, but the order-email reply path is a working interim while the contact page is being built.

Our service commitments. We acknowledge accessibility reports within one business day and provide a substantive response - either a fix, a workaround, or a timeline - within five business days. We do not require a formal complaint to act on a report.

This statement and the conformance posture behind it are reviewed at least every twelve months, and any time we ship a substantial change to the marketing site, the order form, or the brief-delivery experience. Reviews include manual keyboard-only walkthroughs of each critical-path flow, an automated accessibility scan, and a screen-reader pass on the order form. Findings are tracked as defects and fixed before the next public release.

Last reviewed: May 10, 2026.

Next scheduled review: no later than May 10, 2027, or sooner if a substantive site change is shipped.