Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 4 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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

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.

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.

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

17 landmarks

REVIEW

17 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

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

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

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 No encontrado – Esstelar ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA

h2 País/región

1.96:1

#000000

#433D34

needs 3.0:1 (large text)

24px · bottom of viewport

h2 País/región

1.96:1

#000000

#433D34

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Artículo agregado a tu carrito

1.96:1

#000000

#433D34

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Preguntas frecuentes

1.96:1

#000000

#433D34

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Suscríbete para recibir notis esstelar …

1.96:1

#000000

#433D34

needs 3.0:1 (large text)

24px · bottom of viewport

h2 País/región

1.96:1

#000000

#433D34

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Cuándo llega mi pedido?

1.96:1

#000000

#433D34

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Hacen envíos internacionales?

1.96:1

#000000

#433D34

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Donde esta mi guia de envio?

1.96:1

#000000

#433D34

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Hay descuentos o hacen pedidos a mayoreo…

1.96:1

#000000

#433D34

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Hacen personalizados?

1.96:1

#000000

#433D34

needs 3.0:1 (large text)

19px · bottom of viewport

title Esstelar

1.06:1

#000000

#0B090A

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Ir directamente al contenido

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span slow fashion hecho especialmente para ti…

1.05:1

#000000

#080808

needs 4.5:1 (normal text)

16px · top of page (header area)

a YOYOSIE X ESSTELAR

4.01:1

#000000

#DA0607

needs 4.5:1 (normal text)

16px · above the fold

a accesorios

4.01:1

#000000

#DA0607

needs 4.5:1 (normal text)

16px · above the fold

summary T-shirt´s

4.01:1

#000000

#DA0607

needs 4.5:1 (normal text)

16px · above the fold

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)

Element	Ratio	Required	FG	BG	Result
h2 País/región	1.96:1	3.0:1	#000000	#433D34	Fail
h2 País/región	1.96:1	3.0:1	#000000	#433D34	Fail
h2 Artículo agregado a…	1.96:1	3.0:1	#000000	#433D34	Fail
h2 Preguntas frecuentes	1.96:1	3.0:1	#000000	#433D34	Fail
h2 Suscríbete para rec…	1.96:1	3.0:1	#000000	#433D34	Fail
h2 País/región	1.96:1	3.0:1	#000000	#433D34	Fail
h3 Cuándo llega mi ped…	1.96:1	3.0:1	#000000	#433D34	Fail
h3 Hacen envíos intern…	1.96:1	3.0:1	#000000	#433D34	Fail
h3 Donde esta mi guia d…	1.96:1	3.0:1	#000000	#433D34	Fail
h3 Hay descuentos o hac…	1.96:1	3.0:1	#000000	#433D34	Fail
h3 Hacen personalizados…	1.96:1	3.0:1	#000000	#433D34	Fail
title Esstelar	1.06:1	4.5:1	#000000	#0B090A	Fail
a Ir directamente al c…	1.00:1	4.5:1	#000000	#000000	Fail
span slow fashion hecho e…	1.05:1	4.5:1	#000000	#080808	Fail
span Paga a MSI y aprovec…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span +de 1000 pedidos ent…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Inicio	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a YOYOSIE X ESSTELAR	4.01:1	4.5:1	#000000	#DA0607	Fail
a accesorios	4.01:1	4.5:1	#000000	#DA0607	Fail
summary T-shirt´s	4.01:1	4.5:1	#000000	#DA0607	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.

Lighthouse Accessibility Audits

Score 87/100 — 4 failing, 28 passed

REVIEW

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

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
¡¡10% EN TU PRIMERA COMPRA!! <3 VÁLIDO SI ES TU PRIMERA VEZ COMPRANDO AQUÍ No… `div#app-embed > div._container_3eyaa_70 > div#form-container-ref > section._overlay_1q1d2_100`

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
Se ve igual que en las fotos 😭 `div.swiper-slide > div.AirReviews-Carousel__Card > div.AirReviews-Carousel__CardContent > div.AirReviews-Pop__Content`
Valentina `div.AirReviews-Blocks__ReviewDetails--AuthorBlock > div.AirReviews-Blocks__AuthorNameContainer > div.AirReviews-Blocks__AuthorRight > span.AirReviews-Blocks__AuthorName`
02/26/2026 `div.AirReviews-Blocks__ReviewDetails--AuthorBlock > div.AirReviews-Blocks__AuthorNameContainer > div.AirReviews-Blocks__Carousel--BadgeAndDate > div.AirReviews-Blocks__Date`
El diseño está demasiado cool y envian a todo méxico ;) `div.swiper-slide > div.AirReviews-Carousel__Card > div.AirReviews-Carousel__CardContent > div.AirReviews-Pop__Content`
Alex `div.AirReviews-Blocks__ReviewDetails--AuthorBlock > div.AirReviews-Blocks__AuthorNameContainer > div.AirReviews-Blocks__AuthorRight > span.AirReviews-Blocks__AuthorName`
02/20/2026 `div.AirReviews-Blocks__ReviewDetails--AuthorBlock > div.AirReviews-Blocks__AuthorNameContainer > div.AirReviews-Blocks__Carousel--BadgeAndDate > div.AirReviews-Blocks__Date`
Didn’t expect the quality to be this good tbh. The print looks sick and the fit… `div.swiper-slide > div.AirReviews-Carousel__Card > div.AirReviews-Carousel__CardContent > div.AirReviews-Pop__Content`
See more `div.swiper-slide > div.AirReviews-Carousel__Card > div.AirReviews-Carousel__CardContent > div.AirReviews-Pop__Content--SeeMore`
Suscríbete para recibir notis esstelar .𖥔 ݁ ˖๋ ࣭ ⭑⠀xoxo⠀⠀ ⠀⠀ ⠀⠀ ⠀⠀ ⠀⠀ ⠀⠀ ⠀⠀ `div.footer__content-top > div.footer-block--newsletter > div.footer-block__newsletter > h2.footer-block__heading`
form#ContactFooter > div.newsletter-form__field-wrapper > div.field > input#NewsletterForm--sections--17162018750573__footer `form#ContactFooter > div.newsletter-form__field-wrapper > div.field > input#NewsletterForm--sections--17162018750573__footer`
Correo electrónico `form#ContactFooter > div.newsletter-form__field-wrapper > div.field > label.field__label`
Nombre `div._gridItem_1q1d2_172 > form._formFieldset_48bzm_110 > div._formFieldContainer_1mxsl_5 > label#label-first_name`
Correo electrónico `div._gridItem_1q1d2_172 > form._formFieldset_48bzm_110 > div._formFieldContainer_1mxsl_5 > label#label-email`

These are opportunities to improve the legibility of your content.

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
AKRIILA! `div.card > div.card__content > div.card__information > h3#title-template--17162018291821__featured_collection_MHqkTg-8242652414061`

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.video-section > div.video-section__media > video > img `div.video-section > div.video-section__media > video > 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.

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

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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

●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

○`[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

○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

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

○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

45 headings

PASS

45 headings

Single H1 present

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 País/región
H1 (empty)
H2 País/región
H2 Artículo agregado a tu carrito
H3 AKRIILA!
H3 AKRIILA!
H3 AKRIILA!
H3 AKRIILA!
H3 AKRIILA!
H3 AKRIILA!
H3 AKRIILA!
H3 AKRIILA!
H3 NSQK!
H3 NSQK!
H3 ROSALIA!
H3 ROSALIA!
H3 Amarte duele
H3 Amarte duele
H3 IZA TKM
H3 IZA TKM
H3 Gael y Diego!
H3 Gael y Diego!
H3 windows!
H3 windows!
H3 Catr7el y paco!
H3 Catr7el y paco!
H3 music!
H3 music!
H3 bikini yoyosie!
H3 bikini yoyosie!
H3 yoyosie top!
H3 yoyosie top!
H3 mini shorts!
H3 mini shorts!
H3 yoyosie top!
H3 yoyosie top!
H2 Preguntas frecuentes
H3 Cuándo llega mi pedido?
H3 Hacen envíos internacionales?
H3 Donde esta mi guia de envio?
H3 Hay descuentos o hacen pedidos a mayoreo?
H3 Hacen personalizados?
H2 Información Útil
H2 Suscríbete para recibir notis esstelar .𖥔 ݁ ˖๋ ࣭ ⭑⠀xoxo⠀⠀ ⠀⠀ ⠀⠀ ⠀⠀ ⠀⠀ ⠀⠀ ⠀⠀
H2 País/región

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

14 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: 14 all-caps heading(s)

Alt Text Quality

1 of 106 images have issues

PASS

1 of 106 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

8 decorative image(s) correctly marked

97 image(s) with good alt text

106 images 97 good alt text 8 decorative 1 missing

Issue	Count
missing	1 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

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
#country-filter-input	search	Buscar	for/id
#country-filter-input	search	Buscar	for/id
#Search-In-Modal	search	Búsqueda	for/id
#NewsletterForm--sections--17162018750573__footer	email	Correo electrónico	for/id
#country-filter-input	search	Buscar	for/id

A+

Link & Button Quality

214 links, 31 buttons — all OK

PASS

214 links, 31 buttons — all OK

214 link(s) with descriptive text

214 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

245 links and buttons have descriptive text

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

5 form control(s) checked, no input-semantic issues

PASS

5 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

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

Got: es

A+

Tabindex Anti-Patterns

163 explicit tabindex attribute(s) checked, no anti-patterns

PASS

163 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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+

Mobile-Readable Font Sizes

All 4 visible text node(s) render at >= 12 CSS pixels

PASS

All 4 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

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

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