Accessibility Statement
Last updated: March 2026
1. Our Commitment to Accessibility
38os is committed to ensuring digital accessibility for people with disabilities. We continually work to improve the user experience for everyone and apply the relevant accessibility standards to ensure we provide equal access to all users.
We believe that the web should be accessible to all, and we are dedicated to making our platform as inclusive and user-friendly as possible, regardless of ability or the technology used to access it.
2. Conformance Status
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards. These guidelines explain how to make web content more accessible to people with a wide array of disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.
While we strive to adhere to the accepted guidelines and standards for accessibility and usability, it is not always possible to do so in all areas of the platform. We are actively working to increase the accessibility and usability of our platform and, in doing so, adhere to many of the available standards and guidelines.
3. Measures We Have Taken
We have taken the following measures to ensure the accessibility of 38os:
- Semantic HTML Structure: We use proper HTML5 semantic elements (headings, landmarks, lists, and navigation) to provide a logical and meaningful document structure that assistive technologies can interpret correctly.
- Keyboard Navigable Interfaces: All core functionality of the platform is operable through a keyboard interface, ensuring that users who cannot use a mouse can still navigate and interact with the Service.
- Color Contrast Ratios: We maintain color contrast ratios that meet WCAG guidelines, ensuring text and interactive elements are distinguishable for users with low vision or color vision deficiencies.
- Screen Reader Compatible Components: Our components are built to work with popular screen readers, including NVDA, JAWS, and VoiceOver, providing meaningful announcements and navigation cues.
- Responsive Design Across Devices: The platform is designed to be fully responsive, adapting to various screen sizes and orientations, including mobile devices and tablets.
- Focus Management and Visible Focus Indicators: We provide visible focus indicators on interactive elements so that keyboard users can always identify which element is currently focused. Focus is managed programmatically during dynamic content changes.
- Alt Text for Images: All meaningful images include descriptive alternative text, enabling screen reader users to understand the content and purpose of visual elements.
- ARIA Labels Where Needed: We use WAI-ARIA (Accessible Rich Internet Applications) attributes to enhance the accessibility of dynamic content and custom interface components that go beyond native HTML semantics.
4. Known Limitations
Despite our best efforts, some parts of the 38os platform may not be fully accessible. We are transparent about our current limitations and are actively working to address them:
- Data Visualization Charts: Some data visualization charts and graphs may not be fully accessible to screen readers. We are working on providing text-based alternatives and data tables alongside visual representations.
- Complex Interactive Components: Some complex interactive components, such as drag-and-drop interfaces and advanced filtering controls, may have limited keyboard navigation support. We are actively improving keyboard accessibility for these features.
- Continuous Improvement: Accessibility is an ongoing effort. We regularly review and update our platform to address known issues and incorporate feedback from our users. New features are developed with accessibility in mind from the outset.
5. Feedback
We welcome your feedback on the accessibility of 38os. If you encounter any accessibility barriers or have suggestions for improvement, please let us know:
- Email: accessibility@38os.com
- Contact Form: Contact Us
We aim to respond to accessibility feedback within 5 business days and to propose a solution within 10 business days. We take all feedback seriously and use it to guide our accessibility improvements.
6. Assessment Approach
38os assesses the accessibility of our platform through the following methods:
- Self-Evaluation: Our development team regularly conducts internal accessibility reviews of new and existing features using automated testing tools and manual inspection.
- Automated Testing: We use automated accessibility testing tools to identify common issues such as missing alt text, color contrast violations, and improper heading structure.
- Ongoing Testing: Accessibility testing is integrated into our development workflow. We test with keyboard-only navigation, screen readers, and browser accessibility tools as part of our quality assurance process.
We are committed to continually improving the accessibility of 38os and ensuring that our platform serves all users effectively.