Accessibility Statement

← Back to Hume Band

Last updated: July 2026

Making humeband.us and the Hume Health app function properly for people using assistive technology is treated with the same priority as everything else about the site. Below is a summary of our current approach and where to send feedback if something isn't working.

Our Standard

We measure humeband.us against WCAG 2.1, Level AA. In practice, that shapes decisions like:

• Writing alt text that accurately describes what meaningful images actually show — and leaving it empty for pure decoration.
• Maintaining readable text-to-background contrast ratios throughout every page.
• Building every interactive element — the mobile navigation, FAQ accordions, and checkout flow — to be fully operable by keyboard alone.
• Using proper heading structure and ARIA attributes so screen readers announce content in a logical order.
• Keeping layouts stable and functional even when a visitor zooms in or increases their default font size significantly.

An Ongoing Commitment, Not A One-Time Task

Accessibility work doesn't have a finish line — the site evolves, and the work has to move alongside it. If you encounter a barrier on humeband.us or inside the app, letting us know is genuinely how things improve here.

How To Report An Issue

If assistive technology runs into something it can't handle on our site or app, we want the details. A useful report typically includes:

• The specific page URL or the name of the app screen where the problem occurred
• A description of what didn't work as expected
• Which assistive technology, browser, and device you were using at the time

Reports like this get prioritized quickly — especially anything that blocks browsing the product, understanding the features, or completing a purchase.

Components Built By Third Parties

Some sections of humeband.us — the checkout process being the clearest example — run on third-party platforms rather than our own code. We choose partners with a track record of taking accessibility seriously, but their internal implementation is outside our direct control. If you hit a problem there, flag it and we'll either push the vendor or help you find an alternative path through.