Skip to content
https://cnr.it

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
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.
C
Landmark Structure
Action
4 landmarks
REVIEW
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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 Pagina non trovata | Consiglio Nazionale delle Ricerche Custom Styling Navigation Homepage Link Search Form
B
Lighthouse Accessibility Audits
Score 82/100 — 4 failing, 14 passed
REVIEW
82

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Comunicato stampa 21/04/2026 div.image > article.media-box-container > div.media-box-content > div.media-box-date
Nota stampa 21/04/2026 div.image > article.media-box-container > div.media-box-content > div.media-box-date
Evento 21/04/2026 div.image > article.media-box-container > div.media-box-content > div.media-box-date
Nota stampa 20/04/2026 div.image > article.media-box-container > div.media-box-content > div.media-box-date
Nota stampa 20/04/2026 div.image > article.media-box-container > div.media-box-content > div.media-box-date
Evento 22/04/2026 div.image > article.media-box-container > div.media-box-content > div.media-box-date
Nota stampa 17/04/2026 div.image > article.media-box-container > div.media-box-content > div.media-box-date
Comunicato stampa 14/04/2026 div.image > article.media-box-container > div.media-box-content > div.media-box-date
News 17/04/2026 div.image > article.media-box-container > div.media-box-content > div.media-box-date
News 14/04/2026 div.image > article.media-box-container > div.media-box-content > div.media-box-date

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Devolvi il 5x1000 al Cnr div.row > div#footer-address > p > a
protocollo-ammcen@pec.cnr.it div.row > div#footer-address > p > a

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Facebook Twitter Instagram LinkedIn WhatsApp div#menu-bottom > div.menu-bottom-wrapper > section.social-network > ul

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
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
Deprecated ARIA roles were not used
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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 buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
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.
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.
A
Heading Hierarchy
18 headings
PASS
18 headings
Warning::
Multiple H1 headings (18 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Svalbard, la neve artica è un serbatoio di nuovi processi chimici naturali
  • H1 HFSP Symposium "Frontier Science in Italy": dichiarazione del Presidente del Cnr Andrea Lenzi duplicate H1
  • H1 Coesione, sicurezza e trasformazioni globali: il futuro della politica regionale europea duplicate H1
  • H1 Rispetto in rete: la ‘Carta di Assisi dei bambini’ diventa un racconto animato duplicate H1
  • H1 Un "righello" di precisione per le microonde duplicate H1
  • H1 Workshop "Le infrastrutture di ricerca per l'innovazione" duplicate H1
  • H1 Banche del latte umano donato: una nuova tecnologia per i neonati più fragili duplicate H1
  • H1 CNR - Unioncamere: alleanza per portare la ricerca a "casa" delle imprese duplicate H1
  • H1 Cambiamento climatico: le strategie per salvare Venezia duplicate H1
  • H1 Il CNR rafforza la cooperazione scientifica internazionale: aperti nuovi bandi per progetti di ricerca congiunti duplicate H1
  • H1 Gaia Blu nel Mediterraneo per la campagna PAGES: un nuovo modo di osservare il mare duplicate H1
  • H1 La Toscana custodisce enormi accumuli di magma duplicate H1
  • H1 Aree archeologiche santuari della biodiversità duplicate H1
  • H1 CNR: 185 stabilizzazioni e continuità di 328 contratti PNRR duplicate H1
  • H1 Trova subito duplicate H1
  • H1 Canali duplicate H1
  • H1 Aree tematiche duplicate H1
  • H1 Seguici su 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
All 13 images OK
PASS
All 13 images OK
Info::
12 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
13 images 1 good alt text 12 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
searchtext(Cerca)placeholder only

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

<input type="text" name="search">

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

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 Trova subito21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Canali21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Aree tematiche21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Seguici su21.00:13.0:1
#000000
#FFFFFF
Pass
title Home | Consiglio Naz…21.00:14.5:1
#000000
#FFFFFF
Pass
a Salta al contenuto p…21.00:14.5:1
#000000
#FFFFFF
Pass
span Navigazione21.00:14.5:1
#000000
#FFFFFF
Pass
a Scienze biomediche21.00:14.5:1
#000000
#FFFFFF
Pass
a Chimica e tecnologia…21.00:14.5:1
#000000
#FFFFFF
Pass
a Terra e ambiente21.00:14.5:1
#000000
#FFFFFF
Pass
a Ingegneria, ICT, ene…21.00:14.5:1
#000000
#FFFFFF
Pass
a Fisica e materia21.00:14.5:1
#000000
#FFFFFF
Pass
a Scienze umane e patr…21.00:14.5:1
#000000
#FFFFFF
Pass
a Bio e agroalimentare21.00:14.5:1
#000000
#FFFFFF
Pass
a Cittadini21.00:14.5:1
#000000
#FFFFFF
Pass
a Imprese21.00:14.5:1
#000000
#FFFFFF
Pass
a Scuole21.00:14.5:1
#000000
#FFFFFF
Pass
a Ricercatori21.00:14.5:1
#000000
#FFFFFF
Pass
a Giornalisti21.00:14.5:1
#000000
#FFFFFF
Pass
a Personale21.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.

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

Send Feedback