Accessibility

F

Heading Hierarchy

Action

32 headings, 7 skip(s)

FIX

32 headings, 7 skip(s)

Multiple H1 headings (2 found)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H3 → H6 (missing H4)

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

H1 Everything we learned from powering 20% of the Internet—yours by default
H3 The cloud that works for you, not the other way around skipped
H3 Region: Earth
H6 Run everywhere skipped
H6 Run anywhere
H6 Run at massive scale
H3 Cloudflare powers1 in 5 sites on the Internet
H3 Go from
H3 in minutes
H6 From first line to full scale skipped
H6 Deploy with one command
H6 Let it spike. We got you.
H3 Pay only when your code runs
H6 Wall Clock vs. CPU Time skipped
H3 Free
H6 100,000 skipped
H6 1 million
H6 25
H6 10GB
H3 Paid
H6 $0.30 skipped
H6 $0.02
H3 Why choose Cloudflare
H3 Fighting infra with “cloud”
H3 Shipping withCloudflare
H3 Tailored to your working style
H6 Fits into your existing workflows skipped
H6 Instant feedback loops
H6 Observable by default
H6 Compatible with your stack
H1 Build without boundaries duplicate H1
H2 Our site uses cookies

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

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

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

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

F

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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-4mrk6k

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.

D

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

F

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://workers.dev/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://workers.dev/manifest.json

Manifest contains invalid JSON.

D

Print Stylesheet

Action

No print styles

FIX

No print styles

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

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Link & Button Quality

7 issue(s) across 41 links and 42 buttons

REVIEW

7 issue(s) across 41 links and 42 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://blog.cloudflare.com ("here")

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://reactflow.dev

