Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 3 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

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 Present

✗ PNG Icons Missing

✗ 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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Link & Button Quality

4 issue(s) across 45 links and 10 buttons

REVIEW

4 issue(s) across 45 links and 10 buttons

2 link(s) open in new tab without warning

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

Got: https://cookiedatabase.org/tcf/purposes/; https://bytespc.es

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.cmplz-category-toggle (#71 on page); button.cmplz-category-toggle (#84 on page); button.cmplz-category-toggle (#97 on page); button.cmplz-category-toggle (#111 on page)

43 link(s) with descriptive text

45 links

0 empty

0 generic text

2 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
https://cookiedatabase.org/tcf/purposes/	Lee más acerca de los fines d…	new tab	Add '(opens in new tab)' to text
https://bytespc.es	bytespc.es	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

49 links and buttons have descriptive text

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

https://cookiedatabase.org/tcf/purposes/; https://bytespc.es

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.cmplz-category-toggle (#71 on page); button.cmplz-category-toggle (#84 on page); button.cmplz-category-toggle (#97 on page); button.cmplz-category-toggle (#111 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found - Alana Creaciones ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

A+

Heading Hierarchy

13 headings

PASS

13 headings

Single H1 present

H1 Pequeños detalles,grandes recuerdos.
H2 Hecho con calma.Creado para emocionar.
H2 Descubre el universo Alana
H3 Pequeños imprescindibles
H3 Detalles para sus primeros descubrimientos
H3 Delicadeza en cada detalle
H2 Detrás de cada pieza,una historia que contar.
H2 Lo especial está en cómo se hace
H3 Cuidado en cada detalle
H3 Materiales y texturas
H3 Una forma diferente de crear
H2 Historias bonitas, palabras que nos emocionan
H3 Alana Creaciones

A+

Heading Text Quality

All 13 heading(s) have substantive, well-formed text

PASS

All 13 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 5 images OK

PASS

All 5 images OK

5 image(s) with good alt text

5 images 5 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#cmplz-functional-optin	checkbox	Funcional	for/id
#cmplz-preferences-optin	checkbox	Preferencias	for/id
#cmplz-statistics-optin	checkbox	Estadísticas	for/id
#cmplz-marketing-optin	checkbox	Marketing	for/id

A+

Form Input Types

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

4 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

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

PASS

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

No tabindex anti-patterns detected

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+

Mobile-Readable Font Sizes

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

PASS

All 59 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

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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)

Element	Ratio	Required	FG	BG	Result
h1 Pequeños detalles,	18.99:1	3.0:1	#000000	#F6F3EF	Pass
h2 Hecho con calma.	18.99:1	3.0:1	#000000	#F6F3EF	Pass
h2 Descubre el universo…	18.99:1	3.0:1	#000000	#F6F3EF	Pass
h2 Detrás de cada piez…	18.99:1	3.0:1	#000000	#F6F3EF	Pass
h2 Lo especial está en…	18.99:1	3.0:1	#000000	#F6F3EF	Pass
h2 Historias bonitas, p…	18.99:1	3.0:1	#000000	#F6F3EF	Pass
h3 Pequeños imprescind…	18.99:1	3.0:1	#000000	#F6F3EF	Pass
h3 Detalles para sus pr…	18.99:1	3.0:1	#000000	#F6F3EF	Pass
h3 Delicadeza en cada d…	18.99:1	3.0:1	#000000	#F6F3EF	Pass
h3 Cuidado en cada deta…	18.99:1	3.0:1	#000000	#F6F3EF	Pass
h3 Materiales y textura…	18.99:1	3.0:1	#000000	#F6F3EF	Pass
h3 Una forma diferente …	18.99:1	3.0:1	#000000	#F6F3EF	Pass
h3 Alana Creaciones	18.99:1	3.0:1	#000000	#F6F3EF	Pass
title Alana Creaciones -	19.47:1	4.5:1	#000000	#F9F6F0	Pass
div Gestionar consentimi…	19.47:1	4.5:1	#000000	#F9F6F0	Pass
div Para ofrecer las mej…	19.47:1	4.5:1	#000000	#F9F6F0	Pass
span Funcional	19.47:1	4.5:1	#000000	#F9F6F0	Pass
span Funcional	19.47:1	4.5:1	#000000	#F9F6F0	Pass
span Siempre activo	17.86:1	4.5:1	#000000	#EEEDE3	Pass
span El almacenamiento o …	17.86:1	4.5:1	#000000	#EEEDE3	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.

A+

Lighthouse Accessibility Audits

Score 97/100 — 1 failing, 26 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.

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
ACEPTAR `div#cmplz-cookiebanner-container > div#cmplz-cookiebanner-1-optin > div.cmplz-buttons > button.cmplz-btn`
Política de cookies `div.cmplz-documents > ul > li > a.cmplz-link`
Política de Privacidad `div.cmplz-documents > ul > li > a.cmplz-link`
Aviso legal `div.cmplz-documents > ul > li > a.cmplz-link`
DESCUBRIR ALANA `body.home > section.hero > div.hero-content > a.btn`
Creado para emocionar. `section.section > div.wrap > h2 > span.script`
Descubrir pañaleras `div > a.card > div > span.script`
Descubrir sonajeros `div > a.card > div > span.script`
Descubrir diademas `div > a.card > div > span.script`
una historia que contar. `div.wrap > div.txt > h2 > span.script`
© 2026 Alana Creaciones. Todos los derechos reservados. \| Creado por bytespc.es `body.home > footer#contacto > div.wrap > div`
bytespc.es `footer#contacto > div.wrap > div > a`

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

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

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

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

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

○`[accesskey]` values are unique

○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

○Form elements have associated labels

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

○Identical links have the same purpose.

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