Skip to content
https://governo.it

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
5
REVIEW
7
PASS
1
INFO
0
Checks
13
1 PASS 7 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 403, bare page
FIX
HTTP 403, bare page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
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 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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
Heading Hierarchy
30 headings, 1 skip(s)
REVIEW
30 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Governo Italiano Presidenza del Consiglio dei Ministri
  • H2 Focus
  • H2 Da Palazzo Chigi
  • H3 Il Presidente Meloni al Salone Internazionale del Mobile
  • H3 Incontro con il Presidente del Kenya, William Ruto
  • H3 Il Presidente Meloni all'Assemblea Nazionale di Federalberghi
  • H2 Agenda
  • H2 Gallerie
  • H3 Conferenza stampa del Consiglio dei Ministri n. 170  [VIDEO]
  • H3 Conferenza stampa del Consiglio dei Ministri n. 170  [FOTO]
  • H3 Incontro con il Presidente del Kenya, William Ruto  [FOTO]
  • H3 Incontro con il Presidente del Kenya, William Ruto  [VIDEO]
  • H3 Il Presidente Meloni all'Assemblea Nazionale di Federalberghi  [FOTO]
  • H3 Il Presidente Meloni all'Assemblea Nazionale di Federalberghi  [VIDEO]
  • H2 Dalla Presidenza
  • H3 Giornata Nazionale del Made in Italy, Palazzo Chigi si illumina di Tricolore
  • H3 Intervento del Sottosegretario Mantovano al Convegno "La tutela della persona nella regolazione dell'intelligenza artificiale"
  • H3 “Terra dei Fuochi” e interventi di riqualificazione, il Sottosegretario Mantovano in visita ad Afragola, Caivano e Napoli-Secondigliano
  • H2 Trasparenza
  • H3 Accesso Civico
  • H3 Amministrazione Trasparente
  • H3 Pubblicità Legale e Atti di notifica
  • H3 Normattiva
  • H1 Governo Italiano Presidenza del Consiglio dei Ministri duplicate H1
  • H3 Contatti skipped
  • H3 Seguici su
  • H4 Presidenza del Consiglio dei Ministri
  • H4 Corrispondenza cartacea
  • H4 Indirizzi di posta elettronica
  • H4 Recapiti telefonici

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

C
Alt Text Quality
Action
4 of 24 images have issues
REVIEW
4 of 24 images have issues
Critical::
4 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
18 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
24 images 2 good alt text 18 decorative 4 missing
IssueCount
missing4 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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 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" name="op">
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_block_form" id="form-search-input">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#form-search-inputtext(Cerca...)placeholder only
opsubmit(none)none

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

<input type="submit" name="op">

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" name="search_block_form" id="form-search-input">

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
Favicon & Branding
Action
13 icon(s) detected
REVIEW
13 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
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
title www.governo.it | Governo Italiano Presid…
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · top of page (header area)
p Questo sito utilizza cookies tecnici e d…
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · top of page (header area)
strong Privacy policy
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
16px · top of page (header area)
button Più informazioni
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Presidenza del Consi…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Presidenza del Consi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Focus21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Da Palazzo Chigi21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Agenda21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Gallerie21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Dalla Presidenza21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Trasparenza21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Conferenza stampa de…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Conferenza stampa de…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Incontro con il Pres…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Incontro con il Pres…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Il Presidente Meloni…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Il Presidente Meloni…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Contatti21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Seguici su21.00:13.0:1
#000000
#FFFFFF
Pass
title www.governo.it | Gov…1.66:14.5:1
#000000
#333333
Fail
p Questo sito utilizza…1.66:14.5:1
#000000
#333333
Fail
strong Privacy policy1.66:13.0:1
#000000
#333333
Fail
button Più informazioni1.66:14.5:1
#000000
#333333
Fail

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.

C
Lighthouse Accessibility Audits
Action
Score 72/100 — 5 failing, 13 passed
REVIEW
72

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
Privacy policy a > span > u > strong

These are opportunities to improve the legibility of your content.

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
Contatti div.col-md-9 > div.row > div.col-md-12 > h3.contacts_footer

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.col-md-5 > div.slides_home > img.class_img_url_immagine div.row > div.col-md-5 > div.slides_home > img.class_img_url_immagine

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.main_nav_container > div.burger_wrapper > div.burger_container > a.toggle-menu div.main_nav_container > div.burger_wrapper > div.burger_container > a.toggle-menu
div.row > div.col-md-4 > div.banner_corona_home > a div.row > div.col-md-4 > div.banner_corona_home > a
div.row > div.col-md-4 > div.banner_corona_home > a div.row > div.col-md-4 > div.banner_corona_home > a

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.

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
Sala stampa div.col-md-12 > ul.footer_links > li > a
Come fare per div.col-md-12 > ul.footer_links > li > a
Siti Archeologici div.col-md-12 > ul.footer_links > li > a
Privacy policy div.col-md-12 > ul.footer_links > li > a
Note legali div.col-md-12 > ul.footer_links > li > 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-hidden="true"]` is not present on the document `<body>`
●Buttons have an accessible name
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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.
●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
●Document has a main landmark.
●Identical links have the same purpose.
○`[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
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[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
○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.
○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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
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 CONTENTINFO footer

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

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

Send Feedback