Skip to content
https://www.service-public.fr

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
69
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗
Icons 2 icon(s)
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 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 Erreur 404 - Nous ne trouvons pas la page demandée | Service-Public.fr ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 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
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Accès rapide" SEARCH 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
31 headings
PASS
31 headings
Info::
Single H1 present
  • H1 Bienvenue sur le site officiel d’information et de démarches administratives
  • H2 Fiches pratiques par événement de vie
  • H3 Je déménage
  • H3 Je deviens parent
  • H3 Je recherche un emploi
  • H3 Je prépare ma retraite
  • H2 France Services
  • H3 Besoin d’aide près de chez vous ?
  • H2 Fiches pratiques les plus lues
  • H3 Calendrier des vacances scolaires 2025-2026 et 2026-2027
  • H3 Renouvellement du passeport d'un majeur
  • H3 Durée de conservation des papiers
  • H3 Aides pour financer le permis de conduire
  • H3 Bruits de voisinage
  • H3 Inscription au registre des Français établis hors de France
  • H2 Démarches et outils
  • H3 Signaler son changement d'adresse en ligne
  • H3 Calculer le coût d’une carte grise
  • H3 Vérifier combien de temps conserver un document
  • H3 Création d'une association (e-création)
  • H3 Estimer le montant des droits de succession
  • H3 Trouver une mission de bénévolat
  • H3 Calculer les indemnités d'entretien de l'assistante maternelle
  • H3 Estimer la part du locataire pour le paiement des frais d’agence
  • H3 Savoir s'il faut un certificat médical pour faire du sport
  • H2 Actualité de vos droits et démarches
  • H3 Quel est le montant de l'allocation de rentrée scolaire en 2026 ?
  • H3 Collèges et lycées : les indicateurs de résultats 2025
  • H3 Allô Service Public 3939, le service de renseignement administratif
  • H2 Recevoir la lettre de Service Public
  • H2 Suivez-nous sur les réseaux sociaux
A+
Alt Text Quality
All 11 images OK
PASS
All 11 images OK
Info::
6 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
11 images 5 good alt text 6 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#header-search-inputsearchRecherchefor/id
#search-input-fssearchQuelle est votre adresse ? Exemple : 32 rue Olympe de Gouges 89100 Sens, 33700, Toulousefor/id
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 Bienvenue sur le sit…16.06:13.0:1
#000000
#E1E1E1
Pass
h2 Fiches pratiques par…16.06:13.0:1
#000000
#E1E1E1
Pass
h2 Fiches pratiques les…16.06:13.0:1
#000000
#E1E1E1
Pass
h2 Démarches et outils16.06:13.0:1
#000000
#E1E1E1
Pass
h2 Actualité de vos dr…16.06:13.0:1
#000000
#E1E1E1
Pass
h2 Recevoir la lettre d…16.06:13.0:1
#000000
#E1E1E1
Pass
h2 Suivez-nous16.06:13.0:1
#000000
#E1E1E1
Pass
h2 sur les réseaux soc…16.06:13.0:1
#000000
#E1E1E1
Pass
title Accueil | Service Pu…21.00:14.5:1
#000000
#FFFFFF
Pass
p Ce site utilise des …21.00:14.5:1
#000000
#FFFFFF
Pass
button Accepter21.00:14.5:1
#000000
#FFFFFF
Pass
button Refuser21.00:14.5:1
#000000
#FFFFFF
Pass
button Personnaliser21.00:14.5:1
#000000
#FFFFFF
Pass
a Contenu20.82:14.5:1
#000000
#FEFEFE
Pass
a Menu21.00:14.5:1
#000000
#FFFFFF
Pass
a Recherche21.00:14.5:1
#000000
#FFFFFF
Pass
a Pied de page21.00:14.5:1
#000000
#FFFFFF
Pass
p République21.00:14.5:1
#000000
#FFFFFF
Pass
p Française21.00:14.5:1
#000000
#FFFFFF
Pass
button Ouvrir la recherche21.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 100/100 — 0 failing, 28 passed
PASS
100

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.

○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
●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 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
●Links are distinguishable without relying on color.
●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
●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
○`[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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○No element has a `[tabindex]` value greater than 0
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback