Structure a screen reader can follow
Real headings and page regions a screen reader can jump between, plus a skip-to-content link.
Accessibility
Accessibility is part of the craft here, not a box ticked at the end. If you can’t use something we made, that’s on us — tell us and we’ll get on it.
The standard we hold
We build to WCAG 2.2 Level AA, the current version, and we test with a keyboard and a screen reader, not only by eye. What WCAG is, in plain words.
Real headings and page regions a screen reader can jump between, plus a skip-to-content link.
Everything works without a mouse, and the focus outline stays visible so you always know where you are.
Text and controls are checked against WCAG AA contrast, and meaning is never carried by color alone.
If your device asks for reduced motion, the effects go still. Motion never sits behind text you have to read, and nothing flashes.
The honeycomb and light effects are marked so screen readers skip them — they’re atmosphere, not content.
Buttons and links describe their purpose, form fields are labeled, and any image that carries meaning gets text you can hear.
Buttons are big enough to tap, and the menu bar never hides the link or button you’ve tabbed to. Nothing on the site needs a drag.
Found something we missed?
Email Honeybloomstudios@proton.me. We read every message and work to fix accessibility issues promptly. If something is blocking you right now, tell us what you were trying to do and we’ll help you directly while we sort it out.