Skip to content
https://france.tv

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
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 France TV - Replay et Direct tv des chaînes France Télévisions ✓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
No navigation patterns
FIX
No navigation patterns
Info::
4 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 4 <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
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
2 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 "Liens d'évitement" MAIN CONTENTINFO footer

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
7 icon(s) detected
REVIEW
7 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, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 19 pass AA only
h2 Notre sélection
1.11:1
#000000
on
#0D101F
needs 3.0:1 (large text)
24px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Notre sélection1.11:13.0:1
#000000
#0D101F
Fail
h2 En direct3.65:13.0:1
#000000
#5E6487
Pass
h2 Catégories3.65:13.0:1
#000000
#5E6487
Pass
h2 Top 10 du moment3.65:13.0:1
#000000
#5E6487
Pass
h2 Une séance de ciné…3.65:13.0:1
#000000
#5E6487
Pass
h2 Les séries à ne pa…3.65:13.0:1
#000000
#5E6487
Pass
h2 Casting 5 étoiles3.65:13.0:1
#000000
#5E6487
Pass
h2 La grande boucle des…3.65:13.0:1
#000000
#5E6487
Pass
h2 En attendant la cér…3.65:13.0:1
#000000
#5E6487
Pass
h2 Le meilleur du docum…3.65:13.0:1
#000000
#5E6487
Pass
h2 Nos collections3.65:13.0:1
#000000
#5E6487
Pass
h2 On en parle3.65:13.0:1
#000000
#5E6487
Pass
h2 Une Terre en commun3.65:13.0:1
#000000
#5E6487
Pass
h2 Haletants, stressant…3.65:13.0:1
#000000
#5E6487
Pass
h2 Quand l’humour mè…3.65:13.0:1
#000000
#5E6487
Pass
h2 Pour comprendre l'ac…3.65:13.0:1
#000000
#5E6487
Pass
h2 Guerre au Moyen-Orie…3.65:13.0:1
#000000
#5E6487
Pass
h2 Tous les jours avec …3.65:13.0:1
#000000
#5E6487
Pass
h2 Nos partenaires3.65:13.0:1
#000000
#5E6487
Pass
h3 L'offre france.tv3.65:13.0:1
#000000
#5E6487
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.

B
Lighthouse Accessibility Audits
Score 84/100 — 4 failing, 29 passed
REVIEW
84

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Chaînes div.ugoA > nav.llhDgj > div.ilDRWN > div.gwOpWH
Directs div.ugoA > nav.llhDgj > div.ilDRWN > div.gwOpWH
Catégories div.ugoA > nav.llhDgj > div.ilDRWN > div.gwOpWH
France Info div.ugoA > nav.llhDgj > div.ilDRWN > div.gwOpWH
Jeunesse div.ugoA > nav.llhDgj > div.ilDRWN > div.gwOpWH
Services div.ugoA > nav.llhDgj > div.ilDRWN > div.gwOpWH
Contact div.ugoA > nav.llhDgj > div.ilDRWN > div.gwOpWH

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
134 partenaires div.didomi-popup-notice-text > div > p > span

When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label `progressbar` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Progression en cours : 94% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 78% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 82% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 99% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 97% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 42% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 86% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 80% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 65% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 28% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 28% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 84% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 80% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO
Progression en cours : 63% li.glPIQH > span.iAGuGS > span.cHvGDh > div.kjSWHO

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
header.euRjEA > nav.bnyIZY > div > a.bEfsqy header.euRjEA > nav.bnyIZY > div > a.bEfsqy

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.

○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>`
●`[role]`s have all required `[aria-*]` attributes
●`[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.
●`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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` 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>`.
○Image elements do not have `[alt]` attributes that are redundant text.
○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
22 headings
PASS
22 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Accueil France.tv
  • H1 Accueil France.tv duplicate H1
  • H2 Notre sélection
  • H2 En direct
  • H2 Catégories
  • H2 Top 10 du moment
  • H2 Une séance de cinéma ?
  • H2 Les séries à ne pas rater
  • H2 Casting 5 étoiles
  • H2 La grande boucle des polars en séries
  • H2 En attendant la cérémonie des Flammes
  • H2 Le meilleur du documentaire
  • H2 Nos collections
  • H2 On en parle
  • H2 Une Terre en commun
  • H2 Haletants, stressants, palpitants !
  • H2 Quand l’humour mène l’enquête
  • H2 Pour comprendre l'actualité
  • H2 Guerre au Moyen-Orient
  • H2 Tous les jours avec nous
  • H2 Nos partenaires
  • H3 L'offre france.tv

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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