https://fineco.it
Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.SCORE
78
GRADE
C
FIX
6
REVIEW
4
PASS
14
INFO
0
Checks
2414 PASS 4 REVIEW 6 FIX
DHeading HierarchyAction32 headings, 2 skip(s)FIX
Heading Hierarchy
Action32 headings, 2 skip(s)
32 headings, 2 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H6 (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.
- H4 Scopri Fineco
- H2 Scegli il conto Fineco perfetto per te
- H6 Conto completo skipped
- H6 Conto completo
- H6 I vantaggi di One, con in più:
- H6 Conto completo
- H6 I vantaggi di Classic, con in più:
- H6 Soluzione dedicata
- H6 Conto completo
- H6 I vantaggi di One, con in più:
- H6 I vantaggi di Classic, con in più:
- H6 Soluzione dedicata
- H6 Conto completo
- H6 I vantaggi di One, con in più:
- H6 I vantaggi di Classic, con in più:
- H6 Soluzione dedicata
- H2 Tutto quello che ti serve, solo quello che vuoi
- H3 Più di una carta. La tua.
- H3 Fineco per i giovani. Inizia meglio, vivi smart.
- H2 Investi meglio, cresci davvero
- H3 Incontrarsi fa la differenza
- H2 Scegli il trading n.1 in Italia
- H3 Trading puro. Zero distrazioni.
- H2 Private,ma senza filtri
- H3 Ogni fase ha il suo perché
- H3 96%
- H3 +160 MLD
- H3 CET1 23,3%
- H2 Cambiare è una scelta.Scegli di essere avanti.
- H3 CHANGE IS GOOD.
- H2 Hai domande?Ti ascoltiamo.
- H4 Come posso aiutarti? skipped
Every page should have one H1 that describes the page content.
Why this matters
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
Learn more ▾ ▴
The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.
Source: WCAG 2.4.6 / Google Search Central
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Why this matters
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Why this matters
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
DTabindex Anti-PatternsAction0 positive, 73 -1-on-focusableFIX
Tabindex Anti-Patterns
Action0 positive, 73 -1-on-focusable
0 positive, 73 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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>
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.)
DTap Target AdequacyAction16 tap target(s) too small or too close togetherFIX
Tap Target Adequacy
Action16 tap target(s) too small or too close together
16 tap target(s) too small or too close together
Warning::
16 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.
DDark Mode SupportActionTheme color onlyFIX
Dark Mode Support
ActionTheme color only
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #0f8bc1
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 ModePartial Dark Mode
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
Print Stylesheet
ActionNo print styles
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 ✗
CLandmark StructureAction3 landmarksREVIEW
Landmark Structure
Action3 landmarks
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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
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
BLink & Button Quality332 links, 31 buttons — all OKREVIEW
Link & Button Quality
332 links, 31 buttons — all OK
332 links, 31 buttons — all OK
Critical::
1 image-only link(s) without alt text
Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.
Got: a[href="/accessibilita/"]
Warning::
63 link(s) open in new tab without warning
Add '(opens in new tab)' to link text or aria-label.
Got: https://finecobank.com/it/open-account/online; https://www.finecodays.it/; https://about.finecobank.com/it/; https://about.finecobank.com/it/sustainability/; https://about.finecobank.com/it/careers/; https://www.finecodays.it/; https://about.finecobank.com/it/solidarieta/; https://about.finecobank.com/it/initiatives/; https://about.finecobank.com/it/sustainability/; https://finecobank.com/it/open-account/online (+53 more)
Info::
268 link(s) with descriptive text
332 links
0 empty
0 generic text
63 new tab
0 empty buttons
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco | new tab | Add '(opens in new tab)' to text |
| https://www.finecodays.it/ | Fineco Days | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/ | Corporate | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/sustaina… | Sostenibilità | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/careers/ | Careers | new tab | Add '(opens in new tab)' to text |
| https://www.finecodays.it/ | Scopri i Fineco Days | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/solidari… | Scopri di più sui progetti ch… | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/initiati… | Iniziative | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/sustaina… | Sostenibilità | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/sustaina… | Sostenibilità (apre in una nu… | new tab | Add '(opens in new tab)' to text |
| /banking/credit-lombard/ | Credit Lombard | img no alt | Add alt attribute to the image |
| https://about.finecobank.com/it/sustaina… | Sostenibilità (apre in una nu… | new tab | Add '(opens in new tab)' to text |
| https://www.finecodays.it/ | Fineco Days (apre in una nuova… | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/sustaina… | Sostenibilità (apre in una nu… | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/ | Corporate | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/sustaina… | Sostenibilità | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/careers/ | Careers | new tab | Add '(opens in new tab)' to text |
| https://www.finecodays.it/ | Fineco Days | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/solidari… | Solidarietà | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/initiati… | Iniziative | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/investor… | FINECO1,02%positivo | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/investor… | Scopri i risultati Fineco | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco One | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco Classic | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco Max | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco Trading | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco One | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco Classic | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco Max | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco Trading | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco One | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco Classic | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco Max | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco Trading | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco One | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco Classic | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco Max | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco Trading | new tab | Add '(opens in new tab)' to text |
| https://www.finecodays.it/ | Scopri i Fineco Days | new tab | Add '(opens in new tab)' to text |
| https://images.fineco.it/pub/pdf/chi-sia… | CS - Risultati 1Q26 | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/open-account/o… | Apri il conto Fineco | new tab | Add '(opens in new tab)' to text |
| /contattaci/#map-container | Trova il Fineco Center più vi… | img no alt | Add alt attribute to the image |
| /contattaci/help/ | Consulta le domande più frequ… | img no alt | Add alt attribute to the image |
| https://help.finecobank.com/it/mutui-e-p… | Scopri di più sulle iniziativ… | new tab | Add '(opens in new tab)' to text |
| https://devportal.finecobank.com | Approfondisci l’Open Banking | new tab | Add '(opens in new tab)' to text |
| https://finecobank.com/it/public/fogli-i… | fogli informativi e moduli inf… | new tab | Add '(opens in new tab)' to text |
| https://images.finecobank.com/docs/pdf/p… | Report Amf Italia - FY2025 | new tab | Add '(opens in new tab)' to text |
| https://help.finecobank.com/it/mercati-e… | Dettagli sulla tassa di cambio | new tab | Add '(opens in new tab)' to text |
| https://finecobank.it/it/promo/Credit_Lo… | Regolamento | new tab | Add '(opens in new tab)' to text |
| https://www.facebook.com/fineco | Vai sulla pagina Fineco di Fac… | new tab | Add '(opens in new tab)' to text |
| https://twitter.com/FinecoLive | Vai sulla pagina Fineco di X | new tab | Add '(opens in new tab)' to text |
| https://it.linkedin.com/company/finecoba… | Vai sulla pagina Fineco di Lin… | new tab | Add '(opens in new tab)' to text |
| https://www.instagram.com/finecobank/ | Vai sulla pagina Fineco di Ins… | new tab | Add '(opens in new tab)' to text |
| https://open.spotify.com/user/3174fokqgu… | Vai sulla pagina Fineco di Spo… | new tab | Add '(opens in new tab)' to text |
| https://www.reddit.com/user/FinecoBank/ | Vai sulla pagina Fineco di Red… | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/ | Chi siamo | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/sustaina… | Sostenibilità | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/solidari… | Solidarietà | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/initiati… | Iniziative | new tab | Add '(opens in new tab)' to text |
| https://www.finecodays.it/ | Scopri i Fineco Days | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/investor… | Investors | new tab | Add '(opens in new tab)' to text |
| https://about.finecobank.com/it/careers/ | Careers | new tab | Add '(opens in new tab)' to text |
| /accessibilita/ | Scopri di più sull’accessib… | img no alt | Add alt attribute to the image |
| https://about.finecobank.com/it/governan… | Governance | new tab | Add '(opens in new tab)' to text |
| https://www.acf.consob.it/ | Arbitro controversie finanziar… | new tab | Add '(opens in new tab)' to text |
299 links and buttons have descriptive text
Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.
a[href="/accessibilita/"]
Why this matters
Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
https://finecobank.com/it/open-account/online; https://www.finecodays.it/; https://about.finecobank.com/it/; https://about.finecobank.com/it/sustainability/; https://about.finecobank.com/it/careers/; https://www.finecodays.it/; https://about.finecobank.com/it/solidarieta/; https://about.finecobank.com/it/initiatives/; https://about.finecobank.com/it/sustainability/; https://finecobank.com/it/open-account/online (+53 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
B404 Error PageHTTP 404, custom pageREVIEW
404 Error Page
HTTP 404, custom page
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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Noi siamo Fineco - Fineco ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
CFavicon & BrandingAction23 icon(s) detectedREVIEW
Favicon & Branding
Action23 icon(s) detected
23 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+Heading Text Quality1 heading-text-quality issue(s) detectedPASS
Heading Text Quality
1 heading-text-quality issue(s) detected
1 heading-text-quality issue(s) detected
Info::
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)
A+Alt Text QualityAll 14 images OKPASS
Alt Text Quality
All 14 images OK
All 14 images OK
Info::
7 decorative image(s) correctly marked
Info::
7 image(s) with good alt text
14 images 7 good alt text 7 decorative
All images have appropriate alt text.
A+Form AccessibilityAll 1 controls labeledPASS
Form Accessibility
All 1 controls labeled
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
| Control | Type | Label | Method |
|---|---|---|---|
| #message | textarea | Scrivi qui | for/id |
A+Form Input Types1 form control(s) checked, no type mismatchesPASS
Form Input Types
1 form control(s) checked, no type mismatches
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+Form Input Quality1 form control(s) checked, no input-semantic issuesPASS
Form Input Quality
1 form control(s) checked, no input-semantic issues
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
Mobile Keyboard & Autofill
No autofill-eligible form controls
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+Document LanguageLang attribute set to "it"PASS
Document Language
Lang attribute set to "it"
Lang attribute set to "it"
Info::
<html lang="it"> is set and valid
Got: it
A+Iframe AccessibilityNo iframes on this pagePASS
Iframe Accessibility
No iframes on this page
No iframes on this page
Info::
No iframes on this page
A+Mobile-Readable Font SizesAll 351 visible text node(s) render at >= 12 CSS pixelsPASS
Mobile-Readable Font Sizes
All 351 visible text node(s) render at >= 12 CSS pixels
All 351 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+Web ManifestPWA-readyPASS
Web Manifest
PWA-ready
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: FinecoBank
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name FinecoBank ✓192×192 icon ✓512×512 icon ✓Start URL /index.html ✓Display Mode standalone ✓
Name FinecoBank Display Mode standalone Theme Color #0f8bc1 Background Color #fff Icons 7 icon(s)
A+PWA Depth1 PWA signal(s) surfacedPASS
PWA Depth
1 PWA signal(s) surfaced
1 PWA signal(s) surfaced
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).
A+Mobile UX Depth2 mobile-depth signal(s) detectedPASS
Mobile UX Depth
2 mobile-depth signal(s) detected
2 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
Info::
iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)
The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
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 |
|---|---|---|---|---|---|
| h2 Scegli il conto Fine… | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h2 Tutto quello che ti … | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h2 Investi meglio, cres… | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h2 Scegli il trading n.… | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h2 Private, | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h2 ma senza filtri | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h2 Cambiare è una scel… | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h2 Scegli di essere ava… | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h2 Hai domande? | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h2 Ti ascoltiamo. | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h3 Più di una carta. L… | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h3 Fineco per i giovani… | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h3 Incontrarsi fa la di… | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h3 Trading puro. Zero d… | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h3 Ogni fase ha il suo … | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h3 96% | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h3 +160 MLD | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h3 CET1 23,3% | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| h3 CHANGE IS GOOD. | 19.43:1 | 3.0:1 | #000000 | #F6F6F6 | Pass |
| title Banca Fineco: Conti,… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
ALighthouse Accessibility AuditsScore 91/100 — 6 failing, 28 passedPASS
Lighthouse Accessibility Audits
Score 91/100 — 6 failing, 28 passed
91
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.
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 |
|---|
Conto completo div.col > div.card-intro-badge > div.ps-2 > h6.text-primary |
These are opportunities to improve keyboard navigation in your application.
Contrast
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Report Amf Italia - FY2025 div.col-10 > div.mt-2 > p > a |
Dettagli div.col-10 > div.mt-2 > p > a |
Regolamento div.col-10 > div.mt-2 > p > a |
These are opportunities to improve the legibility of your content.
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 |
|---|
Tutte le condizioni div.col > ul.last-section-menu > li > a |
Trasparenza div.col > ul.last-section-menu > li > a |
Reclami e ricorsi div.col > ul.last-section-menu > li > a |
Privacy div.col > ul.last-section-menu > li > a |
Rapporti dormienti div.col > ul.last-section-menu > li > a |
Dati Societari div.col > ul.last-section-menu > li > a |
Servizi di investimento div.col > ul.last-section-menu > li > a |
Preferenze cookies div.col > ul.last-section-menu > li > a.ot-sdk-show-settings |
Governance div.col > ul.last-section-menu > li > a |
Arbitro controversie finanziarie div.col > ul.last-section-menu > li > a |
Open Banking div.col > ul.last-section-menu > li > a |
Dichiarazione di accessibilità div.col > ul.last-section-menu > li > a |
Whistleblowing div.col > ul.last-section-menu > li > a |
Risoluzione bancaria div.col > ul.last-section-menu > li > a |
Sostenibilità (SFDR) div.col > ul.last-section-menu > li > a |
Glossario div.col > ul.last-section-menu > li > a |
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 html |
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 |
|---|
Menu div.col-7 > nav.row > div.col-2 > button.btn |
Scopri di più div.row > div.col > p > a.more-small |
SCEGLI ONE div.card > div.containerRounded > div.card-footer > a.btn |
Scopri di più div.containerRounded > div.card-footer > p.mt-2 > a.more-small |
SCEGLI tbody > tr > td > a.btn |
SCEGLI tbody > tr > td > a.btn |
SCEGLI tbody > tr > td > a.btn |
SCEGLI tbody > tr > td > a.btn |
Confronta tutti i dettagli div.container > div.row > div.col > a.more |
SCEGLI LA TUA CARTA div.row > div.col-12 > div.ps-5 > a.btn |
Scopri il conto per i minori div.col-12 > ul.arrow > li > a.more |
Scopri le condizioni giovani div.col-12 > ul.arrow > li.mt-4 > a.more |
INVESTI CON NOI div.container > div.row > div.col-11 > a.btn |
PARTECIPA div.row > div.col-12 > div.ps-5 > a.btn |
ESPLORA I MERCATI div.container > div.row > div.col-11 > a.btn |
SCEGLI L'ECCELLENZA div.container > div.row > div.col-11 > a.btn |
CONTATTA UN CONSULENTE div.row > div.col-12 > div.ps-5 > a.btn |
Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
One
Classic
Max
Solo Trading
Assistenza
Solo mail
Mail e… div.row > div.col > div.table-responsive > table.table |
○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
●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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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
●Background and foreground colors have a sufficient contrast ratio
●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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Skip links are focusable.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[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 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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.