Skip to content
https://www.webflow.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
2
REVIEW
3
PASS
8
INFO
0
Checks
13
8 PASS 3 REVIEW 2 FIX
D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found<!-- --> - Webflow ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
A
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

A
Heading Hierarchy
56 headings
PASS
56 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 Platform
  • H2 Build
  • H2 Manage
  • H2 Optimize
  • H2 Extend
  • H2 Platform Overview
  • H2 Webflow AI
  • H2 Solutions
  • H2 Marketing
  • H2 Engineering
  • H2 Service Providers
  • H2 Enterprise
  • H2 AEO
  • H2 Resources
  • H2 Get started
  • H2 Learn
  • H2 Discover
  • H2 Get help
  • H2 Site Settings
  • H1 Make your website a growth engine
  • H2 Webflow is the agentic web marketing platform for high-performing brands
  • H3 Build together
  • H3 Publish at scale
  • H3 Optimize for growth
  • H2 300,000+ brands move 
the needle with Webflow
  • H2 From idea to impact, faster
  • H3 Build
  • H3 Manage
  • H3 Optimize
  • H2 Everything marketing teams love about webflow
  • H1 Smarter sites start here duplicate H1
  • H2 Grow your freelance web
design business with Webflow
  • H2 Design it your way
  • H3 Ship fast without cutting corners
  • H3 When clients grow, you grow
  • H3 Empower clients, risk-free
  • H2 Deliver rich experiences
  • H3 Set your site in motion
  • H3 Make content work harder
  • H3 Get discovered in AI search
  • H2 Work better with clients
  • H3 Streamline review cycles
  • H3 Simplify client billing
  • H3 Collaborate in real time
  • H2 Move faster with AI
  • H3 Automate the busywork
  • H3 Generate content, sections, and components
  • H3 Extend your AI workflow
  • H2 Make your website your competitive edge
  • H2 Product
  • H2 Solutions
  • H2 Resources
  • H2 Company
  • H2 Compare
  • H2 Community
  • H2 Get help

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Alt Text Quality
All 228 images OK
PASS
All 228 images OK
Info::
167 decorative image(s) correctly marked
Info::
61 image(s) with good alt text
228 images 61 good alt text 167 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Webflow
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Webflow ✓192×192 icon ✓512×512 icon ✓Start URL https://webflow.com/design/ ✓Display Mode standalone ✓
Name Webflow Display Mode standalone Theme Color #4353FF Background Color #1A1A1A Icons 3 icon(s)
A+
Dark Mode Support
Full dark mode support
PASS
Full dark mode support
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: light dark
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta light dark ✓Dark theme-color #146ef5 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Make your website a …20.29:13.0:1
#000000
#FBFBFB
Pass
h1 Smarter sites start …20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Platform21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Build21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Manage20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Optimize19.77:13.0:1
#000000
#F8F8F8
Pass
h2 Extend20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Platform Overview20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Webflow AI20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Solutions20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Marketing20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Engineering20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Service Providers20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Enterprise20.29:13.0:1
#000000
#FBFBFB
Pass
h2 AEO20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Resources20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Get started20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Learn20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Discover20.29:13.0:1
#000000
#FBFBFB
Pass
h2 Get help20.29:13.0:1
#000000
#FBFBFB
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 30 passed
PASS
97

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
10x In cost savings annually Read story → 67% decrease in dev ticketing Read st… div.logo_grid-layout > div.logo_grid-track > div.logo_grid-logos_wrapper > div.logo_grid-logos
10x In cost savings annually Read story → 67% decrease in dev ticketing Read st… div.logo_grid-layout > div.logo_grid-track > div.logo_grid-logos_wrapper > div.logo_grid-logos

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback