Skip to content
https://fernandolaserna.com/prueba5/#

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
7
REVIEW
4
PASS
13
INFO
0
Checks
24
13 PASS 4 REVIEW 7 FIX
D
Mobile Keyboard & Autofill
Action
4/4 eligible field(s) missing autocomplete or inputmode
FIX
4/4 eligible field(s) missing autocomplete or inputmode
Warning::
2 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: name, email.
Got: <input type="text" name="name" id="name">, <input type="email" name="email" id="email">
Warning::
2 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, url.
Got: <input type="email" name="email" id="email">, <input type="url" name="website" id="website">
F
404 Error Page
Action
HTTP 500, custom page
FIX
HTTP 500, custom page
Warning::
Unexpected status code: HTTP 500
Expected HTTP 404 but received 500. This may confuse search engine crawlers.
Got: HTTP 500
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 500 ✗Page Title Database Error ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
No icons detected
FIX
No icons detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
Critical::
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
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV "Navegación principal" MAIN (missing!) CONTENTINFO footer

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

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

C
Heading Hierarchy
Action
35 headings, 3 skip(s)
REVIEW
35 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Tu web y tus sistemas deberían impulsar tu negocio — no frenarlo
  • H2 ¿Tu infraestructura digital frena el crecimiento de tu empresa?
  • H3 Software genérico que no encaja
  • H3 Web lenta o inestable en campañas
  • H3 Sistemas que no se hablan
  • H3 Proyectos que no llegan a buen puerto
  • H2 Software construido para operar en producción
  • H3 Páginas web y e-commerce
  • H3 Integraciones y APIs
  • H3 Desarrollo a medida
  • H3 Producto digital end-to-end
  • H2 Proyectos que sostienen negocios reales
  • H3 Farmacia Salud+
  • H3 Atlas Logística
  • H3 Vértice PropTech
  • H3 Lumen Edu
  • H2 Sin sorpresas. Solo entrega.
  • H4 Descubrimiento skipped
  • H4 Plan por escrito
  • H4 Desarrollo
  • H4 Lanzamiento
  • H2 Tecnología digital para farmacias que exigen precisión
  • H4 E-commerce farmacéutico skipped
  • H4 Gestión de inventario
  • H4 Cumplimiento normativo
  • H4 Integraciones sectoriales
  • H3 Antes y después
  • H3 Demos y prototipos
  • H2 Preguntas frecuentes
  • H2 Descubre qué frena tu plataforma — sin compromiso
  • H4 ORETANOSLAB skipped
  • H4 Secciones
  • H4 Contacto
  • H4 Ubicaciones
  • H3 Solicita tu auditoría gratuita

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

B
Mobile-Readable Font Sizes
90% of visible text renders at >= 12 CSS px (20 below threshold)
REVIEW
90% of visible text renders at >= 12 CSS px (20 below threshold)
Info::
20 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> 11.2px ("React"); <span> 11.2px ("Stripe"); <span> 11.2px ("AEMPS-ready"); <span> 11.5px ("Páginas web · Farmacia"); <span> 11.2px ("Next.js").
C
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 Tu web y tus sistemas deberían
1.05:1
#000000
on
#08080E
needs 3.0:1 (large text)
32px · above the fold
h1 — no frenarlo
1.05:1
#000000
on
#08080F
needs 3.0:1 (large text)
32px · mid-page
h2 ¿Tu infraestructura digital frena el cr…
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Software construido para operar en produ…
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Proyectos que sostienen negocios reales
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sin sorpresas. Solo entrega.
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tecnología digital para farmacias que e…
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Preguntas frecuentes
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Descubre qué frena tu plataforma — si…
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Software genérico que no encaja
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Web lenta o inestable en campañas
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Sistemas que no se hablan
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Proyectos que no llegan a buen puerto
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Páginas web y e-commerce
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Integraciones y APIs
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Desarrollo a medida
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Producto digital end-to-end
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Farmacia Salud+
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Atlas Logística
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Vértice PropTech
1.07:1
#000000
on
#0B0B14
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Tu web y tus sistema…1.05:13.0:1
#000000
#08080E
Fail
h1 — no frenarlo1.05:13.0:1
#000000
#08080F
Fail
h2 ¿Tu infraestructura…1.07:13.0:1
#000000
#0B0B14
Fail
h2 Software construido …1.07:13.0:1
#000000
#0B0B14
Fail
h2 Proyectos que sostie…1.07:13.0:1
#000000
#0B0B14
Fail
h2 Sin sorpresas. Solo …1.07:13.0:1
#000000
#0B0B14
Fail
h2 Tecnología digital …1.07:13.0:1
#000000
#0B0B14
Fail
h2 Preguntas frecuentes1.07:13.0:1
#000000
#0B0B14
Fail
h2 Descubre qué frena …1.07:13.0:1
#000000
#0B0B14
Fail
h3 Software genérico q…1.07:13.0:1
#000000
#0B0B14
Fail
h3 Web lenta o inestabl…1.07:13.0:1
#000000
#0B0B14
Fail
h3 Sistemas que no se h…1.07:13.0:1
#000000
#0B0B14
Fail
h3 Proyectos que no lle…1.07:13.0:1
#000000
#0B0B14
Fail
h3 Páginas web y e-com…1.07:13.0:1
#000000
#0B0B14
Fail
h3 Integraciones y APIs1.07:13.0:1
#000000
#0B0B14
Fail
h3 Desarrollo a medida1.07:13.0:1
#000000
#0B0B14
Fail
h3 Producto digital end…1.07:13.0:1
#000000
#0B0B14
Fail
h3 Farmacia Salud+1.07:13.0:1
#000000
#0B0B14
Fail
h3 Atlas Logística1.07:13.0:1
#000000
#0B0B14
Fail
h3 Vértice PropTech1.07:13.0:1
#000000
#0B0B14
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.

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A+
Alt Text Quality
No images
PASS
No images
Info::
No images on this page
No images on this page.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#auditTypeselectTipo de auditoría *for/id
#nametextTu nombre *for/id
#emailemailEmail *for/id
#websiteurlWeb actualfor/id
#messagetextareaCuéntanos brevemente qué te preocupa…for/id
A+
Form Input Types
5 form control(s) checked, no type mismatches
PASS
5 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
5 form control(s) checked, no input-semantic issues
PASS
5 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "es"
PASS
Lang attribute set to "es"
Info::
<html lang="es"> is set and valid
Got: es
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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
Lighthouse Accessibility Audits
Score 92/100 — 4 failing, 17 passed
PASS
92

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
Auditoría gratuita nav#navbar > ul#navLinks > li > a.nav-cta
Solicitar auditoría gratuita section#inicio > div.hero-content > div.hero-buttons > a.btn
Laboratorio de software · Madrid · desde 2012 Páginas web que convierten. Softw… footer > div.footer-grid > div.footer-col > p.footer-contact-info
Problemas habituales div.footer-col > ul > li > a
Servicios div.footer-col > ul > li > a
Proyectos div.footer-col > ul > li > a
Proceso div.footer-col > ul > li > a
División Farmacias div.footer-col > ul > li > a
hola@oretanoslab.com div.footer-col > ul > li > a
Solicitar auditoría div.footer-col > ul > li > a
FAQ div.footer-col > ul > li > a
MADRID · BARCELONA · CIUDAD DE MÉXICO Confirmamos tu consulta en menos de 48 ho… footer > div.footer-grid > div.footer-col > p.footer-contact-info
© 2026 Oretanos Lab S.L. body > footer > div.footer-bottom > span
Aviso Legal body > footer > div.footer-bottom > a
Política de Privacidad body > footer > div.footer-bottom > a
Política de Cookies body > footer > div.footer-bottom > a

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
Descubrimiento div.container > div.process-timeline > div.process-step > h4
E-commerce farmacéutico div.container > div.farma-services-grid > div.farma-service-card > h4
ORETANOSLAB footer > div.footer-grid > div.footer-col > 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.

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
ORETANOS LAB body > nav#navbar > a.nav-logo
○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`[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
○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.
○Image elements have `[alt]` attributes
○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
○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.
○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.

Send Feedback