Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 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

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

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

12 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 12 <nav> element(s)

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.

Landmark Structure

16 landmarks

REVIEW

16 landmarks

<main> landmark present

12 <nav> landmark(s) found

1 of 12 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

Link & Button Quality

1 issue(s) across 244 links and 7 buttons

REVIEW

1 issue(s) across 244 links and 7 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#main-content

2 link(s) open in new tab without warning

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

Got: https://www.unimi.it/it/ateneo/normative/privacy; https://www.unimi.it/it/privacy-e-cookie

241 link(s) with descriptive text

244 links

1 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
https://www.unimi.it/it/ateneo/normative…	Privacy policy	new tab	Add '(opens in new tab)' to text
https://www.unimi.it/it/privacy-e-cookie	Documentazione cookie	new tab	Add '(opens in new tab)' to text

248 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#main-content

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://www.unimi.it/it/ateneo/normative/privacy; https://www.unimi.it/it/privacy-e-cookie

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Pagina non trovata | Università degli Studi di Milano Statale ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA 2 pass AA only

h2 Language switcher

1.06:1

#000000

#0B0B06

needs 3.0:1 (large text)

24px · top of page (header area)

h2 Profili

1.05:1

#000000

#070806

needs 3.0:1 (large text)

24px · above the fold

h2 Main navigation

2.06:1

#000000

#004082

needs 3.0:1 (large text)

24px · bottom of viewport

h2 I corsi

2.06:1

#000000

#004082

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Main navigation

2.06:1

#000000

#004082

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Top navbar

2.06:1

#000000

#004082

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Strutture

2.06:1

#000000

#004082

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Servizi

2.06:1

#000000

#004082

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Concorsi, selezioni e gare

2.06:1

#000000

#004082

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Come fare per

2.06:1

#000000

#004082

needs 3.0:1 (large text)

24px · bottom of viewport

h2 footer

2.06:1

#000000

#004082

needs 3.0:1 (large text)

24px · bottom of viewport

h2 social

2.06:1

#000000

#004082

needs 3.0:1 (large text)

24px · bottom of viewport

a ITA

2.48:1

#000000

#5F492F

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a ENG

1.05:1

#000000

#070905

needs 4.5:1 (normal text)

16px · above the fold

a Unimia

1.65:1

#000000

#183453

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Segreterie

2.06:1

#000000

#004082

needs 4.5:1 (normal text)

16px · above the fold

a Ariel

2.06:1

#000000

#004082

needs 4.5:1 (normal text)

16px · above the fold

a Biblioteche

2.06:1

#000000

#004082

needs 4.5:1 (normal text)

16px · above the fold

2 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)

Element	Ratio	Required	FG	BG	Result
h2 Language switcher	1.06:1	3.0:1	#000000	#0B0B06	Fail
h2 Profili	1.05:1	3.0:1	#000000	#070806	Fail
h2 Main navigation	2.06:1	3.0:1	#000000	#004082	Fail
h2 I corsi	2.06:1	3.0:1	#000000	#004082	Fail
h2 Main navigation	2.06:1	3.0:1	#000000	#004082	Fail
h2 Top navbar	2.06:1	3.0:1	#000000	#004082	Fail
h2 Strutture	2.06:1	3.0:1	#000000	#004082	Fail
h2 Servizi	2.06:1	3.0:1	#000000	#004082	Fail
h2 Concorsi, selezioni …	2.06:1	3.0:1	#000000	#004082	Fail
h2 Come fare per	2.06:1	3.0:1	#000000	#004082	Fail
h2 footer	2.06:1	3.0:1	#000000	#004082	Fail
h2 social	2.06:1	3.0:1	#000000	#004082	Fail
title home \| Università d…	5.59:1	4.5:1	#000000	#738697	Pass
a Salta al contenuto p…	5.96:1	4.5:1	#000000	#778B9C	Pass
a ITA	2.48:1	4.5:1	#000000	#5F492F	Fail
a ENG	1.05:1	4.5:1	#000000	#070905	Fail
a Unimia	1.65:1	4.5:1	#000000	#183453	Fail
a Segreterie	2.06:1	4.5:1	#000000	#004082	Fail
a Ariel	2.06:1	4.5:1	#000000	#004082	Fail
a Biblioteche	2.06:1	4.5:1	#000000	#004082	Fail

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+

Heading Hierarchy

13 headings

PASS

13 headings

Single H1 present

H2 Language switcher
H2 Profili
H2 Main navigation
H2 I corsi
H2 Main navigation
H2 Top navbar
H1 home
H2 Strutture
H2 Servizi
H2 Concorsi, selezioni e gare
H2 Come fare per
H2 footer
H2 social

A+

Alt Text Quality

All 34 images OK

PASS

All 34 images OK

1 decorative image(s) correctly marked

33 image(s) with good alt text

34 images 33 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#edit-keys-2	search	Cerca	for/id
#edit-keys	search	Cerca	for/id

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 23 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.

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
Facoltà e scuole `nav#block-piedipagina > ul.menu > li.first > a`
Dipartimenti `nav#block-piedipagina > ul.menu > li > a`
Sedi `nav#block-piedipagina > ul.menu > li > a`
Uffici `nav#block-piedipagina > ul.menu > li.last > a`
Segreterie studenti `nav#block-piedipagina-3 > ul.menu > li.first > a`
Servizio bibliotecario `nav#block-piedipagina-3 > ul.menu > li > a`
Servizi per studenti con disabilità `nav#block-piedipagina-3 > ul.menu > li > a`
Servizi per studenti con DSA `nav#block-piedipagina-3 > ul.menu > li > a`
Servizi tecnologici `nav#block-piedipagina-3 > ul.menu > li.last > a`
Professori `nav#block-piedipagina-4 > ul.menu > li.first > a`
Ricercatori `nav#block-piedipagina-4 > ul.menu > li > a`
Tecnici amministrativi e bibliotecari `nav#block-piedipagina-4 > ul.menu > li > a`
Consulenze e collaborazioni `nav#block-piedipagina-4 > ul.menu > li > a`
Incarichi di ricerca `nav#block-piedipagina-4 > ul.menu > li > a`
Gare e contratti `nav#block-piedipagina-4 > ul.menu > li.last > a`
Amministrazione trasparente `nav#block-piedipagina-5 > ul.menu > li.first > a`
Dichiarazione di accessibilità `nav#block-piedipagina-5 > ul.menu > li > a`
Privacy e cookie `nav#block-piedipagina-5 > ul.menu > li > a`
Cookie settings `nav#block-piedipagina-5 > ul.menu > li > a`
Note legali `nav#block-piedipagina-5 > ul.menu > li > a`
Mappa del sito `nav#block-piedipagina-5 > ul.menu > li.last > a`
Tel: +39 02 5032 5032 `div.field > div.field--item > p > a`
InformaStudenti `div.field > div.field--item > p > a`
Posta Elettronica Certificata `div.field > div.field--item > p > 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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

○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.

○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.