Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 3 REVIEW 6 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

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

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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.

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 ✗

Tap Target Adequacy

3 tap target(s) too small or too close together

REVIEW

3 tap target(s) too small or too close together

3 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Lighthouse Accessibility Audits

Action

Score 77/100 — 7 failing, 24 passed

REVIEW

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.home > div.tf-v1-sidetab > button.tf-v1-sidetab-close `body.home > div.tf-v1-sidetab > button.tf-v1-sidetab-close`

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.et_contact_bottom_container > div.et_pb_contact_right > p.clearfix > input.input `div.et_contact_bottom_container > div.et_pb_contact_right > p.clearfix > input.input`

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.cmplz-documents > ul > li > a.cmplz-link `div.cmplz-documents > ul > li > a.cmplz-link`

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.

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
Accepter `div#cmplz-cookiebanner-container > div#cmplz-cookiebanner-1-optin > div.cmplz-buttons > button.cmplz-btn`
Politique de confidentialité `div.cmplz-documents > ul > li > a.cmplz-link`
Demander une démo `div.dipi-button-grid-container > div.et_pb_module > div.et_pb_module_inner > a.et_pb_button`
Digitalisez votre production et pilotez votre performance en temps réel. `div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p`
div.et_pb_contact > form.et_pb_contact_form > p.et_pb_contact_field > input#et_pb_contact_email_0 `div.et_pb_contact > form.et_pb_contact_form > p.et_pb_contact_field > input#et_pb_contact_email_0`
div.et_contact_bottom_container > div.et_pb_contact_right > p.clearfix > input.input `div.et_contact_bottom_container > div.et_pb_contact_right > p.clearfix > input.input`
Télécharger `div.et_pb_contact > form.et_pb_contact_form > div.et_contact_bottom_container > button.et_pb_contact_submit`
Opérationnel en quelques jours, et non en plusieurs mois `div.et_pb_blurb_description > div.p-6 > div.space-y-1 > p.text-sm`
Un retour sur investissement en 3 à 6 mois `div.space-y-1 > div.p-6 > div.space-y-1 > p.text-sm`
Calculez vos gains potentiels `div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button`
Commencez sur une ligne. Décidez ensuite. `div.space-y-1 > div.p-6 > div.space-y-1 > p.text-sm`
En savoir plus sur la ligne pilote `div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button`
Une solution modulaire qui s’adapte à vos besoins `div.space-y-1 > div.p-6 > div.space-y-1 > p.text-sm`
Mais à quel rendement réel ? `div.et_pb_module > div.et_pb_text_inner > h2.text-5xl > span.text-primary`
logiciel MES `p > a > span > span`
logiciels MES `div.text-center > p.text-lg > span > strong`
Performance industrielle `div.et_pb_row > div.et_pb_with_border > div.et_pb_button_module_wrapper > a.et_pb_button`
Voir nos références clients `div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button`
Accéder au calculateur TRS `div.dipi_expanding_cta-content-wrapper > div.dipi_expanding_cta-content > div.dipi-button-wrapper > a.et_pb_button`
NOVOFERM `div.swiper-container > div.dipi-testimonial-wrapper > div.dipi-testimonial-item > div.dipi-company-name`
Sans risque. `div.et_pb_module > div.et_pb_text_inner > p.text-3xl > span.text-primary`
Lancer une ligne pilote `div.dipi-button-grid-container > div.et_pb_module > div.et_pb_module_inner > a.et_pb_button`
Demander une démo `div.dipi-button-grid-container > div.et_pb_module > div.et_pb_module_inner > a.et_pb_button`
VOIR PLUS DE RÉFÉRENCES `div.et_pb_module > div.et_pb_module_inner > div.dipi-reveal > a.et_pb_button`
Demander une démonstration `div.dipi-button-grid-container > div.et_pb_module > div.et_pb_module_inner > a.et_pb_button`
Close and do not switch language `div#trp_ald_modal_container > div#trp_ald_modal_popup > a#trp_ald_x_button_and_textarea > span#trp_ald_x_button_textarea`
Vos gains potentiels ! `body.home > div.tf-v1-sidetab > button.tf-v1-sidetab-button > span.tf-v1-sidetab-button-text`
Téléchargez notre livre blanc `body.home > div.buttonizer > a.buttonizer-closed-0-0-18 > div#buttonizer-button-0-0-13-label`

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport 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
Go to slide 1 `div.dipi-testimonial-main > div.swiper-container-horizontal > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div.dipi-testimonial-main > div.swiper-container-horizontal > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div.dipi-testimonial-main > div.swiper-container-horizontal > div.swiper-pagination > span.swiper-pagination-bullet`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Français `body.home > nav.trp-language-switcher > div.trp-language-switcher-inner > div.trp-language-item`

○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

●Image elements have `[alt]` attributes

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

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

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

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 HTTP 429 Slow down

A+

Heading Text Quality

All 1 heading(s) have substantive, well-formed text

PASS

All 1 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

Alt Text Quality

1 of 1 images have issues

PASS

1 of 1 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 images 1 missing

Issue	Count
missing	1 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

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

3 links, 0 buttons — all OK

PASS

3 links, 0 buttons — all OK

3 link(s) open in new tab without warning

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

Got: https://faq.o2switch.fr/hebergement-mutualise/tutoriels-cpanel/tiger-protect; https://www.o2switch.fr; https://faq.o2switch.fr/hebergement-mutualise/tutoriels-cpanel/tiger-protect

3 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://faq.o2switch.fr/hebergement-mutu…	How to manage this security wi…	new tab	Add '(opens in new tab)' to text
https://www.o2switch.fr	support@o2switch.fr	new tab	Add '(opens in new tab)' to text
https://faq.o2switch.fr/hebergement-mutu…	Tiger Protect	new tab	Add '(opens in new tab)' to text

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

https://faq.o2switch.fr/hebergement-mutualise/tutoriels-cpanel/tiger-protect; https://www.o2switch.fr; https://faq.o2switch.fr/hebergement-mutualise/tutoriels-cpanel/tiger-protect

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+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en-US"

PASS

Lang attribute set to "en-US"

<html lang="en-US"> is set and valid

Got: en-US

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Mobile-Readable Font Sizes

All 9 visible text node(s) render at >= 12 CSS pixels

PASS

All 9 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Color Contrast (Screenshot)

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

10 pass

Show all checked elements (10)

Element	Ratio	Required	FG	BG	Result
h1 HTTP 429	18.75:1	3.0:1	#000000	#F0F2F7	Pass
title HTTP 429	19.36:1	4.5:1	#000000	#F3F6F9	Pass
small Slow down	18.22:1	4.5:1	#000000	#ECEFF4	Pass
p This request was blo…	17.86:1	4.5:1	#000000	#E9EDF2	Pass
p If you are the webma…	17.43:1	4.5:1	#000000	#E7EAF0	Pass
span How to manage this s…	17.08:1	4.5:1	#000000	#E4E8EE	Pass
a support@o2switch.fr	16.63:1	4.5:1	#000000	#E1E5ED	Pass
a Tiger Protect	16.32:1	4.5:1	#000000	#DFE3EB	Pass
strong Request ID	15.99:1	3.0:1	#000000	#DCE1E9	Pass
small : 245ae48ed631c73d13…	15.55:1	4.5:1	#000000	#D9DEE7	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.