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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
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
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.
D
Lighthouse Accessibility Audits
Action
Score 57/100 — 6 failing, 11 passed
FIX
57

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
section.gap-2xl-vertical > div.stack-m-vertical > div.carousel-controls > button.tempo-icon-btn section.gap-2xl-vertical > div.stack-m-vertical > div.carousel-controls > button.tempo-icon-btn
section.gap-2xl-vertical > div.stack-m-vertical > div.carousel-controls > button.tempo-icon-btn section.gap-2xl-vertical > div.stack-m-vertical > div.carousel-controls > button.tempo-icon-btn

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
div.carousel-item > div.border-s > picture.tempo-picture > img div.carousel-item > div.border-s > picture.tempo-picture > img
div.carousel-item > div.border-s > picture.tempo-picture > img div.carousel-item > div.border-s > picture.tempo-picture > img
div.carousel-item > div.border-s > picture.tempo-picture > img div.carousel-item > div.border-s > picture.tempo-picture > img
div.carousel-item > div.border-s > picture.tempo-picture > img div.carousel-item > div.border-s > picture.tempo-picture > img
section.bg-primary > div.w-full > picture.tempo-picture > img section.bg-primary > div.w-full > picture.tempo-picture > img

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Čeština Dansk Deutsch English English (us) Español Español (latam) Français Hrv… div.legal > div.legal-list > div.index-navbar-lang > select#language_select

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
body#unlogged-body > nav.tempo-topbar > a#topbar-deezer-logo body#unlogged-body > nav.tempo-topbar > a#topbar-deezer-logo
div > footer.footer > div.cell > a.logo-container div > footer.footer > div.cell > a.logo-container
div.cell > ul.social-list > li.social-list-item > a#footer-social-link-facebook div.cell > ul.social-list > li.social-list-item > a#footer-social-link-facebook
div.cell > ul.social-list > li.social-list-item > a#footer-social-link-instagram div.cell > ul.social-list > li.social-list-item > a#footer-social-link-instagram
div.cell > ul.social-list > li.social-list-item > a#footer-social-link-twitter div.cell > ul.social-list > li.social-list-item > a#footer-social-link-twitter
div.cell > ul.social-list > li.social-list-item > a#footer-social-link-youtube div.cell > ul.social-list > li.social-list-item > a#footer-social-link-youtube

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
partners div.gdpr-modalScrollableContent > div.gdpr-wrapperCookieContent > p.gdpr-text > a#gdpr-partners-link
Accept div.gdpr-modalContainer > div.gdpr-modalCtas > div.gdpr-ctaContainer > button#gdpr-btn-accept-all

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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-hidden="true"]` is not present on the document `<body>`
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○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.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) 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.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

C
Alt Text Quality
Action
5 of 7 images have issues
REVIEW
5 of 7 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
2 image(s) with good alt text
7 images 2 good alt text 5 missing
IssueCount
missing5 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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page inexistante - Deezer ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Favicon & Branding
8 icon(s) detected
REVIEW
8 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA 2 pass AA only
h2 Choose the offer that works for you
1.43:1
#000000
on
#28282A
needs 3.0:1 (large text)
24px · mid-page · over background image/gradient
h2 Looking for a song?
1.03:1
#000000
on
#060507
needs 3.0:1 (large text)
24px · bottom of viewport
h2 You'll find it on Deezer with high-quali…
1.03:1
#000000
on
#060507
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Much more than a music streaming service
1.03:1
#000000
on
#060507
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The heart of music that beats all over t…
1.03:1
#000000
on
#060507
needs 3.0:1 (large text)
24px · bottom of viewport
h2 by 10 million music lovers
1.03:1
#000000
on
#060507
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Transfer your entire music library to De…
1.03:1
#000000
on
#060507
needs 3.0:1 (large text)
24px · bottom of viewport
h2 FAQ
1.03:1
#000000
on
#060507
needs 3.0:1 (large text)
24px · bottom of viewport
h3 What is Deezer?
1.03:1
#000000
on
#060507
needs 3.0:1 (large text)
19px · bottom of viewport
h3 How much does Deezer cost?
1.03:1
#000000
on
#060507
needs 3.0:1 (large text)
19px · bottom of viewport
h3 How do I use Deezer?
1.03:1
#000000
on
#060507
needs 3.0:1 (large text)
19px · bottom of viewport
h3 How do I cancel my subscription?
1.03:1
#000000
on
#060507
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Where can I listen to Deezer?
1.03:1
#000000
on
#060507
needs 3.0:1 (large text)
19px · bottom of viewport
title Deezer | Listen to music online | Music …
1.03:1
#000000
on
#060507
needs 4.5:1 (normal text)
16px · top of page (header area)
a Plans
1.03:1
#000000
on
#060507
needs 4.5:1 (normal text)
16px · top of page (header area)
a Features
3.61:1
#000000
on
#656566
needs 4.5:1 (normal text)
16px · top of page (header area)
a Music
3.61:1
#000000
on
#656566
needs 4.5:1 (normal text)
16px · top of page (header area)
a Log in
3.45:1
#000000
on
#626263
needs 4.5:1 (normal text)
16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Where music comes to…3.19:13.0:1
#000000
#5D5D5E
Pass
h2 Live the music with …3.19:13.0:1
#000000
#5D5D5E
Pass
h2 Choose the offer tha…1.43:13.0:1
#000000
#28282A
Fail
h2 Looking for a song?1.03:13.0:1
#000000
#060507
Fail
h2 You'll find it on De…1.03:13.0:1
#000000
#060507
Fail
h2 Much more than a mus…1.03:13.0:1
#000000
#060507
Fail
h2 The heart of music t…1.03:13.0:1
#000000
#060507
Fail
h2 by 10 million music …1.03:13.0:1
#000000
#060507
Fail
h2 Transfer your entire…1.03:13.0:1
#000000
#060507
Fail
h2 FAQ1.03:13.0:1
#000000
#060507
Fail
h3 What is Deezer?1.03:13.0:1
#000000
#060507
Fail
h3 How much does Deezer…1.03:13.0:1
#000000
#060507
Fail
h3 How do I use Deezer?1.03:13.0:1
#000000
#060507
Fail
h3 How do I cancel my s…1.03:13.0:1
#000000
#060507
Fail
h3 Where can I listen t…1.03:13.0:1
#000000
#060507
Fail
title Deezer | Listen to m…1.03:14.5:1
#000000
#060507
Fail
a Plans1.03:14.5:1
#000000
#060507
Fail
a Features3.61:14.5:1
#000000
#656566
Fail
a Music3.61:14.5:1
#000000
#656566
Fail
a Log in3.45:14.5:1
#000000
#626263
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+
Heading Hierarchy
14 headings
PASS
14 headings
Info::
Single H1 present
  • H2 Live the music with Deezer
  • H1 Where music comes to life
  • H2 Choose the offer that works for you
  • H2 Looking for a song?You'll find it on Deezer with high-quality sound!
  • H2 Much more than a music streaming service
  • H2 The heart of music that beats all over the world
  • H2 by 10 million music lovers
  • H2 Transfer your entire music library to Deezer in just a few clicks
  • H2 FAQ
  • H3 What is Deezer?
  • H3 How much does Deezer cost?
  • H3 How do I use Deezer?
  • H3 How do I cancel my subscription?
  • H3 Where can I listen to Deezer?
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="language_select">
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#language_selectselect(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select id="language_select">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

Send Feedback