Accessibility

Accessibility statement

Last updated: March 31, 2026

Our commitment

DeeplyHeard is committed to ensuring digital accessibility for people with disabilities. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across the platform. We continually improve the user experience for everyone and apply relevant accessibility standards where possible.

Conformance status

DeeplyHeard is partially conformant with WCAG 2.1 Level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard.

What we have done

  • Semantic HTML5 throughout, with proper heading hierarchy (h1 → h2 → h3)
  • WAI-ARIA roles and labels on all interactive elements (buttons, nav, dialogs)
  • Keyboard navigation supported across all pages and the authenticated app
  • Focus-visible indicators on all focusable elements
  • Color contrast ratios meet WCAG 2.1 AA for all text (≥4.5:1 normal, ≥3:1 large)
  • Indigo color used exclusively for crisis resource links to ensure 3:1 contrast on all backgrounds
  • All images include descriptive alt text; decorative images use aria-hidden
  • Mobile navigation (hamburger drawer) is keyboard and screen-reader accessible
  • Crisis resources (988, Crisis Text Line) use tel: and sms: links with aria-labels
  • Form inputs include visible labels and descriptive error messages
  • Reduced motion respected via prefers-reduced-motion media query

Known limitations

Despite our efforts, some areas of the platform may not fully meet WCAG 2.1 AA. Known limitations include:

  • Some data visualizations on the Insights page do not have full text alternatives (work in progress)
  • Live region announcements in the community feed may be delayed in some screen reader configurations

We are actively working to address these limitations. If you encounter a barrier not listed here, please contact us.

Technical specifications

DeeplyHeard relies on the following technologies for conformance with WCAG 2.1:

  • HTML5
  • WAI-ARIA 1.2
  • CSS3
  • JavaScript (ECMAScript 2020+)

How to report an accessibility issue

We welcome feedback. If you encounter an accessibility barrier or have suggestions for improvement:

  • Email support@deeplyheard.org
  • Include the page URL, a description of the issue, and the assistive technology you were using
  • We aim to respond within one business day

Formal complaints

If you are not satisfied with our response to your accessibility concern, you may contact the relevant enforcement body in your country. In the United States, this is the Department of Justice Civil Rights Division.

DeeplyHeard is free, anonymous, and takes three minutes to join. Find your stage →