Skip to content
https://unizar.es

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ 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
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
Heading Hierarchy
19 headings
REVIEW
19 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Secundario
  • H2 Instittución
  • H2 Estudios
  • H2 I+D+i
  • H2 Vida universitaria
  • H2 Oferta académica
  • H3 Grados
  • H3 Másteres
  • H3 Doctorado
  • H3 Formación continua
  • H2 Actualidad
  • H3 Si no te quieres perder todo lo que pasa en Unizar
  • H2 Síguenos en nuestras redes sociales
  • H2 Unizar en cifras
  • H2 Enlaces que te pueden interesar
  • H3 Campus de Huesca
  • H3 Campus de Teruel
  • H3 Otros enlaces de interés
  • H2 Utilizamos cookies en este sitio web para mejorar su experiencia de usuario.

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

C
Alt Text Quality
Action
3 of 58 images have issues
REVIEW
3 of 58 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
9 decorative image(s) correctly marked
Info::
46 image(s) with good alt text
58 images 46 good alt text 9 decorative 3 missing
IssueCount
missing3 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Página no encontrada | Universidad de Zaragoza ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 13 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Secundario9.73:13.0:1
#000000
#AEB0BB
Pass
h2 Instittución5.74:13.0:1
#000000
#5D8AB1
Pass
h2 Estudios3.77:13.0:1
#000000
#236CA7
Pass
h2 I+D+i3.77:13.0:1
#000000
#236CA7
Pass
h2 Vida universitaria3.77:13.0:1
#000000
#236CA7
Pass
h2 Oferta académica3.77:13.0:1
#000000
#236CA7
Pass
h2 Actualidad3.77:13.0:1
#000000
#236CA7
Pass
h2 Síguenos en nuestra…3.77:13.0:1
#000000
#236CA7
Pass
h2 Unizar en cifras3.77:13.0:1
#000000
#236CA7
Pass
h2 Enlaces que te puede…3.77:13.0:1
#000000
#236CA7
Pass
h2 Utilizamos cookies e…3.77:13.0:1
#000000
#236CA7
Pass
h3 Si no te quieres per…3.77:13.0:1
#000000
#236CA7
Pass
h3 Campus de Huesca3.77:13.0:1
#000000
#236CA7
Pass
h3 Campus de Teruel3.77:13.0:1
#000000
#236CA7
Pass
h3 Otros enlaces de int…3.77:13.0:1
#000000
#236CA7
Pass
title Universidad de Zarag…20.27:14.5:1
#000000
#FAFBFC
Pass
a Salir20.27:14.5:1
#000000
#FAFBFC
Pass
span Perfiles13.12:14.5:1
#000000
#CBCCD3
Pass
span Toggle submenu9.42:14.5:1
#000000
#ACADB8
Pass
a Estudiantes9.42:14.5:1
#000000
#ACADB8
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
11 landmarks
PASS
11 landmarks
Info::
<main> landmark present
Info::
8 <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.
Page Structure — as a screen reader sees it
BANNER header NAV "menu-perfiles navigation" 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
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="buscadorEstudios">
Info::
2 control(s) properly labeled
3 controls
2 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#a2a_copy_link_texttextCopy linkfor/id
#a2apage_findtextFind any servicefor/id
#buscadorEstudiostext(Encuentra tu titulación)placeholder only

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

<input type="text" id="buscadorEstudios">

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

A
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 26 passed
PASS
91

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
21/04/2026 li.new-item > div.texto-noticia > div.fecha-noticia > time.datetime
21/04/2026 li.new-item > div.texto-noticia > div.fecha-noticia > time.datetime
21/04/2026 li.new-item > div.texto-noticia > div.fecha-noticia > time.datetime
21/04/2026 li.new-item > div.texto-noticia > div.fecha-noticia > time.datetime
21/04/2026 li.new-item > div.texto-noticia > div.fecha-noticia > time.datetime
20/04/2026 li.new-item > div.texto-noticia > div.fecha-noticia > time.datetime
17/04/2026 li.new-item > div.texto-noticia > div.fecha-noticia > time.datetime
16/04/2026 li.new-item > div.texto-noticia > div.fecha-noticia > time.datetime
Ver más div.layout-1 > div.view-footer > p.ver-mas > a.ver-mas_news
Ir a la web div.item_campus > div.campus_content > p > a.campus_btn
Ir a la web div.item_campus > div.campus_content > p > a.campus_btn

These are opportunities to improve the legibility of your content.

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.block-content > div.clearfix > div.rrss_imag > img div.block-content > div.clearfix > div.rrss_imag > img
ul.alter1 > li > a > img ul.alter1 > li > a > img

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.

○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
●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
●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
●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
●No element has a `[tabindex]` value greater than 0
●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
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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
○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.
○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
○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.

Send Feedback