Accessibility Statement
Last updated: 27 May 2026
novaverb is committed to making the Service accessible to people with disabilities. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA across the platform's authenticated and public surfaces.
1. Conformance status
The Service is partially conformant with WCAG 2.1 Level AA. Partial conformance means that some content does not yet fully conform; we are actively working to close those gaps.
Specific areas we have audited:
- Keyboard navigation — all interactive elements are reachable and operable via keyboard alone (Tab / Shift+Tab / Enter / Space / arrow keys)
- Screen-reader compatibility — tested with NVDA (Windows), VoiceOver (macOS, iOS), and TalkBack (Android)
- Color contrast — body text + UI controls meet 4.5:1 minimum ratio; large text meets 3:1
- Focus indication — visible 2-pixel outline on focused elements
- Form labels — every form field has a programmatic label associated via
<label for>oraria-label - Semantic HTML — headings (h1–h6), lists, landmarks (header / nav / main / footer), and tables use appropriate elements
- Resizable text — supports 200% zoom without loss of content or function
2. Known issues
Areas where conformance is not yet complete:
- The graph visualization in the Map of Content module is canvas/SVG-based; we provide a tabular equivalent for screen-reader users but the visual graph itself is not navigable via keyboard.
- Some admin charts (cost trends, traffic sparklines) rely on color alone to distinguish data series — patterns/labels coming in a future release.
- Code blocks in documentation pages do not auto-announce language to screen readers.
If you encounter an accessibility issue not listed here, please report it — see Contact below.
3. Assistive technologies tested
| Platform | Screen reader | Browser | Last tested |
|---|---|---|---|
| Windows | NVDA 2024.1 | Firefox 128, Chrome 126 | 2026-05 |
| macOS | VoiceOver | Safari 18, Chrome 126 | 2026-05 |
| iOS 17 | VoiceOver | Safari Mobile | 2026-05 |
| Android 14 | TalkBack | Chrome Mobile | 2026-04 |
4. Approach
Accessibility is part of every release, not a one-time effort:
- Automated — axe-core scans run on every UI build, blocking merge for new WCAG 2.1 AA violations
- Manual — quarterly screen-reader sweep of new + changed pages
- Operator-led — accessibility issues raised by users are triaged within 7 days and prioritized like security bugs
5. Date of this statement
This statement was prepared on 27 May 2026 following an internal evaluation. It is reviewed at least annually or after major UI changes, whichever is sooner.
6. Feedback & contact
We welcome feedback on the accessibility of novaverb. If you experience accessibility barriers:
- Email contact@novaverb.com with the subject line
Accessibility - Describe the barrier, the page URL, your assistive technology, and your browser
- We aim to respond within 5 business days
7. Enforcement
If you are not satisfied with our response, you may file a complaint with the U.S. Department of Justice under Title III of the Americans with Disabilities Act, or with the relevant accessibility regulator in your jurisdiction.