Skip to content
https://nutrimuscle.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
43
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
D
Form Accessibility
Action
5 of 27 controls have issues
FIX
5 of 27 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="checkbox" name="customer[accepts_marketing]">; <input type="checkbox" name="customer[accepts_marketing]">
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="search">; <input type="text" id="search">; <input type="text" name="tag_phone">
Info::
22 control(s) properly labeled
27 controls
22 labeled
3 placeholder only
2 unlabeled
ControlTypeLabelMethod
#SC-CustomerEmailemailE-mailfor/id
#SC-CustomerPasswordpasswordMot de passefor/id
#SC-RegisterForm-FirstNametextPrénomfor/id
#SC-RegisterForm-LastNametextNom de famillefor/id
#SC-RegisterForm-emailemailE-mail*for/id
#SC-RegisterForm-passwordpasswordMot de passe*for/id
#register-form-condition--cart-drawer-v2-optincheckboxEn vous inscrivant, vous acceptez également de recevoir nos communications newsletter.for/id
#register-form-condition--cart-drawer-v2-cgvcheckboxJ'accepte les CGV.for/id
#show-registercheckboxJ'ai déjà un comptefor/id
#RecoverEmail-popinemailE-mailfor/id
#CustomerEmail-popinemailE-mailfor/id
#CustomerPassword-popinpasswordMot de passefor/id
#RegisterForm-FirstNametextPrénom*for/id
#RegisterForm-LastNametextNom de famille*for/id
#RegisterForm-emailemailE-mail*for/id
#RegisterForm-passwordpasswordMot de passe*for/id
#register-form-condition--form_condition_VztthrcheckboxEn vous inscrivant, vous acceptez également de recevoir nos communications newsletter.for/id
#register-form-condition--form_condition_RXaf3kcheckboxPour recevoir nos offres exclusives par SMS.for/id
#NewsletterForm-email--newsletter-footeremailSaisissez votre adresse mailfor/id
#newsletter-footer-checkbox-newsletter-footercheckboxJ'accepte de recevoir des offres et communications par emailfor/id
#email_01KKBRA3KZV8YWRFQDH7489BP7emailEmailfor/id
#Optin_email__4__6radioEn vous inscrivant, vous acceptez notre politique de confidentialité et nos conditions générales de ventearia-label
#searchtext(Protimuscle)placeholder only
#searchtext(Protimuscle)placeholder only
tag_phonetext(Téléphone)placeholder only
customer[accepts_marketing]checkbox(none)none
customer[accepts_marketing]checkbox(none)none

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

<input type="checkbox" name="customer[accepts_marketing]">; <input type="checkbox" name="customer[accepts_marketing]">

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="text" id="search">; <input type="text" id="search">; <input type="text" name="tag_phone">

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

F
404 Error Page
Action
HTTP 429, custom page
FIX
HTTP 429, custom page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Info::
Custom styled 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 429 Page Title Just a moment... Custom Styling Navigation Homepage Link Search Form
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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'>.
favicon.ico Missing
PNG Icons Present
Apple Touch Missing
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.
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 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
Warning::
No <nav> landmark 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 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
Alt Text Quality
4 of 58 images have issues
REVIEW
4 of 58 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
2 image(s) with generic alt text
Info::
36 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
58 images 18 good alt text 36 decorative 2 generic 2 missing
IssueCount
missing2 image(s)
generic2 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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 12 fail WCAG AA
REVIEW

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

8 pass 12 fail WCAG AA
h2 Au coeur de nos protéines
2.12:1
#000000
on
#0C4768
needs 3.0:1 (large text)
24px · bottom of viewport
title Compléments alimentaires, nutrition spo…
1.12:1
#000000
on
#121214
needs 4.5:1 (normal text)
16px · top of page (header area)
a Ignorer et passer au contenu
4.37:1
#000000
on
#727272
needs 4.5:1 (normal text)
16px · top of page (header area)
p Des avantages exclusifs avec le NM Club
4.37:1
#000000
on
#727272
needs 4.5:1 (normal text)
16px · top of page (header area)
button Déjà membre
4.37:1
#000000
on
#727272
needs 4.5:1 (normal text)
16px · top of page (header area)
button Je m'inscris
3.56:1
#000000
on
#67645E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Panier
1.08:1
#000000
on
#0E0D0C
needs 4.5:1 (normal text)
16px · above the fold
p Retour sur la boutique
1.17:1
#000000
on
#171718
needs 4.5:1 (normal text)
16px · above the fold
div Plus que
1.14:1
#000000
on
#151412
needs 4.5:1 (normal text)
16px · above the fold
span 50,00 €
1.20:1
#000000
on
#1A1917
needs 4.5:1 (normal text)
16px · above the fold
span Paiement sécurisé
1.10:1
#000000
on
#10100E
needs 4.5:1 (normal text)
16px · mid-page
span - 0,00€
1.08:1
#000000
on
#0D0D0C
needs 4.5:1 (normal text)
16px · mid-page

1 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)
ElementRatioRequiredFGBGResult
h2 Au coeur de nos prot…2.12:13.0:1
#000000
#0C4768
Fail
title Compléments aliment…1.12:14.5:1
#000000
#121214
Fail
a Ignorer et passer au…4.37:14.5:1
#000000
#727272
Fail
p Des avantages exclus…4.37:14.5:1
#000000
#727272
Fail
button Déjà membre4.37:14.5:1
#000000
#727272
Fail
button Je m'inscris3.56:14.5:1
#000000
#67645E
Fail
span Panier1.08:14.5:1
#000000
#0E0D0C
Fail
p Retour sur la boutiq…1.17:14.5:1
#000000
#171718
Fail
div Plus que1.14:14.5:1
#000000
#151412
Fail
span 50,00 €1.20:14.5:1
#000000
#1A1917
Fail
div restant pour la livr…21.00:14.5:1
#000000
#FFFFFF
Pass
span 50€21.00:14.5:1
#000000
#FFFFFF
Pass
span Livraison en point r…21.00:14.5:1
#000000
#FFFFFF
Pass
span 110€21.00:14.5:1
#000000
#FFFFFF
Pass
span Livraison à domicil…21.00:14.5:1
#000000
#FFFFFF
Pass
p Votre panier est vid…21.00:14.5:1
#000000
#FFFFFF
Pass
span Complétez votre pan…21.00:14.5:1
#000000
#FFFFFF
Pass
p Code promo et parrai…7.93:14.5:1
#000000
#9F9F9F
Pass
span Paiement sécurisé1.10:14.5:1
#000000
#10100E
Fail
span - 0,00€1.08:14.5:1
#000000
#0D0D0C
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 80/100 — 5 failing, 23 passed
REVIEW
80

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
Toutes les actualités et les nouveautés en avant-première div.newsletter-footer > div.newsletter-footer-newsletter > div.newsletter-footer-newsletter__content > p.newsletter-footer-newsletter__content-text
J'accepte de recevoir des offres et communications par email div > form#NewsletterForm--newsletter-footer > div.field > label
JE M'INSCRIS div.needsclick > div.needsclick > div.needsclick > button.needsclick

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.needsclick > div.needsclick > div.needsclick > img.needsclick div.needsclick > div.needsclick > div.needsclick > img.needsclick

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
header.header-mobile > div.header-mobile-bar > div.header-mobile-bar-cta > a.header__icon header.header-mobile > div.header-mobile-bar > div.header-mobile-bar-cta > a.header__icon
div#Swiper-template--19614745592137__5769f06b-d9ef-4f37-b564-3f71cdeab6eb > div#swiper-wrapper-c381b8437b543174 > div.swiper-slide > a.slide-link div#Swiper-template--19614745592137__5769f06b-d9ef-4f37-b564-3f71cdeab6eb > div#swiper-wrapper-c381b8437b543174 > div.swiper-slide > a.slide-link
div#Swiper-template--19614745592137__5769f06b-d9ef-4f37-b564-3f71cdeab6eb > div#swiper-wrapper-c381b8437b543174 > div.swiper-slide > a.slide-link div#Swiper-template--19614745592137__5769f06b-d9ef-4f37-b564-3f71cdeab6eb > div#swiper-wrapper-c381b8437b543174 > div.swiper-slide > a.slide-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.

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
Conditions générales de vente div.footer__container > div.footer__cgu > div.footer__cgu-entries > a.z-text
Politique de confidentialité div.footer__container > div.footer__cgu > div.footer__cgu-entries > a.z-text
Accessibilité : Non conforme div.footer__container > div.footer__cgu > div.footer__cgu-entries > a.z-text

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
Buttons have an accessible name
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
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
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
Document has a main landmark.
Deprecated ARIA roles were not used
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
`[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
`<frame>` or `<iframe>` elements have a title
Heading elements appear in a sequentially-descending order
`<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
Links are distinguishable without relying on color.
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
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+
Heading Hierarchy
3 headings
PASS
3 headings
Info::
Single H1 present
  • H1 Compléments alimentaires Nutrimuscle
  • H2 Les piliers de la sèche
  • H2 Au coeur de nos protéines
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback