Accessibility

D

Heading Hierarchy

Action

4 headings, 2 skip(s)

FIX

4 headings, 2 skip(s)

No H1 heading found

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

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

H2 I Nostri Partners
H4 ``Splendide Emozioni`` skipped
H2 “Grande è la fortuna di colui che possiede una buona bottiglia, un buon libro, un buon amico”
H4 Privacy Overview skipped

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

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

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

F

404 Error Page

Action

HTTP 403, bare page

FIX

HTTP 403, bare page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 403 ✗Page Title Unauthorized Access ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

F

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://vernucciobeverage.it/site.webmanifest contains invalid JSON. Browsers cannot parse it.

Got: https://vernucciobeverage.it/site.webmanifest

Manifest contains invalid JSON.

D

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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

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

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

1 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

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.

B

Link & Button Quality

2 issue(s) across 19 links and 1 buttons

REVIEW

2 issue(s) across 19 links and 1 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #; a.cli-privacy-readmore (#255 on page)

2 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.facebook.com/vernucciobeverage/; https://www.instagram.com/vernuccio_beverage/

15 link(s) with descriptive text

19 links

2 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/vernucciobevera…	facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/vernuccio_beve…	instagram	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label

16 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

#; a.cli-privacy-readmore (#255 on page)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://www.facebook.com/vernucciobeverage/; https://www.instagram.com/vernuccio_beverage/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

B

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

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, 12 fail WCAG AA

REVIEW

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

8 pass 12 fail WCAG AA

h2 I Nostri Partners

1.36:1

#000000

on

#2F2214

needs 3.0:1 (large text)

24px · above the fold

h2 “Grande è la fortuna di colui che pos…

2.33:1

#000000

on

#5E4429

needs 3.0:1 (large text)

24px · mid-page · over background image/gradient

title Vernuccio Beverage

1.08:1

#000000

on

#160909

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to content

1.09:1

#000000

on

#1B0A0A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home

1.20:1

#000000

on

#281410

needs 4.5:1 (normal text)

16px · top of page (header area)

a Chi Siamo

1.49:1

#000000

on

#3A271A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Partners

1.73:1

#000000

on

#48302A

needs 4.5:1 (normal text)

16px · above the fold

a News

2.56:1

#000000

on

#594C4A

needs 4.5:1 (normal text)

16px · above the fold

a Contatti

1.36:1

#000000

on

#3A1C1C

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

h4 ``Splendide Emozioni``

1.21:1

#000000

on

#23180D

needs 3.0:1 (large text)

16px · above the fold

a PARTNERS

1.13:1

#000000

on

#1D100E

needs 4.5:1 (normal text)

16px · mid-page

span Molière

1.54:1

#000000

on

#3F2914

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

3 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 I Nostri Partners	1.36:1	3.0:1	#000000	#2F2214	Fail
h2 “Grande è la fort…	2.33:1	3.0:1	#000000	#5E4429	Fail
title Vernuccio Beverage	1.08:1	4.5:1	#000000	#160909	Fail
a Skip to content	1.09:1	4.5:1	#000000	#1B0A0A	Fail
a Home	1.20:1	4.5:1	#000000	#281410	Fail
a Chi Siamo	1.49:1	4.5:1	#000000	#3A271A	Fail
a Partners	1.73:1	4.5:1	#000000	#48302A	Fail
a News	2.56:1	4.5:1	#000000	#594C4A	Fail
a Contatti	1.36:1	4.5:1	#000000	#3A1C1C	Fail
rs-layer Perché da noi il vi…	16.14:1	4.5:1	#FFFFFF	#331A17	Pass
rs-layer è una poesia imbott…	18.18:1	4.5:1	#FFFFFF	#1E130F	Pass
rs-layer VERNUCCIO BEVERAGE	18.10:1	4.5:1	#FFFFFF	#1D1411	Pass
a CHI SIAMO	18.07:1	4.5:1	#FFFFFF	#1C150C	Pass
h4 ``Splendide Emozioni…	1.21:1	3.0:1	#000000	#23180D	Fail
a PARTNERS	1.13:1	4.5:1	#000000	#1D100E	Fail
span Molière	1.54:1	4.5:1	#000000	#3F2914	Fail
a info@vernucciobevera…	9.64:1	4.5:1	#000000	#B6AFA1	Pass
span Via dell'Imbrecciato…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 00149 Roma	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Tel. 06.5502798	21.00:1	4.5:1	#000000	#FFFFFF	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

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Skip link target(s) don't exist on page: #content

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Page Structure — as a screen reader sees it

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Text Quality

All 4 heading(s) have substantive, well-formed text

PASS

All 4 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#wt-cli-checkbox-necessary	checkbox	Necessario	for/id

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

<html lang="it-IT"> is set and valid

Got: it-IT

A+

Tabindex Anti-Patterns

4 explicit tabindex attribute(s) checked, no anti-patterns

PASS

4 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 14 visible text node(s) render at >= 12 CSS pixels

PASS

All 14 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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 93/100 — 2 failing, 18 passed

PASS

93

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
PARTNERS `div.aligncenter > div.vc_column-inner > div.wpb_wrapper > a.dt-button`
DIGITAL IMPACT ITALIA `footer#colophon > div.container > div.site-info > a`
Cookie settings `body.home > div#cookie-law-info-bar > span > a.cli_settings_button`

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
``Splendide Emozioni`` `div.wpb_wrapper > div.title-center > div.dt-title-wrapper > h4.section-tagline`

These are opportunities to improve keyboard navigation in your application.

○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>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●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.

●`button`, `link`, and `menuitem` elements have accessible names

●`[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

●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.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○ARIA attributes are used as specified for the element's role

○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

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○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

○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.

○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.