PrecisionDocs

Accessibility

PrecisionDocs accessibility statement, WCAG commitments, known limitations, and support contact.

PrecisionDocs AI LLC is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply the relevant accessibility standards.

Conformance Target

We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. These guidelines explain how to make web content more accessible to people with a wide range of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

Note: Accessibility conformance is an active and ongoing effort. Some features may not yet be fully tested with all assistive technologies. We welcome feedback on any barriers you encounter.

Measures Taken

We have implemented the following measures to support accessibility:

  • Semantic HTML structure with proper heading hierarchy.
  • Skip-to-main-content navigation link.
  • Keyboard-navigable interface with visible focus indicators.
  • ARIA attributes on interactive components (modals, dialogs, alerts, status messages).
  • Screen-reader-only labels on form inputs and icon-only buttons.
  • Support for the prefers-reduced-motion media query to reduce or disable animations.
  • Sufficient color contrast ratios for text and interactive elements.
  • No reliance on color alone to convey information.

Known Limitations

While we strive for comprehensive accessibility, the following areas have known limitations:

  • Interactive map components: The parcel selection map (MapLibre GL JS) relies on mouse interaction for parcel picking and boundary visualization. Keyboard and screen reader alternatives for map interaction are limited.
  • PDF report downloads: Generated DOCX and PDF reports may not meet full document accessibility standards (e.g., tagged PDF structure, alt text on all images).
  • Complex data tables: Some dynamically generated data tables in chat responses may not have fully programmatic header associations.
  • Third-party content: Government API data and externally sourced ordinance content may not meet accessibility standards when displayed in the platform.

Testing Methodology

We evaluate accessibility through a combination of:

  • Automated testing tools (axe-core, Lighthouse).
  • Manual keyboard navigation testing.
  • Screen reader testing (NVDA, VoiceOver).
  • Review against WCAG 2.2 Level AA success criteria.

Feedback & Contact

We welcome your feedback on the accessibility of PrecisionDocs. If you encounter accessibility barriers or have suggestions for improvement, please contact us:

We aim to respond to accessibility feedback within 5 business days and will work with you to find a reasonable solution.

Remediation

When we identify accessibility issues, we prioritize them based on severity and impact. We aim to remediate critical accessibility barriers as quickly as possible and address other issues in our regular development cycle.

Formal Complaints

If you are not satisfied with our response to your accessibility feedback, you may escalate your concern to the appropriate regulatory body in your jurisdiction. In the United States, you may file a complaint with the U.S. Department of Justice Civil Rights Division or your state attorney general's office.