Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

10 PASS 8 REVIEW 6 FIX

Link & Button Quality

Action

31 issue(s) across 99 links and 28 buttons

FIX

31 issue(s) across 99 links and 28 buttons

25 link(s) with no accessible text

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

Got: a.u_1207399335 (#1013 on page); a.u_1162584985 (#1025 on page); a.u_1273977077 (#1037 on page); a.u_1291247541 (#1049 on page); a.u_1095446018 (#1061 on page); a.u_1769229713 (#1074 on page); a.u_1531248171 (#1086 on page); a.u_1496490420 (#1098 on page); a.u_1066791930 (#1110 on page); a.u_1564003342 (#1122 on page) (+15 more)

16 link(s) open in new tab without warning

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

Got: https://www.cookiebot.com/en/what-is-behind-powered-by-cookiebot/?utm_source=…; https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UT…; https://www.cookiebot.com/goto/privacy-policy/; https://business.safety.google/privacy/; https://www.italiaonline.it/informativa-privacy/; https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UT…; https://www.cookiebot.com; ; tel:+39 096 8205007; (+6 more)

6 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.pswp__button (#1477 on page); button.pswp__button (#1478 on page); button.pswp__button (#1479 on page); button.pswp__button (#1480 on page); button.pswp__button (#1487 on page); button.pswp__button (#1488 on page)

58 link(s) with descriptive text

99 links

25 empty

0 generic text

16 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
https://www.cookiebot.com/en/what-is-beh…	Cookiebot by Usercentrics - op…	new tab	Add '(opens in new tab)' to text
https://www.amazon.com/gp/help/customer/…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.cookiebot.com/goto/privacy-p…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.italiaonline.it/informativa-…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.amazon.com/gp/help/customer/…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.cookiebot.com	Cookiebot	new tab	Add '(opens in new tab)' to text
	Chiamaci +39 096 8205007	new tab	Add '(opens in new tab)' to text
tel:+39 096 8205007	fa-phone	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
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
	Chiamaci +39 096 8205007	new tab	Add '(opens in new tab)' to text
https://www.italiaonline.it	Italiaonline	new tab	Add '(opens in new tab)' to text
https://www.paginegialle.it	Pagine Gialle	new tab	Add '(opens in new tab)' to text
https://www.paginebianche.it	Pagine Bianche	new tab	Add '(opens in new tab)' to text
https://facebook.com/farmaciamarottaplat…	facebook	new tab	Add '(opens in new tab)' to text
https://instagram.com/farmacia_marotta/	instagram	new tab	Add '(opens in new tab)' to text
https://wa.me/+393500865882	whatsapp	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

80 links and buttons have descriptive text

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

a.u_1207399335 (#1013 on page); a.u_1162584985 (#1025 on page); a.u_1273977077 (#1037 on page); a.u_1291247541 (#1049 on page); a.u_1095446018 (#1061 on page); a.u_1769229713 (#1074 on page); a.u_1531248171 (#1086 on page); a.u_1496490420 (#1098 on page); a.u_1066791930 (#1110 on page); a.u_1564003342 (#1122 on page) (+15 more)

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.cookiebot.com/en/what-is-behind-powered-by-cookiebot/?utm_source=…; https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UT…; https://www.cookiebot.com/goto/privacy-policy/; https://business.safety.google/privacy/; https://www.italiaonline.it/informativa-privacy/; https://www.amazon.com/gp/help/customer/display.html/ref=footer_privacy?ie=UT…; https://www.cookiebot.com; ; tel:+39 096 8205007; (+6 more)

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.pswp__button (#1477 on page); button.pswp__button (#1478 on page); button.pswp__button (#1479 on page); button.pswp__button (#1480 on page); button.pswp__button (#1487 on page); button.pswp__button (#1488 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

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 Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

No 192x192 icon

A 192px icon is required for PWA installation.

PWA Install Criteria Not Installable

Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

6 landmarks

REVIEW

6 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

Alt Text Quality

Action

5 of 42 images have issues

REVIEW

5 of 42 images have issues

4 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image(s) with generic alt text

27 decorative image(s) correctly marked

10 image(s) with good alt text

42 images 10 good alt text 27 decorative 1 generic 4 missing

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

Form Accessibility

Action

4 of 9 controls have issues

REVIEW

4 of 9 controls have issues

4 control(s) without accessible label

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

Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">

5 control(s) properly labeled

9 controls

5 labeled

0 placeholder only

4 unlabeled

Control	Type	Label	Method
#CybotCookiebotDialogBodyLevelButtonNecessary	checkbox	Necessary	for/id
#CybotCookiebotDialogBodyLevelButtonPreferences	checkbox	Functional	for/id
#CybotCookiebotDialogBodyLevelButtonStatistics	checkbox	Analytical	for/id
#CybotCookiebotDialogBodyLevelButtonMarketing	checkbox	Profiling	for/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformation	checkbox	Do not sell or share my personal information	for/id
#CybotCookiebotDialogBodyLevelButtonPreferencesInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonStatisticsInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonMarketingInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonNecessaryInline	checkbox	(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

Tabindex Anti-Patterns

0 positive, 4 -1-on-focusable

REVIEW

0 positive, 4 -1-on-focusable

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogPoweredbyCybot">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavDetails">

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavAdSettings">

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavAbout">

Tap Target Adequacy

Action

8 tap target(s) too small or too close together

REVIEW

8 tap target(s) too small or too close together

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

PWA Depth

3 PWA signal(s) surfaced

REVIEW

3 PWA signal(s) surfaced

Manifest is missing `display` -- defaults to browser, no PWA UX

When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

Manifest is missing `theme_color`

Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.

Lighthouse Accessibility Audits

Score 86/100 — 4 failing, 23 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
CHI SIAMO `div#0576da03 > div#1426744210 > p > strong`
TUTTO PER IL TUO BENESSERE `div#a7fc9d71 > div#1095165816 > p.m-text-align-left > strong`

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
CONTATTI `div#0e61dd62 > div#af62b21c > div#1867803455 > h5.text-align-left`

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.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > img.sc-fqkvVR `div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > img.sc-fqkvVR`
div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > img.sc-fqkvVR `div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > img.sc-fqkvVR`
div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > img.sc-fqkvVR `div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > img.sc-fqkvVR`
div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > img.sc-fqkvVR `div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > img.sc-fqkvVR`

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

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
go to slide 1 `div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > button.sc-jlZhew`
go to slide 2 `div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > button.sc-jlZhew`
go to slide 1 `div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > button.sc-jlZhew`
go to slide 2 `div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > button.sc-jlZhew`
go to slide 3 `div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > button.sc-jlZhew`
go to slide 4 `div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > button.sc-jlZhew`
go to slide 5 `div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > button.sc-jlZhew`
go to slide 6 `div.sc-gEvEer > div.sc-gEvEer > div.sc-gEvEer > button.sc-jlZhew`

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

●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

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●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

●Identical links have the same purpose.

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

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

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

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

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

Heading Hierarchy

21 headings, 1 skip(s)

PASS

21 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H5 (missing H3)

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

H1 La tua farmacia a Platania
H2 vicina ad ogni esigenza
H2 Farmacia Marotta
H3 un punto di riferimento per la tua salute
H2 Prodotti e servizi
H3 per prenderti cura di te
H3 Servizi di prevenzione e controllo
H3 Prodotti per la salute e il benessere
H2 Una farmacia che unisce tradizione e innovazione
H3 Professionalità e competenza
H3 Ascolto
H3 Fiducia e vicinanza
H3 Attenzione alla persona
H2 Più attenzioni, più vantaggi per il tuo benessere
H3 Carta fedeltà
H3 Gift voucher
H3 Visite mensili ed eventi con professionisti sanitari
H3 Promozioni
H2 Prenderti cura di te comincia da un buon consiglio
H5 CONTATTI skipped
H5 ORARIO

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

2 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: 2 all-caps heading(s)

A+

Form Input Types

9 form control(s) checked, no type mismatches

PASS

9 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

9 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"

PASS

Lang attribute set to "it"

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

Got: it

A+

Iframe Accessibility

All 2 iframe(s) have descriptive titles

PASS

All 2 iframe(s) have descriptive titles

All 2 iframe(s) have title attributes

A+

Mobile-Readable Font Sizes

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

PASS

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

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

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

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

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

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)

Element	Ratio	Required	FG	BG	Result
title Farmacia a Platania …	19.95:1	4.5:1	#000000	#F9F9F9	Pass
a Consent	17.94:1	4.5:1	#000000	#EDEDED	Pass
a Details	16.36:1	4.5:1	#000000	#E3E3E3	Pass
a [#IABV2SETTINGS#]	15.76:1	4.5:1	#000000	#DFDFDF	Pass
a About	15.76:1	4.5:1	#000000	#DFDFDF	Pass
div This website uses co…	15.76:1	4.5:1	#000000	#DFDFDF	Pass
p This Site uses techn…	15.76:1	4.5:1	#000000	#DFDFDF	Pass
p You can freely accep…	15.76:1	4.5:1	#000000	#DFDFDF	Pass
p by clicking on 'Acce…	15.76:1	4.5:1	#000000	#DFDFDF	Pass
a cookie policy	15.76:1	4.5:1	#000000	#DFDFDF	Pass
p at any time.	15.76:1	4.5:1	#000000	#DFDFDF	Pass
button Show more	15.76:1	4.5:1	#000000	#DFDFDF	Pass
div [#GPC_BANNER_ICON#]	15.76:1	4.5:1	#000000	#DFDFDF	Pass
div [#GPC_TOAST_TEXT#]	15.76:1	4.5:1	#000000	#DFDFDF	Pass
span Consent Selection	15.76:1	4.5:1	#000000	#DFDFDF	Pass
strong Necessary	15.76:1	3.0:1	#000000	#DFDFDF	Pass
strong Functional	15.76:1	3.0:1	#000000	#DFDFDF	Pass
strong Analytical	15.76:1	3.0:1	#000000	#DFDFDF	Pass
strong Profiling	15.76:1	3.0:1	#000000	#DFDFDF	Pass
a Settings	15.76:1	4.5:1	#000000	#DFDFDF	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.