Accessibility Statement
Last updated: March 20, 2026
1. Our Commitment
zoneout is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards to guarantee we provide equal access to all users.
Our accessibility efforts are guided by the requirements of the European Accessibility Act (EAA, Directive 2019/882), which establishes common accessibility requirements for key products and services across the European Union. We strive to meet or exceed these requirements in the design, development, and maintenance of our platform.
We believe that the internet should be available and accessible to anyone, and we are committed to providing a platform that is accessible to the widest possible audience, regardless of circumstance or ability.
2. Conformance Status
The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. WCAG defines three levels of conformance: Level A, Level AA, and Level AAA.
zoneout is partially conformantwith WCAG 2.1 Level AA. "Partially conformant" means that some parts of the content do not fully conform to the accessibility standard. We are actively working toward full conformance and regularly audit our platform to identify and resolve accessibility gaps.
3. Accessible Features
We have implemented the following accessibility features across the zoneout platform:
- Keyboard navigation: all interactive elements on the platform, including navigation menus, buttons, forms, and dialogs, are fully operable using a keyboard alone.
- Semantic HTML: we use proper semantic HTML5 elements (headings, landmarks, lists, nav, main, article) to ensure content structure is meaningful and programmatically determinable.
- ARIA attributes: where native HTML semantics are insufficient, we use WAI-ARIA (Accessible Rich Internet Applications) attributes to convey roles, states, and properties to assistive technologies.
- Color contrast: text and interactive elements are designed to meet WCAG AA contrast ratios (minimum 4.5:1 for normal text, 3:1 for large text) across our dark-mode interface.
- Screen reader support: the platform is developed and tested with screen readers to ensure content, navigation, and interactive elements are properly announced and operable.
- Focus indicators: visible focus indicators are provided for all interactive elements, ensuring keyboard users can always identify their current position on the page.
- Responsive design: the platform adapts to various screen sizes and supports text resizing up to 200% without loss of content or functionality.
- Skip navigation: skip-to-content links are provided to allow keyboard users to bypass repetitive navigation elements.
- Form labels: all form inputs have associated labels, and error messages are clearly communicated to assistive technologies.
4. Known Limitations
Despite our best efforts, some areas of the platform may not yet be fully accessible. We are aware of the following limitations and are actively working to resolve them:
- Dynamic content updates: some dynamically loaded content (such as real-time feed updates, notifications, and messaging) may not be immediately announced by screen readers. We are implementing ARIA live regions to improve this experience.
- Third-party embeds: content embedded from third-party services (such as URL previews, external media players, and OAuth provider pages) may not meet our accessibility standards. We work with these providers to encourage accessibility improvements.
- AI-generated images: images produced through the AI companion image generation features may have limited or generic alternative text descriptions. We are developing improved automated alt text generation for these images.
- Complex interactive components: certain rich interactive features, such as the drag-and-drop functionality and some animated transitions, may have reduced accessibility. Alternative interaction methods are provided where possible.
- User-generated content: posts, comments, and media uploaded by users may not always include adequate alternative text or follow accessibility best practices. We provide guidance and tooling to encourage accessible content creation.
5. Feedback Mechanism
We welcome your feedback on the accessibility of zoneout. If you encounter any accessibility barriers, have suggestions for improvement, or need assistance accessing any part of the platform, please contact us through any of the following channels:
- Email: accessibility@zoneout.io
- Contact form: use our Contact page and select the "Accessibility" category to route your message to our accessibility team.
When reporting an accessibility issue, please include the following information to help us investigate and resolve the matter efficiently:
- A description of the issue and the page or feature affected.
- The browser and operating system you are using.
- Any assistive technology you are using (e.g., screen reader, magnification software).
- Screenshots or recordings, if possible, to illustrate the issue.
We aim to acknowledge all accessibility feedback within 2 business days and provide a substantive response within 5 business days. Where an immediate fix is not possible, we will communicate our plan and timeline for resolution.
6. Enforcement Procedure
Under Article 30 of the European Accessibility Act (Directive 2019/882), EU Member States are required to designate national enforcement bodies responsible for ensuring compliance with accessibility requirements.
If you are unsatisfied with our response to your accessibility concern, you have the right to escalate your complaint to the relevant national enforcement body in your country. These bodies have the authority to:
- Investigate complaints regarding non-compliance with accessibility requirements.
- Order corrective measures to be taken by service providers.
- Impose penalties for persistent or serious non-compliance.
For a list of national enforcement bodies, please consult the European Commission's website or your national government resources. We are committed to cooperating fully with any enforcement proceedings and to resolving accessibility issues promptly.
7. Technical Specifications
zoneout relies on the following technologies for accessibility:
- HTML5
- WAI-ARIA 1.2
- CSS (Tailwind CSS)
- JavaScript (Next.js / React)
Compatible Browsers
The platform is designed to be accessible with the current and previous major versions of the following browsers:
- Google Chrome (desktop and mobile)
- Mozilla Firefox (desktop)
- Apple Safari (desktop and mobile)
- Microsoft Edge (desktop)
Tested Assistive Technologies
We test with the following screen readers and assistive technology combinations:
- VoiceOver with Safari on macOS and iOS
- NVDA with Firefox and Chrome on Windows
- TalkBack with Chrome on Android
8. Assessment Approach
We assess the accessibility of zoneout through a combination of the following methods:
- Self-assessment: our development team conducts regular manual accessibility reviews, including keyboard-only navigation testing, screen reader testing, and visual inspection of color contrast and focus indicators.
- Automated testing: we use industry-standard automated accessibility testing tools including axe-core and Google Lighthouse to identify common accessibility issues during development and in continuous integration pipelines.
- User feedback: we incorporate feedback from users with disabilities to identify real-world accessibility barriers that may not be caught by automated tools or internal testing.
- Continuous improvement: accessibility is integrated into our development workflow. New features are reviewed for accessibility compliance before release, and we maintain an accessibility backlog to track and prioritize improvements.
9. Contact Us
If you have any questions about this accessibility statement or need assistance, please contact us:
- Email: accessibility@zoneout.io
- General inquiries: info@zoneout.io
- Platform: zoneout.io/contact
This statement was prepared on March 20, 2026 and will be reviewed and updated regularly to reflect changes to the platform and our ongoing accessibility improvements.