Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 3 REVIEW 6 FIX

Alt Text Quality

Action

2 of 28 images have issues

FIX

2 of 28 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

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

24 decorative image(s) correctly marked

2 image(s) with good alt text

28 images 2 good alt text 24 decorative 2 missing

Issue	Count
missing	2 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

Link & Button Quality

Action

2 issue(s) across 166 links and 40 buttons

FIX

2 issue(s) across 166 links and 40 buttons

2 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://cnil.fr/fr"]; a[href="/fr/particulier"]

5 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: http://twitter.com/cnil; https://fr.linkedin.com/company/cnil---commission-nationale-de-l%27informatiq…; https://forms.information.cnil.fr/603cfc32b95cee69378a54cd/4fR4m1PsT-W5cBQRkj…; https://tarteaucitron.io/service/matomohightrack/; https://matomo.org/faq/general/faq_146/

2 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.navbar-toggle (#57 on page); button.search-btn (#65 on page)

159 link(s) with descriptive text

166 links

0 empty

0 generic text

5 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://cnil.fr/fr	Accueil - CNIL	img no alt	Add alt attribute to the image
/fr/particulier	Accueil - CNIL	img no alt	Add alt attribute to the image
http://twitter.com/cnil	twitter	new tab	Add '(opens in new tab)' to text
https://fr.linkedin.com/company/cnil---c…	linkedin	new tab	Add '(opens in new tab)' to text
https://forms.information.cnil.fr/603cfc…	S'inscrire à la lettre d'info…	new tab	Add '(opens in new tab)' to text
https://tarteaucitron.io/service/matomoh…	En savoir plus	new tab	Add '(opens in new tab)' to text
https://matomo.org/faq/general/faq_146/	Voir le site officiel	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

197 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://cnil.fr/fr"]; a[href="/fr/particulier"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

http://twitter.com/cnil; https://fr.linkedin.com/company/cnil---commission-nationale-de-l%27informatiq…; https://forms.information.cnil.fr/603cfc32b95cee69378a54cd/4fR4m1PsT-W5cBQRkj…; https://tarteaucitron.io/service/matomohightrack/; https://matomo.org/faq/general/faq_146/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.navbar-toggle (#57 on page); button.search-btn (#65 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Heading Hierarchy

16 headings

REVIEW

16 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 CNIL: search form
H2 J'ai besoin d'aide
H2 Je m'informe
H2 J'agis
H2 J'ai besoin d'aide
H2 Je m'informe
H2 J'agis
H2 J'ai besoin d'aide
H3 Hypertrucage (deepfake) : comment se protéger et signaler les contenus illicites ?
H3 FantomApp : l’application de la CNIL pour aider les adolescents à se protéger sur les réseaux sociaux
H3 Partage de photos et vidéos de votre enfant sur les réseaux sociaux : quels sont les risques ?
H3 Hypertrucage (deepfake) : comment se protéger et signaler les contenus illicites ?
H3 FantomApp : l’application de la CNIL pour aider les adolescents à se protéger sur les réseaux sociaux
H3 Partage de photos et vidéos de votre enfant sur les réseaux sociaux : quels sont les risques ?
H3 Hypertrucage (deepfake) : comment se protéger et signaler les contenus illicites ?
H3 FantomApp : l’application pour aider les 10-15 ans à se protéger sur les réseaux sociaux

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page non trouvée | CNIL ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Lighthouse Accessibility Audits

Action

Score 76/100 — 6 failing, 24 passed

REVIEW

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

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Hypertrucage (deepfake) : comment se protéger et signaler les contenus illicite… `div.row > div.col-xs-12 > div#carousel_accueil > div.carousel-inner`

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
FantomApp : l’application pour aider les 10-15 ans à se protéger sur les réseau… `div.focus-block--wrapper > div.slick-list > div.slick-track > div.section--focus-block`

When an input field 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 more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Hypertrucage (deepfake) : comment se protéger et signaler les contenus illicite… `div.row > div.col-xs-12 > div#carousel_accueil > div.carousel-inner`

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.dialog-off-canvas-main-canvas > header.page--header > div.mobile-navbar > button.navbar-toggle `div.dialog-off-canvas-main-canvas > header.page--header > div.mobile-navbar > button.navbar-toggle`
header.page--header > div.mobile-navbar > div.search > button.search-btn `header.page--header > div.mobile-navbar > div.search > button.search-btn`

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.mobile-navbar > a > picture > img `div.mobile-navbar > a > picture > img`

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Ma sécurité numérique `div.item > ul > li > a`
Sites web et réseaux sociaux `div.item > ul > li > a`
Smartphones et applications `div.item > ul > li > a`
Objets connectés `div.item > ul > li > a`
Enfants et ados `div.item > ul > li > a`
Santé `div.item > ul > li > a`
Social `div.item > ul > li > a`
Logement `div.item > ul > li > a`
Travail `div.item > ul > li > a`
Intelligence artificielle (IA) `div.item > ul > li > a`
Achats et publicité `div.item > ul > li > a`
Banque/Assurance `div.item > ul > li > a`
Citoyenneté `div.item > ul > li > a`
Sport `div.item > ul > li > a`
Transports et mobilité `div.item > ul > li > a`
Vie associative `div.item > ul > li > a`
Missions `div.item > ul > li > a`
Fonctionnement `div.item > ul > li > a`
En Europe et dans le monde `div.item > ul > li > a`
L’histoire de la CNIL en vidéo `div.item > ul > li > a`
Travailler à la CNIL `div.item > ul > li > a`
Marchés publics `div.item > ul > li > a`
Consultations publiques `div.item > ul > li > a`
Saisir la CNIL `div.item > ul > li > a`
Questions/réponses `div.item > ul > li > a`
Ressources pédagogiques `div.item > ul > li > a`
Affiches `div.item > ul > li > a`
Rapports et chiffres clés `div.item > ul > li > a`
FR `li > ul > li > a.is-active`
EN `li > ul > li > a`

These items highlight common accessibility best practices.

○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]`s are contained by their required parent element

●`[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 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 have a discernible name

●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

●`[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

●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 `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

○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>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○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.

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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.

Search landmark present

Page Structure — as a screen reader sees it

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+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#edit-keyword	text	Poser une question ou rechercher un article, une délibération...	for/id

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /themes/custom/bootstrap_base/css/print.css?tboeb7

Print Stylesheet ✓ Print Optimized

Print stylesheet /themes/custom/bootstrap_base/css/print.css?tboeb7 ✓Inline @media print Not detected ✗

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)

Element	Ratio	Required	FG	BG	Result
h2 CNIL: search form	4.66:1	3.0:1	#000000	#3879BF	Pass
h2 J'ai besoin d'aide	4.66:1	3.0:1	#000000	#3879BF	Pass
h2 Je m'informe	4.66:1	3.0:1	#000000	#3879BF	Pass
h2 J'agis	4.66:1	3.0:1	#000000	#3879BF	Pass
h2 J'ai besoin d'aide	4.66:1	3.0:1	#000000	#3879BF	Pass
h2 Je m'informe	4.66:1	3.0:1	#000000	#3879BF	Pass
h2 J'agis	4.66:1	3.0:1	#000000	#3879BF	Pass
h2 J'ai besoin d'aide	4.66:1	3.0:1	#000000	#3879BF	Pass
h3 FantomApp : l’appl…	4.66:1	3.0:1	#000000	#3879BF	Pass
title Particulier \| CNIL	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Aller au contenu pri…	19.95:1	4.5:1	#000000	#F9F9F9	Pass
span Accueil - CNIL	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Particuliers	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Professionnels	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Presse	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Gestionnaire de cook…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Accueil - CNIL	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Particuliers	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Professionnels	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Presse	21.00:1	4.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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.