Skip to content
https://romeronperfumes.com.au

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
6
REVIEW
6
PASS
12
INFO
0
Checks
24
12 PASS 6 REVIEW 6 FIX
D
Tap Target Adequacy
Action
13 tap target(s) too small or too close together
FIX
13 tap target(s) too small or too close together
Warning::
13 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.
F
Favicon & Branding
Action
No icons detected
FIX
No icons 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::
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ 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.
Got: rgb(0 0 0)
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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
5 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Heading Hierarchy
Action
43 headings, 3 skip(s)
REVIEW
43 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 ROMERON PERFUMES AUSTRALIA
  • H2 Inspired by Elegance. Designed to Last.
  • H4 SHOP PERFUMES skipped
  • H4 NICHE 100ml COLLECTION
  • H3 AMALIA - Marc Antoine Barrois Tilia
  • H3 IMPERIUM - Essential Parfums Bois Imperial
  • H3 MEGAMARINE - Orto Paris Megamare
  • H3 PARADIGME - Initio Paragon
  • H3 LOVE IN PARIS - Montale Rendez Vous Paris
  • H3 VERA - Lattafa Yara
  • H3 NEW YORK NIGHT - Bond 9 New York
  • H3 ILLUSION - Amouage Guidance
  • H3 AFFAIRE - Parfums de Marly Althaïr
  • H4 FEATURED PRODUCTS
  • H4 PHEROMONE
  • H3 Romeron Sexy Pheromone EDP 50ml
  • H3 Romeron Romance Pheromone EDP 50ml
  • H3 Romeron Aphrozy Pheromone EDP 50ml
  • H3 Romeron Sensual Pheromone EDP 50ml
  • H3 Romeron Passion Pheromone EDP 50ml
  • H3 Romeron Magic Pheromone EDP 50ml
  • H3 Romeron Amour Pheromone EDP 50ml
  • H3 Romeron Habibi Pheromone Eau de Parfum 50ml
  • H3 Niche EDP 100ml
  • H3 Niche Prive
  • H3 Exclusive Intense
  • H5 Explore Travel & Pen Signature Sizes skipped
  • H4 HAIR & BODY MIST
  • H3 PURE VANILLA HAIR AND BODY SPRAY 250ml
  • H3 DREAM GIRL HAIR AND BODY SPRAY 250ml
  • H3 PINK SEDUCTION HAIR AND BODY SPRAY 250ml
  • H3 MIDNIGHT SPELL HAIR AND BODY SPRAY 250ml
  • H3 ERBA LOVE HAIR AND BODY SPRAY 250ml
  • H3 Coco Dream Hair and Body Spray 250ml
  • H4 Fall in Love at First Scent
  • H5 DISCOVER ROMERON PERFUMES AUSTRALIA
  • H5 Experience the irresistible allure of ROMERON. Inspired by elegance and crafted to leave a lasting impression, our fragrances are designed to captivate from the very first spray. Luxury has never felt
  • H5 PLATIN COLLECTIONOur signature collection of fragrances inspired by iconic scents. Crafted with premium essences and a high fragrance concentration for impressive, long-lasting wear.
  • H5 NICHE COLLECTIONBold, distinctive and sophisticated. Our Niche Collection explores richer compositions and unique scent profiles for those who want something truly memorable.
  • H5 PHEROMONE COLLECTIONThe Art of Attraction. Exclusively curated with a unique fragrance formula, designed to captivate the senses, enhance your presence and leave an irresistible, lasting impression.
  • H3 About Us
  • H2 Search
  • H4 Products skipped

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

C
Alt Text Quality
Action
4 of 89 images have issues
REVIEW
4 of 89 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
6 decorative image(s) correctly marked
Info::
79 image(s) with good alt text
89 images 79 good alt text 6 decorative 4 missing
IssueCount
missing4 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
Mobile-Readable Font Sizes
Action
71% of visible text renders at >= 12 CSS px (10 below threshold)
REVIEW
71% of visible text renders at >= 12 CSS px (10 below threshold)
Warning::
10 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: <strong> 10.0px ("SHOP PERFUMES"); <strong> 10.0px ("NICHE 100ml COLLECTION"); <strong> 10.0px ("Luxury in every detail."); <p> 10.0px ("Our Niche Collection features sophistica..."); <strong> 10.0px ("high concentration of premium fragrance ...").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found – ROMERON PERFUMES AUSTRALIA ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Lighthouse Accessibility Audits
Score 83/100 — 5 failing, 25 passed
REVIEW
83

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
IMPERIUM - Essential Parfums Bois Imperial slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide
MEGAMARINE - Orto Paris Megamare slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide
PARADIGME - Initio Paragon slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide
LOVE IN PARIS - Montale Rendez Vous Paris slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide
VERA - Lattafa Yara slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide
NEW YORK NIGHT - Bond 9 New York slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide
ILLUSION - Amouage Guidance slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide
AFFAIRE - Parfums de Marly Althaïr slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide
Room Sprays slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide
Hanging Car Fragrances slideshow-component.resource-list__carousel > slideshow-container > slideshow-slides > slideshow-slide.resource-list__slide

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.

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
SHOP PERFUMES div.group-block > div.group-block-content > div.spacing-style > h4
Explore Travel & Pen Signature Sizes div.border-style > div.spacing-style > div.spacing-style > h5

