Webflow Accessibility Checklist for WCAG 2.2 AA

Share this post

Articles from Graceful Web Studio on Webflow

A Webflow accessibility checklist for WCAG 2.2 AA covers semantic structure, color contrast, keyboard access, visible focus, form labels, alt text on CMS images, and motion control. Webflow gives you the tools to get each of these right, but it doesn't do any of them for you. Use this list while you build, then again as a final review before you publish.

The Webflow accessibility checklist

Structure and semantics

  • Set landmark tags (header, nav, main, footer) in each element's settings instead of stacking plain divs.
  • Use one H1 per page and keep headings in order without skipping levels.
  • Mark up lists as real lists, including CMS Collection Lists.
  • Write link text that makes sense out of context, not "click here" or "read more".

Color and contrast

  • Body text meets at least 4.5:1 contrast against its background.
  • Large text, icons, and form control borders meet at least 3:1.
  • No information is carried by color alone, such as red-only error states.

Keyboard and focus

  • Every link, button, and control can be reached and used with a keyboard.
  • Each focusable element shows a visible focus style.
  • Tab order matches the visual order, with no focus traps in menus or modals.
  • Sticky headers and cookie banners don't hide the focused element, a check added in WCAG 2.2.

Forms

  • Every input has a visible label tied to it, not just placeholder text.
  • Required fields and expected formats are stated in text.
  • Error messages are clear and connected to the field they describe.

Images and media

  • Meaningful images have descriptive alt text, set in the Asset panel or bound to a CMS field.
  • Decorative images are marked decorative so screen readers skip them.
  • Video and audio have captions or a transcript.

Motion and interactions

  • Animations respect the reduced-motion setting.
  • Auto-playing or moving content can be paused.
  • Sliders, tabs, and dropdowns expose the right roles and work with a keyboard.

Where do Webflow sites usually fall short?

The most common gaps we find are forms with missing or detached labels, custom interactions that only work with a mouse, and CMS images published without alt text. Forms are tricky enough that we wrote a full post on why Webflow forms fail accessibility. If you're new to the topic, start with our introductory guide to Webflow accessibility.

Is passing the checklist enough?

A checklist is the floor, not proof. Conformance is confirmed by a manual keyboard and screen reader pass, which catches the issues a list and an automated scanner miss. See what a full WCAG 2.2 audit covers. When you'd rather hand it off, our Webflow accessibility remediation service fixes issues at the source, and monthly maintenance keeps new content on track.

Want help getting your Webflow site to WCAG 2.2 AA? Request a free project quote.

Related articles

Written by Crystal Scott, founder of Graceful Web Studio. Crystal is a Certified Professional in Web Accessibility (CPWA), a Section 508 Trusted Tester, and a Certified Webflow Expert with over a decade of front-end experience.

Your Website Deserves Better, Let's Team Up

We'd love to meet you, over coffee in Yakima or on a video call. Request a free project quote and we'll review your site, set up a discovery session, and map out goals for a website that grows your business.

Crystal Scott, white female with blue eyes and blonde hair