Skip to content
https://onoranzefunebrisorrentinievallescura.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
5
REVIEW
6
PASS
13
INFO
0
Checks
24
13 PASS 6 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ 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::
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
1 headings
REVIEW
1 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Onoranze Funebri Sorrentini e Vallescura srls

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Iframe Accessibility
2/2 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://www.facebook.com/plugins/page.php?href=https%3A%2F%2Fwww.facebook.com%2…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://www.google.com/maps/embed?pb=!1m14!1m8!1m3!1d11758.981370139318!2d14.12…")
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.
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 Pagina non trovata – Onoranze Funebri Sorrentini ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 13 fail WCAG AA
REVIEW

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

7 pass 13 fail WCAG AA
h2 Onoranze Funebri Sorrentini e Vallescura…
1.46:1
#000000
on
#2A2A2A
needs 3.0:1 (large text)
24px · bottom of viewport
title Onoranze Funebri Sorrentini
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · top of page (header area)
p Diamo valore alla tua privacy
1.01:1
#212121
on
#222222
needs 4.5:1 (normal text)
16px · top of page (header area)
p Utilizziamo i cookie per migliorare la t…
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · top of page (header area)
a Politica sui cookie
2.92:1
#1863DC
on
#222222
needs 4.5:1 (normal text)
16px · top of page (header area)
button Personalizza
2.92:1
#1863DC
on
#222222
needs 4.5:1 (normal text)
16px · above the fold
span Personalizza le preferenze di consenso
1.01:1
#212121
on
#222222
needs 4.5:1 (normal text)
16px · above the fold
p Utilizziamo i cookie per aiutarti a navi…
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · above the fold
button Mostra di più
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · above the fold
button Necessaria
1.01:1
#212121
on
#222222
needs 4.5:1 (normal text)
16px · above the fold
span Sempre attivi
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · above the fold
p I cookie necessari sono fondamentali per…
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · above the fold
div Cookie
1.32:1
#000000
on
#222222
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Onoranze Funebri Sor…1.46:13.0:1
#000000
#2A2A2A
Fail
title Onoranze Funebri Sor…1.32:14.5:1
#000000
#222222
Fail
p Diamo valore alla tu…1.01:14.5:1
#212121
#222222
Fail
p Utilizziamo i cookie…1.32:14.5:1
#000000
#222222
Fail
a Politica sui cookie2.92:14.5:1
#1863DC
#222222
Fail
button Personalizza2.92:14.5:1
#1863DC
#222222
Fail
button Rifiuta tutto15.91:14.5:1
#FFFFFF
#222222
Pass
button Accettare tutto15.91:14.5:1
#FFFFFF
#222222
Pass
span Personalizza le pref…1.01:14.5:1
#212121
#222222
Fail
p Utilizziamo i cookie…1.32:14.5:1
#000000
#222222
Fail
button Mostra di più1.32:14.5:1
#000000
#222222
Fail
button Necessaria1.01:14.5:1
#212121
#222222
Fail
span Sempre attivi1.32:14.5:1
#000000
#222222
Fail
p I cookie necessari s…1.32:14.5:1
#000000
#222222
Fail
div Cookie1.32:14.5:1
#000000
#222222
Fail
div cookieyes-consent19.09:14.5:1
#000000
#F4F4F4
Pass
div Durata19.09:14.5:1
#000000
#F4F4F4
Pass
div 1 anno19.09:14.5:1
#000000
#F4F4F4
Pass
div descrizione19.09:14.5:1
#000000
#F4F4F4
Pass
div CookieYes utilizza q…19.09:14.5:1
#000000
#F4F4F4
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.

B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 24 passed
REVIEW
86

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
085 935 0601 div.wpb_text_column > div.wpb_wrapper > p > a
335.13.80.819 div.wpb_text_column > div.wpb_wrapper > p > a
Siamo reperibili 24 ore su 24, 7 giorni su 7, festivi inclusi. div.wpb_wrapper > div.wpb_text_column > div.wpb_wrapper > p
© 2021 Onoranze Funebri Sorrentini, All Rights Reserved. div.copyright > div.col-md-12 > div.header-elem > p.copyright-text

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Onoranze Funebri Sorrentini div.col-md-12 > div.header-elem > p.copyright-text > 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
div#pageFooter > div#custom_html-2 > div.textwidget > iframe div#pageFooter > div#custom_html-2 > div.textwidget > iframe
div#pageFooter > div#custom_html-3 > div.textwidget > iframe div#pageFooter > div#custom_html-3 > div.textwidget > iframe

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.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover
div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover
div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover
div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover
div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover
div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover
div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover
div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover
div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover div.portfolio-hover > div.gallery-icons > div.center-wrap > a.port-icon-hover

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.

○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
●`[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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●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
○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 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
○Form elements have associated labels
○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.
A
Landmark Structure
5 landmarks
PASS
5 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 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
All 1 heading(s) have substantive, well-formed text
PASS
All 1 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 15 images OK
PASS
All 15 images OK
Info::
11 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
15 images 4 good alt text 11 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ckySwitchanalyticscheckboxAbilitare Analiticaaria-label
stext(Search)placeholder only

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

<input type="text" name="s">

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

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 "s" should use type="search" (currently type="text")
Field name "s" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
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
3 explicit tabindex attribute(s) checked, no anti-patterns
PASS
3 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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 35 visible text node(s) render at >= 12 CSS pixels
PASS
All 35 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