Accessibility.
Ongoing work.
Glowbite is committed to making our website usable for everyone — including people using screen readers, keyboard-only navigation, and assistive tech.
Our commitment
What we build
toward.
Target standard
We design and test glowbite.us against WCAG 2.1 Level AA. That's the same standard used by most US federal and state accessibility mandates.
Keyboard & screen readers
All interactive controls — nav, cart drawer, quiz, FAQ accordions, forms — are reachable by keyboard. All images have alt text. All icon-only buttons have aria-labels.
Contrast & type
Body text maintains a minimum 4.5:1 contrast ratio against its background. Large display headings maintain a minimum 3:1. We use real text, not images of text.
Motion
Decorative motion (marquee, fade-ins) respects the user's prefers-reduced-motion preference and pauses/softens automatically.
Forms
All form fields have visible labels, programmatic labels for assistive tech, and descriptive error messages. We don't rely on placeholder text as the only label.
What we haven't gotten to yet
Known gaps,
listed honestly.
The opposite of “we pride ourselves on being accessible” is telling you what we still have to fix. Here's that list.
- 01.The Supplement Facts panel on the Safety page is rendered as a real HTML table rather than an image, so it can be read by a screen reader and reflowed at any zoom level. We do not publish Certificates of Analysis — the Safety page explains why — so there are no scanned PDFs on this site to make accessible.
- 02.Motion-heavy sections (the homepage hero, the category marquee) are intentionally simple but still contain animation. If you need a fully static version of a page, email us and we'll provide one.
- 03.Non-English translations are community-contributed and may lag behind English page updates by 1–2 weeks.
Tell us when we fall short
If something here
doesn't work for you,
email access@glowbite.us with a short description of the issue and, if possible, the page URL and your assistive technology. We commit to responding within two business days and to fixing WCAG 2.1 AA failures within 30 days when technically feasible.
Last reviewed April 2026.