Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 42 -1-on-focusable

FIX

0 positive, 42 -1-on-focusable

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

F

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title mobify-storefront.com ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

D

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.

D

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.

D

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 ✗

F

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

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

Heading Hierarchy

10 headings

REVIEW

10 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H3 Découvrez notre sélection de lots BISSELL exclusifs et soigneusement sélectionnés, recommandés par les experts.
H3 Le tout nouveau CrossWave® HydroScrub™ est désormais disponible !
H3 Faites face aux saletés tenaces pour moins cher
H2 Produits sélectionnés
H3 Pour vous aider à maîtriser le nettoyage
H3 Inscrivez-vous à notre newsletter et recevez 10% de réduction sur votre prochaine commande!
H4 Catégories de produits
H4 En savoir plus
H4 Nous contacter
H4 Confidentialité

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B

Link & Button Quality

1 issue(s) across 83 links and 33 buttons

REVIEW

1 issue(s) across 83 links and 33 buttons

1 link(s) with no accessible text

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

Got: a#contentarea

5 link(s) open in new tab without warning

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

Got: https://www.bissell.fr/pieces-rechange; https://recall.bissell.com/fr/ ; https://www.bissell.fr/pieces-rechange; https://recall.bissell.com/fr/ ; https://www.bissell.fr/politique-de-confidentialite-bissell

77 link(s) with descriptive text

83 links

1 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.bissell.fr/pieces-rechange	Des pièces de rechange	new tab	Add '(opens in new tab)' to text
https://recall.bissell.com/fr/	Rappel de produit	new tab	Add '(opens in new tab)' to text
https://www.bissell.fr/pieces-rechange	Des pièces de rechange	new tab	Add '(opens in new tab)' to text
https://recall.bissell.com/fr/	Rappel de produit	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
https://www.bissell.fr/promos	Jusqu'à -40 % dès maintenant…	img no alt	Add alt attribute to the image
https://www.bissell.fr/type-de-nettoyage…	Aspirateur	img no alt	Add alt attribute to the image
https://www.bissell.fr/type-de-nettoyage…	Aspirateur eau et poussière	img no alt	Add alt attribute to the image
https://www.bissell.fr/type-de-nettoyage…	Appareils sans fil	img no alt	Add alt attribute to the image
https://www.bissell.fr/type-de-nettoyage…	Appareils pour propriétaires …	img no alt	Add alt attribute to the image
https://www.bissell.fr/type-de-nettoyage…	Nettoyeur de taches	img no alt	Add alt attribute to the image
https://www.bissell.fr/type-de-nettoyage…	Nettoyeur de tapis	img no alt	Add alt attribute to the image
https://www.bissell.fr/type-de-nettoyage…	Nettoyeurs d’extérieur	img no alt	Add alt attribute to the image
https://www.bissell.fr/surface-de-nettoy…	Tapis et moquettes	img no alt	Add alt attribute to the image
https://www.bissell.fr/surface-de-nettoy…	Sols durs carrelés et scellé…	img no alt	Add alt attribute to the image
https://www.bissell.fr/surface-de-nettoy…	Sols en bois	img no alt	Add alt attribute to the image
https://www.bissell.fr/surface-de-nettoy…	Multi-surfaces	img no alt	Add alt attribute to the image
https://www.bissell.fr/surface-de-nettoy…	Rembourrages	img no alt	Add alt attribute to the image
https://www.bissell.fr/politique-de-conf…	Pourquoi cette information est…	new tab	Add '(opens in new tab)' to text

110 links and buttons have descriptive text

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

a#contentarea

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.

https://www.bissell.fr/pieces-rechange; https://recall.bissell.com/fr/ ; https://www.bissell.fr/pieces-rechange; https://recall.bissell.com/fr/ ; https://www.bissell.fr/politique-de-confidentialite-bissell

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

C

Mobile Keyboard & Autofill

Action

4/6 eligible field(s) missing autocomplete or inputmode

REVIEW

4/6 eligible field(s) missing autocomplete or inputmode

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

3 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="login[username]" id="email">, <input type="email" name="email" id="newsletter">, <input type="email" name="username" id="customer-email">

B

Mobile-Readable Font Sizes

97% of visible text renders at >= 12 CSS px (1 below threshold)

REVIEW

97% of visible text renders at >= 12 CSS px (1 below threshold)

1 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <div> 8.8px ("Menu").

B

Favicon & Branding

6 icon(s) detected

REVIEW

6 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

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 14 fail WCAG AA

REVIEW

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

6 pass 14 fail WCAG AA 6 pass AA only

h2 Produits sélectionnés

1.63:1

#000000

on

#2E3237

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Découvrez notre sélection de lots BISS…

1.63:1

#000000

on

#2E3237

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Le tout nouveau CrossWave® HydroScrub�…

1.63:1

#000000

on

#2E3237

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Faites face aux saletés tenaces pour mo…

1.63:1

#000000

on

#2E3237

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Pour vous aider à maîtriser le nettoya…

1.63:1

#000000

on

#2E3237

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Inscrivez-vous à notre newsletter et re…

1.63:1

#000000

on

#2E3237

needs 3.0:1 (large text)

19px · bottom of viewport

title BISSELL France | Site Officiel BISSELL -…

1.03:1

#000000

on

#000610

needs 4.5:1 (normal text)

16px · top of page (header area)

a Aller au contenu principal

1.03:1

#000000

on

#000610

needs 4.5:1 (normal text)

16px · top of page (header area)

div Livraison: 2 à 3 jours ouvrables

1.03:1

#000000

on

#000610

needs 4.5:1 (normal text)

16px · top of page (header area)

div 150 ans d'expérience

1.85:1

#000000

on

#3A3A3A

needs 4.5:1 (normal text)

16px · top of page (header area)

div Jusqu'à 5 ans de garantie

1.33:1

#000000

on

#391A17

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

div Livraison gratuite à partir de 100 €

2.35:1

#000000

on

#6D3C36

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

div Livraison: 2 à 3 jours ouvrables

4.15:1

#000000

on

#6C6F70

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

div 150 ans d'expérience

4.15:1

#000000

on

#6C6F70

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

4 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Produits sélectionn…	1.63:1	3.0:1	#000000	#2E3237	Fail
h3 Découvrez notre sé…	1.63:1	3.0:1	#000000	#2E3237	Fail
h3 Le tout nouveau Cros…	1.63:1	3.0:1	#000000	#2E3237	Fail
h3 Faites face aux sale…	1.63:1	3.0:1	#000000	#2E3237	Fail
h3 Pour vous aider à m…	1.63:1	3.0:1	#000000	#2E3237	Fail
h3 Inscrivez-vous à no…	1.63:1	3.0:1	#000000	#2E3237	Fail
title BISSELL France \| Sit…	1.03:1	4.5:1	#000000	#000610	Fail
a Aller au contenu pri…	1.03:1	4.5:1	#000000	#000610	Fail
div Livraison: 2 à 3 jo…	1.03:1	4.5:1	#000000	#000610	Fail
div 150 ans d'expérienc…	1.85:1	4.5:1	#000000	#3A3A3A	Fail
div Jusqu'à 5 ans de ga…	1.33:1	4.5:1	#000000	#391A17	Fail
div Livraison gratuite �…	2.35:1	4.5:1	#000000	#6D3C36	Fail
div Livraison: 2 à 3 jo…	4.15:1	4.5:1	#000000	#6C6F70	Fail
div 150 ans d'expérienc…	4.15:1	4.5:1	#000000	#6C6F70	Fail
div Jusqu'à 5 ans de ga…	6.35:1	4.5:1	#000000	#908D87	Pass
div Livraison gratuite �…	6.35:1	4.5:1	#000000	#908D87	Pass
div Livraison: 2 à 3 jo…	4.96:1	4.5:1	#000000	#7B7B7A	Pass
div 150 ans d'expérienc…	6.35:1	4.5:1	#000000	#908D87	Pass
span ‹	5.02:1	4.5:1	#000000	#7C7C79	Pass
span ›	6.03:1	4.5:1	#000000	#878A89	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.

B

Lighthouse Accessibility Audits

Score 83/100 — 4 failing, 28 passed

REVIEW

83

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
ul.flex-container-container > li.flexbox > div.element > button `ul.flex-container-container > li.flexbox > div.element > button`

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
li.flexbox > div.element > button > img `li.flexbox > div.element > button > img`

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
Découvrez maintenant `div.container-fluid > div.aw-hero__block > div.hero-cta > div.button-cta`
Surface de nettoyage `section.section > div.container > div.aw-category-tabs > a.aw-category-tab`
Inscription `div.d-flex > div.d-flex > button.button-cta > span`

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`

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-*]` 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

●Form elements have associated labels

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

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

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Uses ARIA roles only on compatible elements

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

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

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

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

○Identical links have the same purpose.

○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

Landmark Structure

13 landmarks

PASS

13 landmarks

<main> landmark present

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

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 Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 40 images OK

PASS

All 40 images OK

20 decorative image(s) correctly marked

20 image(s) with good alt text

40 images 20 good alt text 20 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 5 controls labeled

PASS

All 5 controls labeled

5 control(s) properly labeled

5 controls

5 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#email	email	Email	for/id
#pass	password	Mot de passe	for/id
#newsletter	email	Email	for/id
#customer-email	email	Adresse mail	for/id
#pass	password	Mot de passe	for/id

A+

Form Input Types

5 form control(s) checked, no type mismatches

PASS

5 form control(s) checked, no type mismatches

No input-type mismatches detected

A

Form Input Quality

1 input-semantic issue(s) across 5 form control(s)

PASS

1 input-semantic issue(s) across 5 form control(s)

2 password field(s) missing or with invalid `autocomplete`

Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="login[password]">, <input type="password" name="password">.

A+

Document Language

Lang attribute set to "fr"

PASS

Lang attribute set to "fr"

<html lang="fr"> is set and valid

Got: fr

A

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Service worker registration detected

The page calls `navigator.serviceWorker.register(...)` -- the prerequisite for any real PWA capability (offline support, push notifications, background sync, Cache API). This is a positive signal; whether the registered worker actually does what you want is a separate question (check DevTools > Application > Service Workers).

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

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.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.