Skip to content
https://e-monsite.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
D
Form Accessibility
Action
5 of 5 controls have issues
FIX
5 of 5 controls have issues
Critical::
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" name="credentials_login[submit]">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email" id="login-email">; <input type="text" name="credentials_login[loginOrEmail]" id="login-id">; <input type="password" name="credentials_login[password]" id="login-pasword">
5 controls
0 labeled
3 placeholder only
2 unlabeled
ControlTypeLabelMethod
#login-emailemail(Adresse e-mail)placeholder only
#login-idtext(Nom d'utilisateur)placeholder only
#login-paswordpassword(Mot de passe)placeholder only
inputsubmit(none)none
credentials_login[submit]submit(none)none

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

<input type="submit">; <input type="submit" name="credentials_login[submit]">

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.

<input type="email" name="email" id="login-email">; <input type="text" name="credentials_login[loginOrEmail]" id="login-id">; <input type="password" name="credentials_login[password]" id="login-pasword">

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: rgb(255, 255, 255)
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 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.

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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
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 (missing!) 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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Erreur 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
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::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A+
Heading Hierarchy
36 headings
PASS
36 headings
Info::
Single H1 present
  • H1 Créer un site internet gratuit ou professionnel, la création de site web pour tous
  • H2 Des applications en ligne pour créer un site internet facilement avec des fonctionnalités et des contenus web de qualité
  • H3 Créer des pages web illimitées
  • H3 Créer un blog
  • H3 Créer un site e-commerce
  • H3 Planifier un agenda
  • H3 Gérer des réservations
  • H3 Publier un portfolio
  • H2 Aide gratuite à la création de site internet
  • H2 Tutoriels pour créer un site internet
  • H2 Référencement naturel sur Google
  • H2 Des thèmes designs gratuits et personnalisables
  • H2 Création de site internet gratuit
  • H2 Applications web externes
  • H2 Et pleins d'autres avantages à faire un site sur e-monsite.
  • H2 Hébérgement gratuit et illimité
  • H2 Un CMS en ligne
  • H2 CMS sécurisé et mises à jour automatiques
  • H2 Une solution de création de site internet adapté aux besoins de votre projet
  • H3 Créer une boutique en ligne
  • H3 Créer un site web pour une entreprise
  • H3 Créer un site internet pour une association
  • H3 Créer un site internet de location
  • H3 Créer un site web pour un institut de beauté
  • H3 Créer un site internet pour une commune
  • H2 Les étapes pour créer un site internet
  • H2 Vos questions sur la création de site internet
  • H3 Est-ce difficile de créer un site web ?
  • H3 Est-ce que je serais visible sur Google ?
  • H3 Est-ce que je dois trouver un hébergeur pour mon site ?
  • H3 Est-ce que je peux créer une adresse mail pro ?
  • H3 Comment faire pour créer un site web gratuitement ?
  • H3 Quel est le prix d'un site internet ?
  • H3 Est-ce que je peux transférer mon nom de domaine depuis OVH ?
  • H3 Le paiement d'un site internet est-il avec un engagement ?
  • H2 Tout savoir sur la création de site internet
A+
Alt Text Quality
All 24 images OK
PASS
All 24 images OK
Info::
1 decorative image(s) correctly marked
Info::
23 image(s) with good alt text
24 images 23 good alt text 1 decorative
All images have appropriate alt text.
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 Créer un site inter…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Des applications en …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Aide gratuite à la …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Tutoriels pour crée…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Référencement natu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Des thèmes designs …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Création de site in…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Applications web ext…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Et pleins d'autres a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Hébérgement gratui…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Un CMS en ligne21.00:13.0:1
#000000
#FFFFFF
Pass
h2 CMS sécurisé et mi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Une solution de cré…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 adapté aux besoins …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Les étapes pour cr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Vos questions sur la…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Tout savoir sur la c…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Est-ce difficile de …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Est-ce que je serais…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Est-ce que je dois t…21.00:13.0: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 91/100 — 2 failing, 19 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.

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
100% de réponses en 48h div#cell-5d7659939eded4558d13ebfc > div.col-content > div.ems_support_tickets > p.ems_support_tickets_48h

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
200 tutoriels pour apprendre à créer un site Internet div#cell-6746eaddbbf43422841e74ca > div.col-content > p > a
ressources en ligne pour créer un site internet de qualité div#cell-6746eaddbbf43422841e74ca > div.col-content > p > a
référencer sur Google div#cell-639af70827e3d4558d138705 > div.col-content > p > a

These are opportunities to improve the legibility of your content.

○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>`
●`[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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Document has a main landmark.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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.
○`[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.

Send Feedback