Skip to content
https://unipi.it

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
5
REVIEW
7
PASS
1
INFO
0
Checks
13
1 PASS 7 REVIEW 5 FIX
D
Heading Hierarchy
Action
43 headings, 2 skip(s)
FIX
43 headings, 2 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Didattica
  • H2 Campus e Servizi
  • H2 Ricerca
  • H2 Innovazione
  • H2 Università e Società
  • H2 Ateneo
  • H2 News
  • H2 I corsi di laurea
  • H2 Corsi di Dottorato a.a. 2026/2027
  • H2 In evidenza
  • H3 Elezioni delle rappresentanze studentesche
  • H3 Aperte le candidature a Venture Kneading
  • H2 Circle U.
  • H2 Politiche di genere
  • H2 Sviluppo Sostenibile e Agenda 2030
  • H2 Unipi news
  • H2 Eventi
  • H4 Unipi per la pace e i diritti umani skipped
  • H2 I Valori
  • H2 Valorizzare i talenti
  • H2 Espandere le frontiere della conoscenza
  • H2 Aprirsi al mondo
  • H2 Gestire in modo trasparente
  • H2 Coltivare coesione e condivisione
  • H2 Gestire in modo sostenibile le risorse collettive
  • H2 Il Piano strategico di Ateneo
  • H2 Avvisi
  • H4 Incontri e visite gratuite per il “Marzo delle Donne” all’AOUP skipped
  • H4 Welcome Week Erasmus Students 2024/2025
  • H4 Incontri e visite gratuite per il “Marzo delle Donne” all’AOUP
  • H4 Welcome Week Erasmus Students 2024/2025
  • H4 Incontri e visite gratuite per il “Marzo delle Donne” all’AOUP
  • H4 Welcome Week Erasmus Students 2024/2025
  • H5 Assegnazione di contributi da parte del CUG per favorire la mobilità di persone con disabilità a copertura dei costi di trasporto nel tragitto casa/lavoro
  • H5 Festival Puccini 2026
  • H5 Programmazione aprile e maggio 2026 al Teatro Nuovo
  • H5 Elezioni studentesche per il biennio 2026/28: posticipazione termini presentazione liste, candidature e sottoscrizioni
  • H5 Assegnazione di contributi da parte del CUG per favorire la mobilità di persone con disabilità a copertura dei costi di trasporto nel tragitto casa/lavoro
  • H5 Festival Puccini 2026
  • H5 Programmazione aprile e maggio 2026 al Teatro Nuovo
  • H5 Elezioni studentesche per il biennio 2026/28: posticipazione termini presentazione liste, candidature e sottoscrizioni
  • H5 Assegnazione di contributi da parte del CUG per favorire la mobilità di persone con disabilità a copertura dei costi di trasporto nel tragitto casa/lavoro
  • H5 Festival Puccini 2026

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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::
4 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 4 <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.
C
Landmark Structure
Action
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
1 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) NAV "Selettore lingua" MAIN CONTENTINFO (missing!)

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

C
Alt Text Quality
Action
22 of 37 images have issues
REVIEW
22 of 37 images have issues
Critical::
21 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Warning::
1 image(s) with generic alt text
Info::
1 image(s) with alt text over 125 characters
Info::
1 decorative image(s) correctly marked
Info::
13 image(s) with good alt text
37 images 13 good alt text 1 decorative 1 generic 21 missing
IssueCount
missing21 image(s)
generic1 image(s)
too long1 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

C
Form Accessibility
Action
3 of 5 controls have issues
REVIEW
3 of 5 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="dida" id="didasearch">; <input type="text">; <input type="submit" name="submit" id="searchsubmit">
Info::
2 control(s) properly labeled
5 controls
2 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#stextCercafor/id
event_highlightselectIn Evidenzaaria-label
#didasearchselect(none)none
#searchsubmitsubmit(none)none
inputtext(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select name="dida" id="didasearch">; <input type="text">; <input type="submit" name="submit" id="searchsubmit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 88/100 — 5 failing, 29 passed
REVIEW
88

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
offerta didattica div.elementor-element > div.elementor-element > div.e-con-inner > div.elementor-element

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

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Unipi per la pace e i diritti umani div.elementor-element > div.elementor-element > div.elementor-widget-container > h4.elementor-heading-title
Programmazione aprile e maggio 2026 al Teatro Nuovo div#slick-slide-control20 > div.jet-carousel__item-inner > div.jet-carousel__content > h5.jet-carousel__item-title

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Tutti i corsi Tutte le Lauree triennali e magistrali a ciclo unico Agraria e Ve… div.elementor-widget-container > div.elementor-shortcode > form#searchform > select#didasearch

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon
div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button div.elementor-element > div.elementor-widget-container > div.elementor-button-wrapper > a.elementor-button

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Vai alla funzione di ricerca del sito body.home > a.skip-link

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
●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
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●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
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○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
○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
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<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
○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.
○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.
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
h2 Didattica21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Campus e Servizi21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ricerca21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Innovazione21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Università e Societ…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ateneo21.00:13.0:1
#000000
#FFFFFF
Pass
h2 News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 I corsi di laurea21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Corsi di Dottorato a…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 In evidenza21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Unipi news21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Eventi21.00:13.0:1
#000000
#FFFFFF
Pass
h2 I Valori21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Valorizzare i talent…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Espandere le frontie…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Aprirsi al mondo21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Gestire in modo tras…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Coltivare coesione e…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Gestire in modo sost…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Il Piano strategico …21.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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback