Our commitment to making the platform usable for everyone. We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA.
Standard
WCAG 2.1 Level AA. These guidelines explain how to make web content more accessible to people with disabilities.
What we've implemented
Keyboard navigation, Every interactive element (buttons, links, form fields, modals, table rows) is reachable and operable via keyboard. Tab order follows visual layout. Modal dialogs trap focus.
Screen reader support, ARIA labels on navigation landmarks, form controls, and interactive widgets. Live regions announce toast notifications and loading state changes.
Color contrast, Text and interactive elements meet the 4.5:1 contrast ratio for normal text and 3:1 for large text against all backgrounds.
Reduced motion, All animations and transitions respect prefers-reduced-motion: reduce. Count-up animations, skeleton shimmers, and hover effects are suppressed when this preference is active.
Touch targets, On touch devices, all interactive elements meet the 44x44px minimum tap target size per Apple HIG and WCAG 2.5.5.
Focus indicators, Visible :focus-visible rings on all interactive elements using the gold outline pattern.
Skip links, "Skip to content" link on the landing page for keyboard users.
Semantic HTML, Proper heading hierarchy, landmark roles, and form labels throughout.
Known limitations
Map Explorer, The interactive WebGL map (MapLibre GL JS) has limited keyboard accessibility. Parcel selection and layer toggling require mouse interaction. We provide the Property Search view as a fully accessible alternative for finding and reviewing parcels.
3D Terrain View, The WebGL 3D viewer is not screen-reader accessible. It is a supplementary visualization, not required for any core workflow.
Charts, SVG charts (bar, donut) include basic titles but do not have full data table alternatives yet.
Feedback
If you encounter an accessibility barrier or have suggestions for improvement, please contact us: