Accessibility

F

Heading Hierarchy

Action

143 headings, 41 skip(s)

FIX

143 headings, 41 skip(s)

Multiple H1 headings (2 found)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H4 → H6 (missing H5)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H3 → H6 (missing H4)

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H4 → H6 (missing H5)

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

H4 Esplora Il Politecnico Scopri
H6 Strutture del Politecnico skipped
H6 Documenti ufficiali
H4 Esplora le nostre proposte di Formazione Scopri
H6 OFFERTA FORMATIVA CURRICULARE skipped
H6 ALTRE OPPORTUNITÀ FORMATIVE
H2 Test e ammissione
H6 Risorse utili skipped
H4 Esplora la nostra offerta di Dottorato Scopri
H2 News Dottorato di Ricerca
H2 Corsi di Dottorato
H4 Esplora la Ricerca Scopri skipped
H2 In evidenza
H4 Polimi AI skipped
H2 Magazine
H4 Frontiere skipped
H4 Esplora lo Sviluppo sostenibile Scopri
H4 POLIMI Sustainability
H6 Altre risorse skipped
H4 Esplora i nostri Campus e servizi Scopri
H6 SERVIZI PER LO STUDIO skipped
H6 VIVERE IL CAMPUS
H6 OPPORTUNITÀ
H6 Utilità
H4 Esplora le informazioni per Futuri studenti Scopri
H2 Entra al Politecnico come
H4 Studente di mobilità internazionale skipped
H6 Servizi e opportunità skipped
H4 Esplora le informazioni per Studenti Scopri
H6 Opportunità skipped
H6 Altre risorse
H4 Esplora le informazioni per Alumni Scopri
H2 Vai a
H2 Sito Alumni
H4 Esplora le informazioni per Docenti e ricercatori Scopri skipped
H6 Altre risorse skipped
H2 Vai a
H2 Servizio di Prevenzione e Protezione
H4 Esplora le informazioni per Staff Scopri skipped
H6 Altre risorse skipped
H2 Vai a
H2 Servizio di Prevenzione e Protezione
H4 Esplora le informazioni per Imprese Scopri skipped
H6 Altre risorse skipped
H2 Vai a
H2 Servizio di Prevenzione e Protezione
H4 Esplora le informazioni per Stampa Scopri skipped
H2 Magazine
H4 Frontiere skipped
H6 Altre risorse skipped
H6 Il Politecnico
H6 Strutture del Politecnico
H6 Documenti ufficiali
H6 Formazione
H2 Test e ammissione
H6 Risorse utili skipped
H6 Dottorato
H2 News Dottorato di Ricerca
H2 Corsi di Dottorato
H6 Ricerca skipped
H2 In evidenza
H4 Polimi AI skipped
H2 Magazine
H4 Frontiere skipped
H6 Sviluppo sostenibile skipped
H4 POLIMI Sustainability
H6 Altre risorse skipped
H6 Campus e servizi
H6 Utilità
H6 Futuri studenti
H2 Entra al Politecnico come
H4 Studente di mobilità internazionale skipped
H6 Servizi e opportunità skipped
H6 Studenti
H6 Opportunità
H6 Altre risorse
H6 Alumni
H2 Vai a
H2 Sito Alumni
H6 Docenti e ricercatori skipped
H6 Altre risorse
H2 Vai a
H2 Servizio di Prevenzione e Protezione
H6 Staff skipped
H6 Altre risorse
H2 Vai a
H2 Servizio di Prevenzione e Protezione
H6 Imprese skipped
H6 Altre risorse
H2 Vai a
H2 Servizio di Prevenzione e Protezione
H6 Stampa skipped
H2 Magazine
H4 Frontiere skipped
H6 Altre risorse skipped
H6 Lavora con noi
H2 Technology for humanity
H1 Politecnico di Milano
H2 In evidenza
H4 Come funziona l'ammissione skipped
H4 Sport e tecnologia
H4 Il mondo di domani
H4 Scopri il nostro Open Day 2026
H4 Una passione per la tecnologia che dura da 160 anni
H2 Le sedi del Politecnico
H2 Donatella Sciuto, Rettrice
H2 Un’eccellenza in Italia e nel mondo
H3 1°
H3 98°
H6 Entra nella community della prima Università d'Italia skipped
H4 Scopri come entrare a far parte del Politecnico di Milano
H2 Le scuole
H4 Architettura Urbanistica Ingegneria delle Costruzioni skipped
H4 Design
H4 Ingegneria Civile, Ambientale e Territoriale
H4 Ingegneria Industriale e dell'Informazione
H4 Partnership internazionali
H2 News
H5 Raffrescamento sostenibile: lanciata EPIC Deploy skipped
H5 Politecnico e Autodromo di Monza, accordo per innovare i circuiti
H5 MSCA Postdoctoral Fellowship 2026: aperta la call europea
H5 Polimi centri estivi 2026
H3 Eventi
H6 Convegno Renewable Energy 2026 skipped
H6 Osservatorio AI4Innovation 2025-2026 | Convegno Finale
H6 ALPI: The way of mountain design
H6 Incontro con MA YANSONG Guest Editor Domus 2026
H6 La pianura è un'avventura - Lingue, tecnologia, idee, mobilità, la casa e l’altrove
H6 Osservatorio Eventi & Live Communication | Primo Workshop
H6 Common Archive. La Notte Bianca del Progetto
H6 La Scienza Delle Relazioni: Il Ruolo delle Competenze Strategico-Relazionali nella Creazione di Valore per le Organizzazioni
H6 The White House. Domestic Propaganda
H6 Interdependence: Past, Present, Future
H6 "TAKING CARE. I segni del cambiamento"
H6 Abitare nell'era del digitale
H2 La vita al Politecnico
H2 Campus e servizi
H4 Polimi Community skipped
H6 Sedi skipped
H6 Naviga il sito
H6 Risorse
H6 Contattaci
H1 Impostazioni privacy 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Link & Button Quality

Action

15 issue(s) across 482 links and 61 buttons

FIX

15 issue(s) across 482 links and 61 buttons

14 link(s) with no accessible text

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

Got: /campus-e-servizi/servizio-di-prevenzione-e-protezione; /campus-e-servizi/servizio-di-prevenzione-e-protezione; /campus-e-servizi/servizio-di-prevenzione-e-protezione; /campus-e-servizi/servizio-di-prevenzione-e-protezione; /campus-e-servizi/servizio-di-prevenzione-e-protezione; /campus-e-servizi/servizio-di-prevenzione-e-protezione; a#main-content-anchor; a#c4696; a#c4688; a#c4701 (+4 more)

57 link(s) open in new tab without warning

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

Got: https://www.normativa.polimi.it/; https://www.protocollo.polimi.it/albo/viewer?view=html; https://webeep.polimi.it/; https://aunicalogin.polimi.it/aunicalogin/getservizio.xml?id_servizio=156; https://aunicalogin.polimi.it/aunicalogin/getservizio.xml?id_servizio=167&evn…; https://aunicalogin.polimi.it/aunicalogin/getservizio.xml?id_servizio=166; https://alumni.polimi.it/; https://www.intranet.polimi.it; https://www.normativa.polimi.it/; https://www.intranet.polimi.it (+47 more)

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.back-to-top (#3229 on page)

411 link(s) with descriptive text

482 links

14 empty

0 generic text

57 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.normativa.polimi.it/	Normativa di Ateneo	new tab	Add '(opens in new tab)' to text
https://www.protocollo.polimi.it/albo/vi…	Albo ufficiale	new tab	Add '(opens in new tab)' to text
https://webeep.polimi.it/	WeBeep	new tab	Add '(opens in new tab)' to text
https://aunicalogin.polimi.it/aunicalogi…	Manifesti degli studi	new tab	Add '(opens in new tab)' to text
https://aunicalogin.polimi.it/aunicalogi…	Cerca docenti	new tab	Add '(opens in new tab)' to text
https://aunicalogin.polimi.it/aunicalogi…	Cerca insegnamenti	new tab	Add '(opens in new tab)' to text
https://alumni.polimi.it/	Vai	new tab	Add '(opens in new tab)' to text
https://www.intranet.polimi.it	Intranet di Ateneo	new tab	Add '(opens in new tab)' to text
https://www.normativa.polimi.it/	Normativa di Ateneo	new tab	Add '(opens in new tab)' to text
/campus-e-servizi/servizio-di-prevenzion…	(empty)	empty	Add link text or aria-label
https://www.intranet.polimi.it	Intranet di Ateneo	new tab	Add '(opens in new tab)' to text
https://www.normativa.polimi.it/	Normativa di Ateneo	new tab	Add '(opens in new tab)' to text
/campus-e-servizi/servizio-di-prevenzion…	(empty)	empty	Add link text or aria-label
https://www.dona.polimi.it/	Dona al Politecnico	new tab	Add '(opens in new tab)' to text
http://www.fondazionepolitecnico.it/	Fondazione Politecnico	new tab	Add '(opens in new tab)' to text
http://www.careerservice.polimi.it/	Career service	new tab	Add '(opens in new tab)' to text
https://diversityandinclusion.polimi.it/	Diversity & Inclusion	new tab	Add '(opens in new tab)' to text
https://www.qualita.polimi.it/index.php/…	Servizio Qualità di Ateneo	new tab	Add '(opens in new tab)' to text
http://www.polihub.it/	PoliHub	new tab	Add '(opens in new tab)' to text
/campus-e-servizi/servizio-di-prevenzion…	(empty)	empty	Add link text or aria-label
https://www.mynewsdesk.com/it/politecnic…	International Press Releases	new tab	Add '(opens in new tab)' to text
https://www.normativa.polimi.it/	Normativa di Ateneo	new tab	Add '(opens in new tab)' to text
https://www.protocollo.polimi.it/albo/vi…	Albo ufficiale	new tab	Add '(opens in new tab)' to text
https://webeep.polimi.it/	WeBeep	new tab	Add '(opens in new tab)' to text
https://aunicalogin.polimi.it/aunicalogi…	Manifesti degli studi	new tab	Add '(opens in new tab)' to text
https://aunicalogin.polimi.it/aunicalogi…	Cerca docenti	new tab	Add '(opens in new tab)' to text
https://aunicalogin.polimi.it/aunicalogi…	Cerca insegnamenti	new tab	Add '(opens in new tab)' to text
https://alumni.polimi.it/	Vai	new tab	Add '(opens in new tab)' to text
https://www.intranet.polimi.it	Intranet di Ateneo	new tab	Add '(opens in new tab)' to text
https://www.normativa.polimi.it/	Normativa di Ateneo	new tab	Add '(opens in new tab)' to text
/campus-e-servizi/servizio-di-prevenzion…	(empty)	empty	Add link text or aria-label
https://www.intranet.polimi.it	Intranet di Ateneo	new tab	Add '(opens in new tab)' to text
https://www.normativa.polimi.it/	Normativa di Ateneo	new tab	Add '(opens in new tab)' to text
/campus-e-servizi/servizio-di-prevenzion…	(empty)	empty	Add link text or aria-label
https://www.dona.polimi.it/	Dona al Politecnico	new tab	Add '(opens in new tab)' to text
http://www.fondazionepolitecnico.it/	Fondazione Politecnico	new tab	Add '(opens in new tab)' to text
http://www.careerservice.polimi.it/	Career service	new tab	Add '(opens in new tab)' to text
https://diversityandinclusion.polimi.it/	Diversity & Inclusion	new tab	Add '(opens in new tab)' to text
https://www.qualita.polimi.it/index.php/…	Servizio Qualità di Ateneo	new tab	Add '(opens in new tab)' to text
http://www.polihub.it/	PoliHub	new tab	Add '(opens in new tab)' to text
/campus-e-servizi/servizio-di-prevenzion…	(empty)	empty	Add link text or aria-label
https://www.mynewsdesk.com/it/politecnic…	International Press Releases	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://www.instagram.com/polimi/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/polimi/	Facebook	new tab	Add '(opens in new tab)' to text
https://x.com/polimi	X	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/polimi	YouTube	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/school/polimi/	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@politecnico.di.m…	TikTok	new tab	Add '(opens in new tab)' to text
/il-politecnico/governance/strutture/sed…	Cremona	new tab	Add '(opens in new tab)' to text
/il-politecnico/governance/strutture/sed…	Lecco	new tab	Add '(opens in new tab)' to text
/il-politecnico/governance/strutture/sed…	Mantova	new tab	Add '(opens in new tab)' to text
/il-politecnico/governance/strutture/sed…	Piacenza	new tab	Add '(opens in new tab)' to text
https://webeep.polimi.it/	WeBeep	new tab	Add '(opens in new tab)' to text
https://aunicalogin.polimi.it/aunicalogi…	Cerca aule	new tab	Add '(opens in new tab)' to text
https://aunicalogin.polimi.it/aunicalogi…	Cerca docenti	new tab	Add '(opens in new tab)' to text
https://aunicalogin.polimi.it/aunicalogi…	Cerca insegnamenti	new tab	Add '(opens in new tab)' to text
https://aunicalogin.polimi.it/aunicalogi…	Orario lezioni	new tab	Add '(opens in new tab)' to text
https://aunicalogin.polimi.it/aunicalogi…	Appelli di esame	new tab	Add '(opens in new tab)' to text
https://documentazione.intranet.polimi.i…	Intranet	new tab	Add '(opens in new tab)' to text
https://aunicalogin.polimi.it/aunicalogi…	Mappe dei campus	new tab	Add '(opens in new tab)' to text
https://go.polimi.it/rubrica	Rubrica telefoni e mail	new tab	Add '(opens in new tab)' to text
/il-politecnico/comunicazione/privacy	Privacy policy	new tab	Add '(opens in new tab)' to text
https://kiprotect.com/klaro	Provided by websedit	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

471 links and buttons have descriptive text

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

/campus-e-servizi/servizio-di-prevenzione-e-protezione; /campus-e-servizi/servizio-di-prevenzione-e-protezione; /campus-e-servizi/servizio-di-prevenzione-e-protezione; /campus-e-servizi/servizio-di-prevenzione-e-protezione; /campus-e-servizi/servizio-di-prevenzione-e-protezione; /campus-e-servizi/servizio-di-prevenzione-e-protezione; a#main-content-anchor; a#c4696; a#c4688; a#c4701 (+4 more)

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.normativa.polimi.it/; https://www.protocollo.polimi.it/albo/viewer?view=html; https://webeep.polimi.it/; https://aunicalogin.polimi.it/aunicalogin/getservizio.xml?id_servizio=156; https://aunicalogin.polimi.it/aunicalogin/getservizio.xml?id_servizio=167&evn…; https://aunicalogin.polimi.it/aunicalogin/getservizio.xml?id_servizio=166; https://alumni.polimi.it/; https://www.intranet.polimi.it; https://www.normativa.polimi.it/; https://www.intranet.polimi.it (+47 more)

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.back-to-top (#3229 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

F

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-cnywhv

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

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 Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

F

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://polimi.it/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://polimi.it/manifest.json

Manifest contains invalid JSON.

D

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.

D

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 ✗

D

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Skip navigation link detected

Back-to-top link detected

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 1 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

A+

Landmark Structure

20 landmarks

PASS

20 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Alt Text Quality

All 42 images OK

PASS

All 42 images OK

39 decorative image(s) correctly marked

3 image(s) with good alt text

42 images 3 good alt text 39 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 14 controls labeled

PASS

All 14 controls labeled

14 control(s) properly labeled

14 controls

14 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#purpose-item-funzionali	checkbox	Funzionali	for/id
#service-item-other-8	checkbox	WE Cookie Consent(Sempre necessario)	for/id
#service-item-other-5	checkbox	Vimeo(Opt-Out)	for/id
#service-item-youtube	checkbox	Youtube	for/id
#purpose-item-analitici	checkbox	Analitici	for/id
#service-item-google-tagmanager-12	checkbox	Google Tag Manager	for/id
#service-item-google-tagmanager-service-14	checkbox	Google Analytics 4	for/id
#service-item-google-analytics-7	checkbox	Google Tag(Opt-Out)	for/id
#service-item-other-5	checkbox	Vimeo(Opt-Out)	for/id
#service-item-youtube	checkbox	Youtube	for/id
#purpose-item-tracciamento	checkbox	Tracciamento	for/id
#service-item-google-tagmanager-service-13	checkbox	Google Ads	for/id
#service-item-other-5	checkbox	Vimeo(Opt-Out)	for/id
#purpose-item-disableAll	checkbox	Accetta tutti	for/id

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)

Element	Ratio	Required	FG	BG	Result
h1 Politecnico di Milan…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Test e ammissione	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 News Dottorato di Ri…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Corsi di Dottorato	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 In evidenza	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Magazine	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Entra al Politecnico…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Vai a	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Sito Alumni	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Vai a	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Servizio di Prevenzi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Vai a	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Servizio di Prevenzi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Vai a	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Servizio di Prevenzi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Magazine	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Test e ammissione	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 News Dottorato di Ri…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Corsi di Dottorato	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 In evidenza	21.00:1	3.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 95/100 — 2 failing, 30 passed

PASS

95

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.

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
Come funziona l'ammissione `div.card > div.card-img-overlay > div.card-body > h4.card-title`
Entra nella community della prima Università d'Italia `div.contentcontainer > div.contentcontainer-column > div.frame-header > h6.element-header`
Architettura Urbanistica Ingegneria delle Costruzioni `div.col-12 > div.card > div.card-body > h4.card-title`
Raffrescamento sostenibile: lanciata EPIC Deploy `div.card__content > div.card-body > header > h5.card-title`
Convegno Renewable Energy 2026 `div.card__content > div.card-body > header > h6.card-title`
Polimi Community `div.container > div.row > div.col-lg-4 > h4.mb-0`
Sedi `section#footer__accordion > section.footer__headquarters > div#c296 > h6`

These are opportunities to improve keyboard navigation in your application.

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
IT `section.footer__header > ul#language_menu_footer > li.active > 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

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

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

●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

●`[lang]` attributes have a valid value

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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