https://precampamentosvider.netlify.app/canvas

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 2 REVIEW 5 FIX

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

No favicon.ico at site root

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

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

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

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

Action

7 landmarks

REVIEW

7 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

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Heading Hierarchy

13 headings, 1 skip(s)

PASS

13 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H5 (missing H3)

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

H1 Canvas Social VIDER
H2 ¿Qué es el CANVAS Social?
H2 Modelo del Canvas Social ampliado
H2 Conexión con los Campamentos Regionales 2026
H2 Ejes estratégicos
H3 Diagnóstico
H3 Co-creación
H3 Dirección
H3 Acción
H3 Medición
H2 Quíntuple hélice
H5 Navegación skipped
H5 Síguenos

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

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 4 images OK

PASS

All 4 images OK

4 image(s) with good alt text

4 images 4 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

18 links, 4 buttons — all OK

PASS

18 links, 4 buttons — all OK

6 link(s) open in new tab without warning

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

Got: assets/canvas-vider-en-blanco.pdf; assets/canvas-vider-en-blanco.pdf; https://www.youtube.com/@oirunad6715; https://www.facebook.com/share/1JHzEAK8ip/; https://www.tiktok.com/@eloirdelasregionesunad; https://x.com/ElOIRdelaRegion

12 link(s) with descriptive text

18 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
assets/canvas-vider-en-blanco.pdf	Ver modelo en blanco	new tab	Add '(opens in new tab)' to text
assets/canvas-vider-en-blanco.pdf	Ver modelo en blanco	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@oirunad6715	YouTube	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/share/1JHzEAK8i…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@eloirdelasregion…	TikTok	new tab	Add '(opens in new tab)' to text
https://x.com/ElOIRdelaRegion	X	new tab	Add '(opens in new tab)' to text

16 links and buttons have descriptive text

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

assets/canvas-vider-en-blanco.pdf; assets/canvas-vider-en-blanco.pdf; https://www.youtube.com/@oirunad6715; https://www.facebook.com/share/1JHzEAK8ip/; https://www.tiktok.com/@eloirdelasregionesunad; https://x.com/ElOIRdelaRegion

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "es"

PASS

Lang attribute set to "es"

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

Got: es

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

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

PASS

All 53 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.

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)

Element	Ratio	Required	FG	BG	Result
h1 Canvas Social VIDER	14.96:1	3.0:1	#000000	#C1DEEF	Pass
h2 ¿Qué es el CANVAS …	14.33:1	3.0:1	#000000	#BADAEC	Pass
h2 Modelo del Canvas So…	13.29:1	3.0:1	#000000	#CDCFC1	Pass
h2 Conexión con los Ca…	13.59:1	3.0:1	#000000	#DBCFB3	Pass
h2 Ejes estratégicos	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Quíntuple hélice	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Diagnóstico	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Co-creación	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Dirección	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Acción	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Medición	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Campamentos VIDER ·…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Volver al inicio	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Inicio	17.11:1	4.5:1	#000000	#DCEAF3	Pass
a Zonas CPT	16.59:1	4.5:1	#000000	#D2E8F4	Pass
a Canvas	16.10:1	4.5:1	#000000	#CDE5F3	Pass
a Formulario	15.60:1	4.5:1	#000000	#C8E2F1	Pass
p El CANVAS Social es …	13.85:1	4.5:1	#000000	#B4D7EA	Pass
p No se trata solo de …	13.41:1	4.5:1	#000000	#AFD4E8	Pass
span Ir al formulario	12.98:1	4.5:1	#000000	#AAD1E7	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.

Lighthouse Accessibility Audits

Score 92/100 — 3 failing, 17 passed

PASS

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
Ver modelo en blanco `section.canvas-hero-split > div.canvas-hero-buttons-mobile > a.hero-cpt-button > span.hero-cpt-button__text`
Lo que construyas en este taller servirá para: `body.canvas-page > section.canvas-conexion > div.section-inner > p.canvas-conexion-lead`
proceso de aprendizaje y acción reticular `section.canvas-conexion > div.section-inner > p.canvas-conexion-cierre > strong`
Nuestros ejes estratégicos orientan nuestras acciones hacia la transformación t… `body.canvas-page > section.canvas-ejes > div.section-inner > p.canvas-ejes-intro`
Red de intercambio de conocimientos. `body.canvas-page > section.canvas-helice > div.section-inner > p.canvas-helice-intro`
© 2026 VIDER. Todos los derechos reservados. `body.canvas-page > footer > div.footer-bottom > p`

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
Navegación `footer > div.footer-columns > div.footer-col > h5`

These are opportunities to improve keyboard navigation in your application.

Best practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` 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

●Image elements have `[alt]` attributes

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

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

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

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