Skip to content
https://unibo.it

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Missing
✗ 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
No navigation patterns
FIX
No navigation patterns
Info::
5 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 5 <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
10 landmarks
REVIEW
10 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
1 of 5 <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 "scorciatoie per la navigazione" 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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Impossibile trovare la pagina richiesta ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
A
Heading Hierarchy
42 headings
PASS
42 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Questo sito web utilizza i cookie
  • H1 Home page duplicate H1
  • H2 Pensiero libero, sapere condiviso
  • H3 Hai o avrai un diploma e vuoi iscriverti all'università?
  • H3 Non sai da dove iniziare per scegliere il corso?
  • H2 In evidenza
  • H3 I risultati delle elezioni suppletive delle Rappresentanze Studentesche di Ateneo
  • H3 MusicAteneo 2026: cori e orchestre universitarie tornano protagonisti in città
  • H3 Come cambiano le politiche alimentari nell'incertezza globale
  • H2 Voci, storie, idee
  • H3 Le amicizie strette all'università?
  • H3 "L'università mi ha aiutata a capire i bisogni degli altri e a conciliarli con i miei"
  • H3 Quale canzone assoceresti all'università?
  • H2 Dalla ricerca alla società
  • H3 Studiosi al lavoro per riportare gli impollinatori in città
  • H3 Sappiamo ancora poco sulla biodiversità delle isole del Mediterraneo
  • H3 Adriatico e One Health: il microbioma delle acque costiere svela i legami tra ambiente e salute
  • H2 I valori dell'Ateneo
  • H3 Oltre gli stereotipi: equità di genere e inclusività per scoprire la ricchezza delle diversità
  • H3 Innovazione, equità, rispetto: la sostenibilità che vogliamo costruire
  • H3 Diritto alla pace. Promuovere il dialogo come chiave per la risoluzione dei conflitti
  • H3 Accesso alla conoscenza come diritto. Studiare come possibilità a prescindere dalla situazione economica
  • H3 Oltre gli stereotipi: equità di genere e inclusività per scoprire la ricchezza delle diversità
  • H3 Innovazione, equità, rispetto: la sostenibilità che vogliamo costruire
  • H3 Diritto alla pace. Promuovere il dialogo come chiave per la risoluzione dei conflitti
  • H3 Accesso alla conoscenza come diritto. Studiare come possibilità a prescindere dalla situazione economica
  • H2 I Campus dell'Ateneo
  • H3 Campus di Bologna
  • H3 Campus di Cesena
  • H3 Campus di Forlì
  • H3 Campus di Ravenna
  • H3 Campus di Rimini
  • H3 Campus di Bologna
  • H3 Campus di Cesena
  • H3 Campus di Forlì
  • H3 Campus di Ravenna
  • H3 Campus di Rimini
  • H3 Campus di Bologna
  • H3 Campus di Cesena
  • H3 Campus di Forlì
  • H3 Campus di Ravenna
  • H3 Campus di Rimini

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Alt Text Quality
All 51 images OK
PASS
All 51 images OK
Info::
15 decorative image(s) correctly marked
Info::
36 image(s) with good alt text
51 images 36 good alt text 15 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 10 controls labeled
PASS
All 10 controls labeled
Info::
10 control(s) properly labeled
10 controls
10 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#chefcookie_group_0checkboxnone
#chefcookie_script_0_youtubecheckboxnone
#chefcookie_script_0_facebookcheckboxnone
#chefcookie_script_0_vimeocheckboxnone
#chefcookie_script_0_linkedincheckboxnone
#chefcookie_group_1checkboxnone
querytextCerca in Unibo.itaria-label
#persradioPersonefor/id
#strutradioStrutturefor/id
querytextCerca nella rubricaaria-label
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Questo sito web util…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Home page21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Pensiero libero, sap…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 In evidenza21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Voci, storie, idee21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dalla ricerca alla s…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 I valori dell'Ateneo21.00:13.0:1
#000000
#FFFFFF
Pass
h2 I Campus dell'Ateneo21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Le amicizie strette …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 "L'università mi ha…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Quale canzone assoce…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Studiosi al lavoro p…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Sappiamo ancora poco…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Adriatico e One Heal…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Campus di Bologna21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Campus di Cesena21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Campus di Forlì21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Campus di Ravenna21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Campus di Rimini21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Campus di Bologna21.00:13.0:1
#000000
#FFFFFF
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+
Lighthouse Accessibility Audits
Score 100/100 — 0 failing, 30 passed
PASS
100

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.

○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
●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.
●`[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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
○`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
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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.
○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.

Send Feedback