Our commitment#
We want Glowwer to be usable with a keyboard alone, with a screen reader, at 200% zoom, on a phone, and by people who see colour differently or need more contrast. We treat an accessibility barrier as a bug, and we fix bugs.
Our target#
Our internal quality target is the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We use it to guide how we build: semantic headings and landmarks, visible focus, text that scales, contrast that clears the AA thresholds, alternative text on meaningful images, and controls that work without a mouse.
We do not claim certified or full conformance. Glowwer has not been audited by a third party, and parts of the product — the design editor, the calendar, the sign-in screens provided by our authentication provider — are still being improved. Where we know of a gap, we say so below.
What we check today#
- Automated checks (axe) on public pages, at phone and desktop widths, in our review runs before a release.
- Keyboard-only walkthroughs of the paste-a-website flow, the weekly review, and these policy pages.
- Contrast of text against its background on public pages, against the AA thresholds.
- That every meaningful image has alternative text, and decorative ones are hidden from assistive technology.
- That pages have one main landmark, one first-level heading, and headings in order.
Known limitations#
- The sign-in and sign-up forms are provided by our authentication provider; we style them but do not control their markup.
- Generated post images are pictures of designed text; the caption and the design’s text are available as text in the review screen, but the image itself is not.
- The pricing page does not yet have a first-level heading, so a screen reader’s headings list starts at the second level there. It is on our list; this entry goes when it is fixed.
- Some product screens were built before our current checks and are being brought up to them.
Tell us what is in your way#
If something in Glowwer does not work for you, write to hello@glowwer.com with the page, what you were trying to do, and the browser and assistive technology you use. We read every report, reply to it, and treat barriers as priority fixes. If you need this statement or any policy in another format, ask and we will provide it.