Built for access. Improved with people.

1. Commitment and target standard

MegaHuddle treats accessibility as an ongoing product and operational responsibility. Our target is substantial alignment with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA for public web content and core digital service paths, while recognizing that conformance requires continuing automated and human evaluation and does not eliminate every individual barrier.

This statement describes an objective and program, not a representation that every page, historical artifact, third-party item, preview, or newly released feature is free from defects at all times.

2. Design and engineering practices

MegaHuddle’s design and development practices seek to include semantic structure, accessible names, logical heading and reading order, keyboard operation, visible focus, sufficient contrast, text resizing, responsive reflow, labels and instructions, status announcements, reduced-motion support, and alternatives for meaningful non-text content.

Core forms, navigation, dialogs, menus, product controls, error states, and account paths are reviewed as interactive experiences, not only as static pages.

3. Testing and monitoring

We use a combination of code review, automated checks, browser and viewport testing, keyboard testing, and manual inspection. Automated results are not treated as proof of full accessibility. Higher-risk paths should also be evaluated with representative assistive technologies and, when appropriate, by people with disabilities or qualified independent reviewers.

Accessibility regressions are prioritized based on whether they block access, prevent completion of a core task, obscure essential information, or materially degrade use with assistive technology.

4. Supported use and compatibility

MegaHuddle is designed for current versions of major browsers and common assistive technologies. Results can vary with operating system, browser, screen reader, magnification, voice control, custom styles, extensions, and security settings. Keeping browsers and assistive technology current can improve compatibility.

Users should be able to zoom text and content, use keyboard navigation, identify focus, understand form errors, and request reduced motion without losing core information or function. If a supported combination fails, please report it.

5. Third-party and connected content

MegaHuddle may display or link to content, feeds, media players, documents, maps, social posts, or interfaces controlled by a customer or third party. Their accessibility may be outside MegaHuddle’s direct control. We seek accessible integration patterns, meaningful labels, and alternative paths where feasible, and we welcome reports identifying a specific third-party barrier.

6. Alternative access and reasonable assistance

If a barrier prevents you from obtaining information or completing a task, MegaHuddle will make reasonable efforts to provide the information or service through an effective alternative while the issue is evaluated. An alternative is not intended to reduce the priority of correcting the underlying digital barrier.

Requested assistance is evaluated in light of the person’s needs, the nature of the service, available technology, security and privacy obligations, and applicable law. We will not require disclosure of a diagnosis when a description of the barrier and needed interaction is sufficient.

7. How to report a barrier

Use the Report accessibility issue link below and provide, if available: the page or product; the task you were attempting; the barrier encountered; browser, device, and assistive technology; and a preferred contact method. Do not include passwords, access tokens, confidential data, or unnecessary medical information.

We aim to acknowledge actionable reports promptly, investigate in proportion to severity, communicate material next steps, and provide an alternative path when reasonably available. Resolution time depends on complexity, third-party dependencies, and the risk of the change.

8. Procurement, customer configuration, and shared responsibility

MegaHuddle evaluates accessibility in product design, component selection, procurement, release review, and vendor relationships. Customers remain responsible for the accessibility of their content, branding, configuration, embedded sources, and downstream implementation. We encourage customers to preserve semantic output, accessible labels, contrast, focus behavior, and alternative content when integrating MegaHuddle into a website or application.

9. No waiver of rights

Nothing in this statement limits rights or remedies available under applicable disability or civil-rights law, modifies a signed contractual accessibility commitment, or requires a person to use a reporting process before exercising a legal right.

10. Updates and contact

MegaHuddle will update this statement as its services, standards, and accessibility program evolve. The Last updated date identifies the current version. Questions, accommodation requests, and feedback should be submitted through the accessibility contact path below.