Skip to content
https://senat.fr

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
3
REVIEW
3
PASS
7
INFO
0
Checks
13
7 PASS 3 REVIEW 3 FIX
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page introuvable | Sénat ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA
h1 Sénat - Accueil
1.30:1
#000000
on
#1C1E3B
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Les derniers travaux parlementaires
1.30:1
#000000
on
#1C1E3B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Découvrir le Sénat
1.30:1
#000000
on
#1C1E3B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 E-petitions
1.30:1
#000000
on
#1C1E3B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 L’activité du Sénat en chiffres
1.30:1
#000000
on
#1C1E3B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Le Sénat, c'est aussi
1.30:1
#000000
on
#1C1E3B
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 À propos des cookie…19.41:13.0:1
#000000
#F5F6F7
Pass
h1 Sénat - Accueil1.30:13.0:1
#000000
#1C1E3B
Fail
h2 Les derniers travaux…1.30:13.0:1
#000000
#1C1E3B
Fail
h2 Découvrir le Sénat1.30:13.0:1
#000000
#1C1E3B
Fail
h2 E-petitions1.30:13.0:1
#000000
#1C1E3B
Fail
h2 L’activité du Sé…1.30:13.0:1
#000000
#1C1E3B
Fail
h2 Le Sénat, c'est aus…1.30:13.0:1
#000000
#1C1E3B
Fail
title Sénat - Travaux par…21.00:14.5:1
#000000
#FFFFFF
Pass
p Bienvenue ! Ce site …19.08:14.5:1
#000000
#F3F4F6
Pass
button Tout accepter19.08:14.5:1
#000000
#F3F4F6
Pass
button Tout refuser19.08:14.5:1
#000000
#F3F4F6
Pass
button Personnaliser19.08:14.5:1
#000000
#F3F4F6
Pass
a Aller au contenu21.00:14.5:1
#000000
#FFFFFF
Pass
a Aller à la navigati…21.00:14.5:1
#000000
#FFFFFF
Pass
button La galaxie Sénat21.00:14.5:1
#000000
#FFFFFF
Pass
button Réseaux sociaux21.00:14.5:1
#000000
#FFFFFF
Pass
a Facebook21.00:14.5:1
#000000
#FFFFFF
Pass
a Linkedin21.00:14.5:1
#000000
#FFFFFF
Pass
a Instagram21.00:14.5:1
#000000
#FFFFFF
Pass
a YouTube21.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
Landmark Structure
6 landmarks
PASS
6 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 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
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 À propos des cookies
  • H1 Sénat - Accueil duplicate H1
  • H2 Les élections sénatoriales auront lieu le 27 septembre 2026
  • H2 Souffrance psychique au travail : un défi sociétal et collectif à relever
  • H2 Les derniers travaux parlementaires
  • H2 Développement des transports
  • H2 Simplification de la vie économique
  • H2 Justice criminelle et respect des victimes
  • H2 Relancer les investissements dans le secteur de l'hydroélectricité
  • H2 Découvrir le Sénat
  • H2 E-petitions
  • H2 L’activité du Sénat en chiffres
  • H2 Le Sénat, c'est aussi
  • H3 Sénatoriales 2026
  • H3 Les événements au Sénat
  • H3 Le Jardin du Luxembourg
  • H3 Le Palais du Luxembourg

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

A+
Alt Text Quality
All 22 images OK
PASS
All 22 images OK
Info::
22 decorative image(s) correctly marked
22 images 22 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 8 controls labeled
PASS
All 8 controls labeled
Info::
8 control(s) properly labeled
8 controls
8 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
unktextSaisir votre recherchearia-label
#rqg_dcheckboxDossiers législatifsfor/id
#rqg_rcheckboxRapports d’informationfor/id
#rqg_qcheckboxQuestions parlementairesfor/id
#crcheckboxComptes rendusfor/id
#rqg_pcheckboxTextes européensfor/id
#rqg_tcheckboxDocuments de travailfor/id
#circonscriptionselectTrouvez vos sénateursfor/id
A
Favicon & Branding
6 icon(s) detected
PASS
6 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 Present
✓ Multiple Sizes Present
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Sénat
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Sénat ✓192×192 icon ✓512×512 icon ✓Start URL /?utm_source=web_app_manifest ✓Display Mode standalone ✓
Name Sénat Display Mode standalone Theme Color #1c1e3b Background Color #1c1e3b Icons 2 icon(s)
A
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 23 passed
PASS
91

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

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
LANGUE SÉLECTIONNÉE FRANÇAIS div#navbar-collapse > div.navbar-header > div.dropdown > button#navbar-bottom-languages

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.

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
Groupe Les Républicains (131 sièges) div.col-md-5 > ul.list-unstyled > li > button.btn
Groupe Socialiste, Écologiste et Républicain (65 sièges) div.col-md-5 > ul.list-unstyled > li > button.btn
Groupe Union Centriste (59 sièges) div.col-md-5 > ul.list-unstyled > li > button.btn
Groupe Les Indépendants - République et Territoires (20 sièges) div.col-md-5 > ul.list-unstyled > li > button.btn
Groupe Écologiste - Solidarité et Territoires (16 sièges) div.col-md-5 > ul.list-unstyled > li > button.btn
Mentions légales div.col-lg > ul.list-inline > li.list-inline-item > a
Plan du site div.col-lg > ul.list-inline > li.list-inline-item > a
Accessibilité : partiellement conforme div.col-lg > ul.list-inline > li.list-inline-item > a
Gestion des cookies div.col-lg > ul.list-inline > li.list-inline-item > a.consent-modal-button
Intr@Sénat div.col-lg > ul.list-inline > li.list-inline-item > 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
●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
●`[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
○`[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 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
○`<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.
○Skip links are focusable.
○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