1. Our Commitment
Sentiva is built to be usable by everyone, including the customers, employees, and candidates who use assistive technologies to navigate the web.
We design, build, and test our marketing website and SaaS platform with accessibility as a core principle, not an afterthought. This page explains how we approach accessibility, where we know our limitations are, and how to reach us if we fall short.
We believe honest disclosure matters more than overclaiming. Where different parts of Sentiva are at different stages of accessibility maturity, we aim to say so clearly.
2. Scope
This Accessibility Statement applies to Sentiva’s public website, Trust Center, candidate-facing experiences, customer-facing SaaS applications, and generated digital content where Sentiva controls the design and delivery of the experience.
Some areas of Sentiva may be at different stages of accessibility maturity. Our marketing website and candidate-facing workflows are prioritized for WCAG 2.2 AA alignment, while some complex in-app administrative workflows, analytics views, dashboards, generated reports, and third-party embedded components may have known limitations.
Where Sentiva uses third-party services or embedded content that we do not fully control, we aim to select accessible vendors where practical and provide accessible alternatives where feasible.
3. Standards We Align With
Sentiva uses WCAG 2.2 Level AA as its primary accessibility target, with WCAG 2.1 Level AA as the baseline for compatibility with many existing regulatory and procurement frameworks.
Our accessibility practices are informed by major accessibility standards and frameworks, including:
- WCAG 2.2 Level AA
- U.S. Section 508 / Revised Section 508
- EU Web Accessibility Directive (Directive 2016/2102)
- European Accessibility Act (Directive 2019/882)
- EN 301 549
- UK Public Sector Bodies (Websites and Mobile Apps) Accessibility Regulations 2018
- Australia — Disability Discrimination Act 1992 (Cth), with WCAG 2.1 AA as the technical standard
- Canada — Accessible Canada Act (ACA); Ontario — Accessibility for Ontarians with Disabilities Act (AODA)
As a global product, Sentiva is designed with the accessibility expectations of customers and candidates in mind across the markets where we are used.
The standards listed above guide how we design, build, test, and improve Sentiva. We continue to review accessibility requirements as Sentiva expands and as customer needs evolve.
4. Accessibility Governance and Process
Accessibility is considered across Sentiva’s product lifecycle, from planning and design through development, testing, release, and support.
| Phase | Accessibility practices | Tools and methods |
|---|---|---|
| Planning | Accessibility requirements are considered when defining user stories, especially for candidate-facing workflows and critical customer journeys. | Product review, WCAG-based acceptance criteria |
| Design | Designs are reviewed for color contrast, layout hierarchy, keyboard flow, focus states, form behavior, and accessible interaction patterns. | Figma, contrast checking tools, accessibility design checklists |
| Development | Engineers use semantic HTML, accessible component patterns, keyboard-friendly interactions, and ARIA where appropriate. | ESLint accessibility rules, component review, code review |
| Testing | Sentiva uses a combination of automated checks and manual review to identify accessibility issues. Candidate-facing flows receive additional attention. | axe-core, Lighthouse, WAVE, browser accessibility tools |
| Assistive technology review | Key flows may be tested with common assistive technologies as part of accessibility review and issue remediation. | NVDA, VoiceOver, TalkBack, keyboard-only testing |
| Release and monitoring | Accessibility issues are triaged through the standard product process. User-reported barriers are reviewed, prioritized, and tracked to resolution. | Product backlog, support process, accessibility issue tracking |
| Independent review | Sentiva may engage third-party accessibility specialists or provide formal accessibility documentation where required by enterprise customers. | External audit, VPAT/ACR roadmap where applicable |
5. How We Apply Accessibility Principles
Sentiva uses WCAG principles to guide how we design, build, and improve our digital experiences. The examples below show how these principles are applied across the Sentiva website, candidate-facing workflows, and SaaS product where Sentiva controls the experience.
| WCAG Principle | Accessibility focus | Sentiva approach |
|---|---|---|
| Perceivable | Content should be available in ways users can perceive. | We use readable layouts, meaningful headings, descriptive labels, alternative text for meaningful images, appropriate treatment of decorative imagery, and sufficient color contrast for text and interface elements. |
| Operable | Users should be able to navigate and use the product without relying on a mouse alone. | We design key flows for keyboard navigation, visible focus states, logical tab order, accessible forms, and controls that can be operated using standard browser and assistive technology patterns. |
| Understandable | Content and interactions should be clear and predictable. | We aim to use clear language, consistent navigation, predictable form behavior, inline validation, clear error messages, and guidance that helps users complete tasks without unexpected context changes. |
| Robust | Experiences should work reliably with modern browsers and assistive technologies. | We use semantic HTML, accessible component patterns, ARIA where appropriate, and testing tools to improve compatibility with common assistive technologies and modern browsers. |
| Candidate accessibility | Hiring workflows should not create unnecessary barriers for candidates. | Candidate-facing experiences receive particular attention, including application forms, assessment flows, communications, and the ability to request an alternative path where AI interviews may not be suitable. |
6. Candidate-facing accessibility
Sentiva powers hiring workflows for our customers, which means candidates of all abilities apply for jobs through Sentiva-powered systems.
We pay particular attention to candidate-facing accessibility because inaccessible hiring workflows can create unfair barriers. Our candidate-facing experiences are designed with WCAG 2.2 AA as the target, including support for keyboard navigation, readable content, accessible forms, and clear error handling.
If a candidate encounters an accessibility barrier in a Sentiva-powered hiring process, they may contact Sentiva using the details below. We will review the issue and, where appropriate, work with the hiring organization to support a resolution.
7. AI interviews and accessibility
Sentiva includes an AI-conducted interview feature called Lumi. We recognize that AI interviews may not be suitable for every candidate, including candidates with speech impairments, hearing impairments, neurodivergent communication styles, anxiety-related barriers, or other accessibility needs.
Sentiva provides a mechanism for candidates to request an alternative evaluation path. Sentiva does not automatically reject or penalise a candidate solely because they request an alternative path. The request is routed to the hiring organization, which decides how to handle the alternative evaluation process.
For more information on AI evaluation, candidate rights, and human oversight, please see our Responsible AI page.
8. Supported Assistive Technologies and Browsers
Sentiva is tested using modern browsers and common assistive technologies, including:
| Platform | Screen Readers / AT | Browsers |
|---|---|---|
| Windows | NVDA, JAWS | Chrome, Edge, Firefox |
| macOS | VoiceOver | Safari, Chrome |
| iOS | VoiceOver | Safari, Chrome |
| Android | TalkBack | Chrome |
Other modern, standards-compliant browsers should work. We aim to support the latest two major versions of supported browsers.
9. Known limitations
We are actively improving accessibility across Sentiva, but some limitations may remain. Known areas of focus include:
- Complex in-app workflows such as dashboards, analytics views, data tables, and drag-and-drop interfaces
- Some administrative interfaces that may not yet meet the same accessibility maturity as candidate-facing flows
- Third-party widgets or embedded content that Sentiva does not fully control
- Ongoing WCAG 2.2 improvements in areas previously designed against WCAG 2.1 AA
10. Continuous Improvement Roadmap
Accessibility is an ongoing process. Our current focus areas include:
- Rolling improvements to in-app accessibility across data tables, dashboards, and complex workflows
- WCAG 2.2 alignment work in areas where 2.1 AA was the previous baseline
- Expanded language support with locale-appropriate accessibility
- Strengthening automated regression scanning, as part of our development workflow
- User feedback integration — accessibility issues raised by customers and candidates are reviewed and prioritized through our standard product process
11. Feedback and Contact
We welcome feedback. If you encounter an accessibility barrier on any Sentiva property, please let us know:
Email: care@sentiva.ai
Phone: +1 (302) 927 2808 (Voice)
Postal: Attn: Care Team, Sentiva LLC, 254 Chapman Rd, Ste 208 #20742, Newark, Delaware 19702.
We aim to acknowledge accessibility reports within 2 business days. Confirmed issues are reviewed based on severity, impact, and available workarounds. Where we cannot resolve an issue within 30 days, we aim to provide a status update and, where practical, an alternative path or workaround.
12. Regulatory Contact
If you believe Sentiva is not meeting applicable accessibility obligations, you may have the right to contact a relevant regulatory, equality, disability, or consumer protection authority in your jurisdiction.
This Accessibility Statement will be reviewed at least annually and updated as standards evolve or significant changes are made to the Sentiva website or platform.