Skip to content
https://cervantes.es

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-zz3pne
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
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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://cervantes.es/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://cervantes.es/manifest.json

Manifest contains invalid JSON.

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::
8 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 8 <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
11 landmarks
REVIEW
11 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Warning::
2 of 8 <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 "block-ica-bootstrap-ic-account-menu-menu" 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

B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 29 passed
REVIEW
89

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

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.dialog-off-canvas-main-canvas > div.main-container > div.row > div.col-sm-12 div.dialog-off-canvas-main-canvas > div.main-container > div.row > div.col-sm-12

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Míticas fotos de Cortázar y Borges y el original de una canción censurada, entr… div.col-xs-12 > div.card > div.card-body > h3.titulo

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.

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
SOBRE NOSOTROS div.col-6 > div.bloqFooter > p.collapsed > a
APRENDER Y ENSEÑAR div.col-6 > div.bloqFooter > p.collapsed > a
CULTURA div.col-6 > div.bloqFooter > p.collapsed > a
BIBLIOTECAS div.col-6 > div.bloqFooter > p.collapsed > a
EXÁMENES div.col-6 > div.bloqFooter > p.collapsed > a
HISPANISMO div.col-6 > div.bloqFooter > p.collapsed > a

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>`
●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.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●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
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Skip links are focusable.
○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.
○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 Hierarchy
24 headings
PASS
24 headings
Info::
Single H1 present
Info::
6 hidden heading(s) (aria-hidden)
  • H1 Instituto Cervantes
  • H2 Cursos de lengua y cultura en España
  • H3 En Granada, Toledo, Madrid y Alcalá de Henares
  • H2 Instituto Cervantes
  • H3 Noticias, convocatorias, actividades, jornadas, emisiones en directo...
  • H2 Actividades en el mundo
  • H3 Exposiciones, cine, literatura, artes, música, escena...
  • H2 Destacados
  • H3 Cursos
  • H3 Cursos hidden
  • H3 Noticias
  • H3 Noticias hidden
  • H3 Biblioteca electrónica
  • H3 Biblioteca electrónica hidden
  • H3 Publicaciones
  • H3 Publicaciones hidden
  • H3 Diplomas DELE
  • H3 Diplomas DELE hidden
  • H2 Agenda
  • H2 Noticias
  • H3 Míticas fotos de Cortázar y Borges y el original de una canción censurada, entre las obras de la muestra de Sara Facio y María Elena Walsh
  • H3 Míticas fotos de Cortázar y Borges y el original de una canción censurada, entre las obras de la muestra de Sara Facio y María Elena Walsh hidden
  • H3 Las mejores letras de canciones en español
  • H3 Legado de Gonzalo Celorio
A+
Alt Text Quality
All 18 images OK
PASS
All 18 images OK
Info::
18 image(s) with good alt text
18 images 18 good alt text
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
#edit-nametextPaísaria-label
#edit-search-universostextedit-search-universosaria-label
#selector-centroselectCentrofor/id
#emailSuscripcionemailcorreo electrónicoaria-label
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 Instituto Cervantes17.17:13.0:1
#000000
#EBE8E2
Pass
h2 Cursos de lengua y c…17.17:13.0:1
#000000
#EBE8E2
Pass
h2 Instituto Cervantes17.17:13.0:1
#000000
#EBE8E2
Pass
h2 Actividades en el mu…17.17:13.0:1
#000000
#EBE8E2
Pass
h2 Destacados17.17:13.0:1
#000000
#EBE8E2
Pass
h2 Agenda17.17:13.0:1
#000000
#EBE8E2
Pass
h2 Noticias17.17:13.0:1
#000000
#EBE8E2
Pass
h3 En Granada, Toledo, …17.17:13.0:1
#000000
#EBE8E2
Pass
h3 Noticias, convocator…17.17:13.0:1
#000000
#EBE8E2
Pass
h3 Exposiciones, cine, …17.17:13.0:1
#000000
#EBE8E2
Pass
h3 Cursos17.17:13.0:1
#000000
#EBE8E2
Pass
h3 Cursos17.17:13.0:1
#000000
#EBE8E2
Pass
h3 Noticias17.17:13.0:1
#000000
#EBE8E2
Pass
h3 Noticias17.17:13.0:1
#000000
#EBE8E2
Pass
h3 Biblioteca electrón…17.17:13.0:1
#000000
#EBE8E2
Pass
h3 Biblioteca electrón…17.17:13.0:1
#000000
#EBE8E2
Pass
h3 Publicaciones17.17:13.0:1
#000000
#EBE8E2
Pass
h3 Publicaciones17.17:13.0:1
#000000
#EBE8E2
Pass
h3 Diplomas DELE17.17:13.0:1
#000000
#EBE8E2
Pass
h3 Diplomas DELE17.17:13.0:1
#000000
#EBE8E2
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.

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

Send Feedback