Skip to content
https://canalcaribe.com.mx

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
7
REVIEW
8
PASS
9
INFO
0
Checks
24
9 PASS 8 REVIEW 7 FIX
D
Landmark Structure
Action
6 landmarks
FIX
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <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 (missing!) ASIDE 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

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

F
404 Error Page
Action
HTTP 429, bare page
FIX
HTTP 429, bare page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 429 ✗Page Title 429 Too Many Requests ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
39 headings, 2 skip(s)
REVIEW
39 headings, 2 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 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Canal Caribe
  • H2 Última entrada
  • H4 Cáncer de mama en Quintana Roo: puede estar ahí antes de que puedas sentirlo skipped
  • H4 Leona Vicario abre una disputa por tierra, dinero y control ejidal
  • H4 Tribunal suspende cobro del SAT contra Roberto Borge
  • H4 Aumento al DNR en 2027: hoteleros cuestionan el cobro y Gobierno defiende su destino
  • H4 Nuevas rutas MOBI en Cancún: 100 autobuses se suman al transporte público
  • H5 Cáncer de mama en Quintana Roo: puede estar ahí antes de que puedas sentirlo
  • H5 Leona Vicario abre una disputa por tierra, dinero y control ejidal
  • H5 Tribunal suspende cobro del SAT contra Roberto Borge
  • H5 Aumento al DNR en 2027: hoteleros cuestionan el cobro y Gobierno defiende su destino
  • H5 EU levanta muro… con 24 mil agentes; detienen a 10 mil migrantes al día, esta semana
  • H5 México recupera de NY ‘el monstruo de la tierra’, la pieza Olmeca más buscada
  • H5 Concluyen mural con rostros de desaparecidos; hablan de posible recompensa por esposa de taquero
  • H5 NFL anuncia los cinco partidos internacionales para 2023 (Video)
  • H5 Cáncer de mama en Quintana Roo: puede estar ahí antes de que puedas sentirlo
  • H5 Leona Vicario abre una disputa por tierra, dinero y control ejidal
  • H5 Tribunal suspende cobro del SAT contra Roberto Borge
  • H5 Aumento al DNR en 2027: hoteleros cuestionan el cobro y Gobierno defiende su destino
  • H4 Cáncer de mama en Quintana Roo: puede estar ahí antes de que puedas sentirlo
  • H4 Leona Vicario abre una disputa por tierra, dinero y control ejidal
  • H4 Tribunal suspende cobro del SAT contra Roberto Borge
  • H4 Aumento al DNR en 2027: hoteleros cuestionan el cobro y Gobierno defiende su destino
  • H4 Nuevas rutas MOBI en Cancún: 100 autobuses se suman al transporte público
  • H4 Alexa Murguía va por el Distrito 03 tras quedar en los últimos lugares de la encuesta estatal
  • H4 Efecto Bolsonaro en Brasil: la bolsa se dispara 7.7% tras la primera vuelta
  • H4 Nueva ley catastral avanza en el Congreso: Monreal descarta aumento al predial
  • H4 Precio del petróleo sigue bajo presión por la guerra con Irán y la crisis en Ormuz
  • H4 Cae “El Tanque”, operador regional del CJNG ligado al ataque contra helicóptero militar
  • H2 Paginación de entradas
  • H3 Canal Caribe
  • H2 Noticias recientes
  • H2 Comentarios recientes
  • H6 El dólar HOY skipped
  • H4 Más contenido...
  • H4 Cáncer de mama en Quintana Roo: puede estar ahí antes de que puedas sentirlo
  • H4 Leona Vicario abre una disputa por tierra, dinero y control ejidal
  • H4 Tribunal suspende cobro del SAT contra Roberto Borge
  • H4 Aumento al DNR en 2027: hoteleros cuestionan el cobro y Gobierno defiende su destino

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

C
Alt Text Quality
Action
8 of 48 images have issues
REVIEW
8 of 48 images have issues
Critical::
8 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
7 decorative image(s) correctly marked
Info::
33 image(s) with good alt text
48 images 33 good alt text 7 decorative 8 missing
IssueCount
missing8 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 3 controls have issues
REVIEW
2 of 3 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s">; <input type="search" name="s">
Info::
1 control(s) properly labeled
3 controls
1 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#wp-block-search__input-1searchBuscarfor/id
ssearch(Buscar)placeholder only
ssearch(Buscar)placeholder only

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

<input type="search" name="s">; <input type="search" name="s">

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

B
Tap Target Adequacy
3 tap target(s) too small or too close together
REVIEW
3 tap target(s) too small or too close together
Info::
3 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
C
Mobile-Readable Font Sizes
Action
79% of visible text renders at >= 12 CSS px (24 below threshold)
REVIEW
79% of visible text renders at >= 12 CSS px (24 below threshold)
Warning::
24 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: <a> 10.0px ("Salud"); <a> 10.0px ("Sin categoría"); <a> 10.0px ("Quintana Roo"); <a> 10.0px ("Turismo"); <a> 10.0px ("Cancún").
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) 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::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 12 fail WCAG AA
REVIEW

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

8 pass 12 fail WCAG AA
title Canal Caribe - Los temas que sí importa…
1.62:1
#000000
on
#202F5B
needs 4.5:1 (normal text)
16px · top of page (header area)
a Saltar al contenido
1.62:1
#000000
on
#202F5B
needs 4.5:1 (normal text)
16px · top of page (header area)
li Mar. Oct 20th, 2026
1.62:1
#000000
on
#202F5B
needs 4.5:1 (normal text)
16px · top of page (header area)
span 3:25:15 PM
1.35:1
#000000
on
#0E1F57
needs 4.5:1 (normal text)
16px · top of page (header area)
a Canal Caribe
1.40:1
#000000
on
#0D2160
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
p Los temas que sí importan
1.32:1
#000000
on
#0E1F4C
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Quintana Roo
1.33:1
#000000
on
#0F204C
needs 4.5:1 (normal text)
16px · above the fold
a Cancún
1.33:1
#000000
on
#0F204D
needs 4.5:1 (normal text)
16px · above the fold
a Chetumal
1.38:1
#000000
on
#0E2254
needs 4.5:1 (normal text)
16px · above the fold
a Cozumel
1.34:1
#000000
on
#0E2051
needs 4.5:1 (normal text)
16px · above the fold
a Holbox
1.49:1
#000000
on
#192955
needs 4.5:1 (normal text)
16px · above the fold
a Isla Mujeres
1.62:1
#000000
on
#202F5B
needs 4.5:1 (normal text)
16px · above the fold

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Última entrada18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Paginación de entra…18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Noticias recientes18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Comentarios reciente…18.10:13.0:1
#000000
#EEEEEE
Pass
h3 Canal Caribe18.10:13.0:1
#000000
#EEEEEE
Pass
title Canal Caribe - Los t…1.62:14.5:1
#000000
#202F5B
Fail
a Saltar al contenido1.62:14.5:1
#000000
#202F5B
Fail
li Mar. Oct 20th, 20261.62:14.5:1
#000000
#202F5B
Fail
span 3:25:15 PM1.35:14.5:1
#000000
#0E1F57
Fail
a Canal Caribe1.40:14.5:1
#000000
#0D2160
Fail
p Los temas que sí im…1.32:14.5:1
#000000
#0E1F4C
Fail
a Quintana Roo1.33:14.5:1
#000000
#0F204C
Fail
a Cancún1.33:14.5:1
#000000
#0F204D
Fail
a Chetumal1.38:14.5:1
#000000
#0E2254
Fail
a Cozumel1.34:14.5:1
#000000
#0E2051
Fail
a Holbox1.49:14.5:1
#000000
#192955
Fail
a Isla Mujeres1.62:14.5:1
#000000
#202F5B
Fail
a Playa del Carmen21.00:14.5:1
#000000
#FFFFFF
Pass
a Puerto Morelos21.00:14.5:1
#000000
#FFFFFF
Pass
a Tulum21.00:14.5:1
#000000
#FFFFFF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

C
Lighthouse Accessibility Audits
Action
Score 77/100 — 7 failing, 24 passed
REVIEW
77

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.

ARIA

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Últimas div#exTab2 > ul.nav > li.nav-item > a.nav-link
Populares div#exTab2 > ul.nav > li.nav-item > a.nav-link
Tendencias div#exTab2 > ul.nav > li.nav-item > a.nav-link

These are opportunities to improve the usage of ARIA in your application which 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
QUINTANA ROO div.small-post > div.small-post-content > div.mg-blog-category > a.newsup-categories
QUINTANA ROO div.mg-blog-post-box > article.small > div.mg-blog-category > a.newsup-categories
QUINTANA ROO div.mg-blog-post-box > article.small > div.mg-blog-category > a.newsup-categories
344 div.col-md-12 > nav.navigation > div.nav-links > a.page-numbers
7 days ago div#cff_109399618814919_1077104948718065 > div.cff-author > div.cff-author-text > p.cff-date
2 weeks ago div#cff_109399618814919_1070792276015999 > div.cff-author > div.cff-author-text > p.cff-date
2 weeks ago div#cff_109399618814919_1070765409352019 > div.cff-author > div.cff-author-text > p.cff-date
Ver todas las entradas en Quintana Roo div.mg-blog-post-3 > div.mg-blog-inner > div.mg-blog-category > a.newsup-categories

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
EL DÓLAR HOY div#sidebar-right > div#ccc_currency_converter_calculator-3 > div.mg-wid-title > h6.wtitle

These are opportunities to improve keyboard navigation in your application.

Names and labels

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
div#cff_109399618814919_1070792276015999 > div.cff-post-text > span.cff-text > img.cff-linebreak div#cff_109399618814919_1070792276015999 > div.cff-post-text > span.cff-text > img.cff-linebreak
div#cff_109399618814919_1070792276015999 > div.cff-post-text > span.cff-text > img.cff-linebreak div#cff_109399618814919_1070792276015999 > div.cff-post-text > span.cff-text > img.cff-linebreak
div#cff_109399618814919_1070792276015999 > div.cff-post-text > span.cff-text > img.cff-linebreak div#cff_109399618814919_1070792276015999 > div.cff-post-text > span.cff-text > img.cff-linebreak
div#cff_109399618814919_1070792276015999 > div.cff-post-text > span.cff-text > img.cff-linebreak div#cff_109399618814919_1070792276015999 > div.cff-post-text > span.cff-text > img.cff-linebreak
div#cff_109399618814919_1070765409352019 > div.cff-post-text > span.cff-text > img.cff-linebreak div#cff_109399618814919_1070765409352019 > div.cff-post-text > span.cff-text > img.cff-linebreak
div#cff_109399618814919_1070765409352019 > div.cff-post-text > span.cff-text > img.cff-linebreak div#cff_109399618814919_1070765409352019 > div.cff-post-text > span.cff-text > img.cff-linebreak
div#cff_109399618814919_1070765409352019 > div.cff-post-text > span.cff-text > img.cff-linebreak div#cff_109399618814919_1070765409352019 > div.cff-post-text > span.cff-text > img.cff-linebreak
div#cff_109399618814919_1070765409352019 > div.cff-post-text > span.cff-text > img.cff-linebreak div#cff_109399618814919_1070765409352019 > div.cff-post-text > span.cff-text > img.cff-linebreak

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.col-md-6 > ul.mg-social > li > a div.col-md-6 > ul.mg-social > li > a
div.col-md-6 > ul.mg-social > li > a div.col-md-6 > ul.mg-social > li > a
div.row > div.col-md-9 > div.header-ads > a.pull-right div.row > div.col-md-9 > div.header-ads > a.pull-right
nav.navbar > div.container-fluid > div.m-header > a.mobilehomebtn nav.navbar > div.container-fluid > div.m-header > a.mobilehomebtn
div.container-fluid > div.m-header > div.dropdown > a#dropdownMenuLink div.container-fluid > div.m-header > div.dropdown > a#dropdownMenuLink
nav.navbar > div.container-fluid > div.m-header > a.btn-bell nav.navbar > div.container-fluid > div.m-header > a.btn-bell
div.owl-item > div.item > div.mg-blog-post > a.link-div div.owl-item > div.item > div.mg-blog-post > a.link-div
div.owl-item > div.item > div.mg-blog-post > a.link-div div.owl-item > div.item > div.mg-blog-post > a.link-div
div.owl-item > div.item > div.mg-blog-post > a.link-div div.owl-item > div.item > div.mg-blog-post > a.link-div
div.owl-item > div.item > div.mg-blog-post > a.link-div div.owl-item > div.item > div.mg-blog-post > a.link-div
div.owl-item > div.item > div.mg-blog-post > a.link-div div.owl-item > div.item > div.mg-blog-post > a.link-div
div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div
div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div
div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div
div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div
div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div
div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div
div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div
div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div
div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div
div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div div.mg-blog-post-box > div.col-12 > div.mg-post-thumb > a.link-div
div.col-md-12 > nav.navigation > div.nav-links > a.next div.col-md-12 > nav.navigation > div.nav-links > a.next
Canal Caribe div#cff_109399618814919_1077104948718065 > div.cff-author > div.cff-author-img > a
Canal Caribe div#cff_109399618814919_1070792276015999 > div.cff-author > div.cff-author-img > a
Canal Caribe div#cff_109399618814919_1070765409352019 > div.cff-author > div.cff-author-img > a
div#sidebar-right > div#block-10 > figure.wp-block-image > a div#sidebar-right > div#block-10 > figure.wp-block-image > a
div.row > div.col-lg-3 > div.mg-blog-post-3 > a.link-div div.row > div.col-lg-3 > div.mg-blog-post-3 > a.link-div
div.row > div.col-lg-3 > div.mg-blog-post-3 > a.link-div div.row > div.col-lg-3 > div.mg-blog-post-3 > a.link-div
div.row > div.col-lg-3 > div.mg-blog-post-3 > a.link-div div.row > div.col-lg-3 > div.mg-blog-post-3 > a.link-div
div.row > div.col-lg-3 > div.mg-blog-post-3 > a.link-div div.row > div.col-lg-3 > div.mg-blog-post-3 > a.link-div
div.col-md-6 > ul.mg-social > li > a div.col-md-6 > ul.mg-social > li > a
div.col-md-6 > ul.mg-social > li > a div.col-md-6 > ul.mg-social > li > a
div.row > div.col-md-12 > p > a div.row > div.col-md-12 > p > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.mg-blog-inner > div.mg-blog-meta > span.mg-blog-date > a div.mg-blog-inner > div.mg-blog-meta > span.mg-blog-date > a
div.mg-blog-inner > div.mg-blog-meta > span.mg-blog-date > a div.mg-blog-inner > div.mg-blog-meta > span.mg-blog-date > a
div.mg-blog-post-3 > div.mg-blog-inner > div.mg-blog-meta > a.auth div.mg-blog-post-3 > div.mg-blog-inner > div.mg-blog-meta > a.auth

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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes 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.
●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
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Skip links are focusable.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●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 an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○No form fields have multiple labels
○`<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.
○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.
○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.
A+
Heading Text Quality
All 39 heading(s) have substantive, well-formed text
PASS
All 39 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Form Input Types
3 form control(s) checked, no type mismatches
PASS
3 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
3 form control(s) checked, no input-semantic issues
PASS
3 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "es"
PASS
Lang attribute set to "es"
Info::
<html lang="es"> is set and valid
Got: es
A+
Tabindex Anti-Patterns
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback