Skip to content
https://quimoratech.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
6
REVIEW
4
PASS
14
INFO
0
Checks
24
14 PASS 4 REVIEW 6 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: email, tel.
Got: <input type="email" id="cf-email">, <input type="tel" id="cf-phone">
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, tel.
Got: <input type="email" id="cf-email">, <input type="tel" id="cf-phone">
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
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'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ 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::
5 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 5 <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.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 header NAV MAIN CONTENTINFO footer

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
Tabindex Anti-Patterns
Action
0 positive, 7 -1-on-focusable
REVIEW
0 positive, 7 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button id="tab-gestion">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="tab-a-medida">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="showcase-tab-menu">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="showcase-tab-producto">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="showcase-tab-carrito">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="showcase-tab-ubicacion">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="showcase-tab-movil">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
B
Mobile-Readable Font Sizes
97% of visible text renders at >= 12 CSS px (6 below threshold)
REVIEW
97% of visible text renders at >= 12 CSS px (6 below threshold)
Info::
6 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> 8.0px ("diosascali.com"); <span> 8.0px ("diosascali.com"); <span> 8.0px ("diosascali.com"); <span> 8.0px ("diosascali.com"); <span> 8.0px ("diosascali.com").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Quimora Tech · Páginas Web que Convierten Visitantes en Clientes ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
A+
Heading Hierarchy
60 headings
PASS
60 headings
Info::
Single H1 present
  • H1 Páginas Web que Convierten tus Visitantes en Clientes Reales
  • H2 Cada día sin una web que venda, pierdes dinero
  • H3 Nadie te encuentra en Google
  • H3 Una web lenta espanta clientes
  • H3 Visitas que no se convierten
  • H3 Tu competencia te adelanta
  • H2 Cada decisión está hecha para hacerte crecer
  • H3 Diseño Mobile-First que Convierte
  • H3 Velocidad de Carga Ultra-Rápida
  • H3 SEO que te Posiciona en Google
  • H3 Gestión Sencilla y Analítica Integrada
  • H2 Desarrollamos soluciones de software a la medida
  • H3 Sitios web corporativos
  • H3 Landing pages
  • H3 Tiendas online (eCommerce)
  • H3 Reservas y citas
  • H3 Sistemas administrativos
  • H3 Paneles de gestión
  • H3 Sistemas de inventario
  • H3 Control de ventas, caja y cotizaciones
  • H3 Portales para clientes
  • H3 Plataformas web personalizadas
  • H3 Automatización de procesos
  • H3 Integraciones con APIs
  • H3 Soluciones con inteligencia artificial
  • H3 Aplicaciones web escalables
  • H3 Cuéntanos tu idea y desarrollamos la solución tecnológica que tu negocio necesita
  • H2 No te contamos que sabemos hacerlo. Te lo mostramos.
  • H3 Diosa's Make up
  • H3 Recorre el sitio por dentro
  • H3 Compruébalo tú mismo
  • H2 Crecer es Simple
  • H3 Diagnóstico
  • H3 Desarrollo
  • H3 Lanzamiento
  • H3 Crecimiento Continuo
  • H3 Diagnóstico
  • H3 Desarrollo
  • H3 Lanzamiento
  • H3 Crecimiento Continuo
  • H2 Especialistas en
  • H3 Ecommerce
  • H3 Sistemas de inventario
  • H3 Control de ventas, caja y cotizaciones
  • H3 Integraciones y automatizaciones
  • H2 ¿Cuál es tu caso?
  • H2 Descubre la mejor solución para tu negocio en menos de 2 minutos
  • H2 Una inversión que se paga sola
  • H3 Emprendedor
  • H3 Presencia
  • H3 Crecimiento
  • H3 A Medida
  • H3 ¿Ya tienes tu web funcionando?
  • H2 Preguntas Frecuentes
  • H2 Cuéntanos sobre tu proyecto
  • H2 No Dejes que tu Competencia te Pase Adelante
  • H3 Navegación
  • H3 Empresa
  • H3 Soluciones por industria
  • H3 Contacto
A+
Heading Text Quality
All 60 heading(s) have substantive, well-formed text
PASS
All 60 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 9 images OK
PASS
All 9 images OK
Info::
2 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
9 images 7 good alt text 2 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 4 controls labeled
PASS
All 4 controls labeled
Info::
4 control(s) properly labeled
4 controls
4 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cf-nametextNombre *for/id
#cf-emailemailEmail *for/id
#cf-phonetelTeléfono (opcional)for/id
#cf-messagetextareaMensaje *for/id
A+
Form Input Types
4 form control(s) checked, no type mismatches
PASS
4 form control(s) checked, no type mismatches
Info::
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
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+
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+
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)
ElementRatioRequiredFGBGResult
h1 Páginas Web que Con…18.29:13.0:1
#000000
#EFEFF1
Pass
h1 tus Visitantes en Cl…18.29:13.0:1
#000000
#EFEFF1
Pass
h2 Cada día sin una we…18.29:13.0:1
#000000
#EFEFF1
Pass
h2 Cada decisión está…18.29:13.0:1
#000000
#EFEFF1
Pass
h2 Desarrollamos soluci…18.29:13.0:1
#000000
#EFEFF1
Pass
h2 No te contamos que s…18.29:13.0:1
#000000
#EFEFF1
Pass
h2 Crecer es Simple18.29:13.0:1
#000000
#EFEFF1
Pass
h2 Especialistas en18.29:13.0:1
#000000
#EFEFF1
Pass
h2 ¿Cuál es tu caso?18.29:13.0:1
#000000
#EFEFF1
Pass
h2 Descubre la mejor so…18.29:13.0:1
#000000
#EFEFF1
Pass
h2 Una inversión que s…18.29:13.0:1
#000000
#EFEFF1
Pass
h2 Preguntas Frecuentes18.29:13.0:1
#000000
#EFEFF1
Pass
h2 Cuéntanos sobre tu …18.29:13.0:1
#000000
#EFEFF1
Pass
h2 No Dejes que tu Comp…18.29:13.0:1
#000000
#EFEFF1
Pass
h3 Nadie te encuentra e…18.29:13.0:1
#000000
#EFEFF1
Pass
h3 Una web lenta espant…18.29:13.0:1
#000000
#EFEFF1
Pass
h3 Visitas que no se co…18.29:13.0:1
#000000
#EFEFF1
Pass
h3 Tu competencia te ad…18.29:13.0:1
#000000
#EFEFF1
Pass
h3 Diseño Mobile-First…18.29:13.0:1
#000000
#EFEFF1
Pass
h3 Velocidad de Carga U…18.29:13.0:1
#000000
#EFEFF1
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 94/100 — 2 failing, 31 passed
PASS
94

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
diosascali.com div.absolute > div.absolute > div.flex > span.ml-[2.5%]
HABLEMOS div.mx-auto > div.grid > div > span.inline-flex
(opcional) div.grid > div > label.font-display > span.text-muted-foreground

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SEMANA 1 Diagnóstico Escuchamos tus metas, analizamos tu competencia y defini… main#main > section#nosotros > div.mx-auto > ol.relative

These are opportunities to improve the experience of reading tabular or list data using 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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○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