Skip to content
https://geiraonlus.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
77
GRADE
C
FIX
6
REVIEW
5
PASS
13
INFO
0
Checks
24
13 PASS 5 REVIEW 6 FIX
F
Alt Text Quality
Action
5 of 15 images have issues
FIX
5 of 15 images have issues
Critical::
5 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
5 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
10 decorative image(s) correctly marked
15 images 10 decorative 5 missing
IssueCount
missing5 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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.
D
Lighthouse Accessibility Audits
Action
Score 69/100 — 5 failing, 11 passed
FIX
69

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
Geira div.et_pb_module > div.et_pb_text_inner > h1 > span
Scopri i servizi div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
Trasferimenti in ambulanza div.et_pb_module > div.et_pb_text_inner > h2 > strong
Trasferimenti regionali, nazionali ed internazionali con ambulanze infermierist… div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p
regionali div.et_pb_module > div.et_pb_text_inner > p > strong
nazionali div.et_pb_module > div.et_pb_text_inner > p > strong
internazionali div.et_pb_module > div.et_pb_text_inner > p > strong
Trasferimento infermi div.et_pb_module > div.et_pb_text_inner > h2 > strong
Offriamo un servizio di trasferimenti per pazienti professionale e sicuro, gara… div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p
Inviaci un whatsapp div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button
Hai bisogno di altre informazioni? div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > h2
Compila il modulo, ti metterai direttamente in contatto con noi e ti rispondere… div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p
div.et_pb_contact > form.et_pb_contact_form > p.et_pb_contact_field > input#et_pb_contact_name_0 div.et_pb_contact > form.et_pb_contact_form > p.et_pb_contact_field > input#et_pb_contact_name_0
div.et_pb_contact > form.et_pb_contact_form > p.et_pb_contact_field > input#et_pb_contact_email_0 div.et_pb_contact > form.et_pb_contact_form > p.et_pb_contact_field > input#et_pb_contact_email_0
div.et_pb_contact > form.et_pb_contact_form > p.et_pb_contact_field > textarea#et_pb_contact_message_0 div.et_pb_contact > form.et_pb_contact_form > p.et_pb_contact_field > textarea#et_pb_contact_message_0
Contatto telefonico div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > h3

These are opportunities to improve the legibility of your content.

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
Orari di apertura div.et_pb_module > div.et_pb_blurb_content > div.et_pb_blurb_container > h4.et_pb_module_header

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.et_pb_gallery_item > div.et_pb_gallery_image > a > img.wp-image-675 div.et_pb_gallery_item > div.et_pb_gallery_image > a > img.wp-image-675
div.et_pb_gallery_item > div.et_pb_gallery_image > a > img.wp-image-679 div.et_pb_gallery_item > div.et_pb_gallery_image > a > img.wp-image-679
div.et_pb_gallery_item > div.et_pb_gallery_image > a > img.wp-image-678 div.et_pb_gallery_item > div.et_pb_gallery_image > a > img.wp-image-678
div.et_pb_gallery_item > div.et_pb_gallery_image > a > img.wp-image-677 div.et_pb_gallery_item > div.et_pb_gallery_image > a > img.wp-image-677
body.home > img.sgpb-background-image-665 body.home > img.sgpb-background-image-665

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.et_pb_row > div.et_pb_column > div.et_pb_module > a div.et_pb_row > div.et_pb_column > div.et_pb_module > 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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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-hidden="true"]` is not present on the document `<body>`
●Buttons have an accessible name
●Form elements have associated labels
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Elements with visible text labels have matching accessible names.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
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
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 404 - Page not found - Geira Onlus ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 E.T.S.
1.93:1
#000000
on
#3D3D3D
needs 3.0:1 (large text)
32px · mid-page
h2 Trasporto infermi
1.79:1
#000000
on
#383838
needs 3.0:1 (large text)
24px · bottom of viewport
h2 I nostri partner
1.79:1
#000000
on
#383838
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Dicono di noi
1.79:1
#000000
on
#383838
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Disponibili h24
1.79:1
#000000
on
#383838
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Hai bisogno di altre informazioni?
1.79:1
#000000
on
#383838
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Pazienti trattati ogni anno
1.79:1
#000000
on
#383838
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Mezzi impiegati
1.79:1
#000000
on
#383838
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Professionisti impiegati
1.79:1
#000000
on
#383838
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Contatto telefonico
1.79:1
#000000
on
#383838
needs 3.0:1 (large text)
19px · bottom of viewport
title Home - Geira Onlus
1.90:1
#000000
on
#3C3C3C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Servizi
1.99:1
#000000
on
#3F3F3F
needs 4.5:1 (normal text)
16px · top of page (header area)
a Flotta
1.87:1
#000000
on
#3B3B3B
needs 4.5:1 (normal text)
16px · top of page (header area)
a Strutture
1.93:1
#000000
on
#3D3D3D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Lavora con noi
1.79:1
#000000
on
#383838
needs 4.5:1 (normal text)
16px · above the fold
a Eventi
1.90:1
#000000
on
#3C3C3C
needs 4.5:1 (normal text)
16px · above the fold
a Contatti
1.99:1
#000000
on
#3F3F3F
needs 4.5:1 (normal text)
16px · above the fold
a Servizi
1.87:1
#000000
on
#3B3B3B
needs 4.5:1 (normal text)
16px · above the fold
a Flotta
1.93:1
#000000
on
#3D3D3D
needs 4.5:1 (normal text)
16px · above the fold
a Strutture
1.79:1
#000000
on
#383838
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 E.T.S.1.93:13.0:1
#000000
#3D3D3D
Fail
h2 Trasporto infermi1.79:13.0:1
#000000
#383838
Fail
h2 I nostri partner1.79:13.0:1
#000000
#383838
Fail
h2 Dicono di noi1.79:13.0:1
#000000
#383838
Fail
h2 Disponibili h241.79:13.0:1
#000000
#383838
Fail
h2 Hai bisogno di altre…1.79:13.0:1
#000000
#383838
Fail
h3 Pazienti trattati og…1.79:13.0:1
#000000
#383838
Fail
h3 Mezzi impiegati1.79:13.0:1
#000000
#383838
Fail
h3 Professionisti impie…1.79:13.0:1
#000000
#383838
Fail
h3 Contatto telefonico1.79:13.0:1
#000000
#383838
Fail
title Home - Geira Onlus1.90:14.5:1
#000000
#3C3C3C
Fail
a Servizi1.99:14.5:1
#000000
#3F3F3F
Fail
a Flotta1.87:14.5:1
#000000
#3B3B3B
Fail
a Strutture1.93:14.5:1
#000000
#3D3D3D
Fail
a Lavora con noi1.79:14.5:1
#000000
#383838
Fail
a Eventi1.90:14.5:1
#000000
#3C3C3C
Fail
a Contatti1.99:14.5:1
#000000
#3F3F3F
Fail
a Servizi1.87:14.5:1
#000000
#3B3B3B
Fail
a Flotta1.93:14.5:1
#000000
#3D3D3D
Fail
a Strutture1.79:14.5:1
#000000
#383838
Fail

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

A
Heading Hierarchy
19 headings, 1 skip(s)
PASS
19 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 GeiraE.T.S.
  • H2 Trasferimenti in ambulanza
  • H2 Trasporto emodializzati
  • H2 Trasferimento infermi
  • H2 Assistenza per eventi
  • H2 Trasporto infermi
  • H3 Pazienti trattati ogni anno
  • H3 Mezzi impiegati
  • H3 Professionisti impiegati
  • H2 I nostri partner
  • H2 Dicono di noi
  • H2 Disponibili h24
  • H4 Orari di apertura skipped
  • H4 Dove trovarci
  • H4 3338177793
  • H2 Hai bisogno di altre informazioni?
  • H3 Contatto telefonico
  • H4 GEIRA
  • H4 Contatti

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
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+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#et_pb_contact_name_0textNomefor/id
#et_pb_contact_email_0textIndirizzo e-mailfor/id
#et_pb_contact_message_0textareaMessaggiofor/id
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "et_pb_contact_email_0" should use type="email" (currently type="text")
Field name "et_pb_contact_email_0" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
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
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
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 73 visible text node(s) render at >= 12 CSS pixels
PASS
All 73 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::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback