Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 6 REVIEW 7 FIX

Landmark Structure

Action

2 landmarks

FIX

2 landmarks

No <main> landmark found

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

No <nav> landmark 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

Mobile Keyboard & Autofill

Action

9/9 eligible field(s) missing autocomplete or inputmode

FIX

9/9 eligible field(s) missing autocomplete or inputmode

3 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" name="email">, <input type="email" name="email" id="email">, <input type="email" name="email" id="modalEmail">

6 field(s) would benefit from inputmode attribute

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

Got: <input type="email" name="email">, <input type="tel" name="telefono">, <input type="email" name="email" id="email">, <input type="tel" name="telefono" id="telefono">, <input type="email" name="email" id="modalEmail">

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ 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 ✗

Heading Hierarchy

15 headings, 1 skip(s)

REVIEW

15 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

1 empty heading(s)

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

H1 Más control, más organización, más tiempo para crecer.
H2 Servicios Modulares
H3 Administración y Documentación
H3 Finanzas y Tesorería
H3 Gestión Comercial y Operaciones
H2 Sobre Vértice
H3 Pilares de Gestión
H2 Contacto
H4 Datos de contacto skipped
H3 ¡Gracias por contactarte con VÉRTICE!
H3 (empty)
H3 Tu solicitud de servicios
H4 Servicios seleccionados
H4 Tus datos
H3 ¡Recibimos tu solicitud!

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

Form Accessibility

Action

4 of 14 controls have issues

REVIEW

4 of 14 controls have issues

4 control(s) without accessible label

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

Got: <input type="text" name="nombre">; <input type="email" name="email">; <input type="tel" name="telefono">; <textarea name="mensaje">

10 control(s) properly labeled

14 controls

10 labeled

0 placeholder only

4 unlabeled

Control	Type	Label	Method
bot-field	input	Don't fill this out if you're human:	none
#nombre	text	Nombre y apellido *	for/id
#email	email	Correo electrónico *	for/id
#telefono	tel	Teléfono *	for/id
#mensaje	textarea	Mensaje	for/id
bot-field	input	Don't fill this out if you're human:	none
#modalNombre	text	Nombre y apellido *	for/id
#modalEmail	email	Correo electrónico *	for/id
#modalTelefono	tel	Teléfono *	for/id
#modalMensaje	textarea	Mensaje adicional (opcional)	for/id
telefono	tel	(none)	none
mensaje	textarea	(none)	none
nombre	text	(none)	none
email	email	(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

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (3 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (3 below threshold)

3 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: <span> 10.4px ("Años de"); <span> 10.4px ("experiencia"); <span> 11.2px ("SOPORTE ADMINISTRATIVO").

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 ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 Más control, más organización, más t…

2.44:1

#000000

#125550

needs 3.0:1 (large text)

32px · above the fold

h2 Servicios Modulares

2.03:1

#000000

#0F4844

needs 3.0:1 (large text)

24px · mid-page

h2 Sobre Vértice

1.77:1

#000000

#0D3E3B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Contacto

1.77:1

#000000

#0D3E3B

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Administración y Documentación

1.89:1

#000000

#0E433F

needs 3.0:1 (large text)

19px · mid-page

h3 Finanzas y Tesorería

1.77:1

#000000

#0C3E3A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Gestión Comercial y Operaciones

1.77:1

#000000

#0D3E3B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Pilares de Gestión

1.77:1

#000000

#0D3E3B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 ¡Gracias por contactarte con VÉRTICE!

1.77:1

#000000

#0D3E3B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Tu solicitud de servicios

1.57:1

#155E59

#0D3E3B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 ¡Recibimos tu solicitud!

1.77:1

#000000

#0D3E3B

needs 3.0:1 (large text)

19px · bottom of viewport

title VÉRTICE — Soporte Administrativo

2.78:1

#000000

#155E59

needs 4.5:1 (normal text)

16px · top of page (header area)

span VÉRTICE

2.78:1

#000000

#155E59

needs 4.5:1 (normal text)

16px · top of page (header area)

span SOPORTE ADMINISTRATIVO

2.78:1

#000000

#155E59

needs 4.5:1 (normal text)

16px · top of page (header area)

a Inicio

2.78:1

#000000

#155E59

needs 4.5:1 (normal text)

16px · top of page (header area)

a Servicios

2.78:1

#000000

#155E59

needs 4.5:1 (normal text)

16px · above the fold

a Sobre VÉRTICE

2.78:1

#000000

#155E59

needs 4.5:1 (normal text)

16px · above the fold

a Contacto

2.78:1

#000000

#155E59

needs 4.5:1 (normal text)

16px · above the fold

div Tu Negocio, Con Más Orden

2.78:1

#000000

#155E59

needs 4.5:1 (normal text)

16px · above the fold

p Brindamos soporte administrativo a empre…

2.24:1

#000000

#114F4B

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Más control, más o…	2.44:1	3.0:1	#000000	#125550	Fail
h2 Servicios Modulares	2.03:1	3.0:1	#000000	#0F4844	Fail
h2 Sobre Vértice	1.77:1	3.0:1	#000000	#0D3E3B	Fail
h2 Contacto	1.77:1	3.0:1	#000000	#0D3E3B	Fail
h3 Administración y Do…	1.89:1	3.0:1	#000000	#0E433F	Fail
h3 Finanzas y Tesorerí…	1.77:1	3.0:1	#000000	#0C3E3A	Fail
h3 Gestión Comercial y…	1.77:1	3.0:1	#000000	#0D3E3B	Fail
h3 Pilares de Gestión	1.77:1	3.0:1	#000000	#0D3E3B	Fail
h3 ¡Gracias por contac…	1.77:1	3.0:1	#000000	#0D3E3B	Fail
h3 Tu solicitud de serv…	1.57:1	3.0:1	#155E59	#0D3E3B	Fail
h3 ¡Recibimos tu solic…	1.77:1	3.0:1	#000000	#0D3E3B	Fail
title VÉRTICE — Soporte…	2.78:1	4.5:1	#000000	#155E59	Fail
span VÉRTICE	2.78:1	4.5:1	#000000	#155E59	Fail
span SOPORTE ADMINISTRATI…	2.78:1	4.5:1	#000000	#155E59	Fail
a Inicio	2.78:1	4.5:1	#000000	#155E59	Fail
a Servicios	2.78:1	4.5:1	#000000	#155E59	Fail
a Sobre VÉRTICE	2.78:1	4.5:1	#000000	#155E59	Fail
a Contacto	2.78:1	4.5:1	#000000	#155E59	Fail
div Tu Negocio, Con Más…	2.78:1	4.5:1	#000000	#155E59	Fail
p Brindamos soporte ad…	2.24:1	4.5:1	#000000	#114F4B	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.

Lighthouse Accessibility Audits

Score 88/100 — 3 failing, 12 passed

REVIEW

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
CONTACTO `div.container > ul.nav-links > li > a.btn`
MÓDULO `div.container > div.servicios-grid > div.area-card > div.area-subtitle`
MÓDULO `div.container > div.servicios-grid > div.area-card > div.area-subtitle`
MÓDULO `div.container > div.servicios-grid > div.area-card > div.area-subtitle`

These are opportunities to improve the legibility of your content.

Navigation

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
DATOS DE CONTACTO `div.contacto-grid > div.contacto-info > div.info-card > h4`

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

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

●Document has a `<title>` element

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

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

●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

●Touch targets have sufficient size and spacing.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

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

○Deprecated ARIA roles were not used

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

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

○`[role]` values are valid

○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

○`[aria-*]` attributes have valid values

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

○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

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

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

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

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 good alt text

All images have appropriate alt text.

Link & Button Quality

9 links, 14 buttons — all OK

PASS

9 links, 14 buttons — all OK

2 link(s) open in new tab without warning

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

Got: https://wa.me/5493585750001?text=Hola,%20quisiera%20hacer%20una%20consulta%20…; https://wa.me/5493585750001?text=Hola,%20quisiera%20hacer%20una%20consulta%20…

7 link(s) with descriptive text

9 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/5493585750001?text=Hola,%2…	Consultar por WhatsApp	new tab	Add '(opens in new tab)' to text
https://wa.me/5493585750001?text=Hola,%2…	Consultar por WhatsApp	new tab	Add '(opens in new tab)' to text

21 links and buttons have descriptive text

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

https://wa.me/5493585750001?text=Hola,%20quisiera%20hacer%20una%20consulta%20…; https://wa.me/5493585750001?text=Hola,%20quisiera%20hacer%20una%20consulta%20…

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

A+

Form Input Types

14 form control(s) checked, no type mismatches

PASS

14 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Document Language

Lang attribute set to "es"

PASS

Lang attribute set to "es"

<html lang="es"> is set and valid

Got: es

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

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.

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