Skip to content
https://creative.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
D
Form Accessibility
Action
4 of 7 controls have issues
FIX
4 of 7 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="email" id="et_pb_signup_email">; <input type="submit">; <input type="text">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="keywords" id="search-keywords">
Info::
3 control(s) properly labeled
7 controls
3 labeled
1 placeholder only
3 unlabeled
ControlTypeLabelMethod
#cookies_necessarycheckboxCookies necesarias Estas cookies son esenciales para el funcionamiento de la web en su plena capacidad. No pueden desactivarse. Más informaciónfor/id
#cookies_analyticscheckboxCookies analíticas Estas cookies nos ayudan a mejorar nuestra website entendiendo el rendimiento y su uso anónimamente. Más informaciónfor/id
#cookies_thirdPartycheckboxCookies de terceros Estas cookies nos ayudan a llegarle a través de otros sitios con comunicaciones de marketing y ofertas especiales. Más informaciónfor/id
#search-keywordstext(Buscar por nombre de producto o palabras clave)placeholder only
inputsubmit(none)none
inputtext(none)none
#et_pb_signup_emailemail(none)none

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

<input type="email" id="et_pb_signup_email">; <input type="submit">; <input type="text">

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.

<input type="text" name="keywords" id="search-keywords">

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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
No dark mode signals
FIX
No dark mode signals
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 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.

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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
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.
D
Lighthouse Accessibility Audits
Action
Score 61/100 — 11 failing, 20 passed
FIX
61

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
div.et_pb_section > div.et_pb_row > ul.slick-dots > li#slick-slide00 div.et_pb_section > div.et_pb_row > ul.slick-dots > li#slick-slide00
1 div.et_pb_section > div.et_pb_row > ul.slick-dots > li#slick-slide20

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.et_builder_inner_content > div.et_pb_section > div.et_pb_row > ul.slick-dots div.et_builder_inner_content > div.et_pb_section > div.et_pb_row > ul.slick-dots
1 2 3 4 5 div.et_builder_inner_content > div.et_pb_section > div.et_pb_row > ul.slick-dots

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.et_pb_section > div.et_pb_row > ul.slick-dots > li#slick-slide00 div.et_pb_section > div.et_pb_row > ul.slick-dots > li#slick-slide00
1 div.et_pb_section > div.et_pb_row > ul.slick-dots > li#slick-slide20

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.et_pb_row > div.et_pb_column > div.slick-list > div.slick-track div.et_pb_row > div.et_pb_column > div.slick-list > div.slick-track
SOUND BLASTER GS5 ILUMINA TU JUEGO MÁS INFORMACIÓN NUEVO PEBBLE NOVA UN NUEVO… div.et_pb_row > div.et_pb_column > div.slick-list > div.slick-track
SOBRE LA MARCHA JUEGOS FITNESS PELIS Y MÚSICA TRABAJAR Y ESTUDIAR SOBRE LA… div.et_pb_section > div.et_pb_row > div.slick-list > div.slick-track

When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about toggle fields.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.et_pb_column > div.slick-list > div.slick-track > div.et_pb_module div.et_pb_column > div.slick-list > div.slick-track > div.et_pb_module

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.et_pb_row > ul.slick-dots > li#slick-slide00 > button.slick-dot div.et_pb_row > ul.slick-dots > li#slick-slide00 > button.slick-dot

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.et_pb_code_inner > form#form_signup > div.mdl-textfield > input#et_pb_signup_email div.et_pb_code_inner > form#form_signup > div.mdl-textfield > input#et_pb_signup_email

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
li#alert-box-container > div#alert-box > div.alert-box-inner > a.close li#alert-box-container > div#alert-box > div.alert-box-inner > a.close
div#sec-menu > ul.nav > li > a#nav-sitemap div#sec-menu > ul.nav > li > a#nav-sitemap
div.slick-list > div.slick-track > div.et_pb_module > a div.slick-list > div.slick-track > div.et_pb_module > a
div#__layout > div#page-container > div#search-bar > a.close div#__layout > div#page-container > div#search-bar > a.close
div#__layout > div#page-container > div#nav-account-menu > a.i-cross div#__layout > div#page-container > div#nav-account-menu > a.i-cross
div#__layout > div#page-container > div#product-menu > a.close div#__layout > div#page-container > div#product-menu > a.close
div#__layout > div#page-container > div#sale-menu > a.close div#__layout > div#page-container > div#sale-menu > a.close
div#__layout > div#page-container > div#notification-bar > a.close div#__layout > div#page-container > div#notification-bar > a.close

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
NOVEDADES div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p
NUEVO div.et_pb_module > div.et_pb_code_inner > div.hl_wrapper > div.hlnewtag
REDEFINIENDO TU EXPERIENCIA DE AUDIO div.et_pb_row > div.et_pb_column > div.et_pb_module > div.et_pb_text_inner
NUESTRAS MARCAS div.et_pb_row > div.et_pb_column > div.et_pb_module > div.et_pb_text_inner
PREMIOS & RECONOCIMIENTOS div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p
CORREO ELECTRÓNICO* div.et_pb_code_inner > form#form_signup > div.mdl-textfield > label.mdl-textfield__label

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Productos SXFI Ofertas Ofertas de paquetes Help Soporte div#side-menu > div.menu-content > div.home-menu > ul

These are opportunities to improve the experience of reading tabular or list data using 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
div.et_pb_row > ul.slick-dots > li#slick-slide00 > button.slick-dot div.et_pb_row > ul.slick-dots > li#slick-slide00 > button.slick-dot
1 div.et_pb_row > ul.slick-dots > li#slick-slide20 > button

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]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●`[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
●`[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
●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
●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
○Elements with `role="dialog"` or `role="alertdialog"` 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 `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 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
○`<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.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
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.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO footer

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

B
Heading Hierarchy
7 headings
REVIEW
7 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 ¿Necesita ayuda?
  • H2 Explorar
  • H2 Altavoces
  • H2 Auriculares
  • H2 Sound Blaster
  • H2 Cámaras web
  • H2 Adaptadores & accesorios

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

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 - File or directory not found. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
h2 ¿Necesita ayuda?
1.74:1
#000000
on
#21384D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explorar
1.74:1
#000000
on
#21384D
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 ¿Necesita ayuda?1.74:13.0:1
#000000
#21384D
Fail
h2 Explorar1.74:13.0:1
#000000
#21384D
Fail
title Creative Labs (Espa…21.00:14.5:1
#000000
#FFFFFF
Pass
p Usamos cookies, que …21.00:14.5:1
#000000
#FFFFFF
Pass
button MÁS INFO21.00:14.5:1
#000000
#FFFFFF
Pass
button HECHO21.00:14.5:1
#000000
#FFFFFF
Pass
button PERMITIR TODAS21.00:14.5:1
#000000
#FFFFFF
Pass
strong Cookies necesarias21.00:13.0:1
#000000
#FFFFFF
Pass
p Estas cookies son es…21.00:14.5:1
#000000
#FFFFFF
Pass
a Más información21.00:14.5:1
#000000
#FFFFFF
Pass
strong Cookies analíticas21.00:13.0:1
#000000
#FFFFFF
Pass
p Estas cookies nos ay…21.00:14.5:1
#000000
#FFFFFF
Pass
a Más información21.00:14.5:1
#000000
#FFFFFF
Pass
strong Cookies de terceros21.00:13.0:1
#000000
#FFFFFF
Pass
p Estas cookies nos ay…21.00:14.5:1
#000000
#FFFFFF
Pass
a Más información20.65:14.5:1
#000000
#FDFDFD
Pass
a Productos21.00:14.5:1
#000000
#FFFFFF
Pass
a SXFI21.00:14.5:1
#000000
#FFFFFF
Pass
a Comprar21.00:14.5:1
#000000
#FFFFFF
Pass
a Ayuda21.00:14.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.

A+
Alt Text Quality
All 46 images OK
PASS
All 46 images OK
Info::
27 decorative image(s) correctly marked
Info::
19 image(s) with good alt text
46 images 19 good alt text 27 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback