Accessibility
This site is designed and built against WCAG 2.2 level AA as its target. No independent audit has been performed, so this page describes measures and limitations — it is not a conformance claim.
Measures taken
- Semantic landmarks on every page (skip link, header/navigation, main, footer).
- The ownership explorer renders fully without JavaScript as a labeled tree plus the complete card list; with JavaScript it follows the treeview keyboard pattern (arrow keys to move, Enter to select, live-region announcements).
- Color pairs come from measured design tokens (body text at 16.7:1 on this surface); the one restricted pair is never used for body text.
- Forms associate errors with fields, move focus to an error summary, and never erase your input on failure.
- Focus is always visible; touch targets are at least 44×44 px.
- Reduced-motion preferences are honored; nothing on this site animates content critical to reading.
- Content renders at text level — no information is carried by images or color alone.
Known limitations
- Screen-reader testing so far covers a keyboard/announcement pass on the explorer, not a full multi-reader audit.
- The intake form depends on a separate local service in this staging build; when it is unreachable the form says so and keeps your input.
Report a barrier
If something on this site blocks you, tell us via the contact form and describe the page and what happened. Accessibility reports are treated as support requests, not feedback trivia.