Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 2 REVIEW 7 FIX

Heading Hierarchy

Action

27 headings, 3 skip(s)

FIX

27 headings, 3 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

H2 The global edge platform that truly hops
H2 The global edge platform that truly hops
H2 Hop to the edge and never look back
H4 CDN skipped
H4 Stream
H4 Storage
H4 Optimizer
H4 Edge Scripting
H4 Magic Containers
H4 DNS
H4 Shield
H2 Hop ahead of the competition
H2 Simple to start. Built to scale.
H2 A global network built for more than speed
H4 Unlock every corner of the globe skipped
H3 The best support in the CDN business
H2 Join 85k+ happy customers
H2 Join 85k+ happy customers
H3 Recipe for success
H4 Dmitry Muzyka
H2 Hop on the fastest delivery
H4 bunny.net skipped
H4 Products
H4 Developers
H4 Support
H4 Big traffic? Talk to Sales
H4 Stay up to date with bunny.net

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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 ▾

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

Action

11 issue(s) across 199 links and 1 buttons

FIX

11 issue(s) across 199 links and 1 buttons

10 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: ; /cdn/; /stream/; /storage/; /optimizer/; /edge-scripting/; /magic-containers/; /dns/; /shield; /careers/

1 link(s) with generic text

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

Got: https://bunny.net/privacy ("Learn more")

10 link(s) open in new tab without warning

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

Got: https://www.g2.com/products/bunnycdn/reviews; https://www.g2.com/products/bunnycdn/reviews; mailto:hello@bunny.net; mailto:sales@bunny.net; tel:+1 (828) 660-1813; https://www.facebook.com/bunnycdn; https://bsky.app/profile/bunny.net; https://twitter.com/BunnyCDN; https://www.linkedin.com/company/bunnynet/; https://discord.gg/bunnynet?ref=bunny.net

178 link(s) with descriptive text

199 links

10 empty

1 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://www.g2.com/products/bunnycdn/rev…	4.8on G2	new tab	Add '(opens in new tab)' to text
/cdn/	(empty)	empty	Add link text or aria-label
/stream/	(empty)	empty	Add link text or aria-label
/storage/	(empty)	empty	Add link text or aria-label
/optimizer/	(empty)	empty	Add link text or aria-label
/edge-scripting/	(empty)	empty	Add link text or aria-label
/magic-containers/	(empty)	empty	Add link text or aria-label
/dns/	(empty)	empty	Add link text or aria-label
/shield	(empty)	empty	Add link text or aria-label
https://www.g2.com/products/bunnycdn/rev…	4.8on G2	new tab	Add '(opens in new tab)' to text
https://bunny.net/privacy	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Privacy
/careers/	(empty)	empty	Add link text or aria-label
mailto:hello@bunny.net	hello@bunny.net	new tab	Add '(opens in new tab)' to text
mailto:sales@bunny.net	sales@bunny.net	new tab	Add '(opens in new tab)' to text
tel:+1 (828) 660-1813	+1 (828) 660-1813	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/bunnycdn	bunny.net on Facebook	new tab	Add '(opens in new tab)' to text
https://bsky.app/profile/bunny.net	bunny.net on BlueSky	new tab	Add '(opens in new tab)' to text
https://twitter.com/BunnyCDN	bunny.net on Twitter	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/bunnyne…	bunny.net on Linkedin	new tab	Add '(opens in new tab)' to text
https://discord.gg/bunnynet?ref=bunny.ne…	bunny.net on Discord	new tab	Add '(opens in new tab)' to text

179 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

; /cdn/; /stream/; /storage/; /optimizer/; /edge-scripting/; /magic-containers/; /dns/; /shield; /careers/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://bunny.net/privacy ("Learn more")

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://www.g2.com/products/bunnycdn/reviews; https://www.g2.com/products/bunnycdn/reviews; mailto:hello@bunny.net; mailto:sales@bunny.net; tel:+1 (828) 660-1813; https://www.facebook.com/bunnycdn; https://bsky.app/profile/bunny.net; https://twitter.com/BunnyCDN; https://www.linkedin.com/company/bunnynet/; https://discord.gg/bunnynet?ref=bunny.net

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

404 Error Page

Action

HTTP 404, custom page

FIX

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗

Icons 8 icon(s)

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Favicon & Branding

18 icon(s) detected

REVIEW

18 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h2 The global edge platform that

1.24:1

#000000

#041D37

needs 3.0:1 (large text)

24px · bottom of viewport

h2 truly hops

1.24:1

#000000

#041D37

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The global edge platform that truly hops

1.24:1

#000000

#041D37

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Hop to the edge and never look back

1.24:1

#000000

#041D37

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Simple to start. Built to scale.

1.24:1

#000000

#041D37

needs 3.0:1 (large text)

24px · bottom of viewport

h2 A global network built for more than spe…

1.24:1

#000000

#041D37

needs 3.0:1 (large text)

24px · bottom of viewport

h2 85k+

1.24:1

#000000

#041D37

needs 3.0:1 (large text)

24px · bottom of viewport

h2 85k+ happy customers

1.24:1

#000000

#041D37

needs 3.0:1 (large text)

24px · bottom of viewport

h3 The best support in the CDN business

1.24:1

#000000

#041D37

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Recipe for success

1.24:1

#000000

#041D37

needs 3.0:1 (large text)

19px · bottom of viewport

title bunny.net - The Global Edge Platform tha…

1.25:1

#000000

#051E38

needs 4.5:1 (normal text)

16px · top of page (header area)

a Network

1.25:1

#000000

#051E38

needs 4.5:1 (normal text)

16px · top of page (header area)

a Pricing

1.25:1

#000000

#051E38

needs 4.5:1 (normal text)

16px · top of page (header area)

a Products

1.25:1

#000000

#051E38

needs 4.5:1 (normal text)

16px · top of page (header area)

li Products

1.25:1

#000000

#051E38

needs 4.5:1 (normal text)

16px · above the fold

div CDN

1.25:1

#000000

#051E38

needs 4.5:1 (normal text)

16px · above the fold

p Lightning-fast global CDN

1.25:1

#000000

#051E38

needs 4.5:1 (normal text)

16px · above the fold

li CDN

1.25:1

#000000

#051E38

needs 4.5:1 (normal text)

16px · above the fold

div Bunny CDN

1.25:1

#000000

#051E38

needs 4.5:1 (normal text)

16px · above the fold

div CDN Features

1.25:1

#000000

#051E38

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 The global edge plat…	1.24:1	3.0:1	#000000	#041D37	Fail
h2 truly hops	1.24:1	3.0:1	#000000	#041D37	Fail
h2 The global edge plat…	1.24:1	3.0:1	#000000	#041D37	Fail
h2 Hop to the edge and …	1.24:1	3.0:1	#000000	#041D37	Fail
h2 Simple to start. Bui…	1.24:1	3.0:1	#000000	#041D37	Fail
h2 A global network bui…	1.24:1	3.0:1	#000000	#041D37	Fail
h2 85k+	1.24:1	3.0:1	#000000	#041D37	Fail
h2 85k+ happy customers	1.24:1	3.0:1	#000000	#041D37	Fail
h3 The best support in …	1.24:1	3.0:1	#000000	#041D37	Fail
h3 Recipe for success	1.24:1	3.0:1	#000000	#041D37	Fail
title bunny.net - The Glob…	1.25:1	4.5:1	#000000	#051E38	Fail
a Network	1.25:1	4.5:1	#000000	#051E38	Fail
a Pricing	1.25:1	4.5:1	#000000	#051E38	Fail
a Products	1.25:1	4.5:1	#000000	#051E38	Fail
li Products	1.25:1	4.5:1	#000000	#051E38	Fail
div CDN	1.25:1	4.5:1	#000000	#051E38	Fail
p Lightning-fast globa…	1.25:1	4.5:1	#000000	#051E38	Fail
li CDN	1.25:1	4.5:1	#000000	#051E38	Fail
div Bunny CDN	1.25:1	4.5:1	#000000	#051E38	Fail
div CDN Features	1.25:1	4.5:1	#000000	#051E38	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.

Landmark Structure

4 landmarks

PASS

4 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

Alt Text Quality

1 of 139 images have issues

PASS

1 of 139 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

138 image(s) with good alt text

139 images 138 good alt text 1 missing

Issue	Count
missing	1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Lighthouse Accessibility Audits

Score 90/100 — 3 failing, 23 passed

PASS

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.

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
24 `li > div.numbers-wr > p.value-holder > p.value`
ms `li > div.numbers-wr > p.value-holder > p.value`
119 `li > div.numbers-wr > p.value-holder > p.value`
1.5 `li > div.numbers-wr > p.value-holder > p.value`
+ mil `li > div.numbers-wr > p.value-holder > p.value`
SRE Samsung Food `div.case-study > div.case-study__author > div.case-study__credit > p.author-details`

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
CDN `div.product > div.product-wr > div.product-content > h4`
Unlock every corner of the globe `div.banner-wr > div.content > div.content-wr > h4`
bunny.net `div.col-lg-10 > div.row > div.menu-col > h4`

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.products > div.product > div.product-wr > a `div.products > div.product > div.product-wr > a`
div.products > div.product > div.product-wr > a `div.products > div.product > div.product-wr > a`
div.products > div.product > div.product-wr > a `div.products > div.product > div.product-wr > a`
div.products > div.product > div.product-wr > a `div.products > div.product > div.product-wr > a`
div.products > div.product > div.product-wr > a `div.products > div.product > div.product-wr > a`
div.products > div.product > div.product-wr > a `div.products > div.product > div.product-wr > a`
div.products > div.product > div.product-wr > a `div.products > div.product > div.product-wr > a`
div.products > div.product > div.product-wr > a `div.products > div.product > div.product-wr > a`

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.

○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

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

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

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

●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-hidden="true"]` elements do not contain focusable descendents

○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

○Buttons have an accessible name

○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

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

○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

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.