Building for everyone

Our commitment

We believe the web should be accessible to everyone. ReplyMagic, operated by ZipLyne, aims to provide a consistent and inclusive experience across our landing page and product. We are continuously working to improve the accessibility of our product and welcome any feedback.

Standards we aim for

We aim to meet WCAG 2.1 Level AA — the Web Content Accessibility Guidelines published by the W3C Web Accessibility Initiative. These guidelines define how to make web content more accessible to people with disabilities, including those with visual, auditory, motor, and cognitive impairments.

What we've done

Across the ReplyMagic landing page and product, we have implemented:

• Semantic HTML throughout. We use correct heading hierarchy, landmark regions (<header>, <main>, <footer>), and native interactive elements so structure is communicated to assistive technologies.
• Keyboard navigation support. All interactive elements — buttons, links, and form controls — are reachable and operable via keyboard alone, with visible focus indicators that meet contrast requirements.
• Screen reader compatibility. Images include descriptive alt text, decorative images are marked with alt="", and interactive elements use ARIA labels where native semantics are insufficient.
• Sufficient color contrast. Text and interactive elements are designed to meet WCAG 2.1 AA contrast ratios — at least 4.5:1 for normal text and 3:1 for large text and graphical components.
• Responsive design. The site scales fluidly across all viewport sizes — from mobile phones to wide desktop monitors — without loss of content or functionality.
• Reduced motion support. Animations respect the prefers-reduced-motion media query. When a user has indicated they prefer less motion in their operating system settings, decorative animations are disabled or replaced with static equivalents.

Known limitations

We are an early-stage product and some areas are still being improved:

• App dashboard. Some interactive components within the ReplyMagic dashboard — including data tables, comment management panels, and dynamic overlays — are still being audited and improved for full keyboard and screen reader support.
• Third-party embeds. Certain third-party components (such as authentication flows and analytics widgets) may not fully conform to WCAG 2.1 AA. We are monitoring these and pushing vendors to improve where possible.

We are actively working to address these gaps. If you encounter a barrier that prevents you from using any part of ReplyMagic, please let us know — we treat accessibility issues with the same priority as bugs.

Feedback and contact

If you experience any accessibility barriers, find something that isn't working as expected, or have suggestions for improvement, we want to hear from you. Please contact us at [email protected]. We aim to respond to all accessibility-related enquiries within 2 business days.

When you contact us, it helps to include:

• A description of the issue and where you encountered it.
• The browser, operating system, and assistive technology you are using.
• Any steps to reproduce the problem, if known.