Accessibility

F

Heading Hierarchy

Action

21 headings, 5 skip(s)

FIX

21 headings, 5 skip(s)

Multiple H1 headings (3 found)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

2 empty heading(s)

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

H1 El Valor de mi Sitio Web
H4 Calcule rápidamente el valor estimado de su sitio web y cree informes de SEO en PDF. skipped
H1 El Valor de mi Sitio Web duplicate H1
H4 Calcule rápidamente el valor estimado de su sitio web y cree informes de SEO en PDF. skipped
H1 El Valor de mi Sitio Web duplicate H1
H4 Calcule rápidamente el valor estimado de su sitio web y cree informes de SEO en PDF. skipped
H4 (empty)
H2 Sitios Populares
H4 Google.com skipped
H4 Facebook.com
H4 Youtube.com
H4 (empty)
H2 Sitios Recientes
H4 Engage.it skipped
H4 Aiseomate.com
H4 Bancaditalia.it
H4 Ilquotidianodellazio.it
H4 Zazoom.it
H4 Findkey-movie.com
H4 Ingresar
H4 Registrarse

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

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

Link & Button Quality

Action

5 issue(s) across 55 links and 9 buttons

FIX

5 issue(s) across 55 links and 9 buttons

3 link(s) with no accessible text

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

Got: https://www.facebook.com/alexynior; https://x.com/alexynior15; https://www.youtube.com/@AlexisJunior

9 link(s) open in new tab without warning

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

Got: http://google.com; http://facebook.com; http://youtube.com; http://engage.it; http://aiseomate.com; http://bancaditalia.it; http://ilquotidianodellazio.it; http://zazoom.it; http://findkey-movie.com

2 button(s) with no accessible text

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

Got: button.btn (#105 on page); button.btn (#131 on page)

43 link(s) with descriptive text

55 links

3 empty

0 generic text

9 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
http://google.com	Visitar	new tab	Add '(opens in new tab)' to text
http://facebook.com	Visitar	new tab	Add '(opens in new tab)' to text
http://youtube.com	Visitar	new tab	Add '(opens in new tab)' to text
http://engage.it	Visitar	new tab	Add '(opens in new tab)' to text
http://aiseomate.com	Visitar	new tab	Add '(opens in new tab)' to text
http://bancaditalia.it	Visitar	new tab	Add '(opens in new tab)' to text
http://ilquotidianodellazio.it	Visitar	new tab	Add '(opens in new tab)' to text
http://zazoom.it	Visitar	new tab	Add '(opens in new tab)' to text
http://findkey-movie.com	Visitar	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/alexynior	(empty)	empty	Add link text or aria-label
https://x.com/alexynior15	(empty)	empty	Add link text or aria-label
https://www.youtube.com/@AlexisJunior	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

50 links and buttons have descriptive text

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

https://www.facebook.com/alexynior; https://x.com/alexynior15; https://www.youtube.com/@AlexisJunior

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.

http://google.com; http://facebook.com; http://youtube.com; http://engage.it; http://aiseomate.com; http://bancaditalia.it; http://ilquotidianodellazio.it; http://zazoom.it; http://findkey-movie.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.btn (#105 on page); button.btn (#131 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

Mobile Keyboard & Autofill

Action

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

FIX

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

5 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: username, current-password, email.

Got: <input type="text" name="username">, <input type="password" name="password">, <input type="text" name="username">, <input type="text" name="email">, <input type="password" name="password">

F

Document Language

Action

Missing <html lang> attribute (WCAG 3.1.1)

FIX

Missing <html lang> attribute (WCAG 3.1.1)

Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.

F

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-htx8xr

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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

F

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://elvalordemiweb.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://elvalordemiweb.com/manifest.json

Manifest contains invalid JSON.

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

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

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 63/100 — 7 failing, 12 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.

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.row > div.input-group > div.input-group-btn > button.btn `div.row > div.input-group > div.input-group-btn > button.btn`

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
center > div > div > img.imageres `center > div > div > img.imageres`
div.container > center > div > img.imageres `div.container > center > div > img.imageres`

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.container > div.row > div.none > a.ultm `div.container > div.row > div.none > a.ultm`
div.container > div.row > div.none > a.ultm `div.container > div.row > div.none > a.ultm`
div.container > div.row > div.none > a.ultm `div.container > div.row > div.none > a.ultm`

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
Visitar `div.thumbnail > div.caption > p > a.btn`
Ver Detalles `div.thumbnail > div.caption > p > a.btn`
Visitar `div.thumbnail > div.caption > p > a.btn`
Ver Detalles `div.thumbnail > div.caption > p > a.btn`
Visitar `div.thumbnail > div.caption > p > a.btn`
Ver Detalles `div.thumbnail > div.caption > p > a.btn`
Visitar `div.thumbnail > div.caption > p > a.btn`
Ver Detalles `div.thumbnail > div.caption > p > a.btn`
Visitar `div.thumbnail > div.caption > p > a.btn`
Ver Detalles `div.thumbnail > div.caption > p > a.btn`
Visitar `div.thumbnail > div.caption > p > a.btn`
Ver Detalles `div.thumbnail > div.caption > p > a.btn`
Visitar `div.thumbnail > div.caption > p > a.btn`
Ver Detalles `div.thumbnail > div.caption > p > a.btn`
Visitar `div.thumbnail > div.caption > p > a.btn`
Ver Detalles `div.thumbnail > div.caption > p > a.btn`
Visitar `div.thumbnail > div.caption > p > a.btn`
Ver Detalles `div.thumbnail > div.caption > p > a.btn`

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
Calcule rápidamente el valor estimado de su sitio web y cree informes de SEO en… `div#myhome > div.container > div.row > h4`
Google.com `div.col-md-4 > div.thumbnail > div.caption > h4`
Engage.it `div.col-md-4 > div.thumbnail > div.caption > h4`

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

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

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

●`[role]` values are valid

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

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

●Document has a `<title>` element

●Links are distinguishable without relying on color.

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●Identical links have the same purpose.

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

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted 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

○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 a valid value for its `[lang]` attribute

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

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

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

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

○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

No <main> landmark found

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

1 <nav> landmark(s) found

No banner (header) landmark

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

B

Alt Text Quality

2 of 12 images have issues

REVIEW

2 of 12 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

10 image(s) with good alt text

12 images 10 good alt text 2 missing

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

B

Form Accessibility

2 of 8 controls have issues

REVIEW

2 of 8 controls have issues

2 control(s) rely on placeholder only

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

Got: <input type="text" name="url" id="url">; <input type="text" name="cap_url" id="cap_url">

6 control(s) properly labeled

8 controls

6 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
username	text	Usuario	none
password	password	Contrase�a	none
username	text	Usuario	none
email	text	Email	none
full	text	Nombres	none
password	password	Contrase�a	none
#url	text	(Introduce tu dominio....)	placeholder only
#cap_url	text	(Introduce tu dominio....)	placeholder only

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

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA 12 pass AA only

div Por favor, espere... Analizando su sitio…

3.45:1

#FFFFFF

on

#4F8BDE

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 El Valor de mi Sitio…	5.73:1	3.0:1	#000000	#4586DF	Pass
h1 El Valor de mi Sitio…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 El Valor de mi Sitio…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Sitios Populares	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Sitios Recientes	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Calcula el Valor de …	20.06:1	4.5:1	#000000	#F7FAFE	Pass
span Toggle navigation	20.06:1	4.5:1	#000000	#F7FAFE	Pass
a Inicio	5.30:1	4.5:1	#000000	#3B80DB	Pass
a Sitios Principales	5.31:1	4.5:1	#000000	#3B80DC	Pass
a Contacto	5.39:1	4.5:1	#000000	#3C81DE	Pass
a Acerca de	5.24:1	4.5:1	#000000	#3A7FDB	Pass
a Politica privacidad	5.46:1	4.5:1	#000000	#3D82DF	Pass
a Condiciones servicio	5.24:1	4.5:1	#000000	#3C7FDA	Pass
a Ingresar	5.52:1	4.5:1	#000000	#3E83DF	Pass
a Registrarse	5.57:1	4.5:1	#000000	#4084DE	Pass
h4 Calcule rápidamente…	3.42:1	3.0:1	#FFFFFF	#4B8CE1	Pass
div Por favor, espere...…	3.45:1	4.5:1	#FFFFFF	#4F8BDE	Fail
div Crea tu página web …	6.44:1	4.5:1	#000000	#5290E1	Pass
a CLIC AQUÍ	5.39:1	4.5:1	#000000	#3C81DE	Pass
div Consigue un enlace d…	5.39:1	4.5:1	#000000	#3C81DE	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+

Heading Text Quality

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

PASS

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

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

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "email" should use type="email" (currently type="text")

Field name "email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.

A

Form Input Quality

1 input-semantic issue(s) across 8 form control(s)

PASS

1 input-semantic issue(s) across 8 form control(s)

2 password field(s) missing or with invalid `autocomplete`

Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="password">, <input type="password" name="password">.

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+

Mobile-Readable Font Sizes

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

PASS

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

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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

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