Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 3 REVIEW 4 FIX

404 Error Page

Action

HTTP 403, custom page

FIX

HTTP 403, custom page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 403 ✗Page Title Just a moment... ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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.

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

40 landmarks

REVIEW

40 landmarks

<main> landmark present

20 <nav> landmark(s) found

3 of 20 <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

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 3 pass AA only

label Campo di ricerca

3.66:1

#000000

#6B646B

needs 4.5:1 (normal text)

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

span Cerca

1.70:1

#000000

#343534

needs 4.5:1 (normal text)

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

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 Informazioni per	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Unito news \| Otto	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Avvisi	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Prossimi eventi	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Offerta formativa	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 I numeri del nostro …	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 I Dipartimenti di Un…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Perché scegliere l'…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 UniTo Store	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 RISORSE	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 STUDENTI	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 AMMINISTRAZIONE	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 RIFERIMENTI	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h2 Informativa sui cook…	5.24:1	3.0:1	#000000	#7F7F7F	Pass
h3 Calendario	5.24:1	3.0:1	#000000	#7F7F7F	Pass
title L'Università di Tor…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
a Salta al contenuto p…	5.24:1	4.5:1	#000000	#7F7F7F	Pass
span Form di ricerca	5.24:1	4.5:1	#000000	#7F7F7F	Pass
label Campo di ricerca	3.66:1	4.5:1	#000000	#6B646B	Fail
span Cerca	1.70:1	4.5:1	#000000	#343534	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

28 headings

PASS

28 headings

Single H1 present

H1 Home page
H2 Informazioni per
H2 Unito news | Otto
H2 Avvisi
H3 Avviso di selezione pubblica per il ruolo di Direttrice/Direttore Generale presso l'Università degli Studi di Torino
H3 CineAmbiente Campus: call per studentesse e studenti
H3 Bandi di selezione per il conferimento di incarichi post-doc
H3 III edizione del Corso Specialistico - Sanificazione aziendale: tecnologie ed approcci sostenibili
H3 Indagine Good Practice 2026 sui servizi di UniTo 2025
H3 Porte aperte UniTo: scopri corsi e sedi dell’Ateneo
H3 Bando Visiting Professor per l'a.a. 2026-2027 - Call for application
H3 Aperte le candidature per MSCA@UniTo
H2 Prossimi eventi
H3 L’abbaglio della luce. Natura e fascino della luce
H3 Diritti, Comunità, Salute Mentale - Dialogo tra Società Scientifiche
H3 Seminario Centro Scansetti - Challenge in the quantification of micro and nanoplatics in human samples
H3 ERC@Unito: la ricerca di eccellenza all’Università di Torino
H3 Calendario
H2 Offerta formativa
H2 I numeri del nostro Ateneo
H2 I Dipartimenti di UniTo
H2 Perché scegliere l'Università di Torino
H2 UniTo Store
H2 RISORSE
H2 STUDENTI
H2 AMMINISTRAZIONE
H2 RIFERIMENTI
H2 Informativa sui cookie

A+

Alt Text Quality

All 59 images OK

PASS

All 59 images OK

1 image(s) with alt text over 125 characters

1 decorative image(s) correctly marked

57 image(s) with good alt text

59 images 57 good alt text 1 decorative

Issue	Count
too long	1 image(s)

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-modal	search	Campo di ricerca	for/id
#edit-keys	search	Inserisci i termini da cercare	for/id

A+

Link & Button Quality

314 links, 54 buttons — all OK

PASS

314 links, 54 buttons — all OK

314 link(s) with descriptive text

314 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

368 links and buttons have descriptive text

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: /sites/default/files/css/css_lU0mAMaQg1_3yj5j047QhIgvQrkWmGZCwUr8bVoRP60.css?delta=4&language=it&theme=unito_portale&include=eJxtkQGuwyAIhi9k65EMVdaSIRjRLdvpn2uWdOteYsgPH6gApEwSopmHl5qGcgvEa2g6TvEfOlBUcQvD8-FZIZGsblFt1iqUsECtpH5lXYAnaw_-l1OGFcOFO6VfmNFsYAv3jRr-ctGELgKjJHj5hwxdqKmLWtFHzUUFpdl8vmGaMkp3V4aqfrefetIbjqzxRoEK6yjbzKfaC_B8ROYupS9MtmFyxhSvfrfza3SffgaSOeEFOrcv0DbM6OxhDfMYsKHbfx9W1ZVxLAP9OfDOKFrb6NkffcUkJ3bR0fkpdtrKNxwbgScJuhvh3fxu56ypM_4B6HjVOQ

Print Stylesheet ✓ Print Optimized

Print stylesheet /sites/default/files/css/css_lU0mAMaQg1_3yj5j047QhIgvQrkWmGZCwUr8bVoRP60.css?delta=4&language=it&theme=unito_portale&include=eJxtkQGuwyAIhi9k65EMVdaSIRjRLdvpn2uWdOteYsgPH6gApEwSopmHl5qGcgvEa2g6TvEfOlBUcQvD8-FZIZGsblFt1iqUsECtpH5lXYAnaw_-l1OGFcOFO6VfmNFsYAv3jRr-ctGELgKjJHj5hwxdqKmLWtFHzUUFpdl8vmGaMkp3V4aqfrefetIbjqzxRoEK6yjbzKfaC_B8ROYupS9MtmFyxhSvfrfza3SffgaSOeEFOrcv0DbM6OxhDfMYsKHbfx9W1ZVxLAP9OfDOKFrb6NkffcUkJ3bR0fkpdtrKNxwbgScJuhvh3fxu56ypM_4B6HjVOQ ✓Inline @media print Not detected ✗

Lighthouse Accessibility Audits

Score 90/100 — 1 failing, 13 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

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●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

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted 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

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

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

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

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