Skip to content
https://uniroma1.it

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
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::
1 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 1 <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
2 landmarks
REVIEW
2 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 MAIN CONTENTINFO (missing!)

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
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="btn-cerca-corso">
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="search-term">; <input type="search" name="keyword" id="txt-cerca-corso">
3 controls
0 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
#search-termtext(cerca nel sito)placeholder only
#txt-cerca-corsosearch(Cerca il tuo corso)placeholder only
#btn-cerca-corsosubmit(none)none

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

<input type="submit" id="btn-cerca-corso">

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

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

<input type="text" id="search-term">; <input type="search" name="keyword" id="txt-cerca-corso">

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA
h1 Sapienza Store
2.25:1
#000000
on
#822433
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h2 Notizie
2.25:1
#000000
on
#822433
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Eventi
2.25:1
#000000
on
#822433
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Social
2.25:1
#000000
on
#822433
needs 3.0:1 (large text)
24px · bottom of viewport

1 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)
ElementRatioRequiredFGBGResult
h1 Sapienza Store2.25:13.0:1
#000000
#822433
Fail
h2 Notizie2.25:13.0:1
#000000
#822433
Fail
h2 Eventi2.25:13.0:1
#000000
#822433
Fail
h2 Social2.25:13.0:1
#000000
#822433
Fail
title Home | Sapienza Univ…21.00:14.5:1
#000000
#FFFFFF
Pass
a Salta al contenuto p…21.00:14.5:1
#000000
#FFFFFF
Pass
span Toggle navigation21.00:14.5:1
#000000
#FFFFFF
Pass
a Studenti21.00:14.5:1
#000000
#FFFFFF
Pass
a Laureati21.00:14.5:1
#000000
#FFFFFF
Pass
a Docenti21.00:14.5:1
#000000
#FFFFFF
Pass
a Personale21.00:14.5:1
#000000
#FFFFFF
Pass
a Contatti21.00:14.5:1
#000000
#FFFFFF
Pass
a #IoScelgoSapienza21.00:14.5:1
#000000
#FFFFFF
Pass
a Didattica21.00:14.5:1
#000000
#FFFFFF
Pass
a Ricerca scientifica21.00:14.5:1
#000000
#FFFFFF
Pass
a Internazionale21.00:14.5:1
#000000
#FFFFFF
Pass
a Terza missione21.00:14.5:1
#000000
#FFFFFF
Pass
a Ateneo21.00:14.5:1
#000000
#FFFFFF
Pass
a NOTIZIE21.00:14.5:1
#000000
#FFFFFF
Pass
a EVENTI21.00:14.5: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
Heading Hierarchy
41 headings
PASS
41 headings
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 #IoScelgoSapienza
  • H2 Notizie
  • H2 Tutte le notizie
  • H2 Eventi
  • H2 22 Apr, 2026
  • H2 14:00
  • H3 Grammatiche d'autore. Incontri sulla lingua del romanzo
  • H3 RM021 - Circonvallazione Tiburtina 4, Roma
  • H3 Aule 101
  • H2 22 Apr, 2026
  • H2 16:00
  • H3 Diari di Scavo - Incontri del Museo del Vicino Oriente
  • H3 CU001 - Palazzo del Rettorato - spazio antistante il Ciao - Piazzale Aldo Moro 5, Roma
  • H3 Museo del Vicino Oriente
  • H2 22 Apr, 2026
  • H2 16:00
  • H3 Società, coesione, complessità: comunità calcolitiche in Mesopotamia nord orientale
  • H3 CU001 - Palazzo del Rettorato - Piazzale Aldo Moro 5, Roma
  • H3 Museo del Vicino Oriente
  • H2 22 Apr, 2026
  • H2 19:00
  • H3 Concerto MuSa Jazz Meets – International Jazz Day
  • H3 CU017 - Teatro Ateneo - Viale delle Scienze 1-3, Roma
  • H3 Nuovo Teatro Ateneo
  • H2 23 Apr, 2026
  • H2 09:00
  • H3 Disinformazione e deepfake: la democrazia in pericolo
  • H3 RM062 - sede di Via Salaria 113/117
  • H3 Aula Mauro Wolf
  • H2 23 Apr, 2026
  • H2 09:00
  • H3 Il sugo della storia. Sul finale dei Promessi sposi
  • H3 CU003 - Edificio di Lettere - Piazzale Aldo Moro 5, Roma
  • H3 Biblioteca Angelo Monteverdi
  • H2 Tutti gli eventi
  • H2 Social
  • H1 Sapienza Store duplicate H1
  • H1 Didattica duplicate H1
  • H1 Internazionale duplicate H1
  • H1 Ricerca scientifica duplicate H1
  • H1 Ateneo duplicate H1

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
3 of 38 images have issues
PASS
3 of 38 images have issues
Warning::
3 image(s) with filename as alt text
Info::
35 image(s) with good alt text
38 images 35 good alt text 3 generic
IssueCount
filename3 image(s)
A
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 23 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.

Names and labels

Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-sm-12 > section#cerca-corso > form#ricerca-offerta-formativa > input#btn-cerca-corso div.col-sm-12 > section#cerca-corso > form#ricerca-offerta-formativa > input#btn-cerca-corso

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
Social icon div.col > div.box-social > div.post-link > a.social-icon
Scrutinio elezioni Senato Accademico e Consiglio di Amministrazione div.box-social > div.same-height > div.field-content > a
Social icon div.col > div.box-social > div.post-link > a.social-icon
Social icon div.col > div.box-social > div.post-link > a.social-icon
Social icon div.col > div.box-social > div.post-link > a.social-icon

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
●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.
●ARIA attributes are used as specified for the element's role
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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 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.
○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.
○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