Skip to content
https://free.fr

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 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
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 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

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Free : offres internet Fibre, Wi-Fi 7, TV et ligne fixe sans engagement ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
16 icon(s) detected
REVIEW
16 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 Present
✓ Multiple Sizes Present
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Free ADSL
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Free ADSL ✓192×192 icon ✗512×512 icon ✗Start URL ./index.html ✓Display Mode standalone ✓
Name Free ADSL Display Mode standalone Theme Color #000000 Background Color #ffffff Icons 1 icon(s)
A+
Heading Hierarchy
19 headings
PASS
19 headings
Info::
Single H1 present
  • H1 Choisissez plus qu’une Box internet, choisissez une Freebox
  • H2 Freebox Pop
  • H2 Freebox Ultra Essentiel
  • H2 Freebox Ultra
  • H3 Forfait Free Max
  • H2 Pourquoi Free ?
  • H2 Ensemble pour l’avis
  • H2 Apps-solument indispensables
  • H3 Free TV
  • H3 Free
  • H2 Pour tout capter sur votre offre internet Freebox
  • H3 Quel est le meilleur Wi-Fi ?
  • H3 Quelles box internet sont compatibles Fibre ?
  • H3 Quelle est l'offre internet la moins chère chez Free ?
  • H3 Comment souscrire à Free et résilier mon abonnement internet chez mon ancien opérateur ?
  • H3 Abonné Freebox, ai-je droit à une réduction sur mon forfait mobile ?
  • H3 Comment profiter des 100€ remboursés sur les frais de résiliation de mon ancien opérateur internet ?
  • H3 Ai-je accès aux services de streaming tels que Netflix, Prime Video et Disney+ avec mon offre Freebox ?
  • H3 Mentions Légales
A+
Alt Text Quality
1 of 50 images have issues
PASS
1 of 50 images have issues
Warning::
1 image(s) with generic alt text
Info::
5 decorative image(s) correctly marked
Info::
44 image(s) with good alt text
50 images 44 good alt text 5 decorative 1 generic
IssueCount
generic1 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Choisissez plus qu…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Freebox19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Freebox19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Freebox19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Pourquoi Free ?19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Ensemble pour l’av…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Apps-solument indisp…19.09:13.0:1
#000000
#F4F4F4
Pass
h2 Pour tout capter sur…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Forfait Free Max19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Free TV19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Free19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Quel est le meilleur…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Quelles box internet…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Quelle est l'offre i…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Comment souscrire à…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Abonné Freebox, ai-…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Comment profiter des…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Ai-je accès aux ser…19.09:13.0:1
#000000
#F4F4F4
Pass
h3 Mentions Légales19.09:13.0:1
#000000
#F4F4F4
Pass
title Free : offres intern…21.00:14.5:1
#000000
#FFFFFF
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.

A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 30 passed
PASS
92

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

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Offres & Services div.BusinessNavigation-module_businessNavigationAccordions__TI-41 > div > div.Accordion-module_accordion__6l-pT > div.Accordion-module_titleContainer__q2Jfm
Abonné div.BusinessNavigation-module_businessNavigationAccordions__TI-41 > div > div.Accordion-module_accordion__6l-pT > div.Accordion-module_titleContainer__q2Jfm
Aide & Contact div.BusinessNavigation-module_businessNavigationAccordions__TI-41 > div > div.Accordion-module_accordion__6l-pT > div.Accordion-module_titleContainer__q2Jfm
Société div.BusinessNavigation-module_businessNavigationAccordions__TI-41 > div > div.Accordion-module_accordion__6l-pT > div.Accordion-module_titleContainer__q2Jfm

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#nav-header > ul.nav-extra-menu > li.nav-extra-menu-item > a.nav-header-button-icon header#nav-header > ul.nav-extra-menu > li.nav-extra-menu-item > a.nav-header-button-icon
div.w-full > div.flex > div.relative > a.items-center div.w-full > div.flex > div.relative > a.items-center
div.w-full > div.flex > div.relative > a.items-center div.w-full > div.flex > div.relative > a.items-center
div.w-full > div.flex > div.relative > a.items-center div.w-full > div.flex > div.relative > a.items-center

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-*]` 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 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
●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
●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
○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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback