Accessibility
An accessible website works for people using screen readers, keyboards, zoom or just a phone in bright sunshine. That’s a lot of your customers. Our accessibility standards follow WCAG and go further, into how it actually feels to use your site.
Why it matters.
Accessibility problems are among the most common issues on the web, and many are simple design fixes: contrast, labels, focus states and sensible headings.
Automated scanners catch some of these. A designer catches the rest: whether the keyboard order makes sense, whether an error is announced, whether the page still works zoomed to 200%. We use both.
What our reviewers look for.
Text is easy to read
Body text and labels meet WCAG AA contrast (4.5:1), including text over images.
Images are described
Meaningful images have alt text that says what matters; decorative ones stay silent.
Everything works with a keyboard
Menus, filters, modals and checkout can be used without a mouse, with a clear focus outline.
Every field has a real label
Labels stay visible as people type, rather than placeholders that disappear.
Motion can be turned down
Animations respect the “reduce motion” setting and nothing flashes.
Headings form a clear outline
Screen-reader users can skim the page by its headings, just as everyone else does.
These are a few of the standards in this area. Inside a Flume review, every standard comes with examples, the reasoning behind it and how to fix it.
The slip, and the fix.
Related standards.
SEO & AI visibility
Found by search engines and answer engines alike.
e.g.Products carry structured data for price and stockPerformance
Fast where it counts: on a phone, on a so-so connection.
e.g.The main content loads in under 2.5 secondsGrowth
Ideas to lift order value and bring customers back.
e.g.The cart suggests genuinely relevant add-onsHow does your site measure up? Find out first.
Join the beta and we’ll be in touch when a review spot opens. We’re running a limited number of free case-study reviews while we build.