Skip to content
https://www.studiovarotto.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
4
REVIEW
7
PASS
13
INFO
0
Checks
24
13 PASS 7 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
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.
B
Heading Hierarchy
19 headings, 1 skip(s)
REVIEW
19 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Psychology of Community – Dr.ssa Alessandra Varotto
  • H3 Menu principale skipped
  • H1 Home duplicate H1
  • H2 STUDIO DI PSICOLOGIA VAROTTO
  • H3 PSYCHOLOGY OF COMMUNITY – Servizi di psicologia di comunitàDr.ssa Alessandra Varotto  amministratrice unica del sito www.studiovarotto.com. Tutti i contenuti Web, in particolare testi, fotografie
  • H2 (empty)
  • H3 05.10.2021 Famiglia tra tradizione e modernità: un confronto tra Italia e Germania
  • H3 09.04.2021 Il burnout, un male sociale nascosto
  • H3 22.05.2020
  • H3 02.05.2020
  • H3 01.04.2020
  • H3 27.03.2020
  • H3 13.12.2019
  • H3 03.12.2019
  • H3 25.04.2018
  • H3 20.12.2017
  • H3 05.07.2017
  • H3 26.02.2017
  • H3 Rubrica Genitori e Figli Viversani e Belli

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

C
Tap Target Adequacy
Action
4 tap target(s) too small or too close together
REVIEW
4 tap target(s) too small or too close together
Warning::
4 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
C
Mobile-Readable Font Sizes
Action
78% of visible text renders at >= 12 CSS px (26 below threshold)
REVIEW
78% of visible text renders at >= 12 CSS px (26 below threshold)
Warning::
26 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: <h3> 10.0px ("PSYCHOLOGY OF COMMUNITY – Servizi di psi..."); <h3> 10.0px ("Dr.ssa Alessandra Varotto\u00a0 amministratri..."); <strong> 10.0px ("Tutti i contenuti Web, in particolare te..."); <a> 10.0px ("copyright"); <th> 10.0px ("Rank").
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Pagina non trovata | Psychology of Community – Dr.ssa Alessandra Varotto ✓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
B
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 24 passed
REVIEW
85

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
TO WHOM IT MAY CONCERN figure.aligncenter > figcaption.wp-element-caption > strong > a
COPYRIGHT div.entry-content > h3 > strong > a
Deutsch ul > li.lang-item > a > span
English ul > li.lang-item > a > span
Italiano ul > li.lang-item > a > span
Flirting online al posto del contatto corporeo? Un approfondimento sul tema dei… div.textwidget > p > a > span
Modi e mode di stare insieme: un’approfondimento sulle coppie che si formano on… div.textwidget > p > a > span
Gli occhi, lo sguardo e il loro significato psicologico: un approfondimento sui… div.textwidget > p > a > span
La prima impressione e i suoi fattori d’influenza div.textwidget > p > a > span
Perchè il contatto corporeo provoca effetti positivi sulla salute psicofisica? aside#custom_html-5 > div.textwidget > a > font
Allarme smartphone e benessere psicologico div.textwidget > p > a > font
Bisogni di appartenenza e senso di solitudine. Crisi e opportunità per lo svilu… div.textwidget > p > a > font
L’incontro interculturale e i nuovi scenari di terapia div.textwidget > p > a > font
Trasferirsi in un altro paese: il mal di casa e il processo di adattamento del … div.textwidget > p > a > font
L’invecchiamento secondo una prospettiva di sviluppo div.textwidget > p > a > font
Psicologi-Italia.it div.wp-widget-group__inner-blocks > div#iw_widget_8ac8110290b70e16f85a0b88f964ee87b0518a5b > div > a

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
aside#block-7 > div.wp-widget-group__inner-blocks > div#iw_widget_8ac8110290b70e16f85a0b88f964ee87b0518a5b > iframe#WidgetFrameId_8ac8110290b70e16f85a0b88f964ee87b0518a5b aside#block-7 > div.wp-widget-group__inner-blocks > div#iw_widget_8ac8110290b70e16f85a0b88f964ee87b0518a5b > iframe#WidgetFrameId_8ac8110290b70e16f85a0b88f964ee87b0518a5b

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
body.home > div#page > header#branding > a body.home > div#page > header#branding > a
article#post-63 > div.entry-content > div#cycloneslider-perche-lapproccio-ecologico-alla-psicologia-di-comunita-1 > a.cycloneslider-prev article#post-63 > div.entry-content > div#cycloneslider-perche-lapproccio-ecologico-alla-psicologia-di-comunita-1 > a.cycloneslider-prev
article#post-63 > div.entry-content > div#cycloneslider-perche-lapproccio-ecologico-alla-psicologia-di-comunita-1 > a.cycloneslider-next article#post-63 > div.entry-content > div#cycloneslider-perche-lapproccio-ecologico-alla-psicologia-di-comunita-1 > a.cycloneslider-next
div.entry-content > div.wp-block-image > figure.aligncenter > a div.entry-content > div.wp-block-image > figure.aligncenter > a
div#main > div#secondary > aside#media_image-25 > a div#main > div#secondary > aside#media_image-25 > a
div#main > div#secondary > aside#media_image-22 > a div#main > div#secondary > aside#media_image-22 > a
div#main > div#secondary > aside#media_image-14 > a div#main > div#secondary > aside#media_image-14 > a
div#main > div#secondary > aside#media_image-17 > a div#main > div#secondary > aside#media_image-17 > a
div#main > div#secondary > aside#media_image-19 > a div#main > div#secondary > aside#media_image-19 > a
div#supplementary > div#second > aside#media_image-9 > a div#supplementary > div#second > aside#media_image-9 > a
div#supplementary > div#third > aside#media_image-6 > a div#supplementary > div#third > aside#media_image-6 > 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.

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
Menu principale div#page > header#branding > nav#access > h3.assistive-text

These are opportunities to improve keyboard navigation in your application.

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
article#post-63 > div.entry-content > details.wp-block-details > summary article#post-63 > div.entry-content > details.wp-block-details > summary
Deutsch aside#polylang-7 > ul > li.lang-item > a
English aside#polylang-7 > ul > li.lang-item > a
Italiano aside#polylang-7 > ul > li.lang-item > 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 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
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○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.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Landmark Structure
35 landmarks
PASS
35 landmarks
Info::
<main> landmark present
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 ASIDE CONTENTINFO footer

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

A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 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: 195 chars
Got: 1 >120-char heading(s)
Info::
1 heading(s) are all-uppercase (excluding short acronyms)
Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.
Got: 1 all-caps heading(s)
A+
Alt Text Quality
All 35 images OK
PASS
All 35 images OK
Info::
24 decorative image(s) correctly marked
Info::
11 image(s) with good alt text
35 images 11 good alt text 24 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="submit" id="searchsubmit">
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#stextCercafor/id
#wp-block-search__input-1searchCercafor/id
#searchsubmitsubmit(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input type="submit" name="submit" id="searchsubmit">

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+
Form Input Types
3 form control(s) checked, no type mismatches
PASS
3 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
3 form control(s) checked, no input-semantic issues
PASS
3 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
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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+
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 Home8.83:13.0:1
#000000
#96B400
Pass
h2 STUDIO DI PSICOLOGIA…6.76:13.0:1
#000000
#7D9E01
Pass
h3 Menu principale8.94:13.0:1
#000000
#98B500
Pass
h3 PSYCHOLOGY OF COMMUN…5.70:13.0:1
#000000
#6D9101
Pass
h3 Dr.ssa Alessandra Va…5.70:13.0:1
#000000
#6D9101
Pass
h3 05.10.2021 Famiglia …5.70:13.0:1
#000000
#6D9101
Pass
h3 09.04.2021 Il burnou…5.70:13.0:1
#000000
#6D9101
Pass
h3 22.05.20205.70:13.0:1
#000000
#6D9101
Pass
h3 02.05.20205.70:13.0:1
#000000
#6D9101
Pass
h3 01.04.20205.70:13.0:1
#000000
#6D9101
Pass
h3 27.03.20205.70:13.0:1
#000000
#6D9101
Pass
h3 13.12.20195.70:13.0:1
#000000
#6D9101
Pass
h3 03.12.20195.70:13.0:1
#000000
#6D9101
Pass
h3 25.04.20185.70:13.0:1
#000000
#6D9101
Pass
h3 20.12.20175.70:13.0:1
#000000
#6D9101
Pass
h3 05.07.20175.70:13.0:1
#000000
#6D9101
Pass
h3 26.02.20175.70:13.0:1
#000000
#6D9101
Pass
h3 Rubrica Genitori e F…5.70:13.0:1
#000000
#6D9101
Pass
title Psychology of Commun…7.57:14.5:1
#000000
#88A700
Pass
a Vai al contenuto pri…8.55:14.5:1
#000000
#94B100
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