Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 7 REVIEW 5 FIX

Form Accessibility

Action

5 of 5 controls have issues

FIX

5 of 5 controls have issues

2 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="submit">; <input type="submit">

3 control(s) rely on placeholder only

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

Got: <input type="search" name="f_libelle">; <input type="email" name="email">; <input type="email" name="email">

5 controls

0 labeled

3 placeholder only

2 unlabeled

Control	Type	Label	Method
f_libelle	search	(Chercher une entreprise, un dirigeant, une tendance)	placeholder only
email	email	(Entrer son email pour s'abonner)	placeholder only
email	email	(Entrer son email pour s'abonner)	placeholder only
input	submit	(none)	none
input	submit	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

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

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #ffffff

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 ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Lighthouse Accessibility Audits

Action

Score 68/100 — 6 failing, 15 passed

FIX

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Suivez-nous `div.layout > div.grid_row > div.grid_col > h3.app_mod_int_title`
Restez connecté `div.layout > div.grid_row > div.grid_col > h3.app_mod_int_title`

These are opportunities to improve the legibility of your content.

Names and labels

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
body.app--rwd > div.ccmcss_offcanvas_1 > div.ccmcss_offcanvas_2 > img `body.app--rwd > div.ccmcss_offcanvas_1 > div.ccmcss_offcanvas_2 > img`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.app--rwd > div#appconsent > iframe `body.app--rwd > div#appconsent > iframe`

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
div.app_header__right > ul > li > a.jDropBtn `div.app_header__right > ul > li > a.jDropBtn`
div.app_header__right > ul > li > a.jHeaderDisconnected `div.app_header__right > ul > li > a.jHeaderDisconnected`
div.grid_row > div.grid_col > div.app_share_icons > a `div.grid_row > div.grid_col > div.app_share_icons > a`
div.grid_row > div.grid_col > div.app_share_icons > a `div.grid_row > div.grid_col > div.app_share_icons > a`
div.grid_row > div.grid_col > div.app_share_icons > a `div.grid_row > div.grid_col > div.app_share_icons > a`
div.ccmcss_offcanvas_2 > footer.cp_footer > div.cp_footer__logo > a `div.ccmcss_offcanvas_2 > footer.cp_footer > div.cp_footer__logo > a`

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

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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
Qui sommes-nous ? `div#footer_internal_links > ul > li > a`
L'équipe `div#footer_internal_links > ul > li > a`
Notre société `div#footer_internal_links > ul > li > a`
Publicité `div#footer_internal_links > ul > li > a`
Contact `div#footer_internal_links > ul > li > a`
Recrutement `div#footer_internal_links > ul > li > a`
Données personnelles `div#footer_internal_links > ul > li > a`
Paramétrer les cookies `div#footer_internal_links > ul > li > a.jConsentChoice`
Gérer Utiq `div#footer_internal_links > ul > li > a#utiq__modal-manager`
Tous les articles `div#footer_internal_links > ul > li > a`
RSS `div#footer_internal_links > ul > li > a`
Corrections `div#footer_internal_links > ul > li > a`
Mentions légales `div#footer_internal_links > ul > li > a`
Groupe Figaro `div#footer_internal_links > ul > li > a`
© 2025 CCM Benchmark `div#footer_internal_links > 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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●Input buttons have discernible text.

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Image elements do not have `[alt]` attributes that are redundant text.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted 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

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

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

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

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

Landmark Structure

Action

14 landmarks

REVIEW

14 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Heading Hierarchy

22 headings, 2 skip(s)

REVIEW

22 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Google Cloud Next 2026 : Google veut devenir le système d'exploitation de l'entreprise agentique
H2 Des frissons et un tremplin : comment l'armée de Terre séduit la Gen Z de la cybersécurité
H2 Créer sa start-up : les 5 meilleurs conseils des repeat founders
H2 Mythos, IA et cybersécurité : la fin du mythe de l'exclusivité
H2 La cybersécurité est avant tout une affaire de gouvernance
H4 Elie Ohayon (Master The Monster) skipped
H2 "Avec l'IA, les agences ne peuvent plus se rémunérer au temps passé"
H2 Les robots humanoïdes bientôt au cœur de la silver economy ?
H4 Vincent Arvers (Libération) skipped
H2 "Les recettes publicitaires digitales de Libération ont progressé de près de 10% en 2025"
H2 Cybersécurité : tout ce que les attaquants savent déjà sur votre entreprise
H2 EUDI : comment le portefeuille d'identité numérique européen peut devenir indispensable
H2 RSSI : 7 red flag qui doivent vous faire refuser un poste
H2 Les levées de fonds de la medtech française, un succès en trompe-l'oeil
H2 Relations presse : l'humain n'a jamais été aussi stratégique qu'à l'ère de l'IA !
H2 L'IA n'est pas (encore) responsable de la baisse des embauches selon LinkedIn
H2 Votre PME industrielle est une cible réputationnelle. Voici pourquoi vous n'êtes pas prêt.
H2 Détroit d'Hormuz : la stratégie invisible de l'Iran qui inquiète les puissances occidentales
H2 YouTube teste les miniatures géolocalisées : une évolution majeure pour la Creator Economy
H3 Suivez-nous
H3 Restez connecté
H3 Devenez chroniqueur

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Alt Text Quality

2 of 19 images have issues

REVIEW

2 of 19 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 decorative image(s) correctly marked

16 image(s) with good alt text

19 images 16 good alt text 1 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

Link & Button Quality

Action

7 issue(s) across 136 links and 3 buttons

REVIEW

7 issue(s) across 136 links and 3 buttons

7 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #; #; #; //www.facebook.com/pages/Journal-du-Net/204045139612793; //twitter.com/journaldunet; //www.journaldunet.com/rss.shtml; https://jobs.ccmbenchmark.com/

7 link(s) open in new tab without warning

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

Got: //mailing.ccmbg.com/archive/last-50; https://www.ccmbenchmark.com/donnees-personnelles-partenaires-data?origin=jdn; https://www.ccmbenchmark.com/donnees-personnelles?origin=www.journaldunet.com; https://www.ccmbenchmark.com/donnees-personnelles-cookie?origin=jdn; https://www.ccmbenchmark.com/donnees-personnelles-partenaires-data?origin=jdn; https://www.ccmbenchmark.com/donnees-personnelles?origin=www.journaldunet.com; https://www.ccmbenchmark.com/donnees-personnelles-cookie?origin=jdn

122 link(s) with descriptive text

136 links

7 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
//mailing.ccmbg.com/archive/last-50	Voir un exemple	new tab	Add '(opens in new tab)' to text
https://www.ccmbenchmark.com/donnees-per…	à tout moment	new tab	Add '(opens in new tab)' to text
https://www.ccmbenchmark.com/donnees-per…	politique de confidentialité	new tab	Add '(opens in new tab)' to text
https://www.ccmbenchmark.com/donnees-per…	politique Cookies	new tab	Add '(opens in new tab)' to text
//www.facebook.com/pages/Journal-du-Net/…	(empty)	empty	Add link text or aria-label
//twitter.com/journaldunet	(empty)	empty	Add link text or aria-label
//www.journaldunet.com/rss.shtml	(empty)	empty	Add link text or aria-label
https://www.ccmbenchmark.com/donnees-per…	à tout moment	new tab	Add '(opens in new tab)' to text
https://www.ccmbenchmark.com/donnees-per…	politique de confidentialité	new tab	Add '(opens in new tab)' to text
https://www.ccmbenchmark.com/donnees-per…	politique Cookies	new tab	Add '(opens in new tab)' to text
https://jobs.ccmbenchmark.com/	(empty)	empty	Add link text or aria-label

125 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

#; #; #; //www.facebook.com/pages/Journal-du-Net/204045139612793; //twitter.com/journaldunet; //www.journaldunet.com/rss.shtml; https://jobs.ccmbenchmark.com/

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

//mailing.ccmbg.com/archive/last-50; https://www.ccmbenchmark.com/donnees-personnelles-partenaires-data?origin=jdn; https://www.ccmbenchmark.com/donnees-personnelles?origin=www.journaldunet.com; https://www.ccmbenchmark.com/donnees-personnelles-cookie?origin=jdn; https://www.ccmbenchmark.com/donnees-personnelles-partenaires-data?origin=jdn; https://www.ccmbenchmark.com/donnees-personnelles?origin=www.journaldunet.com; https://www.ccmbenchmark.com/donnees-personnelles-cookie?origin=jdn

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

7 icon(s) detected

REVIEW

7 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 Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 16 fail WCAG AA

REVIEW

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

4 pass 16 fail WCAG AA 4 pass AA only

title JDN : Business, IA, Tech-Média, Cybers�…

3.14:1

#000000

#5C5C5C

needs 4.5:1 (normal text)

16px · top of page (header area)

a IA News

1.93:1

#000000

#3D3C46

needs 4.5:1 (normal text)

16px · top of page (header area)

a Tech

1.79:1

#000000

#373742

needs 4.5:1 (normal text)

16px · top of page (header area)

a Media / Adtech

1.66:1

#000000

#31323E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Start-up

1.55:1

#000000

#2B2E3A

needs 4.5:1 (normal text)

16px · above the fold

a Cybersécurité

1.46:1

#000000

#242A36

needs 4.5:1 (normal text)

16px · above the fold

a Robotique

1.34:1

#000000

#1D242E

needs 4.5:1 (normal text)

16px · above the fold

a Cloud

1.15:1

#000000

#131518

needs 4.5:1 (normal text)

16px · above the fold

a Economie

3.14:1

#000000

#5C5C5C

needs 4.5:1 (normal text)

16px · above the fold

a IA News

3.14:1

#000000

#5C5C5C

needs 4.5:1 (normal text)

16px · above the fold

a Tech

3.14:1

#000000

#5C5C5C

needs 4.5:1 (normal text)

16px · above the fold

a Media / Adtech

3.14:1

#000000

#5C5C5C

needs 4.5:1 (normal text)

16px · above the fold

a Start-up

3.14:1

#000000

#5C5C5C

needs 4.5:1 (normal text)

16px · above the fold

a Cybersécurité

3.14:1

#000000

#5C5C5C

needs 4.5:1 (normal text)

16px · mid-page

a Robotique

3.14:1

#000000

#5C5C5C

needs 4.5:1 (normal text)

16px · mid-page

a Cloud

3.14:1

#000000

#5C5C5C

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Google Cloud Next 20…	3.14:1	3.0:1	#000000	#5C5C5C	Pass
h3 Suivez-nous	3.14:1	3.0:1	#000000	#5C5C5C	Pass
h3 Restez connecté	3.14:1	3.0:1	#000000	#5C5C5C	Pass
h3 Devenez chroniqueur	3.14:1	3.0:1	#000000	#5C5C5C	Pass
title JDN : Business, IA, …	3.14:1	4.5:1	#000000	#5C5C5C	Fail
a IA News	1.93:1	4.5:1	#000000	#3D3C46	Fail
a Tech	1.79:1	4.5:1	#000000	#373742	Fail
a Media / Adtech	1.66:1	4.5:1	#000000	#31323E	Fail
a Start-up	1.55:1	4.5:1	#000000	#2B2E3A	Fail
a Cybersécurité	1.46:1	4.5:1	#000000	#242A36	Fail
a Robotique	1.34:1	4.5:1	#000000	#1D242E	Fail
a Cloud	1.15:1	4.5:1	#000000	#131518	Fail
a Economie	3.14:1	4.5:1	#000000	#5C5C5C	Fail
a IA News	3.14:1	4.5:1	#000000	#5C5C5C	Fail
a Tech	3.14:1	4.5:1	#000000	#5C5C5C	Fail
a Media / Adtech	3.14:1	4.5:1	#000000	#5C5C5C	Fail
a Start-up	3.14:1	4.5:1	#000000	#5C5C5C	Fail
a Cybersécurité	3.14:1	4.5:1	#000000	#5C5C5C	Fail
a Robotique	3.14:1	4.5:1	#000000	#5C5C5C	Fail
a Cloud	3.14:1	4.5:1	#000000	#5C5C5C	Fail

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.

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: JDN

192x192 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name JDN ✓192×192 icon ✓512×512 icon ✗Start URL https://www.journaldunet.com ✓Display Mode standalone ✓

Name JDN Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

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