Skip to content
https://www.sixgearengineering.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
69
GRADE
D
FIX
7
REVIEW
8
PASS
9
INFO
0
Checks
24
9 PASS 8 REVIEW 7 FIX
F
Heading Hierarchy
Action
63 headings, 5 skip(s)
FIX
63 headings, 5 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Tutto per la tua auto. Tutto online.
  • H3 Ricambi nuovi e usati, spediti in tutta Italia skipped
  • H3 Esperienza completa
  • H3 Affidabilità garantita anche sull'usato
  • H2 Cosa puoi trovare nel nostro shop
  • H3 Spinterogeno distributore d'accensione MZ29 Mazda B2600 MPV motore benzina 2.606 cc aspirato. Distributor Spectra MZ29.
  • H3 Rotore distributore spinterogeno Facet 3.8229 per Fiat vecchia 500. Nuovo.
  • H3 Centralina relè preriscaldamento Volvo 8692616 V70 C70.
  • H3 Calotta Facet 2.7714 per Fiat Panda (141A), Seta Ibiza I (021A), Seta Marbella (28) motore 903. Nuova.
  • H2 Perché scegliere Sixgear Engineering
  • H4 Ricambi selezionati e testati skipped
  • H2 01.
  • H4 Rimborso garantito sull'usato skipped
  • H2 02.
  • H4 Oltre 15anni di esperienza skipped
  • H2 03.
  • H4 Spedizioni rapide in tutta Italia skipped
  • H2 04.
  • H2 Trova subito quello che ti serve
  • H3 Accensioni e bobine
  • H3 Airbag
  • H3 Alternatori
  • H3 Assetti e sospensioni
  • H3 Ammortizzatori
  • H3 Barre Stabilizzatrici
  • H3 Boccole e tiranti
  • H3 Bracci sospensioni
  • H3 Molle
  • H3 Mozzi
  • H3 Varie.
  • H3 Auto e Moto usate
  • H3 Batterie
  • H3 Cambi automatici
  • H3 Cambi meccanici
  • H3 Candele cavi e calotte
  • H3 Carrozzeria
  • H3 Cofani
  • H3 Griglie mascherine
  • H3 Paraurti
  • H3 Porte
  • H3 Maniglie
  • H3 Specchi
  • H3 Telaio
  • H3 Vetri
  • H3 Cavi, corde e funi
  • H3 Centraline, cablaggi e connettori
  • H3 Body computer
  • H3 Centraline ABS
  • H3 Centraline clima
  • H3 Centraline portafusibili
  • H3 Cerchi in ferro
  • H3 Cerchi in lega
  • H3 Clima
  • H3 Radiatori riscaldamento
  • H3 Stufe riscaldamento e Ventilatori
  • H2 Hai bisogno di assistenza o informazioni? Scrivici!
  • H3 Contattaci
  • H3 Dicono di noi
  • H4 Sede
  • H4 Recapiti
  • H4 Pagamenti
  • H4 Legale
  • H4 Place an image or any other element you want

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

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

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
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
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 ✗
D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 5 <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
Landmark Structure
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Info::
5 <nav> landmark(s) found
Warning::
5 of 5 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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

C
Form Accessibility
Action
5 of 17 controls have issues
REVIEW
5 of 17 controls have issues
Critical::
5 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">; <input type="submit" name="submit" id="1488389325">
Info::
12 control(s) properly labeled
17 controls
12 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
#CybotCookiebotDialogBodyLevelButtonNecessarycheckboxNecessaryfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencescheckboxFunctionalfor/id
#CybotCookiebotDialogBodyLevelButtonStatisticscheckboxAnalyticalfor/id
#CybotCookiebotDialogBodyLevelButtonMarketingcheckboxProfilingfor/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformationcheckboxDo not sell or share my personal informationfor/id
#1779120068textCercaaria-label
#1010428193textCercaaria-label
#1162920482textCercaaria-label
#1156193319emailE-mail:for/id
#1436774627textareaMessaggio:for/id
#1039022007checkboxnone
#1181332045checkboxnone
#CybotCookiebotDialogBodyLevelButtonNecessaryInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonPreferencesInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonStatisticsInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonMarketingInlinecheckbox(none)none
#1488389325submit(none)none

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

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">; <input type="submit" name="submit" id="1488389325">

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

B
Tabindex Anti-Patterns
0 positive, 4 -1-on-focusable
REVIEW
0 positive, 4 -1-on-focusable
Info::
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.)
Info::
tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavDetails">
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.)
Info::
tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavAdSettings">
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.)
Info::
tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavAbout">
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.)
B
Tap Target Adequacy
3 tap target(s) too small or too close together
REVIEW
3 tap target(s) too small or too close together
Info::
3 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.
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
PWA Depth
4 PWA signal(s) surfaced
REVIEW
4 PWA signal(s) surfaced
Info::
Service worker registration detected
The page calls `navigator.serviceWorker.register(...)` -- the prerequisite for any real PWA capability (offline support, push notifications, background sync, Cache API). This is a positive signal; whether the registered worker actually does what you want is a separate question (check DevTools > Application > Service Workers).
Warning::
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).
Info::
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).
Info::
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.
C
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 Spinterogeno distributore d'accensione M…
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Rotore distributore spinterogeno Facet 3…
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Centralina relè preriscaldamento Volvo …
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Calotta Facet 2.7714 per Fiat Panda (141…
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Accensioni e bobine
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Airbag
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Alternatori
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Assetti e sospensioni
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ammortizzatori
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Barre Stabilizzatrici
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Boccole e tiranti
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Bracci sospensioni
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Molle
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Mozzi
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Varie.
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Auto e Moto usate
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Batterie
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cambi automatici
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cambi meccanici
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Candele cavi e calotte
1.12:1
#000000
on
#131214
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 Spinterogeno distrib…1.12:13.0:1
#000000
#131214
Fail
h3 Rotore distributore …1.12:13.0:1
#000000
#131214
Fail
h3 Centralina relè pre…1.12:13.0:1
#000000
#131214
Fail
h3 Calotta Facet 2.7714…1.12:13.0:1
#000000
#131214
Fail
h3 Accensioni e bobine1.12:13.0:1
#000000
#131214
Fail
h3 Airbag1.12:13.0:1
#000000
#131214
Fail
h3 Alternatori1.12:13.0:1
#000000
#131214
Fail
h3 Assetti e sospension…1.12:13.0:1
#000000
#131214
Fail
h3 Ammortizzatori1.12:13.0:1
#000000
#131214
Fail
h3 Barre Stabilizzatric…1.12:13.0:1
#000000
#131214
Fail
h3 Boccole e tiranti1.12:13.0:1
#000000
#131214
Fail
h3 Bracci sospensioni1.12:13.0:1
#000000
#131214
Fail
h3 Molle1.12:13.0:1
#000000
#131214
Fail
h3 Mozzi1.12:13.0:1
#000000
#131214
Fail
h3 Varie.1.12:13.0:1
#000000
#131214
Fail
h3 Auto e Moto usate1.12:13.0:1
#000000
#131214
Fail
h3 Batterie1.12:13.0:1
#000000
#131214
Fail
h3 Cambi automatici1.12:13.0:1
#000000
#131214
Fail
h3 Cambi meccanici1.12:13.0:1
#000000
#131214
Fail
h3 Candele cavi e calot…1.12:13.0:1
#000000
#131214
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.

B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 23 passed
REVIEW
82

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Visa div.photoGalleryThumbs > div.thumbnailInnerWrapper > div.image-container > a.u_1525464210
PayPal div.photoGalleryThumbs > div.thumbnailInnerWrapper > div.image-container > a.u_1000388742
Nexi div.photoGalleryThumbs > div.thumbnailInnerWrapper > div.image-container > a.u_1716170839
Mastercard div.photoGalleryThumbs > div.thumbnailInnerWrapper > div.image-container > a.u_1394490588

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
"Officina assolutamente da consigliare, personale più che qualificato, gentile … div#review-list > div.col-12 > div.review-card > p.review-text
mario rosati div.review-card > div.review-user > div.review-info > strong.review-username
"Professionali e competenti!" div#review-list > div.col-12 > div.review-card > p.review-text
Massimo CdiC div.review-card > div.review-user > div.review-info > strong.review-username
"Ricambio ordinato domenica, spedito subito al lunedì con BRT ed arrivato merco… div#review-list > div.col-12 > div.review-card > p.review-text
Cow Boe div.review-card > div.review-user > div.review-info > strong.review-username
Via dell'Industria - 06018 Umbertide - Calzolaro (PG) div#widget_nsv > div#4082714354 > p.text-align-left > span
+39 0759302279 div#73f17b87 > div#1167687578 > p.text-align-left > span
+39 3358260113 div#73f17b87 > div#1167687578 > p.text-align-left > span
sixgearengineering@gmail.com div#widget_uo2 > div#1914997443 > p.text-align-left > a
Termini e condizioni div#04fb8c5e > div#1442507344 > p.m-text-align-center > a
Diritto di Recesso div#04fb8c5e > div#1442507344 > p.m-text-align-center > a
Spedizioni div#04fb8c5e > div#1442507344 > p.m-text-align-center > a
+393358260113 div#widget_6cm > div#2658278648 > a.dmWidget > span.text

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
RICAMBI NUOVI E USATI, SPEDITI IN TUTTA ITALIA div#946afaad > div#3fe92c4b > div#1882657119 > h3.text-align-left
RICAMBI SELEZIONATI E TESTATI div#group_2nq > div#widget_ifq > div#1003182690 > h4
RIMBORSO GARANTITO SULL'USATO div#f070d8c2 > div#73b5cf56 > div#1484939834 > h4
OLTRE 15ANNI DI ESPERIENZA div#c70a97c3 > div#214fa721 > div#1204793425 > h4
SPEDIZIONI RAPIDE IN TUTTA ITALIA div#4c6d719c > div#4c15d1bb > div#1909127122 > h4

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.review-user > div.review-info > span.text-muted > img div.review-user > div.review-info > span.text-muted > img
div.review-user > div.review-info > span.text-muted > img div.review-user > div.review-info > span.text-muted > img
div.review-user > div.review-info > span.text-muted > img div.review-user > div.review-info > span.text-muted > 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

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
Termini e condizioni div#04fb8c5e > div#1442507344 > p.m-text-align-center > a
Diritto di Recesso div#04fb8c5e > div#1442507344 > p.m-text-align-center > a
Spedizioni div#04fb8c5e > div#1442507344 > p.m-text-align-center > a

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
●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
●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
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●All heading elements contain content.
○`[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
○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 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.
○Tables have different content in the summary attribute and `<caption>`.
○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 Text Quality
All 63 heading(s) have substantive, well-formed text
PASS
All 63 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
1 of 95 images have issues
PASS
1 of 95 images have issues
Warning::
1 image(s) with generic alt text
Info::
3 decorative image(s) correctly marked
Info::
91 image(s) with good alt text
95 images 91 good alt text 3 decorative 1 generic
IssueCount
generic1 image(s)
A+
Form Input Types
17 form control(s) checked, no type mismatches
PASS
17 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
17 form control(s) checked, no input-semantic issues
PASS
17 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "it"
PASS
Lang attribute set to "it"
Info::
<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
Info::
All 2 iframe(s) have title attributes
A+
Mobile-Readable Font Sizes
All 15 visible text node(s) render at >= 12 CSS pixels
PASS
All 15 visible text node(s) render at >= 12 CSS pixels
Info::
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
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
Info::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback