Skip to content
https://smoft.io

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
8
REVIEW
5
PASS
11
INFO
0
Checks
24
11 PASS 5 REVIEW 8 FIX
D
Heading Hierarchy
Action
37 headings, 3 skip(s)
FIX
37 headings, 3 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 SMOFT | ERP Cloud intelligent avec +65 applications
  • H3 Plateforme cloud avec agents IA personnalisables, no-code et modulaire, adaptée à tous les secteurs et toutes les tailles d’entreprise. Centralisez vos opérations dans une solution unique, intell skipped
  • H1 SMOFT | ERP Cloud intelligent avec +65 applications duplicate H1
  • H2 SMOFT ERP, +65 applications, Tout-en-un.
  • H5 Business skipped
  • H5 Mission
  • H5 Sync
  • H5 Workforce
  • H5 Perf
  • H5 Manufacturing
  • H5 Logistics
  • H5 Data
  • H5 Run
  • H5 Assist
  • H5 Insights
  • H5 IASMO
  • H5 Control
  • H2 Gérer votre quotidien professionnel!
  • H2 ISO 9001, 27001 & 27701
  • H3 Certifications & Conformité
  • H3 Signature électronique
  • H3 Cachet CEV 2D-DOC
  • H3 Certification SSL
  • H3 Facturation électronique
  • H2 Témoignages de nos clients
  • H3 Mohamed Karmani
  • H3 Amen Gahbiche
  • H3 Halim Golli
  • H3 Khaled Kadous
  • H3 Taoufik Ben Zineb
  • H2 Acceptez-vous de nous laisser utiliser des cookies ?
  • H2 Apercu video SMOFT
  • H2 Ne partez pas avant de l'essayer 🚀
  • H5 À propos de nous skipped
  • H5 Entreprise
  • H5 Nos services
  • H5 Contactez-nous

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

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 ▾

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 ▾

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

D
Mobile Keyboard & Autofill
Action
3/4 eligible field(s) missing autocomplete or inputmode
FIX
3/4 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="email" name="email" id="newsletter_email">
Warning::
2 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email" name="email" id="smartExitEmail">, <input type="email" name="email" id="newsletter_email">
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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: #0b5ed7
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::
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
Landmark Structure
Action
8 landmarks
REVIEW
8 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (missing!) CONTENTINFO footer

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

B
Tap Target Adequacy
3 tap target(s) too small or too close together
REVIEW
3 tap target(s) too small or too close together
Info::
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.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 SMOFT | ERP Cloud intelligent avec +65 a…
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
32px · bottom of viewport
h1 SMOFT | ERP Cloud intelligent avec +65 a…
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
32px · bottom of viewport
h2 SMOFT ERP, +65 applications, Tout-en-un.
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Gérer votre quotidien professionnel!
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ISO 9001, 27001 & 27701
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Témoignages de nos clients
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Acceptez-vous de nous laisser utiliser d…
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Apercu video SMOFT
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ne partez pas avant de l'essayer
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Plateforme cloud avec agents IA personna…
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Certifications & Conformité
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Signature électronique
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cachet CEV 2D-DOC
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Certification SSL
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Facturation électronique
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Mohamed Karmani
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Amen Gahbiche
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Halim Golli
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Khaled Kadous
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Taoufik Ben Zineb
1.42:1
#000000
on
#232833
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 SMOFT | ERP Cloud in…1.42:13.0:1
#000000
#232833
Fail
h1 SMOFT | ERP Cloud in…1.42:13.0:1
#000000
#232833
Fail
h2 SMOFT ERP, +65 appli…1.42:13.0:1
#000000
#232833
Fail
h2 Gérer votre quotidi…1.42:13.0:1
#000000
#232833
Fail
h2 ISO 9001, 27001 & 27…1.42:13.0:1
#000000
#232833
Fail
h2 Témoignages de nos …1.42:13.0:1
#000000
#232833
Fail
h2 Acceptez-vous de nou…1.42:13.0:1
#000000
#232833
Fail
h2 Apercu video SMOFT1.42:13.0:1
#000000
#232833
Fail
h2 Ne partez pas avant …1.42:13.0:1
#000000
#232833
Fail
h3 Plateforme cloud ave…1.42:13.0:1
#000000
#232833
Fail
h3 Certifications & Con…1.42:13.0:1
#000000
#232833
Fail
h3 Signature électroni…1.42:13.0:1
#000000
#232833
Fail
h3 Cachet CEV 2D-DOC1.42:13.0:1
#000000
#232833
Fail
h3 Certification SSL1.42:13.0:1
#000000
#232833
Fail
h3 Facturation électro…1.42:13.0:1
#000000
#232833
Fail
h3 Mohamed Karmani1.42:13.0:1
#000000
#232833
Fail
h3 Amen Gahbiche1.42:13.0:1
#000000
#232833
Fail
h3 Halim Golli1.42:13.0:1
#000000
#232833
Fail
h3 Khaled Kadous1.42:13.0:1
#000000
#232833
Fail
h3 Taoufik Ben Zineb1.42:13.0:1
#000000
#232833
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 5 failing, 23 passed
REVIEW
88

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
Politique de confidentialité div.home-hero-content > div#cookieModal > p > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Plateforme cloud avec agents IA personnalisables, no-code et modulaire, adaptée… div.col-lg-5 > div.hero-copy-block > div#pos1 > h3
Business div.erp-suite-grid > a.erp-suite-card > div.erp-suite-content > h5
À Propos De Nous div.container-fluid > div.row > div.col-lg-4 > h5.footer-title2

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.d-flex > div.nav-item > div.dropdown > a#Language

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

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
FAQ div.row > div.col-lg-4 > div.ldiv > a.sidwsroda
Termes div.row > div.col-lg-4 > div.ldiv > a.sidwsroda
Blog div.row > div.col-lg-4 > div.ldiv > a.sidwsroda

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
Business Devis, commandes, stocks et finances en temps réel. div.erp-suite-outer > div.erp-suite-inner > div.erp-suite-grid > a.erp-suite-card
Mission Planifiez et suivez vos projets et tâches. div.erp-suite-outer > div.erp-suite-inner > div.erp-suite-grid > a.erp-suite-card
Sync Réunions et événements clés synchronisés. div.erp-suite-outer > div.erp-suite-inner > div.erp-suite-grid > a.erp-suite-card
Workforce GRH, ATS et recrutement, pointage, KPIs, etc. div.erp-suite-outer > div.erp-suite-inner > div.erp-suite-grid > a.erp-suite-card
Perf Contrôle qualité et performance. div.erp-suite-outer > div.erp-suite-inner > div.erp-suite-grid > a.erp-suite-card
Manufacturing Ordres de fabrication et traçabilité. div.erp-suite-outer > div.erp-suite-inner > div.erp-suite-grid > a.erp-suite-card
Logistics Gestion entrepôts et livraisons. div.erp-suite-outer > div.erp-suite-inner > div.erp-suite-grid > a.erp-suite-card
Data Formulaires et contenus dynamiques no-code. div.erp-suite-outer > div.erp-suite-inner > div.erp-suite-grid > a.erp-suite-card
Run CRM, Marketing et CMS intégrés. div.erp-suite-outer > div.erp-suite-inner > div.erp-suite-grid > a.erp-suite-card
Assist Support SLA et gestion d'incidents. div.erp-suite-outer > div.erp-suite-inner > div.erp-suite-grid > a.erp-suite-card
Insights Reporting et prévisions stratégiques. div.erp-suite-outer > div.erp-suite-inner > div.erp-suite-grid > a.erp-suite-card
IASMO IA orientée métiers intégrée et co-équipier. div.erp-suite-outer > div.erp-suite-inner > div.erp-suite-grid > a.erp-suite-card
Control Paramétrages, contrôle et personnalisation. div.erp-suite-outer > div.erp-suite-inner > div.erp-suite-control-wrap > a.erp-suite-card
Mohamed Karmani Tunisian Cars ★★★★★ div.testimonials-carousel > div.testimonials-grid > article.testimonial-card > button.testimonial-media
○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
●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.
●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
●`<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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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.
○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 Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
1 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 195 chars
Got: 1 >120-char heading(s)
Info::
2 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 2 all-caps heading(s)
A+
Alt Text Quality
All 33 images OK
PASS
All 33 images OK
Info::
16 decorative image(s) correctly marked
Info::
17 image(s) with good alt text
33 images 17 good alt text 16 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="email" id="smartExitEmail">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#newsletter_emailemailVotre adresse e-mailaria-label
#smartExitEmailemail(Saisissez votre e-mail)placeholder only

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

<input type="email" name="email" id="smartExitEmail">

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

A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "fr"
PASS
Lang attribute set to "fr"
Info::
<html lang="fr"> is set and valid
Got: fr
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
A+
Mobile-Readable Font Sizes
All 112 visible text node(s) render at >= 12 CSS pixels
PASS
All 112 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback