Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 6 REVIEW 5 FIX

Tap Target Adequacy

Action

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

FIX

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

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

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.

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

1 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 1 <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

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

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

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

Heading Hierarchy

8 headings

REVIEW

8 headings

No H1 heading found

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

H2 Se puoi immaginarla, puoi guidarla.
H3 STARTER
H3 XTREME
H3 SPORTIVA
H3 Starter
H3 Extreme
H3 Sportiva
H2 Dotazioni di Serie su Tutta la Gamma

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

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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

h3 STARTER

1.23:1

#000000

#1C1C1C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 XTREME

1.23:1

#000000

#1C1C1C

needs 3.0:1 (large text)

19px · bottom of viewport

h3 SPORTIVA

1.23:1

#000000

#1C1C1C

needs 3.0:1 (large text)

19px · bottom of viewport

title Casalini S.r.l. - micro-mobilità itali…

1.30:1

#000000

#282004

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home

1.41:1

#000000

#322602

needs 4.5:1 (normal text)

16px · top of page (header area)

a Chi Siamo

1.51:1

#000000

#3E2808

needs 4.5:1 (normal text)

16px · top of page (header area)

a Contatti

1.42:1

#000000

#382402

needs 4.5:1 (normal text)

16px · top of page (header area)

span Seleziona una pagina

1.32:1

#000000

#24221E

needs 4.5:1 (normal text)

16px · above the fold

a Home

1.44:1

#000000

#242A2C

needs 4.5:1 (normal text)

16px · above the fold

a Chi Siamo

2.42:1

#000000

#5A4839

needs 4.5:1 (normal text)

16px · above the fold

a Contatti

1.53:1

#000000

#332C26

needs 4.5:1 (normal text)

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

span Video Player

1.23:1

#000000

#1C1C1C

needs 4.5:1 (normal text)

16px · above the fold

span 00:01

1.23:1

#000000

#1C1C1C

needs 4.5:1 (normal text)

16px · above the fold

span 00:00

1.23:1

#000000

#1C1C1C

needs 4.5:1 (normal text)

16px · above the fold

span 01:15

1.23:1

#000000

#1C1C1C

needs 4.5:1 (normal text)

16px · above the fold

span Usa i tasti freccia su/giù per aumentar…

1.23:1

#000000

#1C1C1C

needs 4.5:1 (normal text)

16px · above the fold

span Video Player

1.23:1

#000000

#1C1C1C

needs 4.5:1 (normal text)

16px · mid-page

span 00:01

1.23:1

#000000

#1C1C1C

needs 4.5:1 (normal text)

16px · mid-page

span 00:00

1.23:1

#000000

#1C1C1C

needs 4.5:1 (normal text)

16px · mid-page

span 01:15

1.23:1

#000000

#1C1C1C

needs 4.5:1 (normal text)

16px · mid-page

1 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
h3 STARTER	1.23:1	3.0:1	#000000	#1C1C1C	Fail
h3 XTREME	1.23:1	3.0:1	#000000	#1C1C1C	Fail
h3 SPORTIVA	1.23:1	3.0:1	#000000	#1C1C1C	Fail
title Casalini S.r.l. - m…	1.30:1	4.5:1	#000000	#282004	Fail
a Home	1.41:1	4.5:1	#000000	#322602	Fail
a Chi Siamo	1.51:1	4.5:1	#000000	#3E2808	Fail
a Contatti	1.42:1	4.5:1	#000000	#382402	Fail
span Seleziona una pagina	1.32:1	4.5:1	#000000	#24221E	Fail
a Home	1.44:1	4.5:1	#000000	#242A2C	Fail
a Chi Siamo	2.42:1	4.5:1	#000000	#5A4839	Fail
a Contatti	1.53:1	4.5:1	#000000	#332C26	Fail
span Video Player	1.23:1	4.5:1	#000000	#1C1C1C	Fail
span 00:01	1.23:1	4.5:1	#000000	#1C1C1C	Fail
span 00:00	1.23:1	4.5:1	#000000	#1C1C1C	Fail
span 01:15	1.23:1	4.5:1	#000000	#1C1C1C	Fail
span Usa i tasti freccia …	1.23:1	4.5:1	#000000	#1C1C1C	Fail
span Video Player	1.23:1	4.5:1	#000000	#1C1C1C	Fail
span 00:01	1.23:1	4.5:1	#000000	#1C1C1C	Fail
span 00:00	1.23:1	4.5:1	#000000	#1C1C1C	Fail
span 01:15	1.23:1	4.5:1	#000000	#1C1C1C	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

Action

Score 78/100 — 6 failing, 19 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
La città cambia ritmo: scopri la nuova Gamma Casalini 650. `div.et_pb_module > div.et_pb_text_inner > p > b`
La mobilità urbana si evolve e Casalini risponde con la nuova Gamma 650: la min… `div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p`
nuova Gamma 650 `div.et_pb_module > div.et_pb_text_inner > p > b`
Cuore Tecnico: Efficienza e Affidabilità Kubota Al centro della nuova Gamma 650… `div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p`
Cuore Tecnico: Efficienza e Affidabilità Kubota `div.et_pb_module > div.et_pb_text_inner > p > b`
motore bicilindrico Kubota `div.et_pb_module > div.et_pb_text_inner > p > b`
SCR e DPF sviluppato da Casalini `div.et_pb_module > div.et_pb_text_inner > p > b`
STARTER: L’accessibilità e la praticità essenziale per chi cerca comodità nei t… `div.et_pb_text_inner > ul > li > p`
STARTER: `ul > li > p > b`
XTREME: Il carattere e lo stile SUV compatto, perfetto per chi non vuole passar… `div.et_pb_text_inner > ul > li > p`
XTREME: `ul > li > p > b`
SPORTIVA: Dettagli grintosi e look dinamico per chi ama il design audace. `div.et_pb_text_inner > ul > li > p`
SPORTIVA: `ul > li > p > b`
• Interni: sedili Rock Black, ambiente sobrio e funzionale. `div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p`
Interni: `div.et_pb_module > div.et_pb_text_inner > p > strong`
• Interni/comfort: sedili Graphiblack, tappetini moquette, cappelliera e soluzi… `div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p`
Interni/comfort: `div.et_pb_module > div.et_pb_text_inner > p > strong`
• Interni: sedili Black Trofeo, bracciolo, pedali sport, personalizzazione (Kit… `div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p`
Interni: `div.et_pb_module > div.et_pb_text_inner > p > strong`
ESSENZIALE, URBANA, CONCRETA Inizia a guidare la libertà! • Interni: sedili Roc… `div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p`
ESSENZIALE, URBANA, CONCRETA `div.et_pb_module > div.et_pb_text_inner > p > strong`
Interni: `div.et_pb_module > div.et_pb_text_inner > p > strong`
Dotazioni: `div.et_pb_module > div.et_pb_text_inner > p > strong`
Sicurezza/assistenza `div.et_pb_module > div.et_pb_text_inner > p > strong`
Stile e comfort ineguagliabili • Interni/comfort: sedili Graphiblack, tappetini… `div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p`
Interni/comfort: `div.et_pb_module > div.et_pb_text_inner > p > strong`
Dotazioni: `div.et_pb_module > div.et_pb_text_inner > p > strong`
Sicurezza/visibilità: `div.et_pb_module > div.et_pb_text_inner > p > strong`
Eleganza sportiva al massimo • Interni: sedili Black Trofeo, bracciolo, pedali … `div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p`
Eleganza sportiva al massimo `div.et_pb_module > div.et_pb_text_inner > p > strong`
Interni: `div.et_pb_module > div.et_pb_text_inner > p > strong`
Dotazioni: `div.et_pb_module > div.et_pb_text_inner > p > strong`
Apple CarPlay `div.et_pb_module > div.et_pb_text_inner > p > strong`
Android Auto `div.et_pb_module > div.et_pb_text_inner > p > strong`
Sicurezza/manovra: `div.et_pb_module > div.et_pb_text_inner > p > strong`
VEDI TUTTE LE AUTO `div.et_pb_row > div.et_pb_column > div.et_pb_button_module_wrapper > a.et_pb_button`
La NUOVA GAMMA 65O è pensata per chi vive la città ogni giorno e vuole una mobi… `div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p`
NUOVA GAMMA 65O `div.et_pb_module > div.et_pb_text_inner > p > strong`
city car `div.et_pb_module > div.et_pb_text_inner > p > strong`
minicar `div.et_pb_module > div.et_pb_text_inner > p > strong`
COMFORT DI CLASSE SUPERIORE. Sali a bordo e lasciati avvolgere da materiali pre… `div.et_pb_column > div.et_pb_module > div.et_pb_text_inner > p`
COMFORT DI CLASSE SUPERIORE. `div.et_pb_module > div.et_pb_text_inner > p > strong`
avanguardia `div.et_pb_module > div.et_pb_text_inner > p > strong`
integrazione smartphone totale `div.et_pb_module > div.et_pb_text_inner > p > strong`

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.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`
`div.et_pb_module_inner > div > div.carousel_content > img`

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`

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 > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 4 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 5 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 6 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 7 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 8 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 9 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 10 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 11 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 12 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 1 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 2 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 3 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 4 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 5 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 6 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 7 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 8 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 9 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 10 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 11 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 12 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 13 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 14 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 15 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 16 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 17 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`
Go to slide 18 `div > div.own > div.swiper-pagination > span.swiper-pagination-bullet`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js `html.js`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
4 `div > div.own > div.swiper-navi-container > div.swiper-button-prev`
5 `div > div.own > div.swiper-navi-container > div.swiper-button-next`
4 `div > div.own > div.swiper-navi-container > div.swiper-button-prev`
5 `div > div.own > div.swiper-navi-container > div.swiper-button-next`

○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

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

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

●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

●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

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

○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

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

○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

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

○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 Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

Alt Text Quality

34 of 53 images have issues

PASS

34 of 53 images have issues

34 image(s) with generic alt text

18 decorative image(s) correctly marked

1 image(s) with good alt text

53 images 1 good alt text 18 decorative 34 generic

Issue	Count
generic	34 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

18 links, 6 buttons — all OK

PASS

18 links, 6 buttons — all OK

18 link(s) with descriptive text

18 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

24 links and buttons have descriptive text

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

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

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

PASS

46 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+

Mobile-Readable Font Sizes

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

PASS

All 126 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.

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