6 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.relative (#152 on page); button.relative (#242 on page); button.relative (#303 on page); button.relative (#901 on page); button.relative (#1209 on page); button.relative (#1883 on page)

39 link(s) with descriptive text

41 links

0 empty

1 generic text

1 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
https://blog.cloudflare.com	here	generic text	Replace with descriptive text
Before: here Suggested: Blog.Cloudflare.Com
https://reactflow.dev	React Flow attribution	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

75 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://blog.cloudflare.com ("here")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://reactflow.dev

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.relative (#152 on page); button.relative (#242 on page); button.relative (#303 on page); button.relative (#901 on page); button.relative (#1209 on page); button.relative (#1883 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

B

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA 2 pass AA only

button Products

2.22:1

#000000

on

#7F2908

needs 4.5:1 (normal text)

16px · top of page (header area)

button Solutions

2.22:1

#000000

on

#7F2908

needs 4.5:1 (normal text)

16px · top of page (header area)

button Resources

2.22:1

#000000

on

#7F2908

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Everything we learne…	6.08:1	3.0:1	#000000	#B27E69	Pass
h1 Build without bounda…	20.70:1	3.0:1	#000000	#FFFDFB	Pass
h2 Our site uses cookie…	20.70:1	3.0:1	#000000	#FFFDFB	Pass
h3 The cloud that works…	20.70:1	3.0:1	#000000	#FFFDFB	Pass
h3 Region: Earth	20.70:1	3.0:1	#000000	#FFFDFB	Pass
h3 Go from	20.70:1	3.0:1	#000000	#FFFDFB	Pass
h3 in minutes	20.70:1	3.0:1	#000000	#FFFDFB	Pass
h3 Pay only when your c…	20.70:1	3.0:1	#000000	#FFFDFB	Pass
h3 Free	20.70:1	3.0:1	#000000	#FFFDFB	Pass
h3 Paid	20.70:1	3.0:1	#000000	#FFFDFB	Pass
h3 Why choose Cloudflar…	20.70:1	3.0:1	#000000	#FFFDFB	Pass
h3 Fighting infra with …	20.70:1	3.0:1	#000000	#FFFDFB	Pass
h3 Shipping with	20.70:1	3.0:1	#000000	#FFFDFB	Pass
h3 Cloudflare	20.70:1	3.0:1	#000000	#FFFDFB	Pass
h3 Tailored to your wor…	20.70:1	3.0:1	#000000	#FFFDFB	Pass
title Cloudflare	5.18:1	4.5:1	#000000	#7F7E7D	Pass
div Cloudflare	5.18:1	4.5:1	#000000	#7F7E7D	Pass
button Products	2.22:1	4.5:1	#000000	#7F2908	Fail
button Solutions	2.22:1	4.5:1	#000000	#7F2908	Fail
button Resources	2.22:1	4.5:1	#000000	#7F2908	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.

A

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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 12 images OK

PASS

All 12 images OK

12 decorative image(s) correctly marked

12 images 12 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 25 passed

PASS

95

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Start building `div.mx-auto > div#nav-action-buttons > astro-island > a.relative`
Cloudflare is your AI Cloud with compute, AI inference, and storage — letting y… `div.px-section > div.max-w-8xl > div.flex > p.text-light-foreground`
"Cloudflare provided everything from OAuth to out-of-the-box remote MCP support… `div.relative > div#architecture-panel-0 > div.pointer-events-none > p.text-foreground-100/50`
~/workspace/multiplayer-app git:(main) `div.bg-background-100 > astro-island > div.text-xs > div.mb-2`
Paid `div.relative > div.bg-background-100 > div.flex > code.text-accent-100`
Free `div.relative > div.bg-background-100 > div.flex > code.text-accent-100/50`
See more `div.divide-brand-6 > div.relative > div.flex > a.relative`
Starts at $5/month `div.relative > div.flex > div.flex > p.text-accent-100/70`
Start building for free `astro-island > a#start-building-button > astro-slot > span`
View docs `astro-island > a.relative > astro-slot > span`
Getting Started `div.grid > div.flex > div.mb-3 > span.text-foreground-200/50`
Resources `div.grid > div.flex > div.mb-3 > span.text-foreground-200/50`
Solutions `div.grid > div.flex > div.mb-3 > span.text-foreground-200/50`
© 2026 Cloudflare, Inc. `footer.z-10 > div.bg-background-100 > div.pointer-events-auto > span.text-foreground-200/40`
English `div.text-foreground-200/40 > astro-island > button#radix-_r65R_0_ > span`
Your Privacy Choices `div.text-foreground-200/40 > astro-island > button.inline-flex > span`
Privacy Policy, Terms of Service, GDPR `div.bg-background-100 > div.pointer-events-auto > div.text-foreground-200/40 > div`
Privacy Policy `div.pointer-events-auto > div.text-foreground-200/40 > div > a.hover:text-foreground-100/70`
Terms of Service `div.pointer-events-auto > div.text-foreground-200/40 > div > a.hover:text-foreground-100/70`
GDPR `div.pointer-events-auto > div.text-foreground-200/40 > div > a.hover:text-foreground-100/70`
Reject All `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-reject-all-handler`
Accept All Cookies `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-accept-btn-handler`

These are opportunities to improve the legibility of your content.

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
The cloud that works for you, not the other way around `section#home-title-1 > div.flex > div.mx-auto > h3.text-foreground-100`
Run everywhere `div.relative > div.bg-background-100 > div.text-foreground-200 > h6.mt-2`
From first line to full scale `div > div.bg-background-100 > div.relative > h6.text-foreground-100`
Wall Clock vs. CPU Time `div.border-b > div.grid > div.flex > h6.text-foreground-200`
100,000 `div#home-pricing-panel-free-0 > div.flex > div.flex > h6.leading-none`
$0.30 `div#home-pricing-panel-paid-0 > div.flex > div.flex > h6.leading-none`
Fits into your existing workflows `div.lg:col-span-8 > div.bg-background-100 > div.flex > h6.text-foreground-100`

These are opportunities to improve keyboard navigation in your application.

○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

●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●ARIA input fields have accessible names

●Elements use only permitted ARIA attributes

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○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.

○Image elements have `[alt]` attributes

○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>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○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.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○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.