Skip to content
https://ernewyork1.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
5
REVIEW
9
PASS
10
INFO
0
Checks
24
10 PASS 9 REVIEW 5 FIX
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.
Got: rgba(0, 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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 4 <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
13 landmarks
REVIEW
13 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV 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

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

C
Heading Hierarchy
Action
28 headings, 1 skip(s)
REVIEW
28 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Country/Region
  • H2 Country/Region
  • H2 VISTE CON INTENCIÓN
  • H2 PRENDAS QUE ELEVAN TU DÍA
  • H4 LOS MÁS VENDIDOS skipped
  • H3 Polo Texturizado
  • H3 Pantalon sastre regulador
  • H3 Pantalón Catania
  • H3 Camisa seda Mate
  • H4 LOS MÁS VENDIDOS
  • H3 Polo Texturizado
  • H3 Pantalon sastre regulador
  • H3 Pantalón Catania
  • H3 Camisa seda Mate
  • H4 NUESTROS FAVORITOS
  • H3 Bolso
  • H3 Camisa seda Mate
  • H3 Pantalón Catania
  • H3 Pantalon sastre regulador
  • H3 Polo Texturizado
  • H3 ENVÍO RAPIDO
  • H3 COMPRA SEGURA
  • H3 CALIDAD PREMIUM
  • H3 ESTILO UNICO
  • H3 ENVÍO RAPIDO
  • H3 COMPRA SEGURA
  • H3 CALIDAD PREMIUM
  • H3 ESTILO UNICO

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

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

B
Alt Text Quality
2 of 73 images have issues
REVIEW
2 of 73 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
19 decorative image(s) correctly marked
Info::
52 image(s) with good alt text
73 images 52 good alt text 19 decorative 2 missing
IssueCount
missing2 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
Form Accessibility
Action
8 of 36 controls have issues
REVIEW
8 of 36 controls have issues
Critical::
8 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="idGlobo">; <select name="idGlobo">; <select name="idGlobo">; <select name="idGlobo">; <select name="idGlobo">; <select name="idGlobo">; <select name="idGlobo">; <select name="idGlobo">
Info::
28 control(s) properly labeled
36 controls
28 labeled
0 placeholder only
8 unlabeled
ControlTypeLabelMethod
#swatch-collection-51397496013095-1-0-0radioNegroNegrofor/id
#swatch-collection-51397496111399-1-0-0radioBlancoBlancofor/id
#swatch-collection-51397496209703-1-0-0radioAzulAzulfor/id
#swatch-collection-51397495193895-1-0-1radioNegroNegrofor/id
#swatch-collection-51397495324967-1-0-1radioPlomo plataPlomo platafor/id
#swatch-collection-51397495456039-1-0-1radioBeigeBeigefor/id
#swatch-collection-51397494800679-1-0-2radioNegroNegrofor/id
#swatch-collection-51397494898983-1-0-2radioPlomo plataPlomo platafor/id
#swatch-collection-51397494997287-1-0-2radioAzulAzulfor/id
#swatch-collection-51397495095591-1-0-2radioBeigeBeigefor/id
#swatch-collection-51397496308007-1-0-3radioNegroNegrofor/id
#swatch-collection-51397496439079-1-0-3radioAzulAzulfor/id
#swatch-collection-51397496570151-1-0-3radioBlancoBlancofor/id
#swatch-collection-51397496013095-1-0-4radioNegroNegrofor/id
#swatch-collection-51397496111399-1-0-4radioBlancoBlancofor/id
#swatch-collection-51397496209703-1-0-4radioAzulAzulfor/id
#swatch-collection-51397495193895-1-0-5radioNegroNegrofor/id
#swatch-collection-51397495324967-1-0-5radioPlomo plataPlomo platafor/id
#swatch-collection-51397495456039-1-0-5radioBeigeBeigefor/id
#swatch-collection-51397494800679-1-0-6radioNegroNegrofor/id
#swatch-collection-51397494898983-1-0-6radioPlomo plataPlomo platafor/id
#swatch-collection-51397494997287-1-0-6radioAzulAzulfor/id
#swatch-collection-51397495095591-1-0-6radioBeigeBeigefor/id
#swatch-collection-51397496308007-1-0-7radioNegroNegrofor/id
#swatch-collection-51397496439079-1-0-7radioAzulAzulfor/id
#swatch-collection-51397496570151-1-0-7radioBlancoBlancofor/id
#EmailInput-AQzl5M1B4UUxUaUwyc__email_signup_VzJYbkemailCorreo electrónicofor/id
#cmdk-inputsearchBuscarfor/id
idGloboselect(none)none
idGloboselect(none)none
idGloboselect(none)none
idGloboselect(none)none
idGloboselect(none)none
idGloboselect(none)none
idGloboselect(none)none
idGloboselect(none)none

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

<select name="idGlobo">; <select name="idGlobo">; <select name="idGlobo">; <select name="idGlobo">; <select name="idGlobo">; <select name="idGlobo">; <select name="idGlobo">; <select name="idGlobo">

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

B
Tap Target Adequacy
3 tap target(s) too small or too close together
REVIEW
3 tap target(s) too small or too close together
Info::
3 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
Mobile-Readable Font Sizes
93% of visible text renders at >= 12 CSS px (1 below threshold)
REVIEW
93% of visible text renders at >= 12 CSS px (1 below threshold)
Info::
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: <span> 10.0px ("Total de artículos en el carrito: 0").
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 No encontrado – E|R NEW YORK X 365 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Lighthouse Accessibility Audits
Score 80/100 — 5 failing, 24 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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 slideshow-controls > ol.slideshow-controls__dots > li > button.slideshow-control
2 slideshow-controls > ol.slideshow-controls__dots > li > button.slideshow-control
3 slideshow-controls > ol.slideshow-controls__dots > li > button.slideshow-control

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
div.email-signup-block > form#contact_form > div.email-signup__input-group > input#EmailInput-AQzl5M1B4UUxUaUwyc__email_signup_VzJYbk div.email-signup-block > form#contact_form > div.email-signup__input-group > input#EmailInput-AQzl5M1B4UUxUaUwyc__email_signup_VzJYbk

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
slideshow-slide > div.slide__image-container > video.slide__video > img slideshow-slide > div.slide__image-container > video.slide__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.header__row > div.header__columns > div.header__column > a.size-style div.header__row > div.header__columns > div.header__column > a.size-style
div.swiper > div#swiper-wrapper-1014911e19ae278ea > div.circle-item-template--26611732578599__ss_circle_menu_Y7mhin > a.circle-icon-template--26611732578599__ss_circle_menu_Y7mhin div.swiper > div#swiper-wrapper-1014911e19ae278ea > div.circle-item-template--26611732578599__ss_circle_menu_Y7mhin > a.circle-icon-template--26611732578599__ss_circle_menu_Y7mhin
div.swiper > div#swiper-wrapper-1014911e19ae278ea > div.circle-item-template--26611732578599__ss_circle_menu_Y7mhin > a.circle-icon-template--26611732578599__ss_circle_menu_Y7mhin div.swiper > div#swiper-wrapper-1014911e19ae278ea > div.circle-item-template--26611732578599__ss_circle_menu_Y7mhin > a.circle-icon-template--26611732578599__ss_circle_menu_Y7mhin
div.group-block > div.group-block-content > div#shopify-block-AenpxTWRUWVB2bFRLc__icon_AbLUWX > a.text-inherit div.group-block > div.group-block-content > div#shopify-block-AenpxTWRUWVB2bFRLc__icon_AbLUWX > a.text-inherit
div.group-block > div.group-block-content > div#shopify-block-Ac1lKcFBGMlgwbUdId__icon_4DDjLt > a.text-inherit div.group-block > div.group-block-content > div#shopify-block-Ac1lKcFBGMlgwbUdId__icon_4DDjLt > a.text-inherit
div.group-block > div.group-block-content > div#shopify-block-Ac2JHQjZFL3lwbUUyT__icon_6QhL6f > a.text-inherit div.group-block > div.group-block-content > div#shopify-block-Ac2JHQjZFL3lwbUUyT__icon_6QhL6f > a.text-inherit
div > div.ss-isntafeed-img-wrapper > div.ss-gallery_all-item > a div > div.ss-isntafeed-img-wrapper > div.ss-gallery_all-item > a
div > div.ss-isntafeed-img-wrapper > div.ss-gallery_all-item > a div > div.ss-isntafeed-img-wrapper > div.ss-gallery_all-item > a
div > div.ss-isntafeed-img-wrapper > div.ss-gallery_all-item > a div > div.ss-isntafeed-img-wrapper > div.ss-gallery_all-item > a
div > div.ss-isntafeed-img-wrapper > div.ss-gallery_all-item > a div > div.ss-isntafeed-img-wrapper > div.ss-gallery_all-item > a

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
1 slideshow-controls > ol.slideshow-controls__dots > li > button.slideshow-control
2 slideshow-controls > ol.slideshow-controls__dots > li > button.slideshow-control
3 slideshow-controls > ol.slideshow-controls__dots > li > button.slideshow-control

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-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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[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
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○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
○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.
○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 Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
13 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: 13 all-caps heading(s)
A+
Form Input Types
36 form control(s) checked, no type mismatches
PASS
36 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
36 form control(s) checked, no input-semantic issues
PASS
36 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 "es"
PASS
Lang attribute set to "es"
Info::
<html lang="es"> is set and valid
Got: es
A+
Tabindex Anti-Patterns
36 explicit tabindex attribute(s) checked, no anti-patterns
PASS
36 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://ernewyork1.com/web-pixels@a6b9c454w7b023680pb7fefabem62184d01/custom/we…")
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
h2 Country/Region21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Country/Region21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Polo Texturizado21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pantalon sastre regu…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pantalón Catania21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Camisa seda Mate21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Polo Texturizado21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pantalon sastre regu…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pantalón Catania21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Camisa seda Mate21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bolso21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Camisa seda Mate21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pantalón Catania21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pantalon sastre regu…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Polo Texturizado21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ENVÍO RAPIDO21.00:13.0:1
#000000
#FFFFFF
Pass
h3 COMPRA SEGURA21.00:13.0:1
#000000
#FFFFFF
Pass
h3 CALIDAD PREMIUM21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ESTILO UNICO21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ENVÍO RAPIDO21.00:13.0:1
#000000
#FFFFFF
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