Accessibility Statement

1. Our Commitment

Omni, Inc. (“Omni,” “we,” “us,” or “our”), a corporation organized under the laws of the State of Delaware, is committed to ensuring digital accessibility for people of all abilities. We believe that every user — regardless of disability, impairment, or assistive technology used — deserves equal access to our platform and services.

This Accessibility Statement applies to the Omni platform, website located at useomni.org, and all related services, including OmniChat, OmniCalls, and OmniReach (collectively, the “Service”).

2. Conformance Standards

We aim to conform to the following accessibility standards and guidelines:

• Web Content Accessibility Guidelines (WCAG) 2.2 at the AA level — the internationally recognized standard for web accessibility, covering guidelines for visual, auditory, cognitive, and motor accessibility
• Americans with Disabilities Act (ADA) — Title III, which requires places of public accommodation (including commercial websites) to be accessible to individuals with disabilities
• Section 508 of the Rehabilitation Act — to the extent applicable, we design the Service to meet the accessibility requirements of Section 508 for electronic and information technology
• Authoring Tool Accessibility Guidelines (ATAG) 2.0 — as a platform that enables users to create AI-powered communications, we strive to ensure the authoring experience itself is accessible

3. Conformance Status

The Service is partially conformant with WCAG 2.2 Level AA. “Partially conformant” means that some portions of the content do not fully conform to the accessibility standard. We are actively working to achieve full conformance and are making ongoing improvements.

Our current conformance status is based on self-evaluation and third-party auditing (see Section 6). We reassess our conformance status on a quarterly basis.

4. Accessibility Features

We have implemented the following accessibility features across the Service:

4.1 Perceivable

• Text Alternatives: All meaningful images include descriptive alternative text. Decorative images are marked with aria-hidden="true" or empty alt attributes so they are ignored by screen readers.
• Color Contrast: We maintain a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text across both light and dark modes, meeting WCAG 2.2 Level AA requirements.
• Text Resizing: The platform supports browser text resizing up to 200% without loss of content or functionality. Layout adapts responsively to accommodate increased text sizes.
• Color Independence: Information is not conveyed solely through color. Visual indicators such as icons, text labels, and patterns are used alongside color to ensure usability for individuals with color vision deficiencies.

4.2 Operable

• Keyboard Navigation: All interactive elements — buttons, links, form fields, menus, and modals — are fully accessible via keyboard. Tab order follows a logical, predictable sequence.
• Skip Navigation: Skip links are provided to allow keyboard users to bypass repetitive navigation and jump directly to the main content area.
• Focus Management: Visible focus indicators (focus rings) are displayed on all interactive elements. Modals, dialogs, and dynamic content properly manage focus trapping and return.
• Reduced Motion: Animations and transitions respect the prefers-reduced-motion media query. Users who prefer minimal motion will see static or simplified content transitions.
• Timing: Where time limits are used (e.g., session timeouts), users are warned in advance and given the option to extend or disable the time limit where possible.

4.3 Understandable

• Semantic HTML: We use proper heading hierarchy (h1 through h6), landmark regions (main, nav, aside), and ARIA attributes to provide structure and context for assistive technologies.
• Form Accessibility: All form fields have programmatically associated labels. Error messages are linked to their corresponding fields via aria-describedby. Required fields are indicated both visually and programmatically. Inline validation provides immediate feedback.
• Error Prevention: For actions that have significant consequences (e.g., account deletion, payment submission), we provide confirmation dialogs and the ability to review or undo the action.
• Consistent Navigation: Navigation patterns remain consistent across pages. Interactive components behave predictably throughout the application.
• Language: The page language is programmatically declared using the lang attribute to assist screen readers with pronunciation.

4.4 Robust

• Standards-Compliant Markup: Pages are built with valid, well-structured HTML to ensure broad compatibility with current and future assistive technologies.
• ARIA Implementation: We use WAI-ARIA roles, states, and properties to enhance accessibility where native HTML semantics are insufficient, particularly in custom components, dynamic content, and single-page application patterns.
• Responsive Design: The Service works across screen sizes, devices, and orientations. Content reflows correctly at different viewport widths and zoom levels.

5. Assistive Technology Compatibility

The Service is designed to be compatible with the following assistive technologies:

• Screen readers: NVDA (Windows), JAWS (Windows), VoiceOver (macOS/iOS), TalkBack (Android)
• Voice recognition: Dragon NaturallySpeaking, Windows Voice Access, macOS Voice Control
• Screen magnification: ZoomText, Windows Magnifier, macOS Zoom
• Switch access and alternative input devices
• High contrast and custom color modes (Windows High Contrast, forced-colors media query)

The Service is tested primarily with the latest stable versions of Chrome, Firefox, Safari, and Edge. Accessibility features are designed to degrade gracefully in older browsers.

6. Assessment & Auditing

We evaluate the accessibility of the Service through the following methods:

• Automated Testing: Continuous automated accessibility scans integrated into our development and deployment pipeline using industry-standard tools
• Manual Testing: Regular manual audits performed against WCAG 2.2 AA success criteria, including keyboard-only navigation testing and screen reader evaluation
• Third-Party Auditing: We use A11yCore.org for independent accessibility auditing and ongoing monitoring. A11yCore helps us continuously test and improve compliance across the platform through automated scans and manual review processes.
• User Feedback: We actively incorporate feedback from users with disabilities to identify and prioritize accessibility improvements

7. Known Limitations

While we strive for full WCAG 2.2 AA conformance, we are aware of the following limitations and are actively working to address them:

• Third-Party Integrations: Some third-party components and integrations (e.g., embedded messaging widgets from Meta, Telegram, and other channel providers) may not fully meet WCAG 2.2 AA standards. We work with our vendors to encourage accessibility improvements and provide accessible alternatives where feasible.
• Legacy PDF Documents: Some older PDF documents may not be fully accessible. We are working to remediate or replace non-conformant documents with accessible versions.
• AI-Generated Content: Content generated by our AI agents (OmniChat, OmniCalls, OmniReach) may not always meet accessibility best practices, as AI outputs can vary. We are developing safeguards to improve the accessibility of AI-generated communications.
• Real-Time Communications: Live chat and real-time messaging interfaces present inherent accessibility challenges. We are working to improve screen reader announcements for incoming messages and dynamic content updates using ARIA live regions.

If you encounter a barrier not listed above, please contact us so we can address it.

8. Alternative Formats & Accommodations

If you need information in an alternative format or require a reasonable accommodation to access our Service, please contact us. We will work with you to provide the information or service you need in an accessible manner. Examples of accommodations we can provide include:

• Documents in alternative formats (plain text, large print, accessible HTML)
• Assistance with account setup and configuration
• Alternative means of accessing Service features
• Adjustments to communication preferences for OmniCalls interactions

9. Feedback & Contact

We welcome and value your feedback on the accessibility of the Service. If you encounter an accessibility barrier, have suggestions for improvement, or need assistance, please contact us:

When reporting an accessibility issue, please include:

• A description of the issue and where it occurred
• The assistive technology and browser you were using (if applicable)
• The URL or page where you encountered the issue
• Any steps to reproduce the problem

We aim to acknowledge all accessibility feedback within two (2) business days and provide a substantive response or resolution within ten (10) business days.

10. Enforcement & Complaints

We make every effort to resolve accessibility concerns directly. However, if you are not satisfied with our response, you may file a complaint with the following authorities:

• U.S. Department of Justice, ADA Division: File an ADA Complaint
• U.S. Department of Health and Human Services, Office for Civil Rights: File an OCR Complaint
• Your state's Attorney General or disability rights enforcement office

For users in the European Union, you may also contact your national enforcement body under the European Accessibility Directive (EU) 2016/2102.

11. Continuous Improvement

Accessibility is not a one-time effort. We are committed to ongoing improvements, including:

• Incorporating accessibility requirements into all stages of product design and development
• Training our engineering and design teams on accessibility best practices and WCAG guidelines
• Conducting quarterly accessibility reviews and annual third-party audits
• Monitoring and addressing accessibility feedback on an ongoing basis
• Updating this statement as improvements are made and new standards are adopted

12. Related Policies

For information about how we handle your data and the terms governing your use of the Service, please see:

• Terms of Service
• Privacy Policy