What are Flows?
A Flow is a scheduled accessibility check that walks through a real journey on your live site — signing in, adding to a cart, changing a setting — and audits each page it lands on. Instead of testing a single URL, a Flow tests the pages people actually reach by using your product.
Each Flow runs on a cadence you choose (daily or weekly) and alerts you only on new violations. When you approve a Flow, AccessLint records everything it finds as a baseline of “known violations.” From then on, scheduled runs compare against that baseline and surface only regressions — the issues introduced since you last approved — so you’re not re-notified about problems you’ve already triaged.
Flows describe each step in plain language, with no CSS selectors. AccessLint navigates by the page’s accessibility tree — the same structure a screen reader uses — so a Flow keeps working when your markup changes, rather than breaking the moment a class name or DOM path is refactored.
Getting started
- Set up a domain. Flows can only run against a hostname you’ve proven you control, since they type stored credentials into forms and run on a schedule.
- Author a flow. Describe the journey in prose and let AccessLint draft the steps, build them by hand in the step editor, or generate them from your repo.
- Run a dry run and approve it. The dry run resolves every step and audits each page. Approving it seeds the baseline and starts the schedule.
Open Flows and Domains from the navigation in your dashboard to begin. You can sign in with GitHub or with just your email.
Going further
- Read a run’s results — what the step statuses, healed badges, and violation diff mean.
- Generate flows from a list of journeys — draft many flows in one batch from typed rows or a CSV export.
- Manage known violations — dismiss noise, audit past dismissals, and keep the alarm honest.
- Know what emails to expect — when alerts go out, who gets them, and what each kind means.
- Trigger runs on deploy — check a journey minutes after each release, not just on the schedule.
How many flows can I have?
GitHub accounts can have up to 5 flows. Personal (email) workspaces include 1 flow free; subscribing raises the limit to 5 — see How do I change or cancel my plan?