Skip to content
https://Sindacatospettacolo.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
5
REVIEW
8
PASS
11
INFO
0
Checks
24
11 PASS 8 REVIEW 5 FIX
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::
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 1 <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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 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
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="s">; <input type="search" name="s">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
ssearch(Cerca)placeholder only
ssearch(Cerca)placeholder only

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

<input type="search" name="s">; <input type="search" name="s">

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
Tap Target Adequacy
Action
7 tap target(s) too small or too close together
REVIEW
7 tap target(s) too small or too close together
Warning::
7 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
Mobile-Readable Font Sizes
Action
73% of visible text renders at >= 12 CSS px (52 below threshold)
REVIEW
73% of visible text renders at >= 12 CSS px (52 below threshold)
Warning::
52 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <a> 10.0px ("Avvisi e Comunicazioni"); <a> 10.0px ("News"); <a> 10.0px ("Avvisi e Comunicazioni"); <a> 10.0px ("News"); <a> 10.0px ("Avvisi e Comunicazioni").
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Pagina non trovata – agispettacolo@gmail.com info@sindacatospettacolo.it agispettacolo@pec.it ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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 Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 8 fail WCAG AA
REVIEW

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

12 pass 8 fail WCAG AA 5 pass AA only
a agispettacolo@gmail.com info@sindacatosp…
3.75:1
#000000
on
#1A6CA8
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
p TROUPES E GENERICI DELLO SPETTACOLO
3.75:1
#000000
on
#1A6CA8
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Home
3.75:1
#000000
on
#1A6CA8
needs 4.5:1 (normal text)
16px · above the fold
a Avvisi e Comunicazioni
3.75:1
#000000
on
#1A6CA8
needs 4.5:1 (normal text)
16px · above the fold
a Eventi e Manifestazioni
4.41:1
#000000
on
#577A6E
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a News
4.42:1
#000000
on
#76717B
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Ultime dai lavoratori
4.01:1
#000000
on
#746A6A
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Video
2.48:1
#000000
on
#504B54
needs 4.5:1 (normal text)
16px · mid-page

5 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 ARTICOLI RECENTI18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Ultimi articoli18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Categorie18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Archivio18.10:13.0:1
#000000
#EEEEEE
Pass
h2 Link utili18.10:13.0:1
#000000
#EEEEEE
Pass
title agispettacolo@gmail.…9.24:14.5:1
#000000
#A5ACBD
Pass
a Salta al contenuto9.26:14.5:1
#000000
#A6ACBD
Pass
div Mar. Ago 25th, 20266.44:14.5:1
#000000
#6E92B5
Pass
a agispettacolo@gmail.…3.75:14.5:1
#000000
#1A6CA8
Fail
p TROUPES E GENERICI D…3.75:14.5:1
#000000
#1A6CA8
Fail
a Home3.75:14.5:1
#000000
#1A6CA8
Fail
a Avvisi e Comunicazio…3.75:14.5:1
#000000
#1A6CA8
Fail
a Eventi e Manifestazi…4.41:14.5:1
#000000
#577A6E
Fail
a Leggi e Circolari5.18:14.5:1
#000000
#93796A
Pass
a Uncategorized4.99:14.5:1
#000000
#917666
Pass
a News4.42:14.5:1
#000000
#76717B
Fail
a Ultime Sindacali5.50:14.5:1
#000000
#907F7A
Pass
a Ultime dai lavorator…4.01:14.5:1
#000000
#746A6A
Fail
a Nuove lavorazioni5.37:14.5:1
#000000
#907D73
Pass
a Video2.48:14.5:1
#000000
#504B54
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.

B
Lighthouse Accessibility Audits
Score 81/100 — 6 failing, 19 passed
REVIEW
81

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.

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#newsup_posts_list-1 > div.mg-posts-sec > div.mg-sec-title > h4

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
ul.mg-social-header-section > li > span.icon-soci > a ul.mg-social-header-section > li > span.icon-soci > a
ul.mg-social-header-section > li > span.icon-soci > a ul.mg-social-header-section > li > span.icon-soci > a
nav.navbar > div.container-fluid > div.m-header > a.mobilehomebtn nav.navbar > div.container-fluid > div.m-header > a.mobilehomebtn
div.container-fluid > div.m-header > div.dropdown > a#dropdownMenuLink div.container-fluid > div.m-header > div.dropdown > a#dropdownMenuLink
div#block-12 > figure.wp-block-gallery > figure.wp-block-image > a div#block-12 > figure.wp-block-gallery > figure.wp-block-image > a
div#block-12 > figure.wp-block-gallery > figure.wp-block-image > a div#block-12 > figure.wp-block-gallery > figure.wp-block-image > a
div.mg-posts-sec-inner > div.col-lg-6 > div.mg-blog-post > a.link-div div.mg-posts-sec-inner > div.col-lg-6 > div.mg-blog-post > a.link-div
div.row > div.col-md-3 > div.mg-blog-post-3 > a.link-div div.row > div.col-md-3 > div.mg-blog-post-3 > a.link-div
div.row > div.col-md-3 > div.mg-blog-post-3 > a.link-div div.row > div.col-md-3 > div.mg-blog-post-3 > a.link-div
div.row > div.col-md-3 > div.mg-blog-post-3 > a.link-div div.row > div.col-md-3 > div.mg-blog-post-3 > a.link-div
div.row > div.col-md-3 > div.mg-blog-post-3 > a.link-div div.row > div.col-md-3 > div.mg-blog-post-3 > a.link-div
div.row > div.col-md-6 > ul.mg-social > a
div.row > div.col-md-6 > ul.mg-social > a div.row > div.col-md-6 > ul.mg-social > a
div.row > div.col-md-6 > ul.mg-social > a div.row > div.col-md-6 > ul.mg-social > a
div.row > div.col-md-6 > ul.mg-social > a div.row > div.col-md-6 > ul.mg-social > 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.

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
div.container-fluid > div.row > div.col-md-6 > ul.mg-social

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-md-6 > ul.mg-social > a > li div.col-md-6 > ul.mg-social > a > li
div.col-md-6 > ul.mg-social > a > li div.col-md-6 > ul.mg-social > a > li

These are opportunities to improve the experience of reading tabular or list data using 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
AVVISI E COMUNICAZIONI div.mg-blog-post-3 > div.mg-blog-inner > div.mg-blog-category > a.newsup-categories
AVVISI E COMUNICAZIONI div.mg-blog-post-3 > div.mg-blog-inner > div.mg-blog-category > a.newsup-categories
NEWS div.mg-blog-post-3 > div.mg-blog-inner > div.mg-blog-category > a.newsup-categories
AVVISI E COMUNICAZIONI div.mg-blog-post-3 > div.mg-blog-inner > div.mg-blog-category > a.newsup-categories
ULTIME SINDACALI div.mg-blog-post-3 > div.mg-blog-inner > div.mg-blog-category > a.newsup-categories
AVVISI E COMUNICAZIONI div.mg-blog-post-3 > div.mg-blog-inner > div.mg-blog-category > a.newsup-categories
ULTIME SINDACALI div.mg-blog-post-3 > div.mg-blog-inner > div.mg-blog-category > a.newsup-categories

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 html

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
●`[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
●Skip links are focusable.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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 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
○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.
○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
32 headings, 1 skip(s)
PASS
32 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 agispettacolo@gmail.com info@sindacatospettacolo.it agispettacolo@pec.it
  • H2 ARTICOLI RECENTI
  • H4 News skipped
  • H5 NASPI e AUDIOVISIVO NON UN PRIVILEGGIO
  • H5 LAVORATORI RISCHIO CALDO
  • H5 RICHIESTA INCONTRO ASSESSORE MASSIMILIANO SMERIGLIO
  • H5 COMUNICAZIONE EX ART. 34 GDPR – VIOLAZIONE DATI PERSONALI
  • H5 PIATTAFORMA RINNOVO CCNL 2026
  • H5 COMUNICATO x MANIFESTAZIONE
  • H5 ACCORDO STATO REGIONE SICUREZZA SUL LAVORO
  • H5 PROVVEDIMENTO PER LEGGE DEL CINEAUDIOVISIVO
  • H4 Articoli in evidenza
  • H4 FESTIVITA’ DI FERRAGOSTO 2026
  • H4 NASPI e AUDIOVISIVO NON UN PRIVILEGGIO
  • H4 FESTIVITÀ GIUGNO 2026
  • H4 NOTA A VERBALE
  • H4 BASTA LAVORARE SOTTO IL SOLE
  • H4 Attività Sindacale
  • H4 FESTIVITA’ DI FERRAGOSTO 2026
  • H5 FESTIVITA’ DI FERRAGOSTO 2026
  • H5 FESTIVITÀ GIUGNO 2026
  • H5 NOTA A VERBALE
  • H5 BASTA LAVORARE SOTTO IL SOLE
  • H4 Forse ti sei perso qualcosa?
  • H4 FESTIVITA’ DI FERRAGOSTO 2026
  • H4 NASPI e AUDIOVISIVO NON UN PRIVILEGGIO
  • H4 FESTIVITÀ GIUGNO 2026
  • H4 NOTA A VERBALE
  • H2 Ultimi articoli
  • H2 Categorie
  • H2 Archivio
  • H2 Link utili

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

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
19 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: 19 all-caps heading(s)
A+
Alt Text Quality
All 4 images OK
PASS
All 4 images OK
Info::
4 decorative image(s) correctly marked
4 images 4 decorative
All images have appropriate alt text.
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
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback