See app
Digital Accessibility

Accessibility Statement

Last tested: October 16, 2026

Our Commitment

At This Is Why I'm High, we believe that everyone deserves equal access to cannabis education and personal research tools. Accessibility is not an afterthought - it is a core principle that guides how we design and build our products.

We are committed to making both our website (thisiswhyimhigh.com) and our High IQ mobile application accessible to all users, including those with disabilities. Our goal is to ensure that people of all abilities can navigate, understand, and interact with our content effectively.

Our Promise

We continuously work to improve the accessibility of our digital experiences. This is an ongoing effort, and we welcome feedback from our community to help us do better.

Standards We Follow

We strive to conform to the following accessibility standards and guidelines:

WCAG 2.2 Level AA

The Web Content Accessibility Guidelines (WCAG) 2.2 Level AA is our target. The W3C publishes these guidelines. Version 2.2 adds rules for target size and focus visibility that older checks miss.

Conformance status: partially conforms. The website meets most Level AA criteria in our tests, but the issues under Known Limitations below do not yet meet them. We have not had an independent audit.

How we test

Last tested: October 16, 2026. We ran the automated checker axe-core on ten key pages (home, app, strains, a strain page, Learn, an article, dispensaries, FAQ, contact and this page) at phone and desktop widths. We also tested by hand with a keyboard, at 320 px width (400% zoom), and with reduced motion turned on. We have not tested with a screen reader such as VoiceOver, NVDA or TalkBack, and we have not tested the native iOS app against these checks. Automated tools find only part of all problems.

  • Perceivable: Information and user interface components must be presentable to users in ways they can perceive
  • Operable: User interface components and navigation must be operable
  • Understandable: Information and the operation of the user interface must be understandable
  • Robust: Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies

Other standards

We have not assessed the site against Section 508 or the ADA as a separate exercise. WCAG 2.2 AA is the benchmark both usually point to, so we use it as the working target.

Accessibility Features

We have implemented the following accessibility features across our website and mobile app:

Navigation & Interaction

  • Keyboard Navigation: Interactive elements can be reached and operated with only a keyboard on the pages we tested, apart from the exceptions under Known Limitations. The mobile menu holds focus while open and returns it when you close it with Escape. The cookie notice does not take focus or block the rest of the page.
  • Focus Indicators: Visible focus indicators help users understand which element is currently selected when navigating with a keyboard.
  • Skip Links: Skip navigation links allow users to bypass repetitive content and jump directly to main content.
  • Consistent Navigation: Navigation menus and page layouts are consistent throughout the site for predictability.

Visual Design

  • Color Contrast: We aim for contrast of at least 4.5:1 for normal text and 3:1 for large text. We fixed the failures our October 2026 check found (tag chips and muted gray text). Some text may still fall short; see Known Limitations.
  • Text Resizing: Content stays readable and usable when text is resized to 200%, and at 400% zoom (320 px wide) the pages we tested did not scroll sideways.
  • Color Independence: We use icons and text labels beside color for most status information. Some links in chip rows are not underlined; see Known Limitations.
  • Responsive Design: Our layout adapts to different screen sizes and orientations without horizontal scrolling.

Content Accessibility

  • Alt Text for Images: Every image on the pages we tested has an alt attribute, and images that carry meaning have descriptive text. We did not review every image on the site.
  • Semantic HTML: We use proper HTML elements (headings, lists, landmarks) to provide structure that assistive technologies can interpret.
  • Descriptive Links: Link text clearly describes the destination or purpose, avoiding vague phrases like "click here."
  • Form Labels: Form inputs on the pages we tested have labels, and errors are announced to assistive technology.

Assistive Technology Support

  • Screen Reader Compatibility: We build with semantic HTML and ARIA so the site should work with screen readers. We have not yet tested with VoiceOver, NVDA or TalkBack, so we cannot confirm this.
  • ARIA Attributes: We use ARIA (Accessible Rich Internet Applications) attributes where needed to enhance the accessibility of dynamic content.
  • Reduced Motion: Users who prefer reduced motion (via their system settings) will see minimal or no animations.

High IQ Mobile App

The High IQ iOS app is designed with Apple's accessibility guidelines in mind. The tests described on this page covered the website only; we have not verified the app.

Known Limitations

While we strive for comprehensive accessibility, we acknowledge that some areas may have limitations. We are actively working to address these:

Known issues on the website (October 16, 2026)

  • Small targets: Some links are smaller than the 24 by 24 pixel minimum in WCAG 2.2 (criterion 2.5.8), for example some list links on the home, FAQ and app pages, and the breadcrumb on Learn. We fixed the strain page chip links. Links inside sentences are exempt.
  • Voice control names: A few links have an accessible name that does not start with the visible text (the header app button, the A to Z letter links on the strains page and some social links), so saying the visible words may not work in voice control.
  • Link cues: Effect, terpene and activity chips on strain pages look like plain chips until you hover or focus them, so sighted users may not know they are links.
  • Landmarks: The app-download banner on strain and article pages sits outside any landmark, and the app page has two note landmarks with the same name.
  • Motion: Decorative smoke animation runs longer than five seconds on some pages with no pause button. It stops if you turn on reduced motion in your system settings.
  • Header: The sticky header is slightly see-through, which may lower link contrast while scrolling.
  • Contrast: We darkened the muted gray text color, but we checked only a sample of pages, so some text may still be below 4.5:1.

Third-Party Content

  • Some embedded content from third-party sources (such as external lab reports or partner websites) may not meet the same accessibility standards as our own content.
  • Social media widgets and embeds may have accessibility limitations outside our control.

Interactive Data Visualizations

  • Some interactive charts and graphs displaying strain data, consumption analytics, or terpene profiles may have limited screen reader support.
  • We are working to provide text-based alternatives and accessible data tables for these visualizations.

PDF Documents

  • Some downloadable PDF documents may not be fully accessible. We are working to remediate these documents and provide accessible alternatives.

Older Content

  • Some older content on our site may not yet meet our current accessibility standards. We are systematically reviewing and updating this content.

Continuous Improvement

We are committed to addressing these limitations. If you encounter any accessibility barriers, please let us know so we can prioritize improvements.

Feedback & Contact

We value your feedback on the accessibility of our products. If you experience any accessibility barriers, have suggestions for improvement, or need assistance accessing any part of our website or app, please reach out to us.

Contact Us

Email: hello@highailabs.com

Subject Line: "Accessibility Feedback" or "Accessibility Issue"

What to Include in Your Feedback

To help us address your concerns effectively, please include:

  • A description of the accessibility issue you encountered
  • The URL or location (website page or app screen) where you experienced the issue
  • The device, operating system, and browser or app version you were using
  • Any assistive technology you were using (e.g., screen reader, magnification software)
  • Your preferred format for our response

Our Response Commitment

  • We aim to acknowledge your feedback within 2 business days.
  • We will investigate reported issues and provide a substantive response within 10 business days.
  • For issues we can fix, we will prioritize them in our development roadmap.
  • For issues outside our control, we will work to provide alternative access where possible.

Additional Resources

For general questions or other support needs, you can also visit:

Making Cannabis Education Accessible to All

Accessibility is an ongoing journey, not a destination. We are committed to continuously improving our digital experiences to serve all members of our community.

WCAG 2.2 AA

Our target. We partially conform today

Continuous Updates

We re-test and publish the date here

Open Feedback

We welcome and prioritize accessibility feedback

Effective Date: January 2, 2026 | Last tested and updated: October 16, 2026 (axe-core and manual keyboard checks, no screen reader)