zenna is committed to making our product usable by everyone. We aim to conform to WCAG 2.1 Level AA and continually improve accessibility across our app and help center.
Our commitment
- Design and build with accessibility in mind.
- Fix issues that block or meaningfully hinder users with disabilities.
- Provide multiple ways to get support or request accommodations.
Scope
This statement covers zenna (app and help center) at zenna.ai.
Some third-party embeds or integrations may have their own accessibility constraints.
Standards & methods
We reference these standards and practices:
- WCAG 2.1 Level AA
- Keyboard accessibility and focus order
- Semantic HTML + ARIA where appropriate
- Color contrast (4.5:1 for body text / 3:1 for large text)
We test using:
- Automated tools (e.g., WAVE, axe)
- Manual keyboard-only navigation
- Screen reader spot checks (NVDA / VoiceOver)
Current conformance status
We are partially conformant with WCAG 2.1 AA. Known limitations are listed below and tracked on our backlog.
Known issues (examples)
- Occasional heading order inconsistencies
- Alt text missing on a small number of decorative images
- A few contrast exceptions on legacy pages
If you encounter an issue not listed here, please tell us (contact options below).
3rd-party tools & overlays
We provide the All-in-One Accessibility widget to offer features like text sizing and high contrast modes. While helpful, overlays do not replace accessible code. We still prioritize fixing underlying issues.
Feedback & contact
If you need an accessible alternative or want to report a problem, contact us:
- Email: legal@zenna.ai
- Legal contact: legal@zenna.ai
- Response time: We strive to reply within 2 business days and resolve critical blockers as quickly as possible.
If you need content in an alternative format (e.g., accessible PDF), we’ll provide it upon request.
Compatibility
zenna is designed to work with the latest versions of Chrome, Edge, Firefox, and Safari on desktop and mobile, and with common assistive technologies (e.g., screen readers and browser zoom).
Roadmap highlights
- Ongoing alt-text audit & fixes
- Standardized heading patterns in templates
- Color token update for contrast consistency
- Expanded keyboard testing coverage