Webflow × Brink (via agency 8020)
Webflow x 8020/Brink, AA accessibility without a single plugin
Plugin dependency to native compliance
Members read free
Unlock the full breakdown
Enter your email to open every case study in the library: the full screenshot, why it works, and the one thing worth stealing. One email unlocks all of them.
Free. No spam. Unsubscribe anytime.
You're in — enjoy the library.
Why it works
The case study centers on a capability that most practitioners assumed required heavy engineering: full WCAG 2.1 AA compliance built in a visual no-code tool, with no plugins and no custom code. 8020 committed to the no-plugin approach before proving Webflow could clear the bar, and that prior commitment is what gives the story its tension. The result speaks directly to mission-driven organizations and agencies serving regulated or compliance-heavy clients, because it dismantles the assumption that serious accessibility work sits outside the reach of no-code tooling.
Steal this
Lead with the skeptic's objection as a direct quote before showing the result. The co-founder's line about plugins being a flawed approach frames the entire story as a rebuttal, which makes the payoff land harder.
Click to enlarge ↗ This is editorial commentary and curation. The case study, screenshot, and all metrics are Webflow's published work; we link to the source and lead with our analysis.