Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 6 REVIEW 6 FIX

Heading Hierarchy

Action

3 headings, 1 skip(s)

FIX

3 headings, 1 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

2 empty heading(s)

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

H3 Pesquisar e Encontrar
H6 (empty)
H6 (empty)

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

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

404 Error Page

Action

HTTP 429, bare page

FIX

HTTP 429, bare page

Unexpected status code: HTTP 429

Expected HTTP 404 but received 429. This may confuse search engine crawlers.

Got: HTTP 429

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 429 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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

No dark mode signals

FIX

No dark mode signals

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 ModeNo Dark Mode Detected

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 ✗

Landmark Structure

6 landmarks

REVIEW

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) landmark

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.

Search landmark present

Page Structure — as a screen reader sees it

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

Alt Text Quality

Action

3 of 79 images have issues

REVIEW

3 of 79 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

7 image(s) with alt text over 125 characters

19 decorative image(s) correctly marked

50 image(s) with good alt text

79 images 50 good alt text 19 decorative 3 missing

Issue	Count
missing	3 image(s)
too long	7 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

Link & Button Quality

Action

8 issue(s) across 96 links and 22 buttons

REVIEW

8 issue(s) across 96 links and 22 buttons

8 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a.S-product-card__img-container (#810 on page); a.S-product-card__img-container (#833 on page); a.S-product-card__img-container (#862 on page); a.S-product-card__img-container (#885 on page); a.S-product-card__img-container (#914 on page); a.S-product-card__img-container (#937 on page); a.S-product-card__img-container (#976 on page); a.S-product-card__img-container (#999 on page)

2 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: /Privacy-Security-Policy-a-282.html; /Privacy-Security-Policy-a-282.html

86 link(s) with descriptive text

96 links

8 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
/Privacy-Security-Policy-a-282.html	Mais informações	new tab	Add '(opens in new tab)' to text
/Privacy-Security-Policy-a-282.html	Política de Privacidade	new tab	Add '(opens in new tab)' to text

108 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a.S-product-card__img-container (#810 on page); a.S-product-card__img-container (#833 on page); a.S-product-card__img-container (#862 on page); a.S-product-card__img-container (#885 on page); a.S-product-card__img-container (#914 on page); a.S-product-card__img-container (#937 on page); a.S-product-card__img-container (#976 on page); a.S-product-card__img-container (#999 on page)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

/Privacy-Security-Policy-a-282.html; /Privacy-Security-Policy-a-282.html

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 15 fail WCAG AA

REVIEW

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

5 pass 15 fail WCAG AA 1 pass AA only

title Moda feminina | Roupas, Sapatos e Acess�…

3.45:1

#000000

#65625C

needs 4.5:1 (normal text)

16px · top of page (header area)

div VENDA NA SHEIN

1.41:1

#000000

#282725

needs 4.5:1 (normal text)

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

div FRETE GRÁTIS

1.39:1

#000000

#262626

needs 4.5:1 (normal text)

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

div DEVOLUÇÃO GRÁTIS

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

div SHEIN NA REMESSA CONFORME

1.87:1

#000000

#3B3B3B

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span Shein Mod

3.44:1

#000000

#626262

needs 4.5:1 (normal text)

16px · above the fold

span Use up and down arrow keys to navigate s…

3.44:1

#000000

#626262

needs 4.5:1 (normal text)

16px · above the fold

span #SHEINMothersday

3.44:1

#000000

#626262

needs 4.5:1 (normal text)

16px · above the fold

span SHEINxTata&Beatriz

3.44:1

#000000

#626262

needs 4.5:1 (normal text)

16px · above the fold

span Shein Mod

1.58:1

#9462FF

#626262

needs 4.5:1 (normal text)

16px · above the fold

span Vestido

3.44:1

#000000

#626262

needs 4.5:1 (normal text)

16px · above the fold

span Motf

1.58:1

#9462FF

#626262

needs 4.5:1 (normal text)

16px · above the fold

span Romwe Men

1.58:1

#9462FF

#626262

needs 4.5:1 (normal text)

16px · mid-page

span Saia

3.44:1

#000000

#626262

needs 4.5:1 (normal text)

16px · mid-page

span Calça

3.14:1

#000000

#5C5C5C

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)

Element	Ratio	Required	FG	BG	Result
h3 Pesquisar e Encontra…	3.44:1	3.0:1	#000000	#626262	Pass
title Moda feminina \| Roup…	3.45:1	4.5:1	#000000	#65625C	Fail
div VENDA NA SHEIN	1.41:1	4.5:1	#000000	#282725	Fail
div FRETE GRÁTIS	1.39:1	4.5:1	#000000	#262626	Fail
div DEVOLUÇÃO GRÁTIS	1.00:1	4.5:1	#000000	#000000	Fail
div SHEIN NA REMESSA CON…	1.87:1	4.5:1	#000000	#3B3B3B	Fail
span Shein Mod	3.44:1	4.5:1	#000000	#626262	Fail
span Use up and down arro…	3.44:1	4.5:1	#000000	#626262	Fail
span #SHEINMothersday	3.44:1	4.5:1	#000000	#626262	Fail
span SHEINxTata&Beatriz	3.44:1	4.5:1	#000000	#626262	Fail
span Shein Mod	1.58:1	4.5:1	#9462FF	#626262	Fail
span Vestido	3.44:1	4.5:1	#000000	#626262	Fail
span Motf	1.58:1	4.5:1	#9462FF	#626262	Fail
span Romwe Men	1.58:1	4.5:1	#9462FF	#626262	Fail
span Saia	3.44:1	4.5:1	#000000	#626262	Fail
span Calça	3.14:1	4.5:1	#000000	#5C5C5C	Fail
span Conjunto Feminino	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Bolsa	21.00:1	4.5:1	#000000	#FFFFFF	Pass
em Cadastrar-se / Regis…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
em Meus Pedidos	21.00:1	4.5: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.

Lighthouse Accessibility Audits

Score 81/100 — 5 failing, 25 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
Ofertas especiais só para você Novo Usuário 55%OFF Sem gasto min.！ Cupom ger… `div.popup-dialog > div.sui-dialog > div.sui-dialog__ctn > div.sui-dialog__wrapper`

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
R$203,25 `div.immersiveBanner-products-container > div.immersiveBanner-products-container__product-item > div.product-card > div.bff-price-container`
R$152,27 `div.immersiveBanner-products-container > div.immersiveBanner-products-container__product-item > div.product-card > div.bff-price-container`
R$32,25 `div.immersiveBanner-products-container > div.immersiveBanner-products-container__product-item > div.product-card > div.bff-price-container`
R$28,45 `div.immersiveBanner-products-container > div.immersiveBanner-products-container__product-item > div.product-card > div.bff-price-container`
R$64,90 `div.immersiveBanner-products-container > div.immersiveBanner-products-container__product-item > div.product-card > div.bff-price-container`
R$77,00 `div.immersiveBanner-products-container > div.immersiveBanner-products-container__product-item > div.product-card > div.bff-price-container`
R$78,80 `div.immersiveBanner-products-container > div.immersiveBanner-products-container__product-item > div.product-card > div.bff-price-container`
R$79,75 `div.immersiveBanner-products-container > div.immersiveBanner-products-container__product-item > div.product-card > div.bff-price-container`
R$37,90 `div.scroll-snap-wrapper > div.single-container__swiper_slide > div.product-card > div.bff-price-container`
R$34,94 `div.scroll-snap-wrapper > div.single-container__swiper_slide > div.product-card > div.bff-price-container`
R$9,69 `div.scroll-snap-wrapper > div.single-container__swiper_slide > div.product-card > div.bff-price-container`
R$20,85 `div.scroll-snap-wrapper > div.single-container__swiper_slide > div.product-card > div.bff-price-container`
R$31,99 `div.scroll-snap-wrapper > div.single-container__swiper_slide > div.product-card > div.bff-price-container`
R$100,53 `div.multi-line__half-container > div.multi-line__half_container-product > div.product-card > div.bff-price-container`
R$105,68 `div.multi-line__half-container > div.multi-line__half_container-product > div.product-card > div.bff-price-container`
R$97,84 `div.multi-line__half-container > div.multi-line__half_container-product > div.product-card > div.bff-price-container`
R$82,90 `div.multi-line__half-container > div.multi-line__half_container-product > div.product-card > div.bff-price-container`

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.bsc-common-header > header.bsc-common-header__wrap > div.bsc-common-header__left > button.full-hotzone-icon `div.bsc-common-header > header.bsc-common-header__wrap > div.bsc-common-header__left > button.full-hotzone-icon`

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.

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
Cupom geral `main.couponpkg-item__main > div.couponpkg-right > div.couponpkg-right__title > p`

These are opportunities to improve the legibility of your content.

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`

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]`s are contained by their required parent element

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

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

○Form elements have associated labels

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

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

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
header-search	search	Pesquisa:	aria-label
input	checkbox		none
input	checkbox		none
input	checkbox		none
input	checkbox		none

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