Sentiva Website Accessibility Statement
Last Updated:
Apr 23, 2025
Complaint with WCAG 2.1 (AA) and Relevant Global Regulations
1. Our Commitment
Sentiva LLC is committed to providing a website and SaaS platform that are accessible, usable, and inclusive for the widest possible audience, including people with disabilities. We design, build, and test the Sentiva website and in-app experience against the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We also align with:
U.S. Section 508 / EN 301 549
UK Public Sector Bodies (Websites and Mobile Apps) Regulations
Australia – WCAG 2.1 AA (AGWG)
Canada (AODA) and Other Comparable Standards
2. Accessibility Governance and Process
Phase | Key Activities | Tools and Owners |
Planning | • Accessibility requirements captured as user stories • Color-contrast palette locked before design moves to mock-ups | Product Owner, UX Lead |
Design | • Wireframes reviewed with WCAG checklist (contrast, hierarchy, focus order) • Interactive components annotated with ARIA roles | Figma + Stark plugin |
Development | • Semantic HTML5 and ARIA patterns • Keyboard-only navigation validated in every pull request | ESLint-a11y, axe-linter |
Testing | • Automated scan on every build (axe-core CI) • Manual assistive-tech tests (NVDA, VoiceOver, TalkBack) • Color-contrast spot checks in dark/light modes | axe DevTools, Lighthouse, Wave |
Release and Monitoring | • Quarterly third-party audit • User-reported issues triaged and fixed within 30 days | Deque / Level Access |
3. Key WCAG Success Criteria and How Sentiva Meets Them
WCAG Principle | Sample Success Criteria (Level AA) | Sentiva Implementation |
Perceivable | 1.1.1 Non-text Content | • All images, icons, and logos include concise alt text. • Decorative imagery marked role="presentation". |
1.2.5 Audio Descriptions | • Product videos offer captions and an optional audio description track. | |
1.4.3 Contrast (Minimum) and 1.4.11 Non-Text Contrast | • Color palette maintains ≥ 4.5:1 contrast for text and 3:1 for UI components. • High-contrast mode inherits OS/Browser settings. | |
Operable | 2.1.1 Keyboard | • All interactive elements reachable via Tab, Shift-Tab in logical order; dropdowns, modals, and sliders operable without a mouse. |
2.2.1 Timing Adjustable | • Auth sessions warn at 2 min before timeout; users can extend. • Carousel auto-rotation paused/controlled by keyboard. | |
2.4.1 Bypass Blocks | • “Skip to main content” link is visible on focus. • Landmark roles (<header>, <nav>, <main>, <footer>) in use. | |
Understandable | 3.1.2 Language of Parts | • Primary language set to lang="en". Localised pages declare language subcodes. |
3.2.2 On-Input | • No unexpected context changes; forms validate inline and announce errors. | |
Robust | 4.1.2 Name, Role, Value | • Custom controls expose accessible name, ARIA role, and state. • Live-region alerts for background operations (e.g., “Form saved”). |
4. Assistive Technologies and Supported Browsers
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 test against the latest two major versions.
5. Third-Party Content and Integrations
Certain pages embed third-party widgets (e.g., Calendly, LinkedIn feeds). Where we cannot fully control markup, we:
Select vendors with documented WCAG conformance.
Provide accessible fallbacks—e.g., alternative contact methods.
Flag gaps to vendors and track remediation progress.
6. Continuous Improvement Roadmap
Timeline | Upcoming Enhancements |
Q3 2025 | • Publish detailed VPAT 2.4 • Add keyboard-accessible drag-and-drop alternative in Kanban view |
Q4 2025 | • Dark-mode contrast re-audit • Expand language coverage to Spanish and French with full locale-appropriate alt text |
Rolling | • Monthly automated regression scan • User accessibility feedback review in every sprint retro |
7. Feedback and Contact
We welcome feedback. If you encounter an accessibility barrier on any Sentiva property, please let us know:
Email: accessibility@sentiva.com
Phone: +1 (302) 927 2808 (Voice)
Postal: Attn: Accessibility Team, Sentiva LLC, 254 Chapman Rd, Ste 208 #20742, Newark, Delaware 19702.
We aim to acknowledge reports within 2 business days and resolve confirmed issues within 30 days or provide a status update.
8. Enforcement and Compliance
If you believe we are not meeting our accessibility obligations, you may contact your local regulator. EU/EEA users may reach out to their national equality body; U.S. users can contact the Office for Civil Rights.
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.
