Skip to content
https://www.psicologionline.net

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
81
GRADE
B
FIX
4
REVIEW
4
PASS
16
INFO
0
Checks
24
16 PASS 4 REVIEW 4 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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #439bde
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 ModePartial Dark Mode
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::
3 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 3 <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
15 landmarks
REVIEW
15 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN 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
Tabindex Anti-Patterns
0 positive, 6 -1-on-focusable
REVIEW
0 positive, 6 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button>
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 <button>
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 <button>
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 <button>
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 <button>
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 <button>
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.)
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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Contenuto non trovato ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
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
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
A+
Heading Hierarchy
38 headings
PASS
38 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Tu scegli chi ti ascolta. Non un algoritmo.
  • H2 Trova lo psicologo adatto a te
  • H2 3 step chiari e semplici
  • H3 Cerca il professionista (online o in studio)
  • H3 Scegli tu il professionista in basealle tue esigenze
  • H3 Prenota il colloquio
  • H2 Scegli lo psicologo adatto a te
  • H2 A cosa può servirti uno psicologo?
  • H2 Lo psicologo risponde
  • H3 Cosa fare?
  • H3 Calo di desiderio, problema di chimica sessuale
  • H3 Relazione stabile ma pensieri frequenti sull’ex
  • H2 Prima di iniziare
  • H2 Perché non usate un algoritmo?
  • H2 Come posso scegliere lo psicologo più adatto a me?
  • H2 Quanto costa una seduta con uno psicologo?
  • H2 Posso contattare direttamente lo psicologo?
  • H2 Ci sono pacchetti o vincoli?
  • H2 Blog
  • H3 Doomer: chi sono e perché aspettarsi il peggio rassicura
  • H3 I papà che fanno la differenza: la figura del padre nel contesto di depressione materna
  • H3 Il sostegno psicologico
  • H3 La percezione di sé e i pensieri automatici
  • H3 Il concetto di Sé
  • H3 L’ottimismo e gli effetti sulla salute
  • H2 Cerchi uno psicologo in presenza?
  • H3 Libertà vera
  • H3 Prima la relazione
  • H3 Zero vincoli
  • H2 Parlano di noi
  • H2 Per i clienti
  • H2 Per i professionisti
  • H2 About Psicologi Online
  • H3 Per i clienti
  • H3 Per i professionisti
  • H3 About Psicologi Online
  • H3 (empty)
  • H2 Informativa Cookie

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+
Heading Text Quality
All 38 heading(s) have substantive, well-formed text
PASS
All 38 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 96 images OK
PASS
All 96 images OK
Info::
50 decorative image(s) correctly marked
Info::
46 image(s) with good alt text
96 images 46 good alt text 50 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 5 controls labeled
PASS
All 5 controls labeled
Info::
5 control(s) properly labeled
5 controls
5 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
modalityradionone
modalityradionone
#v2-search-topictextCosa vuoi affrontare? Scrivi una difficoltà, un approccio o il nome di un professionistaaria-label
#v2-search-locationtextDove cerchi? Scrivi una città o una provinciaaria-label
#citySelectselectDove cerchi?aria-label
A
Form Input Types
2 input(s) using type=text where a specific type would help
PASS
2 input(s) using type=text where a specific type would help
Info::
Input "v2-search-topic" should use type="search" (currently type="text")
Field name "v2-search-topic" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "v2-search-location" should use type="search" (currently type="text")
Field name "v2-search-location" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
5 form control(s) checked, no input-semantic issues
PASS
5 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"
PASS
Lang attribute set to "it"
Info::
<html lang="it"> is set and valid
Got: it
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 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.
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 90 visible text node(s) render at >= 12 CSS pixels
PASS
All 90 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::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
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 Tu scegli chi ti asc…17.94:13.0:1
#000000
#EDEDED
Pass
h2 Trova lo psicologo17.94:13.0:1
#000000
#EDEDED
Pass
h2 adatto a te17.94:13.0:1
#000000
#EDEDED
Pass
h2 3 step chiari e semp…17.94:13.0:1
#000000
#EDEDED
Pass
h2 Scegli lo psicologo17.94:13.0:1
#000000
#EDEDED
Pass
h2 adatto a te17.94:13.0:1
#000000
#EDEDED
Pass
h2 A cosa può servirti…17.94:13.0:1
#000000
#EDEDED
Pass
h2 Lo psicologo rispond…17.94:13.0:1
#000000
#EDEDED
Pass
h2 Prima di iniziare17.94:13.0:1
#000000
#EDEDED
Pass
h2 Blog17.94:13.0:1
#000000
#EDEDED
Pass
h2 Cerchi uno psicologo17.94:13.0:1
#000000
#EDEDED
Pass
h2 Parlano di noi17.94:13.0:1
#000000
#EDEDED
Pass
h2 Informativa Cookie17.94:13.0:1
#000000
#EDEDED
Pass
h3 (online o in studio)17.94:13.0:1
#000000
#EDEDED
Pass
h3 professionista in ba…17.94:13.0:1
#000000
#EDEDED
Pass
h3 alle tue esigenze17.94:13.0:1
#000000
#EDEDED
Pass
h3 Libertà vera17.94:13.0:1
#000000
#EDEDED
Pass
h3 Prima la relazione17.94:13.0:1
#000000
#EDEDED
Pass
h3 Zero vincoli17.94:13.0:1
#000000
#EDEDED
Pass
h3 Per i clienti17.94:13.0:1
#000000
#EDEDED
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+
Lighthouse Accessibility Audits
Score 97/100 — 2 failing, 31 passed
PASS
97

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
Cerca psicologo div.col-lg-5 > div.search-card-wrap > form#v2-search-form > button.btn-search-psy
vedi tutti i professionisti div.search-card-wrap > form#v2-search-form > p.search-card-footer > a
Per i clienti div.accordion-container > div#ac-5 > h2.ac-header > button#ac-trigger-5
Per i professionisti div.accordion-container > div#ac-6 > h2.ac-header > button#ac-trigger-6
About Psicologi Online div.accordion-container > div#ac-7 > h2.ac-header > button#ac-trigger-7
Psicologi Online s.r.l. footer.site-footer > div.row > div.col-lg-3 > div.company-name
info@psicologionline.net div.row > div.col-lg-3 > div.company-info > a
+39 327 3170512 div.row > div.col-lg-3 > div.company-info > a
Partner: Depositphotos footer.site-footer > div.row > div.col-lg-3 > div.partner-line
Depositphotos div.row > div.col-lg-3 > div.partner-line > a
Via P. Giovanni Battista, 2 20124 Milano (MI) - P. IVA: 04905560282 - REA MI – … body > div.footer-wrap > footer.site-footer > div.footer-bottom
psicologionline@legalmail.it div.footer-wrap > footer.site-footer > div.footer-bottom > a
Accetta tutti div.cf3Tgk > div.cf1lHZ > button.cf2Lf6 > span.cf1y60

These are opportunities to improve the legibility of your content.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Accetta tutti div.cf2L3T > div.cf3Tgk > div.cf1lHZ > button.cf2Lf6
Gestisci div.cf2L3T > div.cf3Tgk > div.cf1lHZ > button.cf2Lf6
○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.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●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.
●Links have a discernible name
●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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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