Guides

Webflow Accessibility in 2026: What the Platform Does, What You Must Do, and the WCAG Checks That Fail Most

Which accessibility work Webflow does for you, which it leaves to the builder, the five checks Webflow sites fail most often, and the order we would test them in before launch.

Summarize with AI
Octo Agency cover: Webflow Accessibility in 2026, with a purple hexagon pattern

Webflow sites averaged a Lighthouse accessibility score of 89.07% across 121,277 pages in the HTTP Archive's 2025 Web Almanac, ahead of WordPress at 85.58% but behind Wix at 94.19% and Squarespace at 93.05%. The five audits Webflow pages failed most often were link names, colour contrast, heading order, a missing page language and target size. Every one of those is a builder decision, not a platform limit.

This guide separates what Webflow does for you from what it leaves to whoever builds the site, using Webflow's own accessibility statement and checklist, the WebAIM Million 2026 report, the Web Almanac and the WCAG 2.2 text. It ends with the order we would run the checks in before a launch.

What Webflow does for you

Webflow's accessibility statement makes a narrow, specific claim. Its most commonly used elements, Tabs, Dropdown, Image, Text Link, Link Block, Button, Section, List, List Item, Collection List, Navbar and Slider, "have been updated and tested for keyboard operability and screen reader support". Sites built with those elements, Webflow says, "conform to levels as high as WCAG 2.1 Level AA". The statement then adds the sentence that matters most for anyone buying a site: "when building an accessible site, the power lies in the hands of the builder."

The platform also gives builders tools inside the Designer. Webflow's accessibility page lists an Audit panel that flags missing alt text, empty links and out-of-sequence headings; a contrast checker for text; a preview that simulates low-vision viewing; alt text fields with a "decorative" option; HTML5 tag settings so a div can become a nav, main or article; and custom attributes for ARIA where the native element falls short.

What the statement does not say. It does not cover form inputs, the Lightbox, background video, or anything built from plain Div Blocks and interactions. It also says the Webflow Designer itself "does not fully support assistive technology", which matters if anyone on the client team who edits the site uses a screen reader. The statement still promises an update "in the latter half of 2021", so treat it as Webflow's position rather than a current audit.

Who is responsible for each WCAG area on a Webflow site
AreaWhat Webflow providesWhat the builder must do
Navbar, Tabs, Dropdown, SliderKeyboard support and ARIA on the native elementsStyle a visible focus state on every one; Webflow's checklist lists focus styling as a builder task
ImagesAlt text field and a decorative optionWrite alt text that describes purpose, mark decoration as decorative, fill CMS alt fields
Page languageA language code setting in project settingsSet it; it is not inferred
Headings and landmarksTag settings for headings, nav, main, header, footerChoose tags by structure, not by font size
Colour contrastA contrast checker in the DesignerCheck every text style, border and icon against its background
FormsForm block and inputsVisible labels, error text, focus states; not in Webflow's tested list
Accordions, modals, custom tabs built from divsInteractions that animateARIA states, focus management and Escape to close, through custom code
Skip linkNothing by defaultAdd one; Webflow's checklist routes it through custom code

Source: Webflow accessibility statement, accessibility page and accessibility checklist, read 2026-11-13

How Webflow sites score compared with other platforms

The HTTP Archive runs Google Lighthouse, which uses Deque's axe-core engine, on millions of home pages each year. Its 2025 accessibility chapter, last updated on 3 November 2026, groups the results by content management system. Lighthouse scores are weighted pass rates on automated checks, so they show where platforms differ on detectable issues, not whether any site conforms.

Average Lighthouse accessibility score by platform, 2025
PlatformPages measuredAverage accessibility score
Wix442,57094.19%
Squarespace250,66393.05%
Webflow121,27789.07%
HubSpot CMS Hub25,70888.41%
Shopify624,12887.89%
Framer Sites18,30587.28%
WordPress5,539,68285.58%

Source: HTTP Archive Web Almanac 2025, Accessibility chapter, Figure 6.40 data sheet

The Almanac's explanation for the gap is that hosted builders like Wix and Squarespace constrain what users can change. Webflow sits between them and WordPress for the opposite reason: it hands the builder raw HTML and CSS control, which gives a careful builder the means to reach a high score and a hurried one the means to break it.

The WebAIM gap. WebAIM's Million report, which tests rendered home pages with its WAVE engine, lists error averages for eight content management systems in 2026, from Adobe Experience Manager at 29.9 errors per page to WordPress at 52.8. Webflow is not in that table. Anyone quoting a WebAIM number for Webflow is quoting something the report does not contain.

The five checks Webflow sites fail most

The Almanac lists the five most common Lighthouse failures per platform. For Webflow, in order, they were link-name, color-contrast, heading-order, html-has-lang and target-size. Here is what each one means in the Designer and how to fix it.

1. Links without a name. A Link Block wrapping only an icon or an image with no alt text gives a screen reader nothing to read. Social icons in footers and card links are the usual cause. Webflow's checklist calls these empty links and routes them to the Audit panel. Fix: give the image meaningful alt text, or add an aria-label custom attribute on the Link Block. Avoid "Read more" repeated twelve times on a blog grid; WebAIM found ambiguous link text such as "click here" and "more" on more home pages in 2026 than in 2025.

2. Colour contrast. WCAG 2.2 requires 4.5:1 for body text and 3:1 for large text (criterion 1.4.3), plus 3:1 for borders, icons and focus indicators (criterion 1.4.11). WebAIM found low-contrast text on 83.9% of home pages in 2026, up from 79.1% in 2025, with an average of 34 instances per page. On Webflow builds the frequent offenders are grey body text on off-white, placeholder text inside form fields, and text over hero images or video. Fix: check each colour pair in the Designer's contrast tool, and add an overlay behind text on imagery.

3. Heading order. Webflow lets any text be any heading level, and the class name decides the look. That freedom is why designers pick an H4 because it is the right size. WebAIM found skipped heading levels on 41.8% of home pages in 2026. Fix: set heading levels by document structure, and let classes handle size. The Audit panel flags out-of-sequence headings.

4. Missing page language. The lang attribute tells a screen reader which pronunciation rules to use. Webflow's checklist puts it in project settings. WebAIM found it missing on 13.5% of home pages in 2026, and the Almanac on roughly 14% of sites, yet it is a single field. For localised sites, check that each locale outputs its own code.

5. Target size. WCAG 2.2 added criterion 2.5.8 at Level AA: pointer targets at least 24 by 24 CSS pixels, or spaced so that a 24 pixel circle around each does not overlap another. Webflow's own checklist goes further and recommends 44 pixels, which matches the stricter AAA criterion 2.5.5. Hamburger icons, close buttons on popups, and slider dots are the usual failures.

What automated tools miss

Lighthouse, WAVE and Webflow's Audit panel test what a rule can see in the markup. Deque, which sells axe, published a 2021 study of 2,000 audits and nearly 300,000 issues that found its automated rules covered 57% of issues by volume. That is a vendor-sourced figure, and it counts issues, not WCAG criteria. Either way, close to half of real barriers need a person to find them.

On Webflow sites, the human checks that matter most are these.

Focus visibility. WCAG 2.4.7 requires a visible focus indicator, and WCAG 2.2 adds 2.4.11: a focused element must not be entirely hidden by author content such as a sticky header or cookie banner. The Almanac found 67% of sites in 2025 removed default focus outlines with CSS, up 14% from 2024. Webflow's checklist asks builders to "clearly style focus states" on Tabs, Dropdown, Slider and Navbar. Fix: style a focus state on every interactive class, or add a site-wide focus-visible rule in custom code.

