> ## Documentation Index > Fetch the complete documentation index at: https://docs.highailabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Accessibility Statement > Our commitment to digital accessibility, WCAG compliance goals, current status, and how to report accessibility issues. ## Overview This Is Why I'm High LLC is committed to ensuring that the High IQ mobile application, the thisiswhyimhigh.com website, and all related documentation are accessible to the widest possible audience, including people with disabilities. We believe that access to cannabis education and strain information should not be limited by ability. This statement outlines our accessibility goals, current status, and how you can help us improve. ## Our Commitment We are working toward conformance with the **Web Content Accessibility Guidelines (WCAG) 2.1** at the **AA level**. These guidelines, published by the World Wide Web Consortium (W3C), are the internationally recognized standard for digital accessibility. WCAG 2.1 AA conformance means our Services should be: * **Perceivable** — Information and interface components are presented in ways users can perceive (e.g., text alternatives for images, sufficient color contrast, content adaptable to different presentations) * **Operable** — Interface components and navigation are operable by all users (e.g., keyboard accessible, sufficient time to interact, no content that causes seizures) * **Understandable** — Information and interface operation are understandable (e.g., readable text, predictable functionality, input assistance) * **Robust** — Content is robust enough to be interpreted by a wide variety of user agents, including assistive technologies (e.g., screen readers, voice controls, magnification tools) ## Current Status ### Website (thisiswhyimhigh.com) Our website is built with Astro and React, and we actively work to maintain accessibility: | Area | Status | Details | | ------------------- | ----------- | ------------------------------------------------------------------------------ | | Semantic HTML | In progress | Using proper heading hierarchy, landmarks, and ARIA attributes | | Keyboard navigation | In progress | All interactive elements are keyboard accessible | | Color contrast | In progress | Text meets WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text) | | Image alternatives | In progress | Strain images and icons include descriptive alt text | | Responsive design | Implemented | Content adapts to all screen sizes and zoom levels up to 200% | | Focus indicators | In progress | Visible focus styles on all interactive elements | | Skip navigation | Planned | Skip-to-content links for keyboard users | ### Mobile App (High IQ) The High IQ iOS app is built with React Native and Expo. We leverage the platform's built-in accessibility features: | Area | Status | Details | | ------------------- | ----------- | ------------------------------------------------------------------- | | VoiceOver support | In progress | Screen elements include accessibility labels and hints | | Dynamic Type | In progress | Text scales with the user's preferred font size settings | | Color contrast | In progress | UI elements meet minimum contrast requirements | | Touch targets | Implemented | Interactive elements meet the minimum 44x44 point touch target size | | Motion | In progress | Respecting the "Reduce Motion" system setting for animations | | Screen reader order | In progress | Logical reading order for screen reader navigation | ### Documentation Site This documentation site is built on Mintlify, which provides a strong accessibility foundation: | Area | Status | Details | | ------------------- | ----------- | ----------------------------------------------------------------------- | | Semantic structure | Implemented | Proper heading hierarchy, landmark regions, and document structure | | Keyboard navigation | Implemented | Full keyboard support for navigation, search, and content interaction | | Color contrast | Implemented | Theme colors meet WCAG AA contrast requirements | | Search | Implemented | Accessible search with keyboard support and screen reader announcements | | Code blocks | Implemented | Syntax-highlighted code with appropriate ARIA attributes | | Dark mode | Implemented | Supports system preference and manual toggle | ## Known Limitations We are transparent about areas where we have not yet achieved full compliance: 1. **Strain data tables** — Some complex data tables on strain profile pages may not fully convey their structure to screen readers. We are working to add proper table headers and ARIA attributes. 2. **AI-generated content** — Content generated by AI features (reports, Professor High responses) may not always include optimal semantic structure. We are improving prompt engineering to produce more accessible output. 3. **Label scanner** — The label scanner feature is inherently visual and requires camera input. We are exploring alternative input methods (manual entry, photo library import) for users who cannot use the camera interface. 4. **Interactive charts** — Stats dashboard charts and data visualizations may not be fully accessible to screen readers. We are investigating accessible charting libraries and textual alternatives for visual data. 5. **Color-dependent information** — Some UI elements (such as High Family color coding) use color as a primary differentiator. We are adding text labels and icons alongside color to ensure information is conveyed through multiple channels. 6. **Third-party components** — Some third-party integrations (authentication flows, payment processing) may have their own accessibility limitations outside our direct control. We select providers that demonstrate commitment to accessibility. ## Accessibility Features ### Currently Available The following accessibility features are currently available across our Services: * **Text resizing** — Content reflows and remains usable when text is enlarged up to 200% * **High contrast support** — Our color themes meet WCAG AA contrast ratios * **Dark mode** — Available on website and in-app, following system preferences * **Keyboard navigation** — Core functionality is accessible via keyboard on web platforms * **Alt text** — Images include descriptive alternative text for screen readers * **Logical tab order** — Interactive elements follow a logical, predictable tab sequence * **Error identification** — Form errors are clearly identified with descriptive messages * **Consistent navigation** — Navigation patterns are consistent across pages and screens ### Planned Improvements We are actively working on the following accessibility enhancements: * **Skip navigation links** — Allow keyboard users to skip repetitive navigation * **ARIA live regions** — Real-time updates (streaming reports, search results) announced to screen readers * **Data table improvements** — Proper table headers and summary attributes for complex strain data * **Chart alternatives** — Text-based summaries for all visual data representations * **Voice control compatibility** — Testing and optimizing for voice control assistive technologies * **Accessibility audit** — Engaging a third-party accessibility consultant for a comprehensive audit ## Assistive Technology Testing We test our Services with the following assistive technologies: | Technology | Platform | Status | | ------------------------ | ----------- | ---------------- | | VoiceOver | iOS / macOS | Regular testing | | Safari + VoiceOver | Web | Regular testing | | Keyboard-only navigation | Web | Regular testing | | Dynamic Type | iOS | Regular testing | | Reduce Motion | iOS | Regular testing | | Increase Contrast | iOS | Periodic testing | We are expanding our testing program to include additional assistive technologies and welcome feedback from users of tools not listed above. ## Standards and Guidelines Our accessibility efforts are guided by: * **[WCAG 2.1 AA](https://www.w3.org/WAI/WCAG21/quickref/)** — Our primary conformance target * **[Apple Human Interface Guidelines - Accessibility](https://developer.apple.com/design/human-interface-guidelines/accessibility)** — iOS-specific guidance for the mobile app * **[WAI-ARIA 1.2](https://www.w3.org/TR/wai-aria-1.2/)** — Accessible Rich Internet Applications specification for dynamic web content * **[Section 508](https://www.section508.gov/)** — U.S. federal accessibility standards (informational reference) ## Reporting Accessibility Issues We welcome and value your feedback on the accessibility of our Services. If you encounter an accessibility barrier or have suggestions for improvement: ### How to Report Send a description of the issue to [accessibility@thisiswhyimhigh.com](mailto:accessibility@thisiswhyimhigh.com). Include: * The page or screen where you encountered the issue * A description of the barrier or difficulty * The assistive technology or browser you were using * Your device and operating system We will acknowledge your report within 3 business days. Our team will investigate the issue and determine a remediation plan. We will follow up with you regarding the status of the issue and our planned resolution timeline. ### Alternative Access If you are unable to access any content or feature due to an accessibility barrier, please contact us and we will work to provide the information or functionality through an alternative method. * **Email:** [accessibility@thisiswhyimhigh.com](mailto:accessibility@thisiswhyimhigh.com) * **General support:** [support@thisiswhyimhigh.com](mailto:support@thisiswhyimhigh.com) ## Continuous Improvement Accessibility is not a one-time effort but an ongoing commitment. We continuously work to improve the accessibility of our Services through: * Regular accessibility testing during development of new features * Team training on accessible design and development practices * Monitoring industry best practices and emerging accessibility standards * Incorporating user feedback into our accessibility roadmap * Periodic reviews of existing content and functionality This accessibility statement was last reviewed and updated in **February 2026**. We review and update this statement at least annually or whenever significant changes are made to our Services.