Skip to content
https://framer.website

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-lf5wvp
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://framer.website/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://framer.website/manifest.json

Manifest contains invalid JSON.

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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
14 headings, 3 skip(s)
REVIEW
14 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Build bettersites, faster
  • H2 Create, collaborate, and go live
  • H5 AI skipped
  • H5 Design
  • H5 CMS
  • H5 Collaborate
  • H2 Scale without switching tools
  • H6 Analytics & insights skipped
  • H6 A/B Testing & optimization
  • H6 SEO & performance
  • H2 Powering ambitious teams worldwide
  • H2 Get pro help from handpicked experts
  • H2 Launch faster with community resources
  • H5 Design bold. Launch fast. skipped

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
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 Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 16 fail WCAG AA
REVIEW

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

4 pass 16 fail WCAG AA
h1 Build better
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · above the fold
h1 sites, faster
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · above the fold
h2 Create, collaborate, and go live
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · mid-page
title Framer: Create a professional website, f…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
p State of Sites ’26
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
p Unlock the report now
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
p •
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
p Framer is the site builder trusted by le…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
p startups and Fortune 500 companies. Buil…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
p fast and scale more easily with an integ…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
p Start for free
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
p Start with AI
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
p Meet our customers
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
p Generate page layouts and advanced compo…
4.07:1
#000000
on
#6E6D6C
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
p Learn more
1.12:1
#000000
on
#121211
needs 4.5:1 (normal text)
16px · mid-page
p Craft responsive layouts and bring them …
1.11:1
#000000
on
#111111
needs 4.5:1 (normal text)
16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Build better1.00:13.0:1
#000000
#000000
Fail
h1 sites, faster1.00:13.0:1
#000000
#000000
Fail
h2 Create, collaborate,…1.00:13.0:1
#000000
#000000
Fail
h2 Scale without switch…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Powering ambitious t…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Get pro help from ha…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Launch faster with c…21.00:13.0:1
#000000
#FFFFFF
Pass
title Framer: Create a pro…1.00:14.5:1
#000000
#000000
Fail
p State of Sites ’261.00:14.5:1
#000000
#000000
Fail
p Unlock the report no…1.00:14.5:1
#000000
#000000
Fail
p •1.00:14.5:1
#000000
#000000
Fail
p Framer is the site b…1.00:14.5:1
#000000
#000000
Fail
p startups and Fortune…1.00:14.5:1
#000000
#000000
Fail
p fast and scale more …1.00:14.5:1
#000000
#000000
Fail
p Start for free1.00:14.5:1
#000000
#000000
Fail
p Start with AI1.00:14.5:1
#000000
#000000
Fail
p Meet our customers1.00:14.5:1
#000000
#000000
Fail
p Generate page layout…4.07:14.5:1
#000000
#6E6D6C
Fail
p Learn more1.12:14.5:1
#000000
#121211
Fail
p Craft responsive lay…1.11:14.5:1
#000000
#111111
Fail

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.

B
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 24 passed
REVIEW
85

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
Read more “Framer gives us everything we need to move fast. We don’t wait on d… section > div > ul > li
Read more “At FLORA, we care about flow—how ideas move from imagination to int… section > div > ul > li
View Expert View Expert View Expert View Expert section > div > ul > li
View Expert View Expert View Expert View Expert section > div > ul > li
View Expert View Expert View Expert View Expert section > div > ul > li

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI div.framer-132x63k > div.framer-dt1v3t > div.framer-1kvkv5h > h5.framer-text
Analytics & insights div.framer-13l79oe > div.framer-1b9p9iv > div.framer-nat20 > h6.framer-text
Design bold. Launch fast. header.framer-wwoz7e > div.framer-18kmygp > div.framer-wnkup0 > h5.framer-text

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.framer-1wamsc4 > div.framer-58u914 > div.framer-1fn0637-container > a.framer-e94vJ div.framer-1wamsc4 > div.framer-58u914 > div.framer-1fn0637-container > a.framer-e94vJ
div.framer-m1tpra > div.framer-bzoid5 > div.framer-1gmkxuw-container > a.framer-e94vJ div.framer-m1tpra > div.framer-bzoid5 > div.framer-1gmkxuw-container > a.framer-e94vJ

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item
div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item
div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item
div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item
div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item
div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item
div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item
div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item div.framer-LKr4t > div.framer-e8l7kg > ul > li.ticker-item
View Component Image Slider Component Before and after images View Template… div.framer-1xu6a61 > ul > div.ssr-variant > li.ticker-item
View Template Apex Films Template Multimedia portfolio View Component Flip… div.framer-1m1m87c > ul > div.ssr-variant > li.ticker-item

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Scroll to page 1 section > fieldset.framer--slideshow-controls > div > button
Scroll to page 2 section > fieldset.framer--slideshow-controls > div > button
Scroll to page 3 section > fieldset.framer--slideshow-controls > div > button
Scroll to page 4 section > fieldset.framer--slideshow-controls > div > button
Scroll to page 5 section > fieldset.framer--slideshow-controls > div > button

These items highlight common accessibility best practices.

○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
●`[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
●Input buttons have discernible text.
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○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
○ARIA IDs are unique
○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 type="image">` elements have `[alt]` text
○Form elements have associated labels
○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.
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○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.
A
Landmark Structure
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A+
Alt Text Quality
All 147 images OK
PASS
All 147 images OK
Info::
75 decorative image(s) correctly marked
Info::
72 image(s) with good alt text
147 images 72 good alt text 75 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback