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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
404 Error Page
Action
HTTP 404, custom page
FIX
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 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

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::
Search functionality detected
Got: role-search
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 2 <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
Landmark Structure
Action
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV SEARCH MAIN CONTENTINFO (missing!)

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

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

B
Favicon & Branding
17 icon(s) detected
REVIEW
17 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
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
h1 Build, Secure, and Deliver. Instantly.
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · mid-page
h2 Want to learn more?
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Let’s build something amazing
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Trusted by the world’s leading digital…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Our platform is fully programmable. You …
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 A more powerful global network
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 The one thing every business needs is fl…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Provide faster and more secure retail ex…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Provide faster and more secure retail ex…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Deliver stellar streaming experiences
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Deliver stellar streaming experiences
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Deliver faster service from the start wi…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Deliver faster service from the start wi…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Try a modern CDN and innovate ahead of t…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Try a modern CDN and innovate ahead of t…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
title Powering the best of the internet | Fast…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Under Attack?
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a (844) 4FASTLY
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Support Center
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Log in
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Build, Secure, and D…1.00:13.0:1
#000000
#000000
Fail
h2 Want to learn more?1.00:13.0:1
#000000
#000000
Fail
h2 Let’s build someth…1.00:13.0:1
#000000
#000000
Fail
h3 Trusted by the world…1.00:13.0:1
#000000
#000000
Fail
h3 Our platform is full…1.00:13.0:1
#000000
#000000
Fail
h3 A more powerful glob…1.00:13.0:1
#000000
#000000
Fail
h3 The one thing every …1.00:13.0:1
#000000
#000000
Fail
h3 Provide faster and m…1.00:13.0:1
#000000
#000000
Fail
h3 Provide faster and m…1.00:13.0:1
#000000
#000000
Fail
h3 Deliver stellar stre…1.00:13.0:1
#000000
#000000
Fail
h3 Deliver stellar stre…1.00:13.0:1
#000000
#000000
Fail
h3 Deliver faster servi…1.00:13.0:1
#000000
#000000
Fail
h3 Deliver faster servi…1.00:13.0:1
#000000
#000000
Fail
h3 Try a modern CDN and…1.00:13.0:1
#000000
#000000
Fail
h3 Try a modern CDN and…1.00:13.0:1
#000000
#000000
Fail
title Powering the best of…1.00:14.5:1
#000000
#000000
Fail
a Under Attack?1.00:14.5:1
#000000
#000000
Fail
a (844) 4FASTLY1.00:14.5:1
#000000
#000000
Fail
a Support Center1.00:14.5:1
#000000
#000000
Fail
a Log in1.00:14.5:1
#000000
#000000
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 89/100 — 5 failing, 28 passed
REVIEW
89

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4 div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4
div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4 div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4
div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4 div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4
div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4 div._3p4evt0 > div._3p4evt1 > div._3p4evt2 > button._3p4evt4
div.xg4goqs > div.xg4goqw > div.jjcfm4 > button.jjcfm5 div.xg4goqs > div.xg4goqw > div.jjcfm4 > button.jjcfm5
div.xg4goqs > div.xg4goqw > div.jjcfm4 > button.jjcfm5 div.xg4goqs > div.xg4goqw > div.jjcfm4 > button.jjcfm5

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.xg4goqd > div.xg4goqg > div.xg4goqj > a.jxvqufi div.xg4goqd > div.xg4goqg > div.xg4goqj > a.jxvqufi

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.

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
as of December 31, 2022 div.j1bsna4 > ul.j1bsna0 > li._6twr8h6 > div._1j2kes810y
as of July 31, 2023 div.j1bsna4 > ul.j1bsna0 > li._6twr8h6 > div._1j2kes810y
as of March 2023 div.j1bsna4 > ul.j1bsna0 > li._6twr8h6 > div._1j2kes810y
as of December 31, 2025 div.j1bsna4 > ul.j1bsna0 > li._6twr8h6 > div._1j2kes810y

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
More announcements main > div._1y3v4p30 > div._1y3v4p31 > h6.nbbs0e9

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookie Policy div.ot-sdk-eight > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●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 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
●ARIA toggle fields have accessible names
●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
○`[accesskey]` values are unique
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○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
○`<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
○`<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.
A
Heading Hierarchy
23 headings, 1 skip(s)
PASS
23 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H6 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Build, Secure, and Deliver. Instantly.
  • H6 More announcements skipped
  • H3 Trusted by the world’s leading digital innovators
  • H3 Our platform is fully programmable. You get smarter solutions, better insights, and more control.
  • H3 Network Services
  • H3 Security
  • H3 Compute
  • H3 Observability
  • H3 A more powerful global network
  • H3 The one thing every business needs is flexibility
  • H3 Provide faster and more secure retail experiences
  • H3 Provide faster and more secure retail experiences
  • H3 Deliver stellar streaming experiences
  • H3 Deliver stellar streaming experiences
  • H3 Deliver faster service from the start with our travel planning experiences
  • H3 Deliver faster service from the start with our travel planning experiences
  • H3 Try a modern CDN and innovate ahead of the market
  • H3 Try a modern CDN and innovate ahead of the market
  • H2 Want to learn more?
  • H3 Fastly Network Effect Threat Report
  • H3 Gartner Voice of the Customer for Cloud Web Application and API Protection
  • H3 What is the modern CDN and why is it important?
  • H2 Let’s build something amazing

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

A+
Alt Text Quality
All 13 images OK
PASS
All 13 images OK
Info::
12 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
13 images 1 good alt text 12 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