Skip to content
https://ilquotidianodellazio.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
6
REVIEW
4
PASS
14
INFO
0
Checks
24
14 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
38 landmarks
FIX
38 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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!) ASIDE 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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
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-q0gzj1
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
26 headings
REVIEW
26 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Peste suina africana, 4 casi a Riano: scatta l’ordinanza nel Lazio, divieti e controlli in 20 Comuni e 2 Municipi di Roma
  • H2 Mario Tozzi: “Gli eventi meteo estremi peggiorano con la crisi climatica”. Dal caldo record alla tragedia in Nepal
  • H2 Acqua sempre più cara nella Tuscia, cittadini contro le bollette Talete: “Aumenti fino al 40% e disservizi”
  • H2 Colleferro, il Data Center può cambiare il futuro del territorio: lavoro, innovazione e sostenibilità ambientale
  • H2 Ilary Blasi sposa Bastian Müller a Ravello: nozze il 13 settembre a Villa Cimbrone, poi subito il ritorno in tv
  • H2 WhatsApp, nuova ondata di attacchi “zero-click”: si può perdere il controllo dell’account senza fare nulla
  • H3 Lecce-Roma 0-4: secondo poker consecutivo
  • H3 Frosinone-Venezia, allo Stirpe in bus con un euro: tornano BRT e navette, ecco parcheggi e orari
  • H3 Roma Capitale, nuovo contratto per i dipendenti: più salario accessorio, 250 euro di welfare e buoni pasto anche in smart working
  • H3 Borgo San Martino saluta l’estate con la “Sagra della Salsiccia”: tre giorni di festa con Iva Zanicchi e l’omaggio a Baglioni
  • H3 Ostia e litorale romano, controlli a tappeto dei Carabinieri: 4 arresti, 8 denunce e droga sequestrata
  • H3 Fontana Candida, accoltella quattro volte al petto l’ex moglie e fugge con il figlio: fermato a Torvajanica dopo sette ore
  • H3 Vissani senza filtri: “Ho fatto soffrire tante donne. Ero un cavallo pazzo. Il mio grande errore? Non andare in America”
  • H3 Alatri, crack e cocaina in casa: un 46enne del posto finisce ai domiciliari
  • H3 Vissani senza filtri: “Ho fatto soffrire tante donne. Ero un cavallo pazzo. Il mio grande errore? Non andare in America”
  • H3 Mario Tozzi: “Questa estate? In futuro ci sembrerà una delle più fresche”
  • H3 Pierluigi Sanna senza filtri: “Il potere non mi ha cambiato, ho dato a Colleferro gli anni più belli della mia vita”
  • H3 Stefano Bartolucci, lo chef che da Valmontone porta il territorio nelle grandi cucine in Italia e nel mondo
  • H3 Caldo record nel Lazio, Mario Tozzi rilancia l’allarme: “La causa è l’uomo”
  • H3 Borgo San Martino saluta l’estate con la “Sagra della Salsiccia”: tre giorni di festa con Iva Zanicchi e l’omaggio a Baglioni
  • H3 Anagni, Cazzullo e Branduardi raccontano San Francesco il 28 agosto
  • H3 Jazz & Wine 2026, Banfi porta Montalcino sui grandi palcoscenici del mondo
  • H3 Jazz & Wine in Montalcino, il weekend del gran finale: Rita Marcotulli ed Enrico Rava celebrano jazz, Brunello e bellezza
  • H3 Edoardo De Angelis al “Ferentino Acustica Festival”: presentazione del nuovo album e concerto serale
  • H3 Alatri Jazz 2026, tre giorni di concerti gratis e masterclass: dal 31 luglio la Ciociaria diventa capitale del jazz
  • H3 Lavorare da casa nel Lazio: come proteggere i dati personali e aziendali

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Tap Target Adequacy
1 tap target(s) too small or too close together
REVIEW
1 tap target(s) too small or too close together
Info::
1 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
Favicon & Branding
9 icon(s) detected
REVIEW
9 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
PWA-ready
REVIEW
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: QL
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name QL ✓192×192 icon ✓512×512 icon ✗Start URL / ✓Display Mode standalone ✓
Name QL Display Mode standalone Icons 1 icon(s)
A
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Warning::
3 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 121 chars - H3: 129 chars - H3: 125 chars
Got: 3 >120-char heading(s)
A+
Alt Text Quality
All 25 images OK
PASS
All 25 images OK
Info::
1 decorative image(s) correctly marked
Info::
24 image(s) with good alt text
25 images 24 good alt text 1 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#stextCERCA NEL SITOfor/id
A+
Form Input Types
1 form control(s) checked, no type mismatches
PASS
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
1 form control(s) checked, no input-semantic issues
PASS
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "it-IT"
PASS
Lang attribute set to "it-IT"
Info::
<html lang="it-IT"> is set and valid
Got: it-IT
A+
Tabindex Anti-Patterns
2 explicit tabindex attribute(s) checked, no anti-patterns
PASS
2 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Mobile-Readable Font Sizes
All 140 visible text node(s) render at >= 12 CSS pixels
PASS
All 140 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A
PWA Depth
2 PWA signal(s) surfaced
PASS
2 PWA signal(s) surfaced
Info::
Manifest has no maskable icon
Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).
Info::
Manifest is missing `theme_color`
Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Mario Tozzi: “Gli …16.13:13.0:1
#000000
#DEE2E6
Pass
h2 Acqua sempre più ca…16.13:13.0:1
#000000
#DEE2E6
Pass
h2 Colleferro, il Data …16.13:13.0:1
#000000
#DEE2E6
Pass
h2 Ilary Blasi sposa Ba…16.13:13.0:1
#000000
#DEE2E6
Pass
h2 WhatsApp, nuova onda…16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Peste suina africana…16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Lecce-Roma 0-4: seco…16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Frosinone-Venezia, a…16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Roma Capitale, nuovo…16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Borgo San Martino sa…16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Ostia e litorale rom…16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Fontana Candida, acc…16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Vissani senza filtri…16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Alatri, crack e coca…16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Vissani senza filtri…16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Mario Tozzi: “Ques…16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Pierluigi Sanna senz…16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Stefano Bartolucci, …16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Caldo record nel Laz…16.13:13.0:1
#000000
#DEE2E6
Pass
h3 Borgo San Martino sa…16.13:13.0:1
#000000
#DEE2E6
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 91/100 — 3 failing, 28 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.

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
Lazio div.p-0 > div.rounded > div.col-12 > span.d-block
Viterbo article.col-12 > div.row > div.col-12 > span.p-2
Italia article.col-12 > div.row > div.col-12 > span.p-2
Roma article.col-12 > div.row > header.col-12 > span.p-2
Roma article.col-12 > div.row > header.col-12 > span.p-2
Roma article.container > div.d-flex > div.ps-2 > a.p-2
Valmontone article.container > div.d-flex > div.ps-2 > a.p-2
Italia article.container > div.d-flex > div.ps-2 > a.p-2
Ferentino article.container > div.d-flex > div.ps-2 > a.p-2

These are opportunities to improve the legibility of your content.

Names and labels

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.mt-1 > div#adv-afd07382 > section#ad-sec-2491 > a.img-fluid div.mt-1 > div#adv-afd07382 > section#ad-sec-2491 > a.img-fluid
div.ms-2 > div#adv-f9061e60 > section#ad-sec-7523 > a.img-fluid div.ms-2 > div#adv-f9061e60 > section#ad-sec-7523 > a.img-fluid
div.col-12 > div#adv-b95ea5bc > section#ad-sec-1017 > a.img-fluid div.col-12 > div#adv-b95ea5bc > section#ad-sec-1017 > a.img-fluid
div.col-12 > div#adv-da342f2d > section#ad-sec-1770 > a.img-fluid div.col-12 > div#adv-da342f2d > section#ad-sec-1770 > a.img-fluid

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
di Alessandra Monti div.p-0 > div.rounded > div.col-12 > a.text-dark

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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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.
●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 `progressbar` elements have accessible names
●Elements use only permitted ARIA attributes
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●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
●No element has a `[tabindex]` value greater than 0
●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
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○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
○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.
○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