Accessibility Statement
Callings.ai is committed to making our platform usable by as many people as possible, including people who use assistive technologies. This page describes where we are today, the standards that guide our work, the limitations we know about, and how to reach us if something gets in your way.
We would rather describe our real, current state than make broad conformance claims. We update this page as our accessibility work progresses.
Last updated: July 12, 2026.
Our Commitment
We want everyone running a job search to be able to use Callings.ai. We use the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA as the reference standard that guides our design and development work, and we treat accessibility feedback from users as a priority.
Where We Are Today
We are candid about our current status:
- In July 2026 we completed a vendor self-evaluation of the product and published an Accessibility Conformance Report (ACR) based on VPAT 2.5 (Revised Section 508 edition), together with a vendor accessibility roadmap. Institutional partners can request the latest versions through their Callings.ai contact or via [email protected].
- Alongside the evaluation, we completed several remediation passes covering account signup, onboarding, primary navigation, the Job Tracker, job matching, and the rest of the signed-in product, on both desktop and mobile layouts.
- We test the product with automated accessibility tooling (two independent WCAG rule engines run against the live application, from account creation through the full signed-in product). As of the last evaluation, the screens we scan have no outstanding automated failures apart from documented component-library limitations tracked on our roadmap.
- The platform is built on established, widely used interface components that provide baseline accessibility behaviors (keyboard interaction, focus management, and semantic markup).
- We do not claim full WCAG 2.1 AA conformance today: automated and code-level testing catches only part of the picture, and a comprehensive assistive technology evaluation (for example with NVDA or VoiceOver) is still ahead of us on the roadmap.
Steps We Take
- We use WCAG 2.1 AA as the reference standard when designing and building new features, backed by internal accessibility coding standards that every interface change is expected to follow.
- We run automated accessibility scans (axe-core and HTML_CodeSniffer) against the real application as part of our development workflow, at desktop and mobile screen sizes, and fix regressions at the source.
- We standardized the product's color palette on values that meet WCAG contrast requirements, including adjusting user-chosen colors (such as Job Tracker column colors) at render time so text on them stays readable.
- We build on mature interface component libraries rather than fully custom controls wherever practical.
- The platform is responsive and supports phones, tablets, and desktop browsers.
- We review accessibility reports from users and prioritize fixes to the core job-search flows first.
Known Limitations
We know about the following limitations, and this list may not be complete:
- Drag-and-drop interactions on the Job Tracker board are not keyboard operable. The same records and actions are available in the Job Tracker's table view, which is keyboard accessible.
- Some images generated by AI features may not include descriptive alternative text.
- We have not yet completed a comprehensive screen reader evaluation (NVDA, JAWS, VoiceOver), so some announcements and reading orders may be imperfect even where automated checks pass.
- Some secondary dialogs have not yet been individually verified with our automated tooling.
- Documents exported from the product (PDF and DOCX) contain real, selectable text but are not yet verified for accessibility structure such as tagged PDF.
- Job listings, company pages, and other third-party content we link to are outside our control and may not meet the same standards.
If a limitation blocks you from completing a task, contact us and we will work with you to provide the information or complete the action through an alternative method where reasonably possible.
Compatibility
Callings.ai is designed for recent versions of major browsers (Chrome, Edge, Firefox, and Safari) on desktop and mobile devices. We have not tested every combination of browser and assistive technology.
Feedback and Assistance
If any part of Callings.ai is difficult for you to use, we want to hear about it.
Email [email protected] and include "Accessibility" in the subject line. Please describe the page or feature, what you were trying to do, and the browser and any assistive technology you were using. We review every accessibility report.