Skip to content
https://uam.es

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
13
6 PASS 2 REVIEW 5 FIX
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
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.
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Universidad Autónoma de Madrid ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA 2 pass AA only
h1 Universidad Autónoma de Madrid - UAM
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
32px · bottom of viewport
h2 COMUNICADOS
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Actualidad UAM
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Noticias científicas
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 EVENTOS
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Conoce los datos de la UAM, la universid…
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 La UAM ante las crisis humanitarias
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 CURSOS DE CORTA DURACIÓN Y MICROCREDENC…
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 [CON]ecta con el planeta
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 COMUNICADOS
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 LA UAM EN CIFRAS
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Universidad Autónom…1.14:13.0:1
#000000
#141414
Fail
h2 COMUNICADOS1.14:13.0:1
#000000
#141414
Fail
h2 Actualidad UAM1.14:13.0:1
#000000
#141414
Fail
h2 Noticias científica…1.14:13.0:1
#000000
#141414
Fail
h2 EVENTOS1.14:13.0:1
#000000
#141414
Fail
h2 Conoce los datos de …1.14:13.0:1
#000000
#141414
Fail
h2 La UAM ante las cris…1.14:13.0:1
#000000
#141414
Fail
h2 CURSOS DE CORTA DURA…1.14:13.0:1
#000000
#141414
Fail
h2 [CON]ecta con el pla…1.14:13.0:1
#000000
#141414
Fail
h2 COMUNICADOS1.14:13.0:1
#000000
#141414
Fail
h2 LA UAM EN CIFRAS1.14:13.0:1
#000000
#141414
Fail
title Universidad Autónom…20.95:14.5:1
#000000
#FEFFFE
Pass
a Accede a Declaració…20.95:14.5:1
#000000
#FEFFFE
Pass
a Accede al menú prin…4.51:14.5:1
#000000
#4C799A
Pass
a Accede al pie5.67:14.5:1
#000000
#6589A4
Pass
a Accede al contenido …15.10:14.5:1
#000000
#DCDBD1
Pass
a CIVIS10.65:14.5:1
#000000
#AEBBBE
Pass
a Biblioteca7.87:14.5:1
#000000
#78A4C0
Pass
button Español10.09:14.5:1
#000000
#96B9CA
Pass
a English7.19:14.5:1
#000000
#7BA174
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
Landmark Structure
6 landmarks
PASS
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Barra superior" SEARCH MAIN CONTENTINFO footer

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

A+
Heading Hierarchy
11 headings
PASS
11 headings
Info::
Single H1 present
  • H1 Universidad Autónoma de Madrid - UAM
  • H2 COMUNICADOS
  • H2 Actualidad UAM
  • H2 Noticias científicas
  • H2 EVENTOS
  • H2 Conoce los datos de la UAM, la universidad donde quieres estudiar
  • H2 La UAM ante las crisis humanitarias
  • H2 CURSOS DE CORTA DURACIÓN Y MICROCREDENCIALES
  • H2 [CON]ecta con el planeta
  • H2 COMUNICADOS
  • H2 LA UAM EN CIFRAS
A
Alt Text Quality
All 36 images OK
PASS
All 36 images OK
Info::
9 image(s) with alt text over 125 characters
Info::
27 image(s) with good alt text
36 images 27 good alt text
IssueCount
too long9 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 28 passed
PASS
92

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
La UAM div.uam-footer-menu > ul#uam-footer-accordion > li.accordion-item > div.accordion-header
Vida universitaria div.uam-footer-menu > ul#uam-footer-accordion > li.accordion-item > div.accordion-header
Información para... div.uam-footer-menu > ul#uam-footer-accordion > li.accordion-item > div.accordion-header

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

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nuestra política de cookies. div.cookies-wrapper > div.cookies-text > p > a.cookies-link
Aceptar div#cookies-policy > div.cookies-wrapper > div.cookies-close > button.cookies-close-button

These are opportunities to improve keyboard navigation in your application.

○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-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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[accesskey]` values are unique
●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
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Elements with visible text labels have matching accessible names.
○`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
○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.
○`[lang]` attributes have a valid value
○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.
○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