Forms. The Almanac found 53% of desktop inputs relied on placeholder text alone as their accessible name in 2025. Forms are absent from Webflow's tested element list, so labels, required-field text and error messages are the builder's job. Keep a visible label above every field.

Custom components. Accordions, modals and mega menus built from interactions need ARIA states and focus management in custom code. Webflow's checklist says modals should trap focus and close with Escape, and accordions should announce open or closed state.

Motion. Webflow interactions make parallax and scroll-triggered animation easy. The checklist advises avoiding parallax, scrolljacking and animated anchor scrolling. Respect the reduced-motion setting in custom code where motion is used.

Accessibility is a legal requirement in more places than it was two years ago, and the rules differ by market.

Rules that most often reach a Webflow marketing site
RuleWho it coversStandardStatus in November 2026
European Accessibility ActProducts and services sold in the EU, including e-commerce and banking; microenterprises providing services are exemptEN 301 549, which references WCAGApplies since 28 June 2025
ADA Title II ruleUS state and local governmentsWCAG 2.1 AACompliance dates moved to 26 April 2027 for entities of 50,000 or more people and 26 April 2028 for smaller ones
ADA Title III, through the courtsUS businesses open to the publicNo codified standard; WCAG used in practice5,114 digital lawsuits filed in 2025

Sources: European Commission EAA page; Deque EAA FAQ; US Department of Justice ADA fact sheet; UsableNet 2025 year-end report

A B2B marketing site is rarely the first target. UsableNet's 2025 report, a vendor report from a company that sells remediation, put e-commerce at 70% of US filings and food service at 21%, with digital media and agencies under 1%. Two numbers from the same report still matter for agencies: 1,427 suits targeted companies sued before, and filings against sites using accessibility widgets ran between 95 and 155 a month through 2025.

Overlays are not a fix. In April 2025 the US Federal Trade Commission finalised a $1 million order against accessiBe, which had claimed its widget "can make any website compliant" with WCAG. The order bars that claim without evidence. If a client asks for a widget instead of a fix, that order is the answer.

The order we would test a Webflow site in

The checks below follow the order in which issues are cheapest to fix. Run the first three during the build, not after it.

Pre-launch accessibility pass for a Webflow site
StepWhereWhat to check
1. SettingsProject settings, page settingsLanguage code set, unique page titles, zoom not disabled in custom code
2. Style guideDesigner, contrast checkerEvery text colour pair, border and icon at the required ratio; focus state on every interactive class
3. StructureNavigatorOne H1, no skipped levels, nav, main and footer tags set, skip link present
4. Audit panelDesignerZero missing alt text, empty links and heading-order flags
5. Automated scanLighthouse or WAVE on stagingEvery template, not only the home page; CMS templates with real content
6. Keyboard passStaging, no mouseEvery menu, tab, slider, form and popup reachable, visible and escapable
7. Screen reader passVoiceOver or NVDALinks and buttons announce a purpose; form errors are read; accordions announce state
8. Content handoverCMSAlt text field required in collections; editors know heading rules

Source: compiled from Webflow's accessibility checklist and WCAG 2.2; order is our recommendation

The last step is the one that decides whether the site stays accessible. A launch-day score drops the first time an editor uploads an image without alt text or picks an H5 for its size. Making the alt field required in each CMS collection, and writing two lines on heading rules into the handover guide, costs less than a re-audit.

What this means for a Webflow build

Webflow does more for accessibility than its reputation suggests, and less than its marketing implies. The native elements carry keyboard and screen reader support, and the Designer has an audit panel and contrast checker. Everything else, including focus states, forms, heading structure, contrast, page language and custom components, is the builder's work. That is why Webflow scores between the closed builders and WordPress in the Almanac data.

When you brief or review a Webflow build, ask which interactive components are native and which are built from divs, ask for a keyboard pass on staging, and check that the CMS will not let an image publish without alt text. We build marketing sites in Webflow over a four-week process, and our marketing websites service page explains how we scope a build.

Frequently asked questions

Is Webflow accessible?

Webflow can produce an accessible site, but it does not make one by default. Its statement says twelve native elements, including Navbar, Tabs, Dropdown and Slider, are tested for keyboard and screen reader use, and sites using them can reach WCAG 2.1 AA. Forms, custom components, contrast, headings and focus styles are the builder's responsibility. In the 2025 Web Almanac, Webflow pages averaged 89.07% on Lighthouse accessibility, above WordPress and below Wix and Squarespace.

Does Webflow have an accessibility checker?

Yes. The Designer has an Audit panel that flags missing alt text, empty links and out-of-sequence headings, a text contrast checker, and a preview that simulates low-vision viewing. These catch common automated issues but not keyboard traps, focus problems or unclear labels. Deque's own vendor study found automated rules covered about 57% of issues by volume, so a manual keyboard and screen reader pass is still needed before launch.

What are the most common accessibility errors on Webflow sites?

In the HTTP Archive's 2025 Web Almanac, the five most frequent Lighthouse failures on Webflow pages were links without a discernible name, insufficient colour contrast, headings out of order, a missing page language and touch targets that are too small. All five are fixed in the Designer or in project settings. Across the wider web, WebAIM found low-contrast text on 83.9% of top home pages in 2026.

Do Webflow sites need to meet WCAG 2.2?

It depends on the market and the law that applies. The European Accessibility Act, in force since June 2025, uses EN 301 549, which references WCAG. The US Title II rule for state and local governments names WCAG 2.1 AA, with compliance dates now in 2027 and 2028. WCAG 2.2, a W3C Recommendation, adds criteria such as target size and focus not obscured. Building to 2.2 AA covers 2.1 as well.

Will an accessibility widget make my Webflow site compliant?

No. In April 2025 the US Federal Trade Commission finalised a $1 million order against accessiBe for claiming its widget could make any website WCAG compliant. UsableNet, which sells remediation services, counted between 95 and 155 lawsuits a month in 2025 against companies already using widgets. Widgets do not change the underlying markup that screen readers and keyboards depend on, so fixes need to happen in the Designer.

Sources

  1. The WebAIM Million: the 2026 report on the accessibility of the top 1,000,000 home pages WebAIM, 2026
  2. Accessibility, Web Almanac 2025 HTTP Archive, 2026
  3. Web Almanac 2025 accessibility chapter data sheet HTTP Archive, 2026
  4. Accessibility statement: conformance status Webflow, 2026
  5. Web accessibility: guide, courses, and features Webflow, 2026
  6. Accessibility checklist Webflow, 2026
  7. Web Content Accessibility Guidelines (WCAG) 2.2 W3C, 2024
  8. What's new in WCAG 2.2 W3C WAI, 2026
  9. Fact sheet: new rule on the accessibility of web content and mobile apps provided by state and local governments US Department of Justice, 2026
  10. European accessibility act European Commission, 2026
  11. European Accessibility Act (EAA): top 20 key questions answered Deque, 2025
  12. 2025 year-end digital accessibility lawsuit report UsableNet, 2026
  13. FTC approves final order requiring accessiBe to pay $1 million US Federal Trade Commission, 2025
  14. Deque study shows its automated testing identifies 57 percent of digital accessibility issues Deque, 2021

Tags

  • Webflow
  • Accessibility
  • WCAG
  • Process
Mihajlo Stojanovic

Mihajlo Stojanovic

Co-founder, Octo Agency

Mihajlo runs the technical side of Octo Agency: Webflow builds, custom backends and the systems that keep a site editable after launch. He has shipped more than twenty Webflow sites a year as a white-label partner and writes about what survives contact with a real marketing team.

Veljko Nikolic

Reviewed by

Veljko Nikolic

Founder, Octo Agency

Veljko runs the build side of Octo Agency. He has shipped marketing sites for B2B teams in legal tech, health and manufacturing, and writes about what survives contact with a real review cycle.