Accessibility

useflower.dev aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, in both the light and the dark theme. The site follows your system’s light or dark setting. This statement covers polystrate.dev too: one page set in the same type and colours, with no form. Its picture of one brief’s records works from the keyboard: the arrow keys move between records, Enter opens one and Esc closes it. “Show as a list” shows the same records as lines of text. Each part of the picture sharpens as you scroll to it, and stays still when you ask your system to reduce motion.

Where it stands

The site partially conforms to WCAG 2.2 Level AA: most criteria are met, and a few are met only in part. The Accessibility Conformance Report goes through every Level A and AA criterion and says which. The known gaps are:

The handwritten correction in the home page tagline (“builders of things”) is drawn as vector outlines, not set as live text. Assistive technology reads the words, and the drawing scales without blurring, but your own fonts and text spacing don’t apply to it.
The waitlist form requires JavaScript. It uses Cloudflare Turnstile, in managed mode, to check that a person is signing up: it runs by itself and at most asks for a click, but its frame is Cloudflare’s and our automated checks don’t cover it.
The meadow, behind the home page and the meadow’s page, is a moving picture of flower’s builds, drawn on a canvas under the page’s text. It carries information: a flower’s stage of growth is its build’s state, its size follows the tokens the build used, and the stream moves faster the more tokens flower’s agents are using. The meadow’s page says this in words. A screen reader hears the picture’s name and its status line (whether it’s live). A flower’s state and tokens are given as text in the tag of a flower you pick. The stream’s speed has no text equivalent beyond the description on the meadow’s page. A pause button at the corner of the window stops it, and it stays still when you ask your system to reduce motion. A flower near enough to pick (at least 24 pixels across) shows its build’s state, tokens and rounds in a small tag when you hover or tap it, or from the keyboard: Tab to the meadow, then the arrow keys. A screen reader announces the tag, and Esc closes it.
The drawing at the foot of the home page, and the names on it, are decoration beside words that say the same thing, so they are hidden from assistive technology.
The site has been tested in Chromium only, by automated checks and by keyboard. It hasn’t yet been tested with a screen reader, or in Firefox or Safari.

What every build checks

Every change to the site goes through a gate, and the gate fails on any of these:

axe-core over every page, in the light and the dark theme, with zero violations against WCAG 2.2 A and AA and axe’s best-practice rules.
Lighthouse accessibility, SEO and best-practices scores of 100 on the home page, the meadow’s page, How it works and the waitlist, and on the home page in the dark theme.
No sideways scrolling at 320 or 390 px wide (nor at 1280 px), with the home page’s quote card open too.
The meadow draws, says whether it’s live, pauses, stays still under reduced motion, lets a flower be picked by hovering, tapping and the keyboard, and falls back to a still picture without WebGL2.
Valid HTML, links that resolve, and the title, description, language and heading structure of every page.
Colour contrast of every text and graphic colour, in both themes: 4.5:1 for text and 3:1 for graphics.

Report a problem

If something on the site doesn’t work for you, please tell us. Email hello@useflower.dev with the page’s address and what went wrong, and we’ll fix it or find you another way to get the content.

About this statement

This statement and the conformance report describe how the site measures against WCAG 2.2. They aren’t a legal certification or a claim of compliance with any law. They were last reviewed on 12 November 2026 and are updated by any release that changes the site’s interface.