These are opportunities to improve keyboard navigation in your application.

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.media-block > deferred-media.media-block__media > video > img div.media-block > deferred-media.media-block__media > video > img
div.media-block > deferred-media.media-block__media > video > img div.media-block > deferred-media.media-block__media > video > img

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.section > div.border-style > div.spacing-style > a.image-block div.section > div.border-style > div.spacing-style > a.image-block
div.section > div.border-style > div.spacing-style > a.image-block div.section > div.border-style > div.spacing-style > a.image-block
div.section > div.border-style > div.spacing-style > a.image-block div.section > div.border-style > div.spacing-style > a.image-block
div.section > div.border-style > div.spacing-style > a.image-block div.section > div.border-style > div.spacing-style > a.image-block

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
nav.details-content > ul.list-unstyled > li.menu__item > a nav.details-content > ul.list-unstyled > li.menu__item > a
nav.details-content > ul.list-unstyled > li.menu__item > a nav.details-content > ul.list-unstyled > li.menu__item > a
nav.details-content > ul.list-unstyled > li.menu__item > a nav.details-content > ul.list-unstyled > li.menu__item > a
nav.details-content > ul.list-unstyled > li.menu__item > a nav.details-content > ul.list-unstyled > li.menu__item > a
nav.details-content > ul.list-unstyled > li.menu__item > a nav.details-content > ul.list-unstyled > li.menu__item > a
nav.details-content > ul.list-unstyled > li.menu__item > a nav.details-content > ul.list-unstyled > li.menu__item > a
nav.details-content > ul.list-unstyled > li.menu__item > a nav.details-content > ul.list-unstyled > li.menu__item > a
nav.details-content > ul.list-unstyled > li.menu__item > a nav.details-content > ul.list-unstyled > li.menu__item > a
nav.details-content > ul.list-unstyled > li.menu__item > a nav.details-content > ul.list-unstyled > li.menu__item > a
nav.details-content > ul.list-unstyled > li.menu__item > a nav.details-content > ul.list-unstyled > li.menu__item > a
nav.details-content > ul.list-unstyled > li.menu__item > a nav.details-content > ul.list-unstyled > li.menu__item > a
nav.details-content > ul.list-unstyled > li.menu__item > a nav.details-content > ul.list-unstyled > li.menu__item > a
nav.details-content > ul.list-unstyled > li.menu__item > a nav.details-content > ul.list-unstyled > li.menu__item > a

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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[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
●`[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 use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[role]`s 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
○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.
○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
○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.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Landmark Structure
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
3 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary" SEARCH MAIN ASIDE 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

A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
3 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: - H5: 200 chars - H5: 182 chars - H5: 174 chars
Got: 3 >120-char heading(s)
Info::
6 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: 6 all-caps heading(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#EmailInput-ATk1jNzh0ZlRxSXNQa__email_signup_TCQELNemailEmailfor/id
#cmdk-inputsearchSearchfor/id
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+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
31 explicit tabindex attribute(s) checked, no anti-patterns
PASS
31 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://romeronperfumes.com.au/web-pixels@979a3e2fw137e9400p4daec9d4mf64d2306/c…")
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+
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.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 ROMERON PERFUMES AUS…7.28:13.0:1
#000000
#989898
Pass
h2 Search17.64:13.0:1
#000000
#EDEBE7
Pass
h3 AMALIA - Marc Antoin…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 IMPERIUM - Essential…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 MEGAMARINE - Orto Pa…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 PARADIGME - Initio P…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 LOVE IN PARIS - Mont…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 VERA - Lattafa Yara17.64:13.0:1
#000000
#EDEBE7
Pass
h3 NEW YORK NIGHT - Bon…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 ILLUSION - Amouage G…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 AFFAIRE - Parfums de…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 Romeron Sexy Pheromo…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 Romeron Romance Pher…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 Romeron Aphrozy Pher…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 Romeron Sensual Pher…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 Romeron Passion Pher…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 Romeron Magic Pherom…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 Romeron Amour Pherom…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 Romeron Habibi Phero…17.64:13.0:1
#000000
#EDEBE7
Pass
h3 Niche EDP 100ml17.64:13.0:1
#000000
#EDEBE7
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback