Skip to content
https://ucm.es

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
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.

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
27 landmarks
REVIEW
27 landmarks
Info::
<main> landmark present
Info::
8 <nav> landmark(s) found
Warning::
8 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 MAIN ASIDE 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
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Universidad Complutense de Madrid ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 2 pass AA only
span Desplegar navegación
3.31:1
#000000
on
#326771
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

1 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 Carrousel - Titulare…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Carrousel - Noticias…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Carrousel - Noticias…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Noticias21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Estudia con nosotros21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Recursos21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Imagen destacada21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Destacados21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Más Destacados21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Mapa Web21.00:13.0:1
#000000
#FFFFFF
Pass
h3 La Universidad Compl…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Estudiar21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Investigar21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Internacional21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Vida Universitaria21.00:13.0:1
#000000
#FFFFFF
Pass
title Universidad Complute…21.00:14.5:1
#000000
#FFFFFF
Pass
a Universidad Complute…21.00:14.5:1
#000000
#FFFFFF
Pass
span Desplegar navegació…3.31:14.5:1
#000000
#326771
Fail
a Navegar identificado5.54:14.5:1
#000000
#3A8F95
Pass
label Buscar en la web5.44:14.5:1
#000000
#A27589
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 29 passed
REVIEW
88

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 parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
¡Un sábado de matemáticas y talento! Casi 4.000 jóvenes -de entre 10 y 17 años … div.news-flex > section#zona_1_3 > div#carouselUcm > div.carousel-inner

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
¡Un sábado de matemáticas y talento! Casi 4.000 jóvenes -de entre 10 y 17 años … div.news-flex > section#zona_1_3 > div#carouselUcm > div.carousel-inner

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.

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
¡Un sábado de matemáticas y talento! Casi 4.000 jóvenes -de entre 10 y 17 años … div.carousel-inner > article.item > div.news1_txt > h3

These are opportunities to improve keyboard navigation in your application.

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
Defensora Universitaria li > ul > li > a
Inspección de Servicios li > ul > li > a
Fundación General nav#pie_1 > ul > li#75 > a
Universia España nav#pie_1 > ul > li#12 > a
Empleo UCM nav#pie_1 > ul > li#175 > a
Alquiler de espacios nav#pie_1 > ul > li#1206 > a
Parque Científico nav#pie_1 > ul > li#3197 > a
Sugerencias y Quejas nav#pie_1 > ul > li#1361 > a
Localización y contacto nav#pie_contacto > ul > li > a
Aviso Legal nav#pie_contacto > ul > li > a
Protección de datos nav#pie_contacto > ul > li > a
RSS nav#pie_contacto > ul > li > 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>`
●`[role]`s have all required `[aria-*]` attributes
●`[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
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●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
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○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
32 headings
PASS
32 headings
Info::
Single H1 present
  • H1 Universidad Complutense de Madrid
  • H2 Carrousel - Titulares
  • H3 ¡Un sábado de matemáticas y talento! Casi 4.000 jóvenes -de entre 10 y 17 años - brillan en el Concurso de Primavera en la Complutense
  • H3 MicroMundo, el proyecto complutense que lleva una década involucrando a jóvenes en la búsqueda de nuevos antibióticos en el suelo
  • H3 Semana de las Letras 2026, la fiesta de los amantes de las palabras
  • H3 Abierto el plazo del Concurso de Ideas para la transformación de Ciudad Universitaria
  • H2 Carrousel - Noticias secundarias 1
  • H3 ¡Inscríbete!
  • H3 Prevención de Riesgos Laborales
  • H2 Carrousel - Noticias secundarias 2
  • H3 Elecciones 2026: procesos en curso
  • H3 Consulta de resultados provisionales
  • H2 Noticias
  • H2 Agenda
  • H2 Estudia con nosotros
  • H3 Cultura Complutense
  • H3 Investigación UCM
  • H3 Deporte UCM
  • H2 Recursos
  • H2 Imagen destacada
  • H3 Competiciones deportivas
  • H2 Destacados
  • H3 Unidad de Cultura Científica UCM
  • H3 Complutense Saludable
  • H3 Fundación Complutense
  • H2 Más Destacados
  • H2 Mapa Web
  • H3 La Universidad Complutense
  • H3 Estudiar
  • H3 Investigar
  • H3 Internacional
  • H3 Vida Universitaria
A+
Alt Text Quality
All 54 images OK
PASS
All 54 images OK
Info::
2 image(s) with alt text over 125 characters
Info::
18 decorative image(s) correctly marked
Info::
34 image(s) with good alt text
54 images 34 good alt text 18 decorative
IssueCount
too long2 image(s)
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#searchsearchBuscar en la webfor/id
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /themes/ucm24/css/print.css?ft=20260421140505
Print Stylesheet ✓ Print Optimized
Print stylesheet /themes/ucm24/css/print.css?ft=20260421140505 ✓Inline @media print Not detected ✗
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback