Accessibility

F

Heading Hierarchy

Action

26 headings, 9 skip(s)

FIX

26 headings, 9 skip(s)

Multiple H1 headings (10 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H3 (missing H2)

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

3 empty heading(s)

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

H1 Every Connection Counts, For You and More
H3 Cada conexión cuenta, para ti y muchos más skipped
H1 Smart Pro sin límites duplicate H1
H3 Apilado físico hasta 9 unidades Uplinks 10G en cobre y fibra Static Routing, OSPF, DCHP Server VLAN advanced Desde 10 a 52 puertos Concentradores de fibra óptica skipped
H1 Scalable IloT Connectivity for Industrial Applications duplicate H1
H3 Reliable, secure, efficient for mission-critical applications skipped
H1 Gestiona tu red sin costes con NUCLIAS duplicate H1
H3 Switching y WiFi Unificado mediante software, controladora local o en la nube skipped
H1 Wi-Fi Empresarial sin complicaciones duplicate H1
H3 Controladoras unificadas DBR-600-P, DBR-700, integran: Router Empresarial VPN/Firewall Switch 2.5G (PoE en DBR-600-P) Controladora WiFi Puntos de Acceso Wi-Fi 6 (DBR-X3000-AP) skipped
H1 Switches Multi-Gigabit duplicate H1
H3 D-Link ofrece la máxima versatilidad para desplegar WiFi 6 y 7 al máximo rendimiento o aumentar el ancho de banda para escalabilidad ilimitada Managed L3 con apilado físico Smart Manage skipped
H1 El mejor corazón para tu red duplicate H1
H3 Switching, Wireless y 5G para redes empresariales, industriales e IoT. skipped
H1 Wi-Fi a unNuevo Nivel duplicate H1
H3 Wi-Fi 7 lo cambia todo skipped
H1 Agilidad en Gestión de red duplicate H1
H3 Gestión de Switches Smart y hasta Managed L3 con stacking Gestión de Puntos Acceso Wi-Fi 6/7 Sin costes ni licencias Software Windows/Linux (DNC-100) Controladora física (DNH-1000/D skipped
H3 (empty)
H3 (empty)
H3 (empty)
H3 Routers M2M 5G
H3 Un fabricante, todas las soluciones
H2 Descubre nuestros productos
H2 Todas las novedades
H1 Subscríbete a nuestra newsletter duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

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

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

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

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

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

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

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

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

F

Alt Text Quality

Action

44 of 46 images have issues

FIX

44 of 46 images have issues

44 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

42 image-in-link without alt text

An image inside a link with no alt creates an empty link.

2 image(s) with good alt text

46 images 2 good alt text 44 missing

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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F

Link & Button Quality

Action

8 issue(s) across 126 links and 24 buttons

FIX

8 issue(s) across 126 links and 24 buttons

4 link(s) with no accessible text

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

Got: https://www.facebook.com/DLinkES/; https://www.linkedin.com/company/dlink/; http://twitter.com/DLink_ES; http://www.youtube.com/user/DLINKIberiaTV

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /es/es/for-industry/mobile ("Learn More")

8 link(s) open in new tab without warning

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

Got: https://www.mydlink.com; https://services.eu.dlink.com/home/main/SSPLogin.aspx?language=S; /es/es/products/dgs-1530-series-gigabit-layer-2-stackable-smart-managed-switches; /es/es/empresas/nuclias; /es/es/hogar-digital/wifi-7; /es/es/empresas/nuclias/nuclias-hardware; /es/es/privacy; https://www.mydlink.com

3 button(s) with no accessible text

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

Got: button.section-nav__button (#100 on page); button.search-bar-button (#186 on page); input[type="submit"] (#195 on page)

113 link(s) with descriptive text

126 links

4 empty

1 generic text

8 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://www.mydlink.com	mydlink	new tab	Add '(opens in new tab)' to text
https://services.eu.dlink.com/home/main/…	Portal de Soporte	new tab	Add '(opens in new tab)' to text
/es/es/hogar-digital/repetidor-wifi-plc-…	Wi‑Fi	img no alt	Add alt attribute to the image
/es/es/hogar-digital/repetidor-wifi-plc-…	4G & 5G	img no alt	Add alt attribute to the image
/es/es/hogar-digital/camaras-wifi	Cámaras	img no alt	Add alt attribute to the image
/es/es/hogar-digital/smart-home	Hogar Inteligente	img no alt	Add alt attribute to the image
/es/es/hogar-digital/switches	Switches	img no alt	Add alt attribute to the image
/es/es/hogar-digital/accessories	Accesorios	img no alt	Add alt attribute to the image
https://www.mydlink.com	mydlink	img no alt	Add alt attribute to the image
/es/es/hogar-digital/where-to-buy	Dónde Comprar	img no alt	Add alt attribute to the image
/es/es/empresas/switches	Switching	img no alt	Add alt attribute to the image
/es/es/empresas/wireless	Wireless	img no alt	Add alt attribute to the image
/es/es/empresas/business-routers	Routers Business con Firewall/…	img no alt	Add alt attribute to the image
/es/es/empresas/nuclias	Switching/Wireless Unificado	img no alt	Add alt attribute to the image
/es/es/empresas/accessories	Accesorios	img no alt	Add alt attribute to the image
/es/es/empresas/where-to-buy	Dónde Comprar	img no alt	Add alt attribute to the image
/es/es/for-industry/mobile	4G/5G M2M	img no alt	Add alt attribute to the image
/es/es/for-industry/d-ecs	D-ECS	img no alt	Add alt attribute to the image
/es/es/for-industry/industrial-switches	Switches	img no alt	Add alt attribute to the image
/es/es/for-industry/accessories	Accessories	img no alt	Add alt attribute to the image
/es/es/resource-centre/catalogos	Catálogos	img no alt	Add alt attribute to the image
/es/es/resource-centre/case-studies	Casos de éxito	img no alt	Add alt attribute to the image
/es/es/resource-centre/videos	Vídeos y Webinars	img no alt	Add alt attribute to the image
/es/es/resource-centre/articles	Formación Técnica	img no alt	Add alt attribute to the image
/es/es/about/novedades	Novedades	img no alt	Add alt attribute to the image
/es/es/resource-centre/promos	Promos	img no alt	Add alt attribute to the image
/es/es/support	Soporte Técnico	img no alt	Add alt attribute to the image
/es/es/support/support-news	Tech Alerts	img no alt	Add alt attribute to the image
/es/es/support/faq	Preguntas frecuentes	img no alt	Add alt attribute to the image
/es/es/support/warranty-information	Garantía	img no alt	Add alt attribute to the image
/es/es/support/contact	¿Necesita ayuda?	img no alt	Add alt attribute to the image
https://services.eu.dlink.com/home/main/…	Portal de Soporte	img no alt	Add alt attribute to the image
/es/es/products/dgs-1530-series-gigabit-…	Descúbrelo	new tab	Add '(opens in new tab)' to text
/es/es/for-industry/mobile	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Mobile
/es/es/empresas/nuclias	Saber más	new tab	Add '(opens in new tab)' to text
/es/es/hogar-digital/wifi-7	Saber más	new tab	Add '(opens in new tab)' to text
/es/es/empresas/nuclias/nuclias-hardware	Descúbrelo	new tab	Add '(opens in new tab)' to text
/es/es/empresas/switches	Switching	img no alt	Add alt attribute to the image
/es/es/empresas/wireless	Wireless	img no alt	Add alt attribute to the image
/es/es/empresas/nuclias	Nuclias	img no alt	Add alt attribute to the image
/es/es/empresas/ip-surveillance-infrastr…	Videovigilancia IP	img no alt	Add alt attribute to the image
/es/es/for-industry/industrial-switches	Industrial	img no alt	Add alt attribute to the image
/es/es/empresas/accessories	Accesorios	img no alt	Add alt attribute to the image
/es/es/hogar-digital/repetidor-wifi-plc-…	Wi‑Fi	img no alt	Add alt attribute to the image
/es/es/hogar-digital/repetidor-wifi-plc-…	4G & 5G	img no alt	Add alt attribute to the image
/es/es/hogar-digital/camaras-wifi	Cámaras	img no alt	Add alt attribute to the image
/es/es/hogar-digital/smart-home	Hogar Inteligente	img no alt	Add alt attribute to the image
/es/es/hogar-digital/switches	Switches	img no alt	Add alt attribute to the image
/es/es/hogar-digital/accessories	Accesorios	img no alt	Add alt attribute to the image
/es/es/privacy	Política de Privacidad	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/DLinkES/	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/dlink/	(empty)	empty	Add link text or aria-label
http://twitter.com/DLink_ES	(empty)	empty	Add link text or aria-label
http://www.youtube.com/user/DLINKIberiaT…	(empty)	empty	Add link text or aria-label
https://www.mydlink.com	mydlink	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
<input>	(empty)	empty	Add button text or aria-label

134 links and buttons have descriptive text

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

https://www.facebook.com/DLinkES/; https://www.linkedin.com/company/dlink/; http://twitter.com/DLink_ES; http://www.youtube.com/user/DLINKIberiaTV

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

Generic link text like 'click here' doesn't describe the destination.

/es/es/for-industry/mobile ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.mydlink.com; https://services.eu.dlink.com/home/main/SSPLogin.aspx?language=S; /es/es/products/dgs-1530-series-gigabit-layer-2-stackable-smart-managed-switches; /es/es/empresas/nuclias; /es/es/hogar-digital/wifi-7; /es/es/empresas/nuclias/nuclias-hardware; /es/es/privacy; https://www.mydlink.com

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.section-nav__button (#100 on page); button.search-bar-button (#186 on page); input[type="submit"] (#195 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

D

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.

D

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.

D

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 ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

4 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

Search

Skip Link

Labeled Navigation 4 <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 63/100 — 13 failing, 25 passed

FIX

63

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
6 `div.slider-wrapper > div.js-progressbar > ul.slick-dots > li#slick-slide05`

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
1 2 3 4 5 6 7 8 9 `main.main > div.slider-wrapper > div.js-progressbar > ul.slick-dots`
NO YES `div.prefPanel > div > div.cookiecat > div.switch`
NO YES `div.prefPanel > div > div.cookiecat > div.switch`

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
Our Brand Every Connection Counts, For You and More Cada conexión cuenta, para … `div.slider-wrapper > div.js-progressbar > div.slick-list > div.slick-track`

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
header#header > div.site-header__container > div.section-nav > button.section-nav__button `header#header > div.site-header__container > div.section-nav > button.section-nav__button`
header#header > div.site-header__container > div.language-search-container > button.search-bar-button `header#header > div.site-header__container > div.language-search-container > button.search-bar-button`

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.language-selector > div.language-selector__toggle > div.language-selector__flag > img.flag-site-header--black `div.language-selector > div.language-selector__toggle > div.language-selector__flag > img.flag-site-header--black`
div.language-selector > div.language-selector__toggle > div.language-selector__flag > img.flag-site-header--white `div.language-selector > div.language-selector__toggle > div.language-selector__flag > img.flag-site-header--white`

Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.search-bar > div.search-bar__container > form#mainSearchBar > input `div.search-bar > div.search-bar__container > form#mainSearchBar > input`

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
div.grid__col > ul.social-list > li.social-list__item > a.social-list__link `div.grid__col > ul.social-list > li.social-list__item > a.social-list__link`
div.grid__col > ul.social-list > li.social-list__item > a.social-list__link `div.grid__col > ul.social-list > li.social-list__item > a.social-list__link`
div.grid__col > ul.social-list > li.social-list__item > a.social-list__link `div.grid__col > ul.social-list > li.social-list__item > a.social-list__link`
div.grid__col > ul.social-list > li.social-list__item > a.social-list__link `div.grid__col > ul.social-list > li.social-list__item > a.social-list__link`

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
Más ancho de banda, mismo cableado `div.hero > div.hero__container > div.hero__content > span.heading`
Switches Multi-Gigabit `div.hero > div.hero__container > div.hero__content > h1.heading`
Saber más `div.hero > div.hero__container > div.hero__content > a.button`
Enviar `div.row > div.grid > div.grid__col > button.c-newsletter__button`
Privacidad `nav.legal-nav > ul.legal-nav__list > li.legal-nav__item > a.legal-nav__link`
Condiciones de uso `nav.legal-nav > ul.legal-nav__list > li.legal-nav__item > a.legal-nav__link`
Codigo Etico `nav.legal-nav > ul.legal-nav__list > li.legal-nav__item > a.legal-nav__link`
Mapa del sitio `nav.legal-nav > ul.legal-nav__list > li.legal-nav__item > a.legal-nav__link`
Suscripción al boletín de noticias `nav.legal-nav > ul.legal-nav__list > li.legal-nav__item > a.legal-nav__link`
© 2026 D‑Link (Europe) Ltd. D-Link Iberia, S.L. - Muntaner, 239-253 (3º "A") - … `div.grid > div.grid__col > nav.legal-nav > span.legal-nav__copyright`
View Required Cookies `div.prefPanel > div > div.cookiecat > a.viewcookie`
Detailed Settings `div.prefPanel > div > div.cookiecat > a.viewcookie`
Detailed Settings `div.prefPanel > div > div.cookiecat > a.viewcookie`
SUBMIT PREFERENCES `div.mainContent > div.gdpr > div.pdynamicbutton > a.submit`
Privacy Policy \| Powered by: `div.wrapper > div > div.footer > div.right`
Privacy Policy `div > div.footer > div.right > a`

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Policy `div > div.footer > div.right > a`

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body#body > div#pop-div2045327103052563755 > div#pop-div3047708773970133644 > div#pop-frame02089283076993136 `body#body > div#pop-div2045327103052563755 > div#pop-div3047708773970133644 > div#pop-frame02089283076993136`

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
D-Link ofrece la máxima versatilidad para desplegar WiFi 6 y 7 al máximo rendim… `div.hero > div.hero__container > div.hero__content > h3.sub-heading`
Required Cookies `div.cookiecat > div > span.gwt-InlineHTML > h3`

These are opportunities to improve keyboard navigation in your application.

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#viewport `head > meta#viewport`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
View Required Cookies `div.prefPanel > div > div.cookiecat > a.viewcookie`
Detailed Settings `div.prefPanel > div > div.cookiecat > a.viewcookie`
NO `div > div.cookiecat > div.switch > span.gwt-InlineHTML`
YES `div > div.cookiecat > div.switch > span.gwt-InlineHTML`
Detailed Settings `div.prefPanel > div > div.cookiecat > a.viewcookie`
NO `div > div.cookiecat > div.switch > span.gwt-InlineHTML`
YES `div > div.cookiecat > div.switch > span.gwt-InlineHTML`

○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 have valid values

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

●Form elements have associated labels

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

●ARIA toggle fields have accessible names

●Document has a `<title>` element

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

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

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

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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

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

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

○Tables have different content in the summary attribute and `<caption>`.

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

B

Landmark Structure

7 landmarks

REVIEW

7 landmarks

<main> landmark present

4 <nav> landmark(s) found

4 of 4 <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

C

Form Accessibility

Action

3 of 5 controls have issues

REVIEW

3 of 5 controls have issues

2 control(s) without accessible label

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

Got: <select id="searchBarTarget">; <input type="submit">

1 control(s) rely on placeholder only

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

Got: <input type="text" name="q" id="searchBar">

2 control(s) properly labeled

5 controls

2 labeled

1 placeholder only

2 unlabeled

Control	Type	Label	Method
emailaddr_	email	Email	aria-label
EmailAuthorize	checkbox		none
#searchBar	text	( Search)	placeholder only
#searchBarTarget	select	(none)	none
input	submit	(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

B

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 | D-Link ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

B

Favicon & Branding

11 icon(s) detected

REVIEW

11 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

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA

title Soluciones avanzadas en redes informáti…

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

button Hogar Digital

1.00:1

#000000

on

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Wi‑Fi

1.20:1

#000000

on

#0D163C

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Every Connection Cou…	6.66:1	3.0:1	#000000	#919191	Pass
h1 Smart Pro sin límit…	6.66:1	3.0:1	#000000	#919191	Pass
h1 Scalable IloT Connec…	6.66:1	3.0:1	#000000	#919191	Pass
h1 Gestiona tu red sin …	6.66:1	3.0:1	#000000	#919191	Pass
h1 Wi-Fi Empresarial si…	6.66:1	3.0:1	#000000	#919191	Pass
h1 Switches	6.66:1	3.0:1	#000000	#919191	Pass
h1 Multi-Gigabit	6.66:1	3.0:1	#000000	#919191	Pass
h1 El mejor corazón pa…	6.66:1	3.0:1	#000000	#919191	Pass
h1 Wi-Fi a un	6.66:1	3.0:1	#000000	#919191	Pass
h1 Nuevo Nivel	6.66:1	3.0:1	#000000	#919191	Pass
h1 Agilidad en Gestión…	6.66:1	3.0:1	#000000	#919191	Pass
h1 Subscríbete a nuest…	6.66:1	3.0:1	#000000	#919191	Pass
h2 Descubre nuestros pr…	6.66:1	3.0:1	#000000	#919191	Pass
h2 Todas las novedades	6.66:1	3.0:1	#000000	#919191	Pass
h3 Reliable, secure, ef…	6.66:1	3.0:1	#000000	#919191	Pass
h3 Routers M2M 5G	6.66:1	3.0:1	#000000	#919191	Pass
h3 Un fabricante, todas…	6.66:1	3.0:1	#000000	#919191	Pass
title Soluciones avanzadas…	1.00:1	4.5:1	#000000	#000000	Fail
button Hogar Digital	1.00:1	4.5:1	#000000	#000000	Fail
a Wi‑Fi	1.20:1	4.5:1	#000000	#0D163C	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.