Skip to content
https://lepoint.fr

Accessibility

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

F
Heading Hierarchy
Action
105 headings, 15 skip(s)
FIX
105 headings, 15 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H4 Entre la France et l’Iran, l’inavouable marché d’otages skipped
  • H4 Xavier Gorce : « Ce qui se passe à Kerguelen reste à Kerguelen »
  • H4 Gabriel Attal : « Je pense savoir comment il faut présider la France »
  • H4 Jordan Bardella : des casseroles du RN aux armoiries princières
  • H4 Donald Trump contre Léon XIV : lequel a plus peur de l’autre ?
  • H4 « L’Ordre entrave la protection des enfants et muselle les médecins »
  • H4 Affaire Sarah Halimi : la famille relance la bataille judiciaire
  • H4 En France, derrière l’unanimité sur la restitution des œuvres pillées, de profondes divisions
  • H4 Liban : la France confond le symptôme et la maladie
  • H2 Gabriel Attal : « Je pense savoir comment il faut présider la France »
  • H4 La diplomatie de l’ombre du sultanat d’Oman skipped
  • H4 Le piège de Suez va-t-il se refermer sur Trump ?
  • H4 L’IA sur un volcan
  • H2 Le classement des hôpitaux et cliniques 2025
  • H2 Le classement des hôpitaux et cliniques 2025
  • H1 Saisons, une autre façon d’habiter le monde duplicate H1
  • H2 Lire nos éditorialistes
  • H3 Péter Magyar, l’homme qui veut karsheriser la Hongrie
  • H3 Pause
  • H3 Mission Artémis II : pourquoi donc la Nasa a-t-elle baptisé Orion le véhicule spatial qui survole la lune ?
  • H3 Encore raté, monsieur Poutine !
  • H3 Juste une illusion ?
  • H3 Saint-Denis : ce royaume « céleste » contre la république terrestre
  • H3 La Chine, grande gagnante de la guerre d’Iran
  • H3 Jeter un sport
  • H3 Poutine, ses tueurs, et le grand retour des mâles dangereux
  • H3 L’Occident sous la tutelle des marchés financiers
  • H3 De la tendresse
  • H3 Faut-il interdire d’appeler à la destruction d’Israël ?
  • H3 Péter Magyar, l’homme qui veut karsheriser la Hongrie
  • H3 Pause
  • H3 Mission Artémis II : pourquoi donc la Nasa a-t-elle baptisé Orion le véhicule spatial qui survole la lune ?
  • H3 Encore raté, monsieur Poutine !
  • H3 Juste une illusion ?
  • H3 Saint-Denis : ce royaume « céleste » contre la république terrestre
  • H4 Budget européen : le Parlement relève encore ses ambitions
  • H4 Sébastien Lecornu ou l’art de la politique du coupe-feu
  • H4 Dans le camp Retailleau, un doux fantasme nommé Baroin
  • H4 Vérification d’âge en ligne : von der Leyen lance une appli universelle et anonyme, inspirée du pass Covid
  • H4 Proposition de loi Yadan : face à l’antisémitisme, l’éternel retour de la chimère censoriale
  • H4 Dix ans après, la loi prostitution de 2016 a-t-elle aggravé le problème ?
  • H2 Trump, le pape et Giorgia Meloni : divorce à l’italienne
  • H2 Articles les plus lus
  • H2 Jeux
  • H3 Projet Voltaire
  • H3 Kangourou
  • H2 Nos vidéos
  • H2 Dessin du jour
  • H2 Sélection de la rédaction
  • H4 Guerre en Iran : « Le nucléaire est une ligne rouge qui ne pourra pas être négociée » skipped
  • H4 Retailleau, Mélenchon, Royal… Comment le coup de sang peut coûter cher en politique
  • H4 Remords sexuels : quand certaines nuits laissent un goût amer
  • H2 Événements
  • H4 Les Dialogues de la santéOpens in new window skipped
  • H4 Rencontre et débat éthique à la Maison de la ChimieOpens in new window
  • H4 Guerres et PaixOpens in new window
  • H4 NeuroplanèteOpens in new window
  • H2 Guide d'achat
  • H4 Les 13 questions à se poser avant de choisir un organisme de soutien scolaire skipped
  • H4 Interview Masterclass par Michel Denisot : Whisper Yachts, le luxe solaire en haute mer
  • H4 Interview Masterclass par Michel Denisot : Oract Advisory, l’actuariat au service des assureurs
  • H2 Le Point Stories
  • H4 Émilien Jacquelin et l’art maîtriser l’instant skipped
  • H4 La Voie, une ode à l’amitié, au courage et à la résilience
  • H4 La Poste, créer du lien
  • H2 Politique
  • H4 Macron, dissolution, couple… les extraits du livre de Gabriel Attal skipped
  • H4 Philippe Raynaud : « Le bloc central reste incontournable »
  • H4 Qui pour remplacer Jordan Bardella ?
  • H2 Monde
  • H4 En France, derrière l’unanimité sur la restitution des œuvres pillées, de profondes divisions skipped
  • H4 Liban : la France confond le symptôme et la maladie
  • H4 Entre la France et l’Iran, l’inavouable marché d’otages
  • H2 Débats
  • H4 « Tout » Régis Debray skipped
  • H4 Encore raté, monsieur Poutine !
  • H4 La Chine, grande gagnante de la guerre d’Iran
  • H2 Économie
  • H4 À Cushing, dans l’épicentre secret où se négocie l’or noir américain skipped
  • H4 Impôts : la France dans le peloton de tête européen
  • H4 Pourquoi vos meilleurs éléments partent… et vous ne voyez rien venir
  • H2 Culture
  • H4 Mercè Rodoreda, la voix catalane qui murmurait au monde entier skipped
  • H4 Djaïli Amadou Amal raconte son enfance
  • H4 Jon Kalman Stefansson : la plume contre l’épée
  • H2 Style
  • H4 Watches and Wonders 2026 : ce qu’il faut retenir du jour 3 skipped
  • H4 De la tendresse
  • H4 Bel argent
  • H2 Société
  • H4 « L’Ordre entrave la protection des enfants et muselle les médecins » skipped
  • H4 Affaire Sarah Halimi : la famille relance la bataille judiciaire
  • H4 Dix ans après, la loi prostitution de 2016 a-t-elle aggravé le problème ?
  • H2 Santé
  • H4 Face à la cocaïne, les certitudes bousculées des médecins skipped
  • H4 Se soigner par les plantes, ce n’est pas naturel
  • H4 Obésité : le nouvel eldorado des Big Pharma
  • H2 Science & innovation
  • H4 Xavier Gorce : « Ce qui se passe à Kerguelen reste à Kerguelen » skipped
  • H4 Richard Dawkins : « C’est très triste à dire, mais le monde est devenu plus hostile à l’examen rationnel »
  • H4 Il y a 5 000 ans, le Bassin parisien changeait de population
  • H4 Lire Le Point
  • H4 Services
  • H4 Liens utiles

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

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

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

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

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

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

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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.

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.
C
Alt Text Quality
Action
3 of 84 images have issues
REVIEW
3 of 84 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
3 decorative image(s) correctly marked
Info::
78 image(s) with good alt text
84 images 78 good alt text 3 decorative 3 missing
IssueCount
missing3 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Page non trouvée ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 20 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Saisons, une autre f…3.00:13.0:1
#000000
#595959
Pass
h2 Gabriel Attal : «…3.00:13.0:1
#000000
#595959
Pass
h2 Le classement des h…3.00:13.0:1
#000000
#595959
Pass
h2 Le classement des h…3.00:13.0:1
#000000
#595959
Pass
h2 Lire nos éditoriali…3.00:13.0:1
#000000
#595959
Pass
h2 Trump, le pape et Gi…3.00:13.0:1
#000000
#595959
Pass
h2 Articles les plus lu…3.00:13.0:1
#000000
#595959
Pass
h2 Jeux3.00:13.0:1
#000000
#595959
Pass
h2 Nos vidéos3.00:13.0:1
#000000
#595959
Pass
h2 Dessin du jour3.00:13.0:1
#000000
#595959
Pass
h2 Sélection de la ré…3.00:13.0:1
#000000
#595959
Pass
h2 Événements3.00:13.0:1
#000000
#595959
Pass
h2 Guide d'achat3.00:13.0:1
#000000
#595959
Pass
h2 Le Point Stories3.00:13.0:1
#000000
#595959
Pass
h3 Péter Magyar, l’h…3.00:13.0:1
#000000
#595959
Pass
h3 Pause3.00:13.0:1
#000000
#595959
Pass
h3 Mission Artémis II…3.00:13.0:1
#000000
#595959
Pass
h3 Encore raté, monsie…3.00:13.0:1
#000000
#595959
Pass
h3 Juste une illusion …3.00:13.0:1
#000000
#595959
Pass
h3 Saint-Denis : ce ro…3.00:13.0:1
#000000
#595959
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 82/100 — 5 failing, 22 passed
REVIEW
82

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

