Accessibility is part of quality, not an optional extra.

Commitment

Meetzo wants the product and website to be usable by as many people as possible, including people with disabilities. We aim to make the core experience understandable, keyboard-friendly, readable, and workable across modern devices and assistive technology setups.

Accessibility target

Meetzo aims to align with WCAG 2.2 Level AA as an accessibility target for the website and product interfaces, while recognizing that work toward accessibility is ongoing rather than a one-time task.

What we currently focus on

• Readable color contrast and typography choices that support long-form reading on policy and help pages.
• Clear link text, visible controls, and straightforward content structure on marketing and policy pages.
• Keyboard operability for core navigation and button interactions where practical.
• Responsive layouts that remain usable on mobile, tablet, and desktop widths.
• Language that is direct and user-facing instead of overly technical whenever possible.

Known limitations

Real-time communication products can present accessibility challenges, especially around motion, live status changes, media permissions, and browser-specific media behavior. Some parts of the current chat experience may still need improvement for screen reader announcements, reduced-motion handling, or advanced keyboard workflows.

We prefer being transparent about limitations rather than implying perfect accessibility where that would not be accurate.

Supported environments

Meetzo is designed to work on current versions of mainstream modern browsers on desktop and mobile. Because live audio and video behavior can vary between browser engines and device permissions, the exact experience may differ across environments.

How to report an accessibility issue

If you encounter an accessibility barrier, email support@meetzo.app with accessibility in the subject line and describe what you were trying to do, what browser or device you used, and what went wrong. The more specific the report, the faster we can reproduce and improve the issue.

Ongoing improvements

We intend to keep reviewing accessibility as the product evolves, including policy content readability, keyboard support, reduced-motion considerations, and live interaction patterns that may need refinement in chat interfaces.