Skip to content
https://sante.fr

Accessibility

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

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.
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 La page que vous avez demandée est introuvable ! | Santé.fr ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA 2 pass AA only
h2 En cas d'urgence
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nos Actualités
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nos services
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 J'agis pour ma santé
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Nos Sélections
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 SANTÉ.FR
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trouver un professionnel de santé, un …
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Le site du Service Public d’informatio…
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Une information fiable et accessible
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
span Menu principal
2.02:1
#000000
on
#473F32
needs 4.5:1 (normal text)
16px · top of page (header area)
a Qui sommes-nous ?
1.73:1
#000000
on
#36362F
needs 4.5:1 (normal text)
16px · above the fold
a Nos missions
3.65:1
#000000
on
#7A6242
needs 4.5:1 (normal text)
16px · above the fold
a Nos partenaires
1.97:1
#000000
on
#3A4129
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Se connecter
2.38:1
#000000
on
#524A32
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

2 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 L'information fiable…7.68:13.0:1
#000000
#AD9A7A
Pass
h2 En cas d'urgence1.66:13.0:1
#000000
#333333
Fail
h2 Nos Actualités1.66:13.0:1
#000000
#333333
Fail
h2 Nos services1.66:13.0:1
#000000
#333333
Fail
h2 J'agis pour ma sant…1.66:13.0:1
#000000
#333333
Fail
h2 Nos Sélections1.66:13.0:1
#000000
#333333
Fail
h2 SANTÉ.FR1.66:13.0:1
#000000
#333333
Fail
h2 Trouver un professio…1.66:13.0:1
#000000
#333333
Fail
h3 Le site du Service P…1.66:13.0:1
#000000
#333333
Fail
h3 Une information fiab…1.66:13.0:1
#000000
#333333
Fail
title Page d'accueil | San…21.00:14.5:1
#000000
#FFFFFF
Pass
a Aller au contenu pri…21.00:14.5:1
#000000
#FFFFFF
Pass
span Ouvrir la recherche10.06:14.5:1
#000000
#B6B3AF
Pass
span Menu principal2.02:14.5:1
#000000
#473F32
Fail
a Qui sommes-nous ?1.73:14.5:1
#000000
#36362F
Fail
a Nos missions3.65:14.5:1
#000000
#7A6242
Fail
a Nos partenaires1.97:14.5:1
#000000
#3A4129
Fail
span Se connecter2.38:14.5:1
#000000
#524A32
Fail
span Rechercher6.61:14.5:1
#000000
#BE8084
Pass
p Les recherches du mo…6.27:14.5:1
#000000
#BC7A87
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.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 6 failing, 27 passed
REVIEW
78

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
div.main-header > div > div.account-panel > div.keycloak-wrapper div.main-header > div > div.account-panel > div.keycloak-wrapper

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
slide 1 div.our-services > div#tns1-ow > div.tns-nav > button.tns-nav-active

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
Cabinets accessibles div#tns1-mw > div#tns1-iw > ul#tns1 > li.bloc-link
Accès professionnels div#tns1-mw > div#tns1-iw > ul#tns1 > li.bloc-link
J'agis pour ma santé div#tns1-mw > div#tns1-iw > ul#tns1 > li.bloc-link
Santé.fr Décryptage div#tns1-mw > div#tns1-iw > ul#tns1 > li.bloc-link
Cabinets accessibles div#tns1-mw > div#tns1-iw > ul#tns1 > li.bloc-link
Accès professionnels div#tns1-mw > div#tns1-iw > ul#tns1 > li.bloc-link
Accès professionnels div#tns1-mw > div#tns1-iw > ul#tns1 > li#tns1-item3
J'agis pour ma santé div#tns1-mw > div#tns1-iw > ul#tns1 > li.bloc-link
Santé.fr Décryptage div#tns1-mw > div#tns1-iw > ul#tns1 > li.bloc-link
Cabinets accessibles div#tns1-mw > div#tns1-iw > ul#tns1 > li.bloc-link
Accès professionnels div#tns1-mw > div#tns1-iw > ul#tns1 > li.bloc-link
J'agis pour ma santé div#tns1-mw > div#tns1-iw > ul#tns1 > li.bloc-link
Santé.fr Décryptage div#tns1-mw > div#tns1-iw > ul#tns1 > li.bloc-link

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
div.keycloak-login-wrapper > form#ans-openid-connect-login-form > div > button#edit-openid-connect-client-espace-pro-login div.keycloak-login-wrapper > form#ans-openid-connect-login-form > div > button#edit-openid-connect-client-espace-pro-login

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
li > div.prevention-box-info > div.card-bottom > a.link li > div.prevention-box-info > div.card-bottom > a.link
li > div.prevention-box-info > div.card-bottom > a.link li > div.prevention-box-info > div.card-bottom > a.link
li > div.prevention-box-info > div.card-bottom > a.link li > div.prevention-box-info > div.card-bottom > a.link

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cabinets accessibles Accès professionnels J'agis pour ma santé Santé.fr Décr… div#tns1-ow > div#tns1-mw > div#tns1-iw > ul#tns1

These are opportunities to improve the experience of reading tabular or list data using 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
●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
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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 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.
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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>`.
○All heading elements contain content.
○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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) 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 NAV "Menu principal" MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
17 headings
PASS
17 headings
Info::
Single H1 present
  • H1 L'information fiable, utile pour votre santé
  • H2 En cas d'urgence
  • H2 Nos Actualités
  • H3 Méningites
  • H3 Maladie de Parkinson
  • H3 Pourquoi faut-il lutter contre l’ambroisie ?
  • H2 Nos services
  • H2 J'agis pour ma santé
  • H2 Nos Sélections
  • H3 Prenez soin de votre santé mentale à tous les âges de la vie
  • H3 Faut-il vraiment « réguler son cortisol » ?
  • H3 Impact du mode de vie :  ce qu'il faut savoir pour préserver sa fertilité
  • H3 ­Comment réduire l’exposition aux polluants pendant les travaux ?
  • H2 SANTÉ.FR
  • H3 Le site du Service Public d’information en santé
  • H3 Une information fiable et accessible
  • H2 Trouver un professionnel de santé, un établissement
A+
Alt Text Quality
All 28 images OK
PASS
All 28 images OK
Info::
24 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
28 images 4 good alt text 24 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtextRechercher une information, un professionnel, un établissement (dernières recherches et recherches fréquentes en ce moment disponibles ci-après)aria-label
inputtextRechercher une ville (dernières recherches et recherches fréquentes en ce moment disponibles ci-après)aria-label
#edit-sexe-femmeradiofemmefor/id
#edit-sexe-hommeradiohommefor/id
#edit-agetextÂge *for/id
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /sites/default/files/css/css_Bukx_1r2PaVmTgEtNRD2uMGJmBzy-fFkBkFFccsMUZ4.css?delta=4&language=fr&theme=santefr&include=eJxVjWuWwiAMhTcEZUk9AcJDU8JJqNrdi6PjTP_dfPeRcMVYB8sKIbDEys191ZKE28AWzQToouwdaIELPE4gViDOJs0s3FF5Q_dPL3f0r1NNB4Es0Iv-Nv_Isre-e6paMBqF-XWtSWDDNfCtRkcIiXB8rNuOF3VlrnfIaBVBQrGeOFxPifeE_UH2FT25n1pBiCjWg7zdJC4TeyCr46Da8heP2g6rVGfc6KEDN-dB8Qn3833b
Print Stylesheet ✓ Print Optimized
Print stylesheet /sites/default/files/css/css_Bukx_1r2PaVmTgEtNRD2uMGJmBzy-fFkBkFFccsMUZ4.css?delta=4&language=fr&theme=santefr&include=eJxVjWuWwiAMhTcEZUk9AcJDU8JJqNrdi6PjTP_dfPeRcMVYB8sKIbDEys191ZKE28AWzQToouwdaIELPE4gViDOJs0s3FF5Q_dPL3f0r1NNB4Es0Iv-Nv_Isre-e6paMBqF-XWtSWDDNfCtRkcIiXB8rNuOF3VlrnfIaBVBQrGeOFxPifeE_UH2FT25n1pBiCjWg7zdJC4TeyCr46Da8heP2g6rVGfc6KEDN-dB8Qn3833b ✓Inline @media print Not detected ✗
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback