Accessibility Statement

Our Commitment. Buildability™ is designed to be usable by the widest possible audience — including people with disabilities. We are working toward WCAG 2.2 Level AA as our standard and welcome feedback when we fall short.

1. Standard

ReadyPermit.AI, Inc. is working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, published by the World Wide Web Consortium. WCAG defines requirements for designers and developers to improve accessibility for people with disabilities, covering a wide range of recommendations across perceivable, operable, understandable, and robust use of web content.

This is a working target, not a conformance claim. A July 2026 audit found color-contrast, skip-link, and modal focus-management issues. The skip link and the dialog focus work have since shipped; a specific contrast gap remains and is described under Known Limitations. We re-audit as we ship.

2. What We Support Today

Keyboard navigation

Core flows — searching an address, viewing a Buildability Report, opening Geo™ responses, checking out, and navigating legal pages — are reachable and operable using a keyboard alone. Focus indicators are visible and follow a logical tab order. A skip link is the first tabbable element on every page. Modal dialogs share one primitive that moves focus in on open, contains Tab inside the dialog, closes on Escape, and returns focus to the control that opened it.

Screen readers and assistive technology

We aim to provide meaningful text alternatives, form labels, landmark regions, and ARIA attributes so that screen-reader users (including VoiceOver, NVDA, and JAWS) can navigate and understand the interface. Interactive components announce their role and state.

Color contrast and text sizing

We target WCAG 2.2 AA contrast ratios for text and essential UI in both light and dark themes, and our design tokens are checked against those ratios by an automated test on every build. One known gap remains, described under Known Limitations. Text resizes with the browser's zoom controls without loss of content or functionality.

Reduced-motion preferences

Decorative animations and transitions respect the prefers-reduced-motion user setting. Users who request reduced motion see a calmer interface without non-essential animation.

3. Known Limitations

We track accessibility as we ship. Areas currently under active improvement include:

• Color contrast — our tertiary text color meets AA on white surfaces (4.52:1) but falls below it on our tinted page background (4.15:1, against a 4.5:1 requirement). This affects small labels and captions that sit on the app canvas rather than on a white card. Primary and secondary text meet AA on every surface.
• Keyboard shortcuts — the command palette and agent shortcuts are listed in an in-app shortcut sheet, but are not yet remappable for users who cannot press chorded keys.
• Complex data visualizations (maps, charts) — we are expanding text-based equivalents for every meaningful chart.
• PDF exports — our goal is accessible PDFs; we are progressively adding tagged structure and alt text to generated documents.

If you encounter a barrier not listed here, please tell us — we treat accessibility reports as bugs, not feature requests.

4. Reporting an Accessibility Barrier

If any part of Buildability or ReadyPermit.ai prevents you or someone you work with from accomplishing a task, please let us know. We aim to respond within 2 business days and to resolve substantive issues on a prioritized schedule.

Email: team@buildability.us

When you report a barrier, the following information helps us resolve it faster (all optional): the page URL, the action you were trying to take, the assistive technology or browser configuration in use, and any error message or behavior you encountered.

5. Third-Party Content and Data

Buildability integrates data from federal, state, and local government sources (FEMA, USGS, EPA, Census Bureau, HUD, and others) and from commercial providers including Regrid, RentCast, and Mapbox. The accessibility of source content — for example, PDFs or map tiles hosted by a third party — can be outside our direct control. Where we can, we surface structured text alternatives in our own interface rather than relying on the underlying source presentation.

6. Feedback and Updates

This statement is reviewed on a regular cadence and updated when the product or our accessibility posture changes materially. The "Last updated" date at the top of this page reflects the most recent review. We welcome suggestions at team@buildability.us.