Usable by everyone, on purpose.

1. The standard

We aim for full conformance with WCAG 2.2 (opens in a new tab) Level AA, which includes every Level A and AA success criterion from WCAG 2.0 and 2.1. Where a Level AAA criterion costs nothing, we meet it too: the focus ring is a solid two-pixel outline with a gap, nothing moves for people who ask their system for less motion, and no text is justified or set below the size the browser is asked for.

2. How we meet it

• Keyboard. Everything works without a mouse. A “Skip to content” link is the first thing the Tab key reaches, the sticky header never hides what the keyboard lands on, menus close with Escape, and nothing is a keyboard trap.
• Contrast. Every color of text, including the quiet gray we use for hints and dates, meets 4.5:1 against every surface it sits on, in light and in dark mode. Form field borders and the focus ring meet 3:1.
• Structure. One h1 per page, headings in order, named landmarks (main, navigation, breadcrumb, footer), real tables with column headers, real lists, real buttons and links. Links in running text are underlined, not only colored, and links that open a new tab say so to screen readers.
• Forms. Every field has a visible label, errors are written in plain words next to the field and announced, nothing is cleared when you make a mistake, and sign-in works with password managers and one-time codes with no puzzles to solve.
• Motion and timing. Animations respect the “reduce motion” setting. Nothing flashes. Nothing times out on the website.
• Zoom and reflow. The site works at 400% zoom and at a 320-pixel width without sideways scrolling, and text can be spaced out by a style sheet without anything being cut off.
• Targets. Buttons and controls are at least 24 by 24 pixels, and most are larger.

3. How we test

Every public page is checked by an automated run of axe-core (opens in a new tab) against the WCAG 2.0, 2.1 and 2.2 A and AA rules, in light and dark mode and at phone and desktop widths, with the cookie banner open and closed; a single finding fails the release. That run is part of the same test suite that checks the product's money and time rules. Alongside it, the pages are used by hand with a keyboard only and with a screen reader (VoiceOver on macOS and iOS, NVDA on Windows).

4. Outside our control

Card payments open Stripe's checkout pages, and the cookie choices load Google's and Meta's scripts; those companies publish their own accessibility statements. Shops upload their own artwork, photos and PDFs; we cannot add descriptions to those, and the product asks for a caption when a photo is added.

5. Tell us

If anything on the website or in the product is in your way, write to hello@usewrapflow.app with the page and what happened. A person answers within two business days and the fix, when one is needed, ships with the next release. You can also ask for any document on this site in another format.

See also the Privacy Policy and the Terms of Service.