Skip to content
https://insee.fr

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
404 Error Page
Action
HTTP 500, custom page
FIX
HTTP 500, custom page
Warning::
Unexpected status code: HTTP 500
Expected HTTP 404 but received 500. This may confuse search engine crawlers.
Got: HTTP 500
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 500 ✗Page Title Erreur | Insee ✓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
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
1 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 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
Heading Hierarchy
28 headings
REVIEW
28 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 L’Institut national de la statistique et des études économiques collecte, produit, analyse et diffuse des informations sur l’économie et la société françaises
  • H2 Dernières publications
  • H2 Dernières publications
  • H3 Compte des ménages par catégories en 2023
  • H3 Revenus des ménages élargis à l’ensemble de l’économie en 2023
  • H3 Privation matérielle et sociale en 2025
  • H3 En mars 2026, les prix à la consommation augmentent de 1,0 % sur un mois et de 1,7 % sur un an
  • H2 Derniers indicateurs conjoncturels
  • H3 Les créations d’entreprises continuent d’augmenter en mars 2026
  • H3 Les index Bâtiment, Travaux publics et divers de la construction en février 2026
  • H3 Au premier trimestre 2026, l’indice de référence des loyers augmente de 0,78 % sur un an
  • H3 En mars 2026, les prix à la consommation augmentent de 1,0 % sur un mois et de 1,7 % sur un an
  • H3 Résultats du commerce extérieur - Importations et exportations de biens
  • H3 En février 2026, la production manufacturière est stable
  • H3 Immatriculations de véhicules neufs
  • H3 En janvier 2026, le chiffre d’affaires dans l’industrie manufacturière se replie (-0,7 %)
  • H3 En février 2026, les prix des produits agricoles à la production se replient sur un an
  • H3 Construction de logements
  • H2 Indicateurs clés
  • H3 Croissance économique
  • H3 Inflation
  • H3 Consommation des ménages en biens
  • H3 Climat des affaires
  • H3 Chômage y compris les DOM
  • H3 Production industrielle (manufacturière)
  • H2 Abonnez-vous
  • H2 Nous suivre
  • H2 Contact

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

B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 24 passed
REVIEW
85

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
NOS SITES PARTENAIRES footer > div.footer-mobile > div.liens-partenaires-mobile > ul.menu-liens-partenaires-mobile

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
body > a.sticky-top body > a.sticky-top

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 require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
NOS SITES PARTENAIRES div.footer-mobile > div.liens-partenaires-mobile > ul.menu-liens-partenaires-mobile > li.lien

These are opportunities to improve the experience of reading tabular or list data using 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
Aide div#banniere > div.bandeau > div.liens-aide-responsive > a#lien-aide-responsive
Thèmes div#banniere > div.bandeau > div.liens-themes-responsive > a.liens-themes-responsive
English div#banniere > div.bandeau > div.langue-responsive > a#lien-changement-langue-responsive
Presse div#banniere > div.bandeau > div.presse-responsive > a#lien-presse-responsive
Accès sourds et malentendants div.bloc-4 > ul.liens-footer > li.lien-footer > 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]` values are valid
●`[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.
●ARIA attributes are used as specified for the element's role
●`[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>`).
●No element has a `[tabindex]` value greater than 0
●`[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
○`[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
○`[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.
○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.
○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+
Alt Text Quality
All 29 images OK
PASS
All 29 images OK
Info::
8 decorative image(s) correctly marked
Info::
21 image(s) with good alt text
29 images 21 good alt text 8 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" id="barre-recherche">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#barre-recherchesearch(Rechercher)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="search" id="barre-recherche">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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
h2 L’Institut nationa…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 analyse et diffuse d…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dernières publicati…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dernières publicati…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Derniers indicateurs…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Indicateurs clés21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Abonnez-vous21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Nous suivre21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Contact21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Compte des ménages…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Revenus des ménages…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Privation matériell…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 En mars 2026, les pr…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Les créations d’e…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 en mars 202621.00:13.0:1
#000000
#FFFFFF
Pass
h3 Les index Bâtiment,…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Au premier trimestre…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 En mars 2026, les pr…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Résultats du commer…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 En février 2026, la…21.00:13.0: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.

Send Feedback