When an 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 make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.footer__links-block > ul.footer__links-list > li.footer__links-item > a div.footer__links-block > ul.footer__links-list > li.footer__links-item > a

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

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
header.header > div.header__container > div.header__menu-link > button.header__menu-icon header.header > div.header__container > div.header__menu-link > button.header__menu-icon

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.custom-image-wrapper > div.custom-image-placeholder > picture > img div.custom-image-wrapper > div.custom-image-placeholder > picture > img
div.custom-image-wrapper > div.custom-image-placeholder > picture > img div.custom-image-wrapper > div.custom-image-placeholder > picture > img
div.custom-image-wrapper > div.custom-image-placeholder > picture > img.author__image div.custom-image-wrapper > div.custom-image-placeholder > picture > img.author__image

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
section.hp-zone-evolution > div.hp-zone-evolution-container > div > a section.hp-zone-evolution > div.hp-zone-evolution-container > div > a
Facebook div.footer__social > ul.footer__social-list > li.footer__social-item > a
X div.footer__social > ul.footer__social-list > li.footer__social-item > a
Linked In div.footer__social > ul.footer__social-list > li.footer__social-item > a
Instagram div.footer__social > ul.footer__social-list > li.footer__social-item > 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.

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
Entre la France et l’Iran, l’inavouable marché d’otages div.hp-alaune-chain__featured--left > article.hp-section-item > div.hp-section-item_wrapper > h4.hp-section-item_headline
La diplomatie de l’ombre du sultanat d’Oman div.hp-cover_related-stories > article.story-item > div.story-item__wrapper > h4.story-item__headline
Guerre en Iran : « Le nucléaire est une ligne rouge qui ne pourra pas être négo… div.hp-selection-redaction__items > article.story-item > div.story-item__wrapper > h4.story-item__headline
Les Dialogues de la santé Opens in new window div.hp-events_items > article.event-item > div.event-item_wrapper > h4.event-item_headline
Les 13 questions à se poser avant de choisir un organisme de soutien scolaire div.hp-ops_items > article.hp-ops-item > div.hp-ops-item_wrapper > h4.hp-ops-item_headline
Émilien Jacquelin et l’art maîtriser l’instant div.hp-ops_items > article.hp-ops-item > div.hp-ops-item_wrapper > h4.hp-ops-item_headline
Macron, dissolution, couple… les extraits du livre de Gabriel Attal div.hp-section_items > article.hp-section-item > div.hp-section-item_wrapper > h4.hp-section-item_headline
En France, derrière l’unanimité sur la restitution des œuvres pillées, de profo… div.hp-section_items > article.hp-section-item > div.hp-section-item_wrapper > h4.hp-section-item_headline
« Tout » Régis Debray div.hp-section_items > article.hp-section-item > div.hp-section-item_wrapper > h4.hp-section-item_headline
À Cushing, dans l’épicentre secret où se négocie l’or noir américain div.hp-section_items > article.hp-section-item > div.hp-section-item_wrapper > h4.hp-section-item_headline
Mercè Rodoreda, la voix catalane qui murmurait au monde entier div.hp-section_items > article.hp-section-item > div.hp-section-item_wrapper > h4.hp-section-item_headline
Watches and Wonders 2026 : ce qu’il faut retenir du jour 3 div.hp-section_items > article.hp-section-item > div.hp-section-item_wrapper > h4.hp-section-item_headline
« L’Ordre entrave la protection des enfants et muselle les médecins » div.hp-section_items > article.hp-section-item > div.hp-section-item_wrapper > h4.hp-section-item_headline
Face à la cocaïne, les certitudes bousculées des médecins div.hp-section_items > article.hp-section-item > div.hp-section-item_wrapper > h4.hp-section-item_headline
Xavier Gorce : « Ce qui se passe à Kerguelen reste à Kerguelen » div.hp-section_items > article.hp-section-item > div.hp-section-item_wrapper > h4.hp-section-item_headline

These are opportunities to improve keyboard navigation in your application.

○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
●`[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
●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
●`<frame>` or `<iframe>` elements have a title
●`<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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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
○`<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.
○`[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.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 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="checkbox" name="queryly_toggle" id="queryly_toggle">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#queryly_querysearchSearcharia-label
#queryly_togglecheckbox(none)none

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

<input type="checkbox" name="queryly_toggle" id="queryly_toggle">

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