Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 4 REVIEW 7 FIX

Mobile-Readable Font Sizes

Action

56% of visible text renders at >= 12 CSS px (59 below threshold)

FIX

56% of visible text renders at >= 12 CSS px (59 below threshold)

59 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: <div> 10.0px ("HASTA UN 50% DE DESCUENTO · HASTA EL 30 ..."); <span> 7.8px ("ES"); <a> 9.5px ("Tienda"); <a> 8.5px ("Todos"); <a> 8.5px ("Rostro").

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

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

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title Verifying your connection... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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

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)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Form Accessibility

2 of 3 controls have issues

REVIEW

2 of 3 controls have issues

1 control(s) without accessible label

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

Got: <input type="checkbox" id="header-brudy-menu-toggle-sections--32754554470734__header_brudy">

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" id="brudy-panel-input">

1 control(s) properly labeled

3 controls

1 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#email_01M3VF4RDPRKPCSF4TVBQF2DAQ	email	Email	aria-label
#brudy-panel-input	text	(Escribe un mensaje…)	placeholder only
#header-brudy-menu-toggle-sections--32754554470734__header_brudy	checkbox	(none)	none

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

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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

1 issue(s) across 75 links and 30 buttons

REVIEW

1 issue(s) across 75 links and 30 buttons

1 link(s) with no accessible text

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

Got: a.header-brudy__drawer-link (#456 on page)

7 link(s) open in new tab without warning

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

Got: https://brudycosmetics.com/policies/privacy-policy; https://es.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=o…; https://seyben.ai; /policies/privacy-policy; https://seyben.ai; /policies/privacy-policy; /policies/terms-of-service

67 link(s) with descriptive text

75 links

1 empty

0 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://brudycosmetics.com/policies/priv…	Política de privacidad	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
https://es.shopify.com?utm_campaign=powe…	Tecnología de Shopify	new tab	Add '(opens in new tab)' to text
https://seyben.ai	Seyben	new tab	Add '(opens in new tab)' to text
/policies/privacy-policy	política de privacidad	new tab	Add '(opens in new tab)' to text
https://seyben.ai	Seyben	new tab	Add '(opens in new tab)' to text
/policies/privacy-policy	Política de privacidad	new tab	Add '(opens in new tab)' to text
/policies/terms-of-service	Términos	new tab	Add '(opens in new tab)' to text

97 links and buttons have descriptive text

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

a.header-brudy__drawer-link (#456 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.

https://brudycosmetics.com/policies/privacy-policy; https://es.shopify.com?utm_campaign=poweredby&utm_medium=shopify&utm_source=o…; https://seyben.ai; /policies/privacy-policy; https://seyben.ai; /policies/privacy-policy; /policies/terms-of-service

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

Mobile Keyboard & Autofill

Action

1/2 eligible field(s) missing autocomplete or inputmode

REVIEW

1/2 eligible field(s) missing autocomplete or inputmode

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" name="email" id="email_01M3VF4RDPRKPCSF4TVBQF2DAQ">

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA 19 pass AA only

h2 Consentimiento para el uso de cookies

1.11:1

#000000

#121112

needs 3.0:1 (large text)

24px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Activa la longevidad…	3.66:1	3.0:1	#000000	#666666	Pass
h2 Consentimiento para …	1.11:1	3.0:1	#000000	#121112	Fail
h2 ¿Qué necesita tu p…	3.66:1	3.0:1	#000000	#666666	Pass
h2 Investigación con p…	3.66:1	3.0:1	#000000	#666666	Pass
h2 Empieza por los favo…	3.66:1	3.0:1	#000000	#666666	Pass
h2 DHA-Algatrium	3.66:1	3.0:1	#000000	#666666	Pass
h2 : antioxidación cel…	3.66:1	3.0:1	#000000	#666666	Pass
h2 No seguimos tendenci…	3.66:1	3.0:1	#000000	#666666	Pass
h2 RUTINAS BRUDY	3.66:1	3.0:1	#000000	#666666	Pass
h2 Lo que más valoran …	3.66:1	3.0:1	#000000	#666666	Pass
h2 Idioma	3.66:1	3.0:1	#000000	#666666	Pass
h2 Antes de empezar	3.66:1	3.0:1	#000000	#666666	Pass
h3 Piel seca	3.66:1	3.0:1	#000000	#666666	Pass
h3 Piel mixta	3.66:1	3.0:1	#000000	#666666	Pass
h3 Piel sensible o con …	3.66:1	3.0:1	#000000	#666666	Pass
h3 Antiedad y piel apag…	3.66:1	3.0:1	#000000	#666666	Pass
h3 Cuerpo	3.66:1	3.0:1	#000000	#666666	Pass
h3 Sérum Reparador 30m…	3.66:1	3.0:1	#000000	#666666	Pass
h3 Contorno Reafirmante…	3.66:1	3.0:1	#000000	#666666	Pass
h3 Aceite Corporal Anti…	3.66:1	3.0:1	#000000	#666666	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.

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

A+

Heading Hierarchy

19 headings

PASS

19 headings

Single H1 present

H2 Consentimiento para el uso de cookies
H1 Activa la longevidad celular de tu piel
H2 ¿Qué necesita tu piel hoy?
H3 Piel seca
H3 Piel mixta
H3 Piel sensible o con rojeces
H3 Antiedad y piel apagada
H3 Cuerpo
H2 Investigación con propósito
H2 Empieza por los favoritos de Brudy
H3 Sérum Reparador 30ml
H3 Contorno Reafirmante 15ml
H3 Aceite Corporal Antiestrías y Nutritivo 100ml
H2 DHA-Algatrium®: antioxidación celular avanzada
H2 No seguimos tendencias, investigamos para crear el futuro de tu piel.
H2 RUTINAS BRUDY
H2 Lo que más valoran nuestras clientas
H2 Idioma
H2 Antes de empezar

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 23 images OK

PASS

All 23 images OK

4 decorative image(s) correctly marked

19 image(s) with good alt text

23 images 19 good alt text 4 decorative

All images have appropriate alt text.

A+

Form Input Types

3 form control(s) checked, no type mismatches

PASS

3 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

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

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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+

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.

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 27 passed

PASS

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

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
5 de 5 estrellas `div.oph__inner > div.oph__grid > article.oph__card > div.oph__stars`
5 de 5 estrellas `div.oph__inner > div.oph__grid > article.oph__card > div.oph__stars`
5 de 5 estrellas `div.oph__inner > div.oph__grid > article.oph__card > div.oph__stars`
5 de 5 estrellas `div.oph__inner > div.oph__grid > article.oph__card > div.oph__stars`

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
39,00 € `div.formulas__scroller > a.formulas__card > p.formulas__price > span.formulas__price-compare`
29,00 € `div.formulas__scroller > a.formulas__card > p.formulas__price > span.formulas__price-compare`

These are opportunities to improve the legibility of your content.

○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

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

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

○Uses ARIA roles only on compatible elements

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

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