Skip to content
https://loreal.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
3
REVIEW
6
PASS
4
INFO
0
Checks
13
4 PASS 6 REVIEW 3 FIX
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: #3d3d3d
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::
3 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 3 <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.
B
Landmark Structure
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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 L'Oréal Groupe ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
10 icon(s) detected
REVIEW
10 icon(s) detected
Info::
favicon.ico present at site root
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'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 16 fail WCAG AA
REVIEW

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

4 pass 16 fail WCAG AA
title L’Oréal, world leader in beauty : mak…
2.27:1
#000000
on
#4A4742
needs 4.5:1 (normal text)
16px · top of page (header area)
span Go to Content
4.30:1
#000000
on
#737169
needs 4.5:1 (normal text)
16px · top of page (header area)
span Go To Footer
4.44:1
#000000
on
#76736C
needs 4.5:1 (normal text)
16px · top of page (header area)
span Main Navigation Menu
1.74:1
#000000
on
#3B3532
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Group
1.18:1
#000000
on
#1D1614
needs 4.5:1 (normal text)
16px · above the fold
button back
1.16:1
#000000
on
#1E130F
needs 4.5:1 (normal text)
16px · above the fold
p Group
1.48:1
#000000
on
#39271E
needs 4.5:1 (normal text)
16px · above the fold
a Who We Are
1.72:1
#000000
on
#532B14
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Our purpose
2.22:1
#000000
on
#6B3916
needs 4.5:1 (normal text)
16px · above the fold
button Our purpose
2.96:1
#000000
on
#66554A
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
button back
3.58:1
#000000
on
#69645D
needs 4.5:1 (normal text)
16px · above the fold
p Our purpose
3.52:1
#000000
on
#67635D
needs 4.5:1 (normal text)
16px · above the fold
a Our purpose
3.21:1
#000000
on
#615D57
needs 4.5:1 (normal text)
16px · above the fold
a Essentiality of Beauty
2.92:1
#000000
on
#5B5750
needs 4.5:1 (normal text)
16px · mid-page
a Strategy & Model
2.57:1
#000000
on
#524F49
needs 4.5:1 (normal text)
16px · mid-page
a Quality & Safety Standards
2.28:1
#000000
on
#4B4742
needs 4.5:1 (normal text)
16px · mid-page

3 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
h1 Life Is Too Short Fo…5.24:13.0:1
#000000
#7F7F7F
Pass
h1 Essentiality of Beau…5.24:13.0:1
#000000
#7F7F7F
Pass
h1 First Quarter 2026 S…5.24:13.0:1
#000000
#7F7F7F
Pass
h1 L’Oréal completes…5.24:13.0:1
#000000
#7F7F7F
Pass
title L’Oréal, world le…2.27:14.5:1
#000000
#4A4742
Fail
span Go to Content4.30:14.5:1
#000000
#737169
Fail
span Go To Footer4.44:14.5:1
#000000
#76736C
Fail
span Main Navigation Menu1.74:14.5:1
#000000
#3B3532
Fail
a Group1.18:14.5:1
#000000
#1D1614
Fail
button back1.16:14.5:1
#000000
#1E130F
Fail
p Group1.48:14.5:1
#000000
#39271E
Fail
a Who We Are1.72:14.5:1
#000000
#532B14
Fail
a Our purpose2.22:14.5:1
#000000
#6B3916
Fail
button Our purpose2.96:14.5:1
#000000
#66554A
Fail
button back3.58:14.5:1
#000000
#69645D
Fail
p Our purpose3.52:14.5:1
#000000
#67635D
Fail
a Our purpose3.21:14.5:1
#000000
#615D57
Fail
a Essentiality of Beau…2.92:14.5:1
#000000
#5B5750
Fail
a Strategy & Model2.57:14.5:1
#000000
#524F49
Fail
a Quality & Safety Sta…2.28:14.5:1
#000000
#4B4742
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 89/100 — 4 failing, 25 passed
REVIEW
89

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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.search-box > div.container--small > div.search-box__bottom > input#site-search section.search-box > div.container--small > div.search-box__bottom > input#site-search

These are opportunities to improve the usage of ARIA in your application which 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
Cookie settings footer.footer__legal > ul.footer__policy > li.footer__item > a
Term of use footer.footer__legal > ul.footer__policy > li.footer__item > a
Privacy Policy footer.footer__legal > ul.footer__policy > li.footer__item > a
Our Policies around the World footer.footer__legal > ul.footer__policy > li.footer__item > a
Accessibility assessment div.footer > div.footer__bottom > footer.footer__legal > a.footer__accessibility

These are opportunities to improve the legibility of your content.

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
Go to slide 1 div.hero-carousel__controls > ul.hero-carousel__dots > li > button.hero-carousel__dot
Go to slide 2 div.hero-carousel__controls > ul.hero-carousel__dots > li > button.hero-carousel__dot
Go to slide 3 div.hero-carousel__controls > ul.hero-carousel__dots > li > button.hero-carousel__dot
Go to slide 4 div.hero-carousel__controls > ul.hero-carousel__dots > li > button.hero-carousel__dot

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
Privacy Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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 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.
●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
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[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.
○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.
○`<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.
○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
5 headings
PASS
5 headings
Warning::
Multiple H1 headings (4 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Life Is Too Short For a Boring Career
  • H1 Essentiality of Beauty duplicate H1
  • H1 First Quarter 2026 Sales duplicate H1
  • H1 L’Oréal completes the acquisition of Kering Beauté... duplicate H1
  • H2 Discover Our beautiful stories

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

A+
Alt Text Quality
All 59 images OK
PASS
All 59 images OK
Info::
52 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
59 images 7 good alt text 52 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#anim-onradioActivatefor/id
#anim-offradioDeactivatefor/id
#contrast-offradioDeactivatefor/id
#contrast-onradioActivatefor/id
#lang-selectorselectLanguage Switcherfor/id
#site-searchsearchFind out more about L'Oréalfor/id
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: L'Oréal
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name L'Oréal ✓192×192 icon ✓512×512 icon ✓Start URL /?utm_source=webapp ✓Display Mode standalone ✓
Name L'Oréal Display Mode standalone Theme Color #eae6e1 Background Color #eae6e1 Icons 8 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback