Access should not depend on how you use the web.
OrgRecon is working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA across its public site and authenticated product.
Current support
OrgRecon is designed to support keyboard navigation, visible focus, semantic headings and landmarks, descriptive form labels and errors, text resizing and reflow, reduced-motion preferences, and assistive-technology announcements for important loading and status changes.
Testing and improvement
Automated regression tests protect core navigation, landmark, focus, form, and status contracts. The release checklist also requires keyboard and assistive-technology review of core owner workflows because automated tools do not detect every barrier.
Known limitations
OrgRecon is an evolving closed-beta product. Complex generated reports, dense evidence tables, interactive visualizations, and third-party authentication screens may still contain accessibility barriers. Third-party services are also governed by their providers, but we will help investigate problems that block access to OrgRecon.
Request help or report a barrier
Email [email protected] with the subject “Accessibility barrier,” the page or workflow, what you were trying to do, the assistive technology or browser you used if relevant, and a description of the barrier. Do not send passwords, authentication codes, Salesforce records, customer data, tokens, or private report contents.
We aim to acknowledge accessibility requests within three business days and provide a status update or practical alternative within seven business days. Resolution time depends on the nature of the issue and any third-party dependency.
Compatibility goal
Our target is current versions of major browsers and commonly used assistive technologies. This statement describes an active accessibility program; it is not a certification that every page or third-party interaction is free of barriers.