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

Link & Button Quality

Action

8 issue(s) across 51 links and 12 buttons

FIX

8 issue(s) across 51 links and 12 buttons

4 link(s) with no accessible text

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

Got: https://www.bytespc.es/; https://www.bytespc.es/; https://www.bytespc.es/; https://www.bytespc.es/

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://wa.me/34604122056?text=Hola%2C%20vengo%20de%20la%20web%20de%20Bytes%2…

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 (#123 on page); button.cmplz-category-toggle (#136 on page); button.cmplz-category-toggle (#149 on page); button.cmplz-category-toggle (#163 on page)

45 link(s) with descriptive text

51 links

4 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://www.bytespc.es/	(empty)	empty	Add link text or aria-label
https://www.bytespc.es/	(empty)	empty	Add link text or aria-label
https://www.bytespc.es/	(empty)	empty	Add link text or aria-label
https://www.bytespc.es/	(empty)	empty	Add link text or aria-label
https://wa.me/34604122056?text=Hola%2C%2…	WhatsApp	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

53 links and buttons have descriptive text

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

https://www.bytespc.es/; https://www.bytespc.es/; https://www.bytespc.es/; https://www.bytespc.es/

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://cookiedatabase.org/tcf/purposes/; https://wa.me/34604122056?text=Hola%2C%20vengo%20de%20la%20web%20de%20Bytes%2…

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 (#123 on page); button.cmplz-category-toggle (#136 on page); button.cmplz-category-toggle (#149 on page); button.cmplz-category-toggle (#163 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

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

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.

Mobile-Readable Font Sizes

Action

89% of visible text renders at >= 12 CSS px (8 below threshold)

REVIEW

89% of visible text renders at >= 12 CSS px (8 below threshold)

8 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: <strong> 11.0px ("Bytes PC"); <a> 11.0px ("+34 604 122 056"); <a> 11.0px ("info@bytespc.es"); <a> 11.0px ("Aviso Legal"); <a> 11.0px ("Privacidad").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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

24 headings

PASS

24 headings

Single H1 present

H1 Reparación de Ordenadores y Soluciones Informáticas en Alcalá de Henares
H2 Nuestros Servicios de Soporte Informático
H3 Reparación y soporte de equipos
H3 Montaje de PCs a Medida
H3 Diseño y desarrollo web
H3 Diagnóstico sin compromiso
H3 Garantía en reparaciones
H3 Cerca de ti
H2 ¿Cómo funciona nuestro Soporte Informático en Alcalá?
H3 1. Contacto y Diagnóstico
H3 2. Presupuesto Cerrado
H3 3. Reparación y Entrega
H2 Expertos en tecnología y soporte local en Alcalá
H2 ¿Por qué elegir Bytes PC?
H3 Soporte Informático Rápido
H3 Experiencia Técnica
H3 Solución Integral
H2 Lo que dicen nuestros clientes
H2 Preguntas frecuentes sobre soporte informático
H3 ¿Cuánto cuesta revisar mi ordenador?
H3 ¿Cuánto tarda una reparación habitual?
H3 ¿Hacéis soporte a domicilio o a empresas?
H3 ¿Los componentes y reparaciones tienen garantía?
H2 ¿Necesitas reparar tu PC o impulsar tu negocio?

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 35 images OK

PASS

All 35 images OK

2 decorative image(s) correctly marked

33 image(s) with good alt text

35 images 33 good alt text 2 decorative

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

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

PASS

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

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 Reparación de Orden…	18.34:1	3.0:1	#1A1025	#FFFFFF	Pass
h2 Nuestros Servicios d…	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h2 ¿Cómo funciona nue…	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h2 Expertos en tecnolog…	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h2 ¿Por qué elegir By…	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h2 Lo que dicen nuestro…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Preguntas frecuentes…	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h2 ¿Necesitas reparar …	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h3 Reparación y soport…	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h3 Montaje de PCs a Med…	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h3 Diseño y desarrollo…	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h3 Diagnóstico sin com…	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h3 Garantía en reparac…	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h3 Cerca de ti	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h3 1. Contacto y Diagn�…	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h3 2. Presupuesto Cerra…	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h3 3. Reparación y Ent…	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h3 Soporte Informático…	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h3 Experiencia Técnica	17.85:1	3.0:1	#0F172A	#FFFFFF	Pass
h3 Solución Integral	17.85:1	3.0:1	#0F172A	#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+

Lighthouse Accessibility Audits

Score 96/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.

Names and labels

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.ast-builder-layout-element > div.site-branding > span.site-logo-img > a.custom-logo-link `div.ast-builder-layout-element > div.site-branding > span.site-logo-img > a.custom-logo-link`
div.site-branding > div.ast-site-title-wrap > span.site-title > a `div.site-branding > div.ast-site-title-wrap > span.site-title > a`

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.

○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

●Background and foreground colors have a sufficient contrast ratio

●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

●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

○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

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

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