Skip to content
https://utorrent.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
20 headings, 2 skip(s)
REVIEW
20 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
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.
  • H6 µTorrent Web
  • H6 µTorrent Classic
  • H6 µTorrent Android
  • H6 µTorrent Remote
  • H2 µTorrent Web
  • H2 Play torrents while you download.
  • H2 Ideal for new users.
  • H2 µTorrent Classic
  • H1 A very tiny desktop torrent client for experienced users.
  • H3 Download torrents in bulk skipped
  • H3 Optimize your bandwidth
  • H3 Schedule your downloads
  • H3 Remotely connect to µTorrent Classic
  • H3 Learn more About our Mobile Torrent Application.
  • H2 µTorrent Android
  • H6 Company skipped
  • H6 Downloads
  • H6 Support
  • H6 Social
  • H6 Languages

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

B
Alt Text Quality
2 of 20 images have issues
REVIEW
2 of 20 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
3 decorative image(s) correctly marked
Info::
15 image(s) with good alt text
20 images 15 good alt text 3 decorative 2 missing
IssueCount
missing2 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

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

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

12 pass 8 fail WCAG AA 1 pass AA only
a Windows
1.68:1
#000000
on
#323246
needs 4.5:1 (normal text)
16px · top of page (header area)
a Mac
1.63:1
#000000
on
#303043
needs 4.5:1 (normal text)
16px · above the fold
a Windows
1.54:1
#000000
on
#2C2C3E
needs 4.5:1 (normal text)
16px · above the fold
a Mac
1.47:1
#000000
on
#29293A
needs 4.5:1 (normal text)
16px · above the fold
a Linux
1.41:1
#000000
on
#262637
needs 4.5:1 (normal text)
16px · above the fold
a Forum
1.32:1
#000000
on
#21212F
needs 4.5:1 (normal text)
16px · above the fold
a Languages
1.28:1
#000000
on
#1E1E2C
needs 4.5:1 (normal text)
16px · above the fold
a English
1.26:1
#000000
on
#1D1D2A
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 A very tiny desktop …20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Play torrents while …20.82:13.0:1
#000000
#FEFEFE
Pass
h2 Ideal for new users.20.82:13.0:1
#000000
#FEFEFE
Pass
h3 Learn more About our…20.82:13.0:1
#000000
#FEFEFE
Pass
title µTorrent (uTorrent)…21.00:14.5:1
#000000
#FFFFFF
Pass
a Try AI21.00:14.5:1
#000000
#FFFFFF
Pass
a Products5.85:14.5:1
#000000
#868694
Pass
a Windows1.68:14.5:1
#000000
#323246
Fail
a Mac1.63:14.5:1
#000000
#303043
Fail
a Windows1.54:14.5:1
#000000
#2C2C3E
Fail
a Mac1.47:14.5:1
#000000
#29293A
Fail
a Linux1.41:14.5:1
#000000
#262637
Fail
a Forum1.32:14.5:1
#000000
#21212F
Fail
a Languages1.28:14.5:1
#000000
#1E1E2C
Fail
a English1.26:14.5:1
#000000
#1D1D2A
Fail
a 中文（简体）20.82:14.5:1
#000000
#FEFEFE
Pass
a 中文（繁體）20.82:14.5:1
#000000
#FEFEFE
Pass
a Deutsch20.82:14.5:1
#000000
#FEFEFE
Pass
a Español20.82:14.5:1
#000000
#FEFEFE
Pass
a Français20.82:14.5:1
#000000
#FEFEFE
Pass

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.

C
Lighthouse Accessibility Audits
Action
Score 79/100 — 6 failing, 23 passed
REVIEW
79

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
FREE DOWNLOAD div.col-lg-6 > a#win-homepage-hero-utweb-comp > button.btn-primary > span.text-nowrap
µTorrent div.col-lg-6 > div.d-block > h2.d-inline > span.font-weight-bold
FREE DOWNLOAD div.col-lg-6 > a#win-homepage-hero-classic-comp > button.btn-primary > span.text-nowrap
LAUNCH NOW div.mx-auto > div.m-auto > a#homepage-lite-launch-mobile > button.btn-primary
WEB div.d-flex > a#panels-hp-web-provpn-link > button.btn > span.text-nowrap
CLASSIC div.d-flex > a#panels-hp-classic-provpn-link > button.btn > span.text-nowrap
POPULAR div#comparison-panels > div.row > div.col-12 > div.popular
WEB div.d-flex > a#panels-hp-web-pro-link > button.btn > span.text-nowrap
CLASSIC div.d-flex > a#panels-hp-classic-pro-link > button.btn > span.text-nowrap
WEB div.d-flex > a#panels-hp-web-af-link > button.btn > span.text-nowrap
CLASSIC div.d-flex > a#panels-hp-classic-af-link > button.btn > span.text-nowrap

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
Download torrents in bulk div.my-4 > div.feature-list-content > div.pl-4 > h3
Company div.row > div.col-md-9 > div.col-6 > h6#company

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main.container-fluid > div.top-section-container > div.position-absolute > img.utlite-lightning main.container-fluid > div.top-section-container > div.position-absolute > img.utlite-lightning
div.d-flex > div.p-3 > div.mb-3 > img div.d-flex > div.p-3 > div.mb-3 > img

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.container > div.row > div.col-lg-6 > a#mac-homepage-hero-utweb-comp div.container > div.row > div.col-lg-6 > a#mac-homepage-hero-utweb-comp
div.container > div.row > div.col-lg-6 > a#mac-homepage-hero-classic-dl div.container > div.row > div.col-lg-6 > a#mac-homepage-hero-classic-dl
div.top-section-container > div.d-flex > div.p-3 > a#homepage-lite-launch-desktop div.top-section-container > div.d-flex > div.p-3 > a#homepage-lite-launch-desktop
div#comparison-panels > div.row > div.col-12 > a#panels-provpn-buynow div#comparison-panels > div.row > div.col-12 > a#panels-provpn-buynow
div#comparison-panels > div.row > div.col-12 > a#panels-pro-buynow div#comparison-panels > div.row > div.col-12 > a#panels-pro-buynow
div#comparison-panels > div.row > div.col-12 > a#panels-af-buynow div#comparison-panels > div.row > div.col-12 > a#panels-af-buynow

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
Includes all Pro features div.col-12 > div.mt-4 > div.panelBullets > li
CyberGhost VPN div.col-12 > div.mt-4 > div.panelBullets > li
VPN on up to 5 devices div.col-12 > div.mt-4 > div.panelBullets > li
Prevent online tracking div.col-12 > div.mt-4 > div.panelBullets > li
Secure torrent downloads div.col-12 > div.mx-3 > div.panelBullets > li
Block malware & viruses div.col-12 > div.mx-3 > div.panelBullets > li
No ads, no distractions* div.col-12 > div.mx-3 > div.panelBullets > li
File conversion* div.col-12 > div.mx-3 > div.panelBullets > li
Use less bandwidth div.col-12 > div.mt-4 > div.panelBullets > li
Simplified torrent downloads div.col-12 > div.mt-4 > div.panelBullets > li
Customer support div.col-12 > div.mt-4 > div.panelBullets > li

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
CLASSIC div.row > div.col-12 > div.d-flex > a#panels-hp-classic-provpn-link
CLASSIC div.row > div.col-12 > div.d-flex > a#panels-hp-classic-pro-link
CLASSIC div.row > div.col-12 > div.d-flex > a#panels-hp-classic-af-link

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
●`[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
●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
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 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.
○`<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
○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
4 landmarks
PASS
4 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
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /fonts/Inter/inter.css
Print Stylesheet ✓ Print Optimized
Print stylesheet /fonts/Inter/inter.css ✓Inline @media print Not detected ✗
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback