Skip to content
https://skyrock.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
46
GRADE
F
FIX
8
REVIEW
3
PASS
2
INFO
0
Checks
13
2 PASS 3 REVIEW 8 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
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.
Page Structure — as a screen reader sees it
BANNER (missing!) MAIN (missing!) CONTENTINFO (missing!)

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

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-k3itux
404 Page Quality Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
PNG Icons Present
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://skyrock.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://skyrock.com/manifest.json

Manifest contains invalid JSON.

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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="range" id="bloc-range-volume">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email">
Info::
1 control(s) properly labeled
3 controls
1 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#conditions-newslettercheckboxJe souhaite recevoir la newsletter de Skyrock. Je peux me désinscrire à tout moment via le lien de désinscription figurant dans la newsletter.for/id
emailemail(Email)placeholder only
#bloc-range-volumerange(none)none

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

<input type="range" id="bloc-range-volume">

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

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

<input type="email" name="email">

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

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

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

1 pass 19 fail WCAG AA
h3 Les Derniers Épisodes
1.05:1
#000000
on
#080804
needs 3.0:1 (large text)
19px · bottom of viewport
title Skyrock
1.75:1
#000000
on
#0021A4
needs 4.5:1 (normal text)
16px · top of page (header area)
span Accueil
1.75:1
#000000
on
#0021A4
needs 4.5:1 (normal text)
16px · top of page (header area)
span Radios
1.60:1
#000000
on
#001E92
needs 4.5:1 (normal text)
16px · top of page (header area)
span Podcasts
1.39:1
#000000
on
#001777
needs 4.5:1 (normal text)
16px · top of page (header area)
span Vidéos
1.42:1
#000000
on
#011979
needs 4.5:1 (normal text)
16px · above the fold
span Actus
1.41:1
#000000
on
#021978
needs 4.5:1 (normal text)
16px · above the fold
span Sons diffusés
1.41:1
#000000
on
#021978
needs 4.5:1 (normal text)
16px · above the fold
span Jeux
1.40:1
#000000
on
#001878
needs 4.5:1 (normal text)
16px · above the fold
span Concerts
1.40:1
#000000
on
#011878
needs 4.5:1 (normal text)
16px · above the fold
span Grille
1.39:1
#000000
on
#001778
needs 4.5:1 (normal text)
16px · above the fold
span Animateurs
1.36:1
#000000
on
#001771
needs 4.5:1 (normal text)
16px · above the fold
span Fréquences
1.32:1
#000000
on
#011668
needs 4.5:1 (normal text)
16px · above the fold
span Applis
1.26:1
#000000
on
#02135F
needs 4.5:1 (normal text)
16px · above the fold
span Chat Skyrock
1.22:1
#000000
on
#011256
needs 4.5:1 (normal text)
16px · mid-page
span Skyrock Shop
1.18:1
#000000
on
#010F4D
needs 4.5:1 (normal text)
16px · mid-page
span PLM
1.15:1
#000000
on
#000E45
needs 4.5:1 (normal text)
16px · mid-page
span Télécharge l’appli Skyrock !
1.12:1
#000000
on
#010C3D
needs 4.5:1 (normal text)
16px · mid-page
span EN DIRECT
1.09:1
#000000
on
#000934
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

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 Difool – Radio Lib…4.72:13.0:1
#000000
#EB1837
Pass
h3 Les Derniers Épisod…1.05:13.0:1
#000000
#080804
Fail
title Skyrock1.75:14.5:1
#000000
#0021A4
Fail
span Accueil1.75:14.5:1
#000000
#0021A4
Fail
span Radios1.60:14.5:1
#000000
#001E92
Fail
span Podcasts1.39:14.5:1
#000000
#001777
Fail
span Vidéos1.42:14.5:1
#000000
#011979
Fail
span Actus1.41:14.5:1
#000000
#021978
Fail
span Sons diffusés1.41:14.5:1
#000000
#021978
Fail
span Jeux1.40:14.5:1
#000000
#001878
Fail
span Concerts1.40:14.5:1
#000000
#011878
Fail
span Grille1.39:14.5:1
#000000
#001778
Fail
span Animateurs1.36:14.5:1
#000000
#001771
Fail
span Fréquences1.32:14.5:1
#000000
#011668
Fail
span Applis1.26:14.5:1
#000000
#02135F
Fail
span Chat Skyrock1.22:14.5:1
#000000
#011256
Fail
span Skyrock Shop1.18:14.5:1
#000000
#010F4D
Fail
span PLM1.15:14.5:1
#000000
#000E45
Fail
span Télécharge l’app…1.12:14.5:1
#000000
#010C3D
Fail
span EN DIRECT1.09:14.5:1
#000000
#000934
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 83/100 — 6 failing, 27 passed
REVIEW
83

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
body.didomi-popup-open > div#__next > div.SideNavBar__BlocNavBar-sc-f04320cd-0 > button.toggleNavbar body.didomi-popup-open > div#__next > div.SideNavBar__BlocNavBar-sc-f04320cd-0 > button.toggleNavbar

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.content-menu > div.cats-choix-items > div.item-cat-choix > a div.content-menu > div.cats-choix-items > div.item-cat-choix > a
div.content-menu > div.cats-choix-items > div.item-cat-choix > a div.content-menu > div.cats-choix-items > div.item-cat-choix > a
div.content-menu > div.cats-choix-items > div.item-cat-choix > a div.content-menu > div.cats-choix-items > div.item-cat-choix > a
div.container > div.podcast-section-content > div.podcast-section-header > a div.container > div.podcast-section-content > div.podcast-section-header > a
ul > li > div.skyrock-app > a ul > li > div.skyrock-app > a
ul > li > div.skyrock-app > a ul > li > div.skyrock-app > 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.

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
DIFOOL – RADIO LIBRE div.content-moment-intro > div.moment-intro > div.info-artist > span.name-son
19H - 22H avec Difool, Cedric le belge, Romano, Karim, Samy, Marie, Guigui div.content-moment-intro > div.moment-intro > div.info-artist > span.name-artist
Skyrock div.content-cart-radio > div.bloc-detail-cart-radio > div.detail-cartr-adio > p.radio-name
LES ENTRÉES EN PLAYLIST ! div.col-md-6 > div.item-actualite > a > p.title-actualite
Découvrez les entrées en playlist Skyrock de la semaine ! div.col-md-6 > div.item-actualite > a > span.excerpt-actualite
RICK ROSS MET LE FEU À TOULOUSE POUR L’ANNIVERSAIRE D’OLI ! div.col-md-6 > div.item-actualite > a > p.title-actualite
C'est la SURPRISE ! div.col-md-6 > div.item-actualite > a > span.excerpt-actualite
LE TOP ALBUMS ! div.col-md-4 > div.item-actualite > a > p.title-actualite
Découvrez le classement ! div.col-md-4 > div.item-actualite > a > span.excerpt-actualite
LE TOP SINGLES ! div.col-md-4 > div.item-actualite > a > p.title-actualite
Découvre le classement maintenant ! div.col-md-4 > div.item-actualite > a > span.excerpt-actualite
LANDY DANS PLANÈTE RAP ! div.col-md-4 > div.item-actualite > a > p.title-actualite
Il est de retour toute la semaine ! div.col-md-4 > div.item-actualite > a > span.excerpt-actualite
DISIZ ET KID CUDI DÉVOILENT LE CLIP DE “TRY TRY TRY” div.col-md-4 > div.item-actualite > a > p.title-actualite
Le clip enfin dévoilé ! div.col-md-4 > div.item-actualite > a > span.excerpt-actualite
LES ENTRÉES EN PLAYLIST DE LA SEMAINE ! div.col-md-4 > div.item-actualite > a > p.title-actualite
Découvrez les entrées en playlist Skyrock de la semaine ! div.col-md-4 > div.item-actualite > a > span.excerpt-actualite
LE TOP ALBUMS div.col-md-4 > div.item-actualite > a > p.title-actualite
Découvrez le classement ! div.col-md-4 > div.item-actualite > a > span.excerpt-actualite
LES LIENS SKYROCK div.links-wrapper > div.footer-links > div.footer-links-wrapper > h4
LES APPLICATIONS div.links-wrapper > div.footer-apps-links > div.footer-links-wrapper > h4
SKYROCK div.content-detail-player > div.info-detail-player > p.cat-player > span

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
Les Derniers Épisodes div.container > div.podcast-section-content > div.podcast-section-header > h3.podcast-section-title

These are opportunities to improve keyboard navigation in your application.

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.

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
Learn More → div.didomi-popup-container > div.didomi-popup-view > div#buttons > button#didomi-notice-learn-more-button
Agree and close div.didomi-popup-container > div.didomi-popup-view > div#buttons > button#didomi-notice-agree-button
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
Form elements have associated labels
`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
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
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.
`[lang]` attributes have a valid value
Document has a main landmark.
Deprecated ARIA roles were not used
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.
`[accesskey]` values are unique
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
Links are distinguishable without relying on color.
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>`.
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
4 headings, 1 skip(s)
PASS
4 headings, 1 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.
  • H1 Difool – Radio Libre
  • H3 Les Derniers Épisodes skipped
  • H4 Les liens Skyrock
  • H4 Les applications

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 170 images OK
PASS
All 170 images OK
Info::
1 decorative image(s) correctly marked
Info::
169 image(s) with good alt text
170 images 169 good alt text 1 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback