1. Commitment to Accessibility
At ivvi, we are committed to making our products and services accessible to everyone who uses them.
Accessibility is central to how we design and build software. We aim for people of all abilities to use our products and websites with confidence.
2. Accessibility Measures
- Internal policies: Accessibility is built into how we plan, design, ship, and maintain products—not only as a one-off audit.
- Goals and ownership: Teams have clear accessibility goals and named responsibilities so progress does not stall between releases.
- Quality assurance: We use structured testing (manual and tool-assisted) to find issues early and track fixes.
3. Conformance Status
The Web Content Accessibility Guidelines (WCAG) describe how to make web content accessible to people with disabilities. Conformance is defined at three levels: Level A, Level AA, and Level AAA.
ivvi's products and services are partially conformant with WCAG 2.1 Level AA. We are working to close remaining gaps; some parts of the product or site may not yet meet every success criterion.
We are not required to meet Section 508 of the US Rehabilitation Act (that law applies to US federal agencies). We still use Section 508 as practical guidance where it helps us support more users.
4. Feedback Mechanism
We welcome feedback on accessibility. If something is hard to use or you have ideas for improvement, email support@ivvi.app. We aim to reply within 24 hours.
5. Compatibility
We design ivvi products to work with common assistive technologies. We test with screen readers including TalkBack, VoiceOver, and JAWS.
Our web application is optimised for recent versions of Chrome and Edge. Other browsers may work; if you hit issues, tell us via the contact details below.
6. Limitations and Alternatives
We know some areas need improvement. Below are known limitations and what we are doing about them.
- Events:If an event title is left blank, several pages may show 'Untitled Event'. We are exploring automatic, unique names so titles stay clear.
- Identical button labels:On the Events screen, every row uses a 'Move Event' label without naming the specific event. The control after the event title shows which item moves. We are reviewing clearer labelling.
- Page titles: Some views need clearer document titles, for example View Event, reorder cards and task lists, home and record event, and account and collections. We are adding more descriptive titles over time.
- Third-party tools: Parts of ivvi rely on third-party components that are not fully accessible yet. We work with those vendors and replace or patch where we can.
- Guided tour and transcription: Not all steps are fully keyboard-operable. You can use our intro video and onboarding articles as alternatives while we improve keyboard support.
- Transcription focus mode: Screen readers work with our transcription service; with NVDA, use Insert+Space to interact in Focus Mode. We want to simplify this in a future release.
7. Assessment Approach
We assess accessibility in three ways:
- Self-evaluation: Our team runs regular checks with common tools and internal test protocols.
- External input: We involve external accessibility experts when we need a deeper review.
- In-house specialists: Accessibility specialists work with design and engineering on every major change.
8. Ongoing Improvements
We keep fixing known issues and improving how ivvi works for assistive technology. That includes design updates, vendor collaboration, and new product ideas that put access first.
9. Contact Information
For accessibility questions or to report a barrier, email support@ivvi.app. We will help where we can and use your feedback to prioritise fixes.