Skip to content
https://splsezzespa.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
6
REVIEW
5
PASS
13
INFO
0
Checks
24
13 PASS 5 REVIEW 6 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 Page Title 404 Not Found Custom Styling Navigation Homepage Link Search Form
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 2 <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
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN CONTENTINFO footer

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

B
Heading Hierarchy
16 headings, 1 skip(s)
REVIEW
16 headings, 1 skip(s)
Warning::
Multiple H1 headings (6 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H5 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Servizi Pubblici Locali Sezze S.p.A.
  • H5 NEWS: skipped
  • H3 Il nuovo sito e l’ App in farmacia
  • H2 Orari di ricevimento al pubblico
  • H2 Contattaci
  • H1 Puoi contattarci agli orari di ricevimento al pubblico e prenotare un Appuntamento. duplicate H1
  • H2 Consulta gli Avvisi al Cittadino
  • H2 Dove siamo
  • H2 Sede Amministrativa
  • H1 Piazza Margherita, 2 duplicate H1
  • H1 (Presso la Biblioteca Comunale duplicate H1
  • H1 Terzo Piano) duplicate H1
  • H1 04018 – Sezze (LT) duplicate H1
  • H2 Sedi Aziendali
  • H2 Contattaci...
  • H2 Seguici sui Social

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
Tap Target Adequacy
Action
4 tap target(s) too small or too close together
REVIEW
4 tap target(s) too small or too close together
Warning::
4 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.
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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
B
Lighthouse Accessibility Audits
Score 87/100 — 4 failing, 23 passed
REVIEW
87

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
Kit Mastelli 2025 div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
CENTRALINO 0773 18 51 636 div.elementor-widget-container > center > button > a.button
Entra nel Canale TELEGRAM div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
Servizi Pubblici Locali Sezze SPA div#block-7 > center > p > b
SEDE LEGALE Via Gattuccia, snc 04018 - Sezze (LT) div.footer-box > div#block-7 > center > p
SEDE LEGALE div#block-7 > center > p > b
SEDE AMMINISTRATIVA Piazza Margherita, 2 - Terzo Piano (Presso la Biblioteca Co… div.footer-box > div#block-7 > center > p
SEDE AMMINISTRATIVA div#block-7 > center > p > b
(Presso la Biblioteca Comunale) div#block-7 > center > p > i
CENTRALINO 0773 18 51 636 div.elementor-widget-container > center > button > a.button
Ok... Accetto e procedo.... div#cookie-notice > div.cookie-notice-container > span#cn-notice-buttons > button#cn-accept-cookie
No div#cookie-notice > div.cookie-notice-container > span#cn-notice-buttons > button#cn-refuse-cookie
Privacy policy div#cookie-notice > div.cookie-notice-container > span#cn-notice-buttons > button#cn-more-info

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
NEWS: div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h5

These are opportunities to improve keyboard navigation in your application.

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.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a.no-lightbox
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
CENTRALINO 0773 18 51 636 div.elementor-element > div.elementor-widget-container > center > button
NumeroVerde div.elementor-element > div.elementor-widget-container > center > button
CENTRALINO 0773 18 51 636 div.elementor-element > div.elementor-widget-container > center > button
NumeroVerde div.elementor-element > div.elementor-widget-container > center > button

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
`[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
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<frame>` or `<iframe>` elements have a title
`<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
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<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.
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.
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 Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A+
Alt Text Quality
All 25 images OK
PASS
All 25 images OK
Info::
15 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
25 images 10 good alt text 15 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ocean-search-form-1searchInserisci una query di ricercaaria-label
#ocean-mobile-search-2searchInserisci una query di ricercaaria-label
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 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
4 explicit tabindex attribute(s) checked, no anti-patterns
PASS
4 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
A+
Mobile-Readable Font Sizes
All 46 visible text node(s) render at >= 12 CSS pixels
PASS
All 46 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
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
h1 Servizi Pubblici Loc…16.69:13.0:1
#000000
#E1E4FB
Pass
h1 04018 – Sezze (LT)16.69:13.0:1
#000000
#E1E4FB
Pass
h2 Orari di ricevimento…16.69:13.0:1
#000000
#E1E4FB
Pass
h2 Contattaci16.69:13.0:1
#000000
#E1E4FB
Pass
h2 Dove siamo16.69:13.0:1
#000000
#E1E4FB
Pass
h2 Sede Amministrativa16.69:13.0:1
#000000
#E1E4FB
Pass
h2 Sedi Aziendali16.69:13.0:1
#000000
#E1E4FB
Pass
h2 Contattaci...16.69:13.0:1
#000000
#E1E4FB
Pass
h2 Seguici sui Social16.69:13.0:1
#000000
#E1E4FB
Pass
title Homepage - S.P.L. SE…21.00:14.5:1
#000000
#FFFFFF
Pass
a Salta al contenuto21.00:14.5:1
#000000
#FFFFFF
Pass
span Homepage7.50:14.5:1
#000000
#8A9DAC
Pass
span DIPENDENTI12.36:14.5:1
#000000
#BDC7DB
Pass
span Comunicati e Avvisi …16.69:14.5:1
#000000
#E1E4FB
Pass
span Servizi alla Cittadi…16.69:14.5:1
#000000
#E1E4FB
Pass
span Tributi16.69:14.5:1
#000000
#E1E4FB
Pass
span Farmacia Comunale16.69:14.5:1
#000000
#E1E4FB
Pass
span Verde e Ambiente16.69:14.5:1
#000000
#E1E4FB
Pass
span Kit Mastelli 202516.69:14.5:1
#000000
#E1E4FB
Pass
span Centro di Raccolta16.69:14.5:1
#000000
#E1E4FB
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