Accessibility Statement

← Back to Hulme Band

Last updated: July 2026

Ensuring hulmeband.com and the Hume Health app work properly for people using assistive technology is as important to us as everything else about the site. Below is a summary of what we've done and how to let us know if something is falling short.

Our Standard

We measure hulmeband.com against WCAG 2.1, Level AA. In practice, that shapes decisions including:

• Writing alt text that accurately describes what meaningful images show — and omitting it entirely for purely decorative elements.
• Maintaining readable text-to-background contrast across every page, in every section.
• Building every interactive element — mobile navigation, FAQ accordions, checkout steps — to be fully operable by keyboard alone.
• Structuring pages with appropriate heading levels and ARIA attributes so that screen readers announce content in a logical, useful sequence.
• Keeping layouts stable and fully functional when a visitor zooms in or increases their default font size.

An Ongoing Process, Not A One-Off Task

Accessibility isn't a box to tick once — the site evolves, and our accessibility work must move alongside it. If you encounter a barrier anywhere on hulmeband.com or within the Hume Health app, reporting it is how things genuinely improve here.

How To Report An Issue

If assistive technology struggles with anything on our site or app, we want the details. A useful report typically includes:

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

Reports like these are prioritised quickly — particularly anything that prevents someone from browsing the product, understanding the features, or completing a purchase.

Third-Party Components

Certain parts of hulmeband.com — the checkout process in particular — operate on third-party platforms rather than our own code. We choose partners with a strong track record on accessibility, but their internal implementations fall outside our direct control. If you encounter a barrier there, flag it and we'll either escalate to the vendor or help you find an alternative path.