Skip to content
https://www.reteassociazioni.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
7
REVIEW
8
PASS
9
INFO
0
Checks
24
9 PASS 8 REVIEW 7 FIX
D
Mobile Keyboard & Autofill
Action
2/2 eligible field(s) missing autocomplete or inputmode
FIX
2/2 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="email" name="EMAIL" id="mce-EMAIL_subscribeNwsletter">
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email" name="EMAIL" id="mce-EMAIL_subscribeNwsletter">
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-xes4q7
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.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://www.reteassociazioni.it/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://www.reteassociazioni.it/manifest.json

Manifest contains invalid JSON.

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
6 landmarks
REVIEW
6 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
Alt Text Quality
6 of 37 images have issues
REVIEW
6 of 37 images have issues
Warning::
6 image(s) with filename as alt text
Info::
4 decorative image(s) correctly marked
Info::
27 image(s) with good alt text
37 images 27 good alt text 4 decorative 6 generic
IssueCount
filename6 image(s)
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="text" name="q">; <input type="email" name="EMAIL" id="mce-EMAIL_subscribeNwsletter">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
qtext(Cerca in Rete Associazioni…)placeholder only
#mce-EMAIL_subscribeNwsletteremail(Scrivi la tua e-mail…)placeholder only

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

<input type="text" name="q">; <input type="email" name="EMAIL" id="mce-EMAIL_subscribeNwsletter">

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

B
Iframe Accessibility
2/3 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
C
Tap Target Adequacy
Action
5 tap target(s) too small or too close together
REVIEW
5 tap target(s) too small or too close together
Warning::
5 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
74% of visible text renders at >= 12 CSS px (42 below threshold)
REVIEW
74% of visible text renders at >= 12 CSS px (42 below threshold)
Warning::
42 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.4px ("Condividi"); <a> 10.4px ("Condividi"); <a> 10.4px ("Condividi"); <a> 10.4px ("Condividi"); <a> 10.4px ("Condividi").
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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
B
Lighthouse Accessibility Audits
Score 80/100 — 6 failing, 23 passed
REVIEW
80

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.span5 > form.simple_form > button.btn div.row > div.span5 > form.simple_form > button.btn

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
nav.navbar > div.navbar-inner > div.clearfix > a.btn nav.navbar > div.navbar-inner > div.clearfix > a.btn
div.articles-container > article.item > div.share-content > a.link-primary div.articles-container > article.item > div.share-content > a.link-primary
div.articles-container > article.item > div.share-content > a.link-primary div.articles-container > article.item > div.share-content > a.link-primary
div.articles-container > article.item > div.share-content > a.link-primary div.articles-container > article.item > div.share-content > a.link-primary
div.articles-container > article.item > div.share-content > a.link-primary div.articles-container > article.item > div.share-content > a.link-primary
div.articles-container > article.item > div.share-content > a.link-primary div.articles-container > article.item > div.share-content > a.link-primary
div.articles-container > article.item > div.share-content > a.link-primary div.articles-container > article.item > div.share-content > a.link-primary
div.articles-container > article.item > div.share-content > a.link-primary div.articles-container > article.item > div.share-content > a.link-primary
div.articles-container > article.item > div.share-content > a.link-primary div.articles-container > article.item > div.share-content > a.link-primary
div.articles-container > article.item > div.share-content > a.link-primary div.articles-container > article.item > div.share-content > a.link-primary
div.articles-container > article.item > div.share-content > a.link-primary div.articles-container > article.item > div.share-content > a.link-primary

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.

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
IL PORTALE DELLE ASSOCIAZONI, FATTO DALLE ASSOCIAZIONI div.span7 > div.logo > a > em
28 Luglio 2026 – article.item > a.link-primary > p > span.muted
CONDIVIDI div.articles-container > article.item > div.share-content > a.dropdown-toggle
09 Giugno 2026 – article.item > a.link-primary > p > span.muted
CONDIVIDI div.articles-container > article.item > div.share-content > a.dropdown-toggle
09 Maggio 2026 – article.item > a.link-primary > p > span.muted
CONDIVIDI div.articles-container > article.item > div.share-content > a.dropdown-toggle
28 Aprile 2026 – article.item > a.link-primary > p > span.muted
CONDIVIDI div.articles-container > article.item > div.share-content > a.dropdown-toggle
12 Aprile 2026 – article.item > a.link-primary > p > span.muted
CONDIVIDI div.articles-container > article.item > div.share-content > a.dropdown-toggle
23 Marzo 2026 – article.item > a.link-primary > p > span.muted
CONDIVIDI div.articles-container > article.item > div.share-content > a.dropdown-toggle
06 Marzo 2026 – article.item > a.link-primary > p > span.muted
CONDIVIDI div.articles-container > article.item > div.share-content > a.dropdown-toggle
28 Gennaio 2026 – article.item > a.link-primary > p > span.muted
CONDIVIDI div.articles-container > article.item > div.share-content > a.dropdown-toggle
20 Gennaio 2026 – article.item > a.link-primary > p > span.muted
CONDIVIDI div.articles-container > article.item > div.share-content > a.dropdown-toggle
29 Agosto 2025 – article.item > a.link-primary > p > span.muted
CONDIVIDI div.articles-container > article.item > div.share-content > a.dropdown-toggle
28 Aprile 2026 – div.articles-container > article.item > p > span.muted
28 Aprile 2026 – div.articles-container > article.item > p > span.muted
29 Agosto 2025 – div.articles-container > article.item > p > span.muted
30 Ottobre 2017 – div.articles-container > article.item > p > span.muted
30 Ottobre 2017 – div.articles-container > article.item > p > span.muted
Copyright © DevInterface srl · Tutti i diritti sono riservati div.container > div.row > div.span7 > p.copyright
Seguici anche su Facebook Twitter div.container > div.row > div.span4 > div.follow-us

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
DevInterface srl div.row > div.span7 > p.copyright > a

