Accessibility

Accessibility Statement

Last updated: August 2026 · Next review: February 2027

Civexa is a feasibility screening tool for real-estate development in the Puget Sound region. It is used by developers, architects, agents, and homeowners, and we want all of them to be able to use it — including people who navigate by keyboard, use a screen reader, rely on magnification, or need reduced motion.

This statement describes where we actually are, not where we would like to be. It names the parts of the product that are not yet accessible, because a statement that only listed successes would not be useful to anyone deciding whether they can rely on Civexa.

Conformance status

Civexa is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means most of the product meets the standard, and some parts — listed under Known limitations below — do not yet.

We deliberately do not claim full conformance. Automated testing catches roughly a third of WCAG issues; the rest require manual and assistive-technology testing that we have only partly completed. Claiming more than we have verified would make this document worthless.

What we have done

• Keyboard operation. Every interactive control is reachable and operable by keyboard. Focus is always visible. Dialogs trap focus while open, close on Escape, and return focus to the control that opened them.
• Skip link. A "Skip to content" link is the first stop on every screen, so keyboard users are not forced through the navigation on each page.
• Colour contrast. Every text and background pair in the product's colour system is checked against the 4.5:1 AA threshold — in both light and dark themes — and the check runs automatically on every code change.
• Reduced motion. Animation is explanatory, never decorative, and is disabled entirely when the operating system requests reduced motion.
• Text and zoom. Body text is set in relative units and the page reflows without horizontal scrolling down to a 320 px viewport. Pinch-zoom is never disabled.
• Structure. Pages use real landmarks and headings in order, so screen reader users can navigate by region and heading rather than reading linearly.
• Forms. Every input has a visible, associated label. Errors appear next to the field they concern and are announced, not shown only by colour.
• Targets. Interactive controls are at least 44 px in their smallest dimension.

Known limitations

These parts of Civexa are not yet accessible to everyone. We list what the barrier is and what to do instead.

• The interactive parcel map is rendered to a canvas by Mapbox GL and is not navigable by screen reader, and its overlays cannot be read as text. Alternative: every figure the map illustrates — lot size, dimensions, zoning, environmental flags, transit distance — also appears as text in the report body and in the downloadable PDF. No information exists only on the map.
• The 3D buildable-envelope view is a canvas rendering with the same limitation. Alternative: the same envelope is given numerically — net buildable area, footprint, stories, FAR, height limit — directly beneath the illustration.
• PDF reports are not yet tagged for accessibility, so heading structure and reading order are not exposed to screen readers. Alternative: the full report is available as a web page, which is structured and does work with assistive technology. Tagging the PDF is on our roadmap.
• We have not yet completed screen reader testing. Our automated checks pass, and we have tested by keyboard, but we have not yet run a full pass with VoiceOver, NVDA and JAWS. Until we have, we cannot claim the experience is good with those tools — only that the underlying markup is sound.
• Payment is handled by Stripe Checkout, and mapping by Mapbox. Those pages and components are outside our control; we rely on their own accessibility work.

How we test

Accessibility checks run automatically as part of our deployment gate, not as a periodic audit. A change that breaks them does not ship.

• Automated axe-core testing against WCAG 2.0 and 2.1, Level A and AA, on every screen of the application and the public site, in both light and dark themes, at desktop and mobile widths.
• A colour-contrast check over the whole design system, evaluated as data rather than by eye, covering both themes.
• Static checks that the keyboard focus trap, the skip link, the visible focus ring and the reduced-motion contract cannot be removed by a later edit.
• Manual keyboard walkthroughs of the sign-in, search, report and account flows.

Tell us about a barrier

If any part of Civexa is unusable for you, we want to hear about it — including things this statement does not mention. That feedback is the fastest way for us to find what our testing missed.

Email contact@civexa.us with the page or feature, what you were trying to do, and the assistive technology you use if that is relevant. We aim to respond within five business days and to tell you either when a fix will land or how to get the same information another way in the meantime.

If you need a report for a specific parcel and cannot obtain it through the product, email us the address and we will run it and send you the results directly, at no charge.

Scope and preparation

This statement applies to the Civexa web application at app.civexa.us and the public site at www.civexa.us.

It was prepared in August 2026 using a self-evaluation: automated testing with axe-core across every screen, a programmatic audit of the colour system, and manual keyboard testing. It has not been reviewed by an independent third party. We review it at least every six months and whenever a substantial change ships.