Skip to content
https://psicologi-italia.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
8
REVIEW
6
PASS
10
INFO
0
Checks
24
10 PASS 6 REVIEW 8 FIX
D
Tabindex Anti-Patterns
Action
0 positive, 32 -1-on-focusable
FIX
0 positive, 32 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
D
Tap Target Adequacy
Action
10 tap target(s) too small or too close together
FIX
10 tap target(s) too small or too close together
Warning::
10 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.
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
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
15 of 15 controls have issues
REVIEW
15 of 15 controls have issues
Warning::
15 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="iw-field-a-search_widget_YQCR7DKJot">; <input type="text" id="iw-field-b-search_widget_YQCR7DKJot">; <input type="text" id="iw-field-name-search_widget_YQCR7DKJot">; <input type="text" name="q">; <input type="text" id="iw-field-a-search_widget_qAAMYJLswJ">; <input type="text" id="iw-field-b-search_widget_qAAMYJLswJ">; <input type="text" id="iw-field-name-search_widget_qAAMYJLswJ">; <input type="text" name="q">; <input type="email" name="login_email" id="lLogin_email">; <input type="password" name="login_pass" id="lLogin_pass"> (+5 more)
15 controls
0 labeled
15 placeholder only
0 unlabeled
ControlTypeLabelMethod
#iw-field-a-search_widget_YQCR7DKJottext(Cosa stai cercando?)placeholder only
#iw-field-b-search_widget_YQCR7DKJottext(Dove? (città, via, cap))placeholder only
#iw-field-name-search_widget_YQCR7DKJottext(Digita il nome o il cognome del professionista...)placeholder only
qtext(Es. “curare l’ansia”)placeholder only
#iw-field-a-search_widget_qAAMYJLswJtext(Cosa stai cercando?)placeholder only
#iw-field-b-search_widget_qAAMYJLswJtext(Dove? (città, via, cap))placeholder only
#iw-field-name-search_widget_qAAMYJLswJtext(Digita il nome o il cognome del professionista...)placeholder only
qtext(Es. "curare l'ansia")placeholder only
#lLogin_emailemail(indirizzo e-mail...)placeholder only
#lLogin_passpassword(password...)placeholder only
#lLogin_email_recoveryemail(indirizzo e-mail...)placeholder only
#log_id_nometext(Nome*)placeholder only
#log_id_cognometext(Cognome)placeholder only
#log_id_emailemail(Indirizzo e-mail*)placeholder only
#log_id_passwordpassword(La tua password*)placeholder only

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

<input type="text" id="iw-field-a-search_widget_YQCR7DKJot">; <input type="text" id="iw-field-b-search_widget_YQCR7DKJot">; <input type="text" id="iw-field-name-search_widget_YQCR7DKJot">; <input type="text" name="q">; <input type="text" id="iw-field-a-search_widget_qAAMYJLswJ">; <input type="text" id="iw-field-b-search_widget_qAAMYJLswJ">; <input type="text" id="iw-field-name-search_widget_qAAMYJLswJ">; <input type="text" name="q">; <input type="email" name="login_email" id="lLogin_email">; <input type="password" name="login_pass" id="lLogin_pass"> (+5 more)

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
Form Input Types
6 input(s) using type=text where a specific type would help
REVIEW
6 input(s) using type=text where a specific type would help
Info::
Input "iw-field-a-search_widget_YQCR7DKJot" should use type="search" (currently type="text")
Field name "iw-field-a-search_widget_YQCR7DKJot" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "iw-field-b-search_widget_YQCR7DKJot" should use type="search" (currently type="text")
Field name "iw-field-b-search_widget_YQCR7DKJot" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "iw-field-name-search_widget_YQCR7DKJot" should use type="search" (currently type="text")
Field name "iw-field-name-search_widget_YQCR7DKJot" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "iw-field-a-search_widget_qAAMYJLswJ" should use type="search" (currently type="text")
Field name "iw-field-a-search_widget_qAAMYJLswJ" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "iw-field-b-search_widget_qAAMYJLswJ" should use type="search" (currently type="text")
Field name "iw-field-b-search_widget_qAAMYJLswJ" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "iw-field-name-search_widget_qAAMYJLswJ" should use type="search" (currently type="text")
Field name "iw-field-name-search_widget_qAAMYJLswJ" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
C
Mobile-Readable Font Sizes
Action
78% of visible text renders at >= 12 CSS px (45 below threshold)
REVIEW
78% of visible text renders at >= 12 CSS px (45 below threshold)
Warning::
45 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: <div> 11.0px ("AREA PROMO"); <li> 11.0px ("Depressione"); <li> 11.0px ("Ipnosi"); <li> 11.0px ("Disturbi sessuali"); <li> 11.0px ("Ansia").
C
404 Error Page
Action
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 20 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Nei momenti più imp…3.75:13.0:1
#000000
#8950A5
Pass
h2 Cerca tra le domande…3.75:13.0:1
#000000
#8950A5
Pass
h2 ultimi Psicologi isc…3.75:13.0:1
#000000
#8950A5
Pass
h2 esperienze reali dei…3.75:13.0:1
#000000
#8950A5
Pass
h2 Trova lo psicologo v…3.75:13.0:1
#000000
#8950A5
Pass
h3 Stefano Ira3.75:13.0:1
#000000
#8950A5
Pass
h3 Problemi di coppia3.75:13.0:1
#000000
#8950A5
Pass
h3 Famiglia e bambini3.75:13.0:1
#000000
#8950A5
Pass
h3 Fabiana Zermiani3.75:13.0:1
#000000
#8950A5
Pass
h3 Sofia Franguelli3.75:13.0:1
#000000
#8950A5
Pass
h3 Fausto Ghidini3.75:13.0:1
#000000
#8950A5
Pass
h3 Matilde Sorrenti3.75:13.0:1
#000000
#8950A5
Pass
h3 Thiago Fernandes3.75:13.0:1
#000000
#8950A5
Pass
h3 Giusi Di Matteo3.75:13.0:1
#000000
#8950A5
Pass
h3 Elisa Della Pietra3.75:13.0:1
#000000
#8950A5
Pass
h3 Sharon M. C. Troiano3.75:13.0:1
#000000
#8950A5
Pass
h3 Gloria Friso3.75:13.0:1
#000000
#8950A5
Pass
h3 Micol Migliorini3.75:13.0:1
#000000
#8950A5
Pass
h3 Emanuele Galli3.75:13.0:1
#000000
#8950A5
Pass
h3 Simona Adorni3.75:13.0:1
#000000
#8950A5
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+
Heading Hierarchy
47 headings
PASS
47 headings
Info::
Single H1 present
  • H1 Nei momenti più importanti Psicologi Italia è con te!
  • H2 Cerca tra le domande già inviate
  • H3 ADHD nell' adulto: quando la difficoltà non è mancanza di volontà
  • H3 L'Impatto Neurobiologico del Trauma Oncologico Familiare in Adolescenza: Tra Vulnerabilità Neurale e Resilienza Psico-oncologica
  • H3 Dott.Stefano Ira
  • H3 Problemi di coppia
  • H3 Relazione finita con bimba di 18 mesi
  • H3 Tradimento totale
  • H3 Famiglia e bambini
  • H3 Conflitto emotivo nella scelta di interrompere una gravidanza
  • H3 Cambiamento bimbo 4 anni
  • H3 Dott.ssaFabiana Zermiani
  • H2 ultimi Psicologi iscritti
  • H3 Dott.ssa Sofia Franguelli
  • H3 Dott. Fausto Ghidini
  • H3 Dott.ssa Matilde Sorrenti
  • H3 Dott. Thiago Fernandes
  • H3 Dott.ssa Giusi Di Matteo
  • H3 Dott.ssa Elisa Della Pietra
  • H3 Dott.ssa Sharon M. C. Troiano
  • H3 Dott.ssa Gloria Friso
  • H3 Dott.ssa Micol Migliorini
  • H3 Dott. Emanuele Galli
  • H3 Dott.ssa Simona Adorni
  • H3 Dott.ssa Marina Bonadeni
  • H3 Dott. Ivan Comiti
  • H3 Dott.ssa Angela Frattaruolo
  • H3 Dott. Fabio Chimenti
  • H3 Dott.ssa Sofia Franguelli
  • H3 Dott. Fausto Ghidini
  • H3 Dott.ssa Matilde Sorrenti
  • H3 Dott. Thiago Fernandes
  • H3 Dott.ssa Giusi Di Matteo
  • H3 Dott.ssa Elisa Della Pietra
  • H3 Dott.ssa Sharon M. C. Troiano
  • H3 Dott.ssa Gloria Friso
  • H3 Dott.ssa Micol Migliorini
  • H3 Dott. Emanuele Galli
  • H3 Dott.ssa Simona Adorni
  • H3 Dott.ssa Marina Bonadeni
  • H3 Dott. Ivan Comiti
  • H3 Dott.ssa Angela Frattaruolo
  • H3 Dott. Fabio Chimenti
  • H3 Dott.ssa Sofia Franguelli
  • H3 Dott. Fausto Ghidini
  • H2 esperienze reali dei pazienti
  • H2 Trova lo psicologo vicino a te
A
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Warning::
1 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: 128 chars
Got: 1 >120-char heading(s)
A+
Alt Text Quality
All 41 images OK
PASS
All 41 images OK
Info::
37 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
41 images 4 good alt text 37 decorative
All images have appropriate alt text.
A
Form Input Quality
1 input-semantic issue(s) across 15 form control(s)
PASS
1 input-semantic issue(s) across 15 form control(s)
Info::
2 password field(s) missing or with invalid `autocomplete`
Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="login_pass">, <input type="password" name="reg_password">.
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"
PASS
Lang attribute set to "it"
Info::
<html lang="it"> is set and valid
Got: it
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.
A
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 26 passed
PASS
90

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
14 LUGLIO 2026 div.col-lg-4 > div.post-box > div.bottom > p.date
03 LUGLIO 2026 div.col-lg-4 > div.post-box > div.bottom > p.date
Psicoterapie brevi div.box-cnt > div.psi-area-list > ul.area-list > li
Psicoterapia individuale, coppia, infanzia e adolescenza div.box-cnt > div.psi-area-list > ul.area-list > li
Attacchi di Panico div.box-cnt > div.psi-area-list > ul.area-list > li
Dipendenza affettiva div.box-cnt > div.psi-area-list > ul.area-list > li
Elaborazione del lutto div.box-cnt > div.psi-area-list > ul.area-list > li
Ansia da prestazione e disfunzione erettile div.box-cnt > div.psi-area-list > ul.area-list > li
VAI ALLA SCHEDA div.col-lg-4 > div#as-banprof-5038efc17a4a15817fb77d9ca4b41dfe > div.psi-box > a.btn-default-light
Depressione Post Partum div.box-cnt > div.psi-area-list > ul.area-list > li
Sostegno per traumi psicologici div.box-cnt > div.psi-area-list > ul.area-list > li
EMDR div.box-cnt > div.psi-area-list > ul.area-list > li
TIST (Trauma Informed Stabilization Treatment) div.box-cnt > div.psi-area-list > ul.area-list > li
Terapia focalizzata sulla compassione div.box-cnt > div.psi-area-list > ul.area-list > li
IFS - Internal Family System div.box-cnt > div.psi-area-list > ul.area-list > li
Psicoterapia ad orientamento sistemico relazionale div.box-cnt > div.psi-area-list > ul.area-list > li
Terapia sensomotoria div.box-cnt > div.psi-area-list > ul.area-list > li
Terapia familiare div.box-cnt > div.psi-area-list > ul.area-list > li
Problemi di coppia div.box-cnt > div.psi-area-list > ul.area-list > li
VAI ALLA SCHEDA div.col-lg-4 > div#as-banprof-24ed48a4f5fad5af89480c76ebb27be8 > div.psi-box > a.btn-default-light
VAI ALLA SCHEDA div.slick-slide > div > div.p-3 > a.btn-default-light
15/07/2026 div.p-3 > div.top > p.user > span
Gestisci preferenze div.cm__btns > div.cm__btn-group > button.cm__btn > span

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.col-lg-4 > div.post-box > div.box-img > a.img-wrap div.col-lg-4 > div.post-box > div.box-img > a.img-wrap
div.col-lg-4 > div.post-box > div.box-img > a.img-wrap div.col-lg-4 > div.post-box > div.box-img > a.img-wrap

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
LEGGI div.row > div.col-md-6 > div.box-cnt > a.link-dark
Chi siamo div.footer-nav-wrap > ul#footer-menu-1 > li > a
Assistenza e contatti div.footer-nav-wrap > ul#footer-menu-1 > li > a
Sitemap div.footer-nav-wrap > ul#footer-menu-1 > li > a
Trova lo Psicologo giusto div.footer-nav-wrap > ul#footer-menu-2 > li > a
Descrivi il tuo problema div.footer-nav-wrap > ul#footer-menu-2 > li > a
Privacy policy - utenti div.footer-nav-wrap > ul#footer-menu-2 > li > a
ISCRIVITI GRATIS su Psicologi Italia div.footer-nav-wrap > ul#footer-menu-3 > li > a
Marketing per Psicologi div.footer-nav-wrap > ul#footer-menu-3 > li > a
Privacy policy - Professionista div.footer-nav-wrap > ul#footer-menu-3 > 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-*]` 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
●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
●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
●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.
●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
○Image elements do not have `[alt]` attributes that are redundant text.
○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