Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

8 PASS 1 REVIEW 4 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-3i74qp

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://vie-publique.fr/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://vie-publique.fr/manifest.json

Manifest contains invalid JSON.

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.

Favicon & Branding

16 icon(s) detected

REVIEW

16 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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+

Heading Hierarchy

22 headings

PASS

22 headings

Single H1 present

H1 Hausse du prix des carburants : quelles conséquences ?
H2 Actualités
H3 Dix questions sur les élections sénatoriales
H3 Santé environnementale : une politique publique sous-dimensionnée
H3 Revenu des ménages : l'Insee montre une hausse des inégalités malgré les mesures de redistribution
H3 La Défenseure des droits dénonce la mise en oeuvre défaillante du "droit au juge"
H3 Collège et lycée publics : l'absentéisme touche 7,2% des élèves en 2024-2025
H3 Violences sur mineurs : un rapport propose l'imprescriptibilité
H2 Les Fiches
H2 Panorama des lois
H3 Projet de loi relatif aux résultats de la gestion et portant approbation des comptes de l’année 2025
H3 Projet de loi de simplification de la vie économique
H3 Proposition de loi visant à renforcer la sécurité, la rétention administrative et la prévention des risques d’attentat
H2 Débats et consultations
H2 Points de vue
H3 Politiques locales de l'habitat : quels sont les leviers des maires pour réguler les logements existants ?
H3 Le détroit d'Ormuz, verrou stratégique du golfe Persique
H3 Le Louvre Abu Dhabi et la valorisation du patrimoine en débat
H2 Bibliothèque média
H2 Publications de La Documentation française
H2 Abonnez-vous à nos lettres d'information
H2 Suivez-noussur les réseaux sociaux

A+

Alt Text Quality

All 15 images OK

PASS

All 15 images OK

14 decorative image(s) correctly marked

1 image(s) with good alt text

15 images 1 good alt text 14 decorative

All images have appropriate alt text.

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
#search_api_fulltext	search	Recherche	for/id

Link & Button Quality

89 links, 15 buttons — all OK

PASS

89 links, 15 buttons — all OK

13 link(s) open in new tab without warning

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

Got: https://www.facebook.com/viepubliquefr/; https://twitter.com/viepubliquefr/; https://www.instagram.com/viepubliquefr/; https://www.linkedin.com/company/vie-publiquefr/; https://www.youtube.com/@ViepubliquefrVP; https://bsky.app/profile/vie-publique.fr; https://www.tiktok.com/@viepublique.fr; https://www.dila.gouv.fr/; https://www.legifrance.gouv.fr/; https://www.info.gouv.fr/ (+3 more)

76 link(s) with descriptive text

89 links

0 empty

0 generic text

13 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/viepubliquefr/	facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/viepubliquefr/	X (anciennement Twitter)	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/viepubliquefr/	instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/vie-pub…	linkedin	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@ViepubliquefrVP	youtube	new tab	Add '(opens in new tab)' to text
https://bsky.app/profile/vie-publique.fr	Bluesky	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@viepublique.fr	TikTok	new tab	Add '(opens in new tab)' to text
https://www.dila.gouv.fr/	Direction de l'information lé…	new tab	Add '(opens in new tab)' to text
https://www.legifrance.gouv.fr/	legifrance.gouv.fr	new tab	Add '(opens in new tab)' to text
https://www.info.gouv.fr/	info.gouv.fr	new tab	Add '(opens in new tab)' to text
https://www.data.gouv.fr/fr/	data.gouv.fr	new tab	Add '(opens in new tab)' to text
https://www.service-public.gouv.fr/	service-public.gouv.fr	new tab	Add '(opens in new tab)' to text
https://github.com/etalab/licence-ouvert…	licence etalab-2.0	new tab	Add '(opens in new tab)' to text

91 links and buttons have descriptive text

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

https://www.facebook.com/viepubliquefr/; https://twitter.com/viepubliquefr/; https://www.instagram.com/viepubliquefr/; https://www.linkedin.com/company/vie-publiquefr/; https://www.youtube.com/@ViepubliquefrVP; https://bsky.app/profile/vie-publique.fr; https://www.tiktok.com/@viepublique.fr; https://www.dila.gouv.fr/; https://www.legifrance.gouv.fr/; https://www.info.gouv.fr/ (+3 more)

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

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /themes/custom/vp_dsfr/dsfr/dist/dsfr.print.min.css?tditb3

Print Stylesheet ✓ Print Optimized

Print stylesheet /themes/custom/vp_dsfr/dsfr/dist/dsfr.print.min.css?tditb3 ✓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 Actualités	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h2 Les Fiches	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h2 Panorama des lois	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h2 Débats et consultat…	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h2 Points de vue	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h2 Bibliothèque média	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h2 Publications de La D…	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h2 Abonnez-vous à nos …	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h2 Suivez-nous	15.46:1	3.0:1	#000000	#DDDDDD	Pass
h2 sur les réseaux soc…	15.46:1	3.0:1	#000000	#DDDDDD	Pass
title Vie publique : au co…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Ce site utilise des …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Accepter	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Refuser	8.49:1	4.5:1	#000000	#A1A5AB	Pass
button Gérer les cookies	8.92:1	4.5:1	#000000	#A6A9AF	Pass
a Contenu	9.10:1	4.5:1	#000000	#A7ABB0	Pass
a Menu	13.26:1	4.5:1	#000000	#6FE49D	Pass
a Recherche	10.36:1	4.5:1	#000000	#8FC1A8	Pass
a Pied de page	12.63:1	4.5:1	#000000	#C6C9CC	Pass
p République	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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 25 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

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

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

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

○`[lang]` attributes have a valid value

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