Alt Text Generator
Writes descriptive alt texts for CMS and static images. Review the suggestion, approve it, write it back.
1 credit per image32 tools in four categories
FlowPowerUser connects your Webflow sites to tools that read what is there, check it against clear criteria and write corrections back. Nothing changes until you approve it.
Why bother
Anyone running ten Webflow projects does the same steps ten times: adding alt texts, filling meta fields, checking links, testing accessibility. None of it is hard, all of it takes long.
And every publish can break something that nobody checks, because nobody has the time to walk through every page again.
Every new site brings the same passes with it. Ten sites means ten times the same pass, by hand.
A moved CMS field, a deleted slug, an image without alt text: visible only once someone trips over it.
By email, days later, in wording you then have to translate into a ticket.
How it works
Every tool follows the same run. Learn one and you know them all.
Authorise the Webflow site once. The workspace reads pages, CMS items and assets, read-only until you allow more.
Set the scope: whole site, one collection, one page. The run shows how many credits it needs before it starts.
Every finding arrives as a suggestion with its location. Approve, edit or discard, one by one or all at once.
What you approved gets written back to Webflow. What was written stays in the log.
The tools
Writes descriptive alt texts for CMS and static images. Review the suggestion, approve it, write it back.
1 credit per imageUsable, but still in testing. Please report what you find
Checks a site against a fixed set of quality criteria and collects every finding in one place.
Checks whether the markup says what it is: landmarks, lists, controls — instead of a surface made of divs.
Finds dead links before your client does. It only reports real errors.
Checks the site for accessibility under the German Accessibility Strengthening Act.
Measures what makes the page slow and shows the element the load is waiting for.
Shows which files a site actually uses and which ones only sit there.
Finds every place a word or an image appears, across pages, CMS and meta data.
Reads the published CSS, groups colours and radii by property and shows hard-coded values along with their classes and where they appear.
The order follows what the waitlist asks for most
What is measurably wrong is something a machine finds more reliably than the eye.
Texts, meta fields and languages. Everywhere the CMS holds many items.
Fields, classes, tokens: the frame everything else breaks against later.
Handover, approvals, access: the work around the work.
What it costs
There is no per-seat licence and no per-site package. You hold credits, and a run spends credits. How many, you see before it starts.
Every run states what it will spend beforehand. A run that never starts costs nothing.
What the beta tools will cost is not settled yet. While they are in testing we would rather say nothing than say it wrong.
One tool is running, eight are in beta. Whoever is on the list gets the beta tools first and has a say in which one gets built next.
One email to confirm, after that only when a new tool ships.
Access currently by invitation only
Waitlist
Free and non-binding. No purchase yet, just a pre-registration so we can see who wants to be part of it.