https://www.gazzoseticinesi.ch/home.html

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 6 REVIEW 6 FIX

Alt Text Quality

Action

10 of 24 images have issues

FIX

10 of 24 images have issues

7 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 image-in-link without alt text

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

3 image(s) with generic alt text

9 decorative image(s) correctly marked

5 image(s) with good alt text

24 images 5 good alt text 9 decorative 3 generic 7 missing

Issue	Count
missing	7 image(s)
generic	3 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

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

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 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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.

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

Form Accessibility

2 of 6 controls have issues

REVIEW

2 of 6 controls have issues

2 control(s) without accessible label

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

Got: <input type="text" name="imSpProt" id="imObjectForm_67_prot">; <input type="button" id="imObjectForm_67_form_submit">

4 control(s) properly labeled

6 controls

4 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#imObjectForm_67_1	text	Nome	aria-label
#imObjectForm_67_2	email	Indirizzo e-mail	aria-label
#imObjectForm_67_3	textarea	Messaggio	aria-label
#iuvl5ob7-imCpt	text	Parola di controllo:	for/id
#imObjectForm_67_prot	text	(none)	none
#imObjectForm_67_form_submit	button	(none)	none

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

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

Link & Button Quality

Action

6 issue(s) across 42 links and 14 buttons

REVIEW

6 issue(s) across 42 links and 14 buttons

6 link(s) with no accessible text

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

Got: a#imHeader_imMenuObject_03_after_menu; a#imStickyBar_imMenuObject_06_after_menu; a#imGoToCont; http://www.sprell.ch/; http://www.fizzy.ch; https://mez-mez.ch/

8 link(s) open in new tab without warning

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

Got: http://www.fizzy.ch; http://www.sprell.ch; https://www.brughera.ch/; https://www.bibiteperi.ch/; http://www.romeriobibite.ch; https://www.instagram.com/fizzy.ch/; https://www.facebook.com/Fizzy-Gazzose-Ticinesi-108679736703/?ref=ts; https://www.youtube.com/channel/UCLfLRXSSFbeV7OkT7bOTzCw

28 link(s) with descriptive text

42 links

6 empty

0 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
http://www.fizzy.ch	fizzy	new tab	Add '(opens in new tab)' to text
http://www.sprell.ch	Sprell	new tab	Add '(opens in new tab)' to text
https://www.brughera.ch/	S. Nicolao	new tab	Add '(opens in new tab)' to text
https://www.bibiteperi.ch/	Peri	new tab	Add '(opens in new tab)' to text
http://www.romeriobibite.ch	Romerio	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/fizzy.ch/	instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Fizzy-Gazzose-T…	facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCLfLRXS…	youtube	new tab	Add '(opens in new tab)' to text
http://www.sprell.ch/	(empty)	empty	Add link text or aria-label
http://www.fizzy.ch	(empty)	empty	Add link text or aria-label
https://mez-mez.ch/	(empty)	empty	Add link text or aria-label

42 links and buttons have descriptive text

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

a#imHeader_imMenuObject_03_after_menu; a#imStickyBar_imMenuObject_06_after_menu; a#imGoToCont; http://www.sprell.ch/; http://www.fizzy.ch; https://mez-mez.ch/

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.

http://www.fizzy.ch; http://www.sprell.ch; https://www.brughera.ch/; https://www.bibiteperi.ch/; http://www.romeriobibite.ch; https://www.instagram.com/fizzy.ch/; https://www.facebook.com/Fizzy-Gazzose-Ticinesi-108679736703/?ref=ts; https://www.youtube.com/channel/UCLfLRXSSFbeV7OkT7bOTzCw

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

Mobile-Readable Font Sizes

97% of visible text renders at >= 12 CSS px (1 below threshold)

REVIEW

97% of visible text renders at >= 12 CSS px (1 below threshold)

1 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: <a> 11.0px ("Cookie Policy").

Color Contrast (Screenshot)

Action

20 text elements analyzed, 11 fail WCAG AA

REVIEW

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

9 pass 11 fail WCAG AA 3 pass AA only

a Team

4.41:1

#000000

#6A747D

needs 4.5:1 (normal text)

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

a La Gazzosa

3.59:1

#000000

#5D666E

needs 4.5:1 (normal text)

16px · above the fold

a Produzioni

1.39:1

#000000

#1F272E

needs 4.5:1 (normal text)

16px · above the fold

button ▼

1.61:1

#000000

#2A3239

needs 4.5:1 (normal text)

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

a Politica aziendale

2.86:1

#000000

#4F575E

needs 4.5:1 (normal text)

16px · mid-page

a Jobs

2.48:1

#000000

#464E55

needs 4.5:1 (normal text)

16px · mid-page

button ▼

2.98:1

#000000

#505A63

needs 4.5:1 (normal text)

16px · mid-page

a Contatti

2.72:1

#000000

#4A545D

needs 4.5:1 (normal text)

16px · mid-page

button ENG

1.32:1

#000000

#19232C

needs 4.5:1 (normal text)

16px · mid-page

a Salta menù

2.76:1

#000000

#4B555E

needs 4.5:1 (normal text)

16px · mid-page

span About Us

2.51:1

#000000

#454F58

needs 4.5:1 (normal text)

16px · mid-page

2 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
h1 Home - Gazzose Ticin…	15.38:1	3.0:1	#000000	#D9DDE1	Pass
title Home - Gazzose Ticin…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Vai ai contenuti	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button FRA	8.49:1	4.5:1	#000000	#9CA6AF	Pass
a Salta menù	8.39:1	4.5:1	#000000	#9BA5AE	Pass
span About Us	7.07:1	4.5:1	#000000	#8D97A0	Pass
button ▼	6.13:1	4.5:1	#000000	#828C95	Pass
a L'azienda	5.08:1	4.5:1	#000000	#747E87	Pass
a Team	4.41:1	4.5:1	#000000	#6A747D	Fail
a La Gazzosa	3.59:1	4.5:1	#000000	#5D666E	Fail
a Produzioni	1.39:1	4.5:1	#000000	#1F272E	Fail
button ▼	1.61:1	4.5:1	#000000	#2A3239	Fail
a Politica aziendale	2.86:1	4.5:1	#000000	#4F575E	Fail
a Jobs	2.48:1	4.5:1	#000000	#464E55	Fail
button ▼	2.98:1	4.5:1	#000000	#505A63	Fail
a Contatti	2.72:1	4.5:1	#000000	#4A545D	Fail
a Shop	6.46:1	4.5:1	#000000	#869099	Pass
button ENG	1.32:1	4.5:1	#000000	#19232C	Fail
a Salta menù	2.76:1	4.5:1	#000000	#4B555E	Fail
span About Us	2.51:1	4.5:1	#000000	#454F58	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.

Lighthouse Accessibility Audits

Score 84/100 — 4 failing, 20 passed

REVIEW

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
Il Team `div#imCell_124 > div#imObjectTitle_37_124 > span#imObjectTitle_37_124_text > a`
condizioni di vendita `div#imFooter_imTextObject_03 > div#imFooter_imTextObject_03_tab0 > div.text-inner > a.imCssLink`

These are opportunities to improve the legibility of your content.

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.lh1 > div > div > img.image-1 `div.lh1 > div > div > img.image-1`
div#imTextObject_37_95_tab0 > div.text-inner > div.imTACenter > img.image-0 `div#imTextObject_37_95_tab0 > div.text-inner > div.imTACenter > img.image-0`
div#imTextObject_37_97_tab0 > div.text-inner > div.imTACenter > img.image-0 `div#imTextObject_37_97_tab0 > div.text-inner > div.imTACenter > img.image-0`
div.text-inner > div.lh2 > a.imCssLink > img.image-3 `div.text-inner > div.lh2 > a.imCssLink > img.image-3`
div.lh2 > span.fs11lh2 > a.imCssLink > img.image-0 `div.lh2 > span.fs11lh2 > a.imCssLink > img.image-0`
div.text-inner > div.lh2 > a.imCssLink > img.image-2 `div.text-inner > div.lh2 > a.imCssLink > img.image-2`

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
form#imObjectForm_67_form > fieldset > div.x5captcha-wrap > iframe.captcha-container `form#imObjectForm_67_form > fieldset > div.x5captcha-wrap > iframe.captcha-container`

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#imTextObject_37_127_tab0 > div.text-inner > div.lh2 > a.imCssLink `div#imTextObject_37_127_tab0 > div.text-inner > div.lh2 > a.imCssLink`
div.text-inner > div.lh2 > span.fs11lh2 > a.imCssLink `div.text-inner > div.lh2 > span.fs11lh2 > a.imCssLink`
div#imTextObject_37_127_tab0 > div.text-inner > div.lh2 > a.imCssLink `div#imTextObject_37_127_tab0 > div.text-inner > div.lh2 > a.imCssLink`

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

●Input buttons have discernible text.

●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

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

●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

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

○Heading elements appear in a sequentially-descending order

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

○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

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

A+

Heading Hierarchy

1 headings

PASS

1 headings

Single H1 present

H1 Home - Gazzose Ticinesi SA

A+

Heading Text Quality

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

PASS

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

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

A+

Form Input Types

6 form control(s) checked, no type mismatches

PASS

6 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

6 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

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

PASS

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

No tabindex anti-patterns detected

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Print Stylesheet

Print styles detected

PASS

Print styles detected

External print stylesheet detected

Got: style/print.css?2026-3-6-0

Print Stylesheet ✓ Print Optimized

Print stylesheet style/print.css?2026-3-6-0 ✓Inline @media print Not 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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.