These are opportunities to improve the legibility of your content.

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
1 div.photo-carousel > div#photoCarousel > div.carousel-nav > a
2 div.photo-carousel > div#photoCarousel > div.carousel-nav > a.active
3 div.photo-carousel > div#photoCarousel > div.carousel-nav > a
4 div.photo-carousel > div#photoCarousel > div.carousel-nav > a
5 div.photo-carousel > div#photoCarousel > div.carousel-nav > a

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
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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
●`<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
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●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
○`<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
○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
○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 Hierarchy
22 headings
PASS
22 headings
Info::
Single H1 present
  • H1 Il portale delle Associazioni, fatto dalle Associazioni
  • H2 A FRANCESCO CUSA IL DIPLOMA HONORIS CAUSA DELL'ACCADEMIA SICULO-NORMANNA
  • H2 Women for Progress 2026: vince il Kenya con un progetto per le detenute
  • H2 Women for Progress 2026: in Salento le giovani donne che cambiano il mondo
  • H2 Conferito a Sigfrido Ranucci il diploma “honoris causa” dell’Accademia Siculo-Normanna
  • H2 CONCESSO AL “PREMIO DI CULTURA CITTÀ DI MONREALE 2026” L’ALTO PATROCINIO DEL PARLAMENTO EUROPEO
  • H2 Alto Patrocinio del Parlamento Europeo per Women for Progress 2026
  • H2 A “Women for Progress” Nicole Bertolini Ambasciatrice del Progresso
  • H2 LE NOSTRE ATTIVITA'
  • H2 L’Università di Bari e “Women for Progress”: una nuova sinergia nel segno della cultura dei diritti
  • H2 A.E.O.P.C. SOS
  • H2 Ricevi la newsletter di Rete Associazioni
  • H2 Notizie brevi
  • H3 Seguici su YouTube!
  • H3 Seguici su Instagram!
  • H3 "A.E.O.P.C." e logotipo sono ora depositati.
  • H3 Laboratori per bambini
  • H3 Ripetizioni tutte le materie scuole medie e superiori
  • H2 Foto delle associazioni
  • H2 Ultime Associazioni iscritte
  • H2 Link sponsorizzati
  • H2 Informativa
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
4 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: 4 all-caps heading(s)
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+
Document Language
Lang attribute set to "it"
PASS
Lang attribute set to "it"
Info::
<html lang="it"> is set and valid
Got: it
A+
Tabindex Anti-Patterns
5 explicit tabindex attribute(s) checked, no anti-patterns
PASS
5 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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 Il portale delle Ass…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A FRANCESCO CUSA IL …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Women for Progress 2…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Women for Progress 2…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Conferito a Sigfrido…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 CONCESSO AL “PREMI…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Alto Patrocinio del …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A “Women for Progr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 LE NOSTRE ATTIVITA'21.00:13.0:1
#000000
#FFFFFF
Pass
h2 L’Università di B…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A.E.O.P.C. SOS21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ricevi la newsletter…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Notizie brevi21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Foto delle associazi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ultime Associazioni …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Link sponsorizzati21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Informativa21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Seguici su YouTube!21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Seguici su Instagram…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 "A.E.O.P.C." e logot…21.00:13.0: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