Skip to content
https://speedtest.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
D
Alt Text Quality
Action
3 of 17 images have issues
FIX
3 of 17 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
2 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
4 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
17 images 10 good alt text 4 decorative 3 missing
IssueCount
missing3 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗
Icons 2 icon(s)
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
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.
B
Heading Hierarchy
10 headings
REVIEW
10 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Having Internet Problems?
  • H4 Find Your Next ISP with Speedtest’s Help
  • H5 Servers close to you:
  • H2 Become a Host
  • H2 Try Speedtest for Desktop
  • H2 Remove ads on Speedtest.net for life
  • H3 Speedtest®
  • H3 Ziff Davis
  • H3 Ookla® Brands
  • H3 Apps

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Speedtest ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA
title Speedtest by Ookla - The Global Broadban…
1.16:1
#000000
on
#141526
needs 4.5:1 (normal text)
16px · top of page (header area)
span English
1.15:1
#000000
on
#131425
needs 4.5:1 (normal text)
16px · top of page (header area)
a العربية
1.15:1
#000000
on
#131424
needs 4.5:1 (normal text)
16px · top of page (header area)
a Deutsch
1.15:1
#000000
on
#131424
needs 4.5:1 (normal text)
16px · top of page (header area)
a English
1.15:1
#000000
on
#131424
needs 4.5:1 (normal text)
16px · above the fold
a Español
1.15:1
#000000
on
#131424
needs 4.5:1 (normal text)
16px · above the fold
a Français
1.15:1
#000000
on
#131424
needs 4.5:1 (normal text)
16px · above the fold
a Bahasa Indonesia
1.15:1
#000000
on
#131424
needs 4.5:1 (normal text)
16px · above the fold
a Italiano
1.15:1
#000000
on
#131424
needs 4.5:1 (normal text)
16px · above the fold
a 日本語
1.15:1
#000000
on
#131424
needs 4.5:1 (normal text)
16px · above the fold
a 한국어
1.15:1
#000000
on
#131424
needs 4.5:1 (normal text)
16px · above the fold
a Nederlands
1.15:1
#000000
on
#131424
needs 4.5:1 (normal text)
16px · above the fold
a Polski
1.15:1
#000000
on
#131424
needs 4.5:1 (normal text)
16px · above the fold
a Português
1.15:1
#000000
on
#131424
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Become a Host9.04:13.0:1
#000000
#AAAAAA
Pass
h2 Try Speedtest for De…9.04:13.0:1
#000000
#AAAAAA
Pass
h2 Remove ads on Speedt…9.04:13.0:1
#000000
#AAAAAA
Pass
h3 Having Internet Prob…9.04:13.0:1
#000000
#AAAAAA
Pass
h3 Ookla9.04:13.0:1
#000000
#AAAAAA
Pass
h3 Brands9.04:13.0:1
#000000
#AAAAAA
Pass
title Speedtest by Ookla -…1.16:14.5:1
#000000
#141526
Fail
span English1.15:14.5:1
#000000
#131425
Fail
a العربية1.15:14.5:1
#000000
#131424
Fail
a Deutsch1.15:14.5:1
#000000
#131424
Fail
a English1.15:14.5:1
#000000
#131424
Fail
a Español1.15:14.5:1
#000000
#131424
Fail
a Français1.15:14.5:1
#000000
#131424
Fail
a Bahasa Indonesia1.15:14.5:1
#000000
#131424
Fail
a Italiano1.15:14.5:1
#000000
#131424
Fail
a 日本語1.15:14.5:1
#000000
#131424
Fail
a 한국어1.15:14.5:1
#000000
#131424
Fail
a Nederlands1.15:14.5:1
#000000
#131424
Fail
a Polski1.15:14.5:1
#000000
#131424
Fail
a Português1.15:14.5:1
#000000
#131424
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 86/100 — 5 failing, 23 passed
REVIEW
86

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Speedtest is better with the app. Download the Speedtest app for more metrics, … div.main-view > div > div.mobile-pretest > div.mobile-pretest-new

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.

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 > div.mobile-pretest > div.mobile-pretest-new > a.close-btn div > div.mobile-pretest > div.mobile-pretest-new > a.close-btn

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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Speedtest div.nav > div.pure-g > div.pure-u-1 > a.masthead-logo
GO div.pure-u-1 > div.mobile-start-wrapper > div.start-button > a.js-start-test

These are opportunities to improve keyboard navigation in your application.

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
Android div.apps > ul.menu-footer > li > a
Apple TV div.apps > ul.menu-footer > li > a
macOS div.apps > ul.menu-footer > li > a
Windows div.apps > ul.menu-footer > li > a

These items highlight common accessibility best practices.

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
GO div.pure-u-1 > div.mobile-start-wrapper > div.start-button > a.js-start-test
Our Privacy Policy div#onetrust-group-container > 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
●`[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.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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 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
○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
Landmark Structure
6 landmarks
PASS
6 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
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="zip-code-search-input-primary" id="zip-code-search-input-primary">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#host-searchtextSearchfor/id
#zip-code-search-input-primarytext(ie. 12345)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="zip-code-search-input-primary" id="zip-code-search-input-primary">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A
Favicon & Branding
7 icon(s) detected
PASS
7 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 Present
✓ Multiple Sizes Present
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback