Skip to content
https://sblob.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
81
GRADE
B
FIX
4
REVIEW
6
PASS
14
INFO
0
Checks
24
14 PASS 6 REVIEW 4 FIX
D
Mobile-Readable Font Sizes
Action
52% of visible text renders at >= 12 CSS px (48 below threshold)
FIX
52% of visible text renders at >= 12 CSS px (48 below threshold)
Warning::
48 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <p> 10.9px ("Aggiornata in tempo reale"); <a> 11.2px ("strong-tech.com"); <a> 10.1px ("02/10/2026"); <span> 10.5px ("Event"); <a> 11.2px ("openwebinarworld.com").
D
Dark Mode Support
Action
Theme color only
FIX
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: #007bff
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.

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::
2 navigation landmark(s) detected
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 2 <nav> element(s)
Back to Top
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.
B
Landmark Structure
9 landmarks
REVIEW
9 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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 "Navigazione principale" MAIN CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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
Mobile Keyboard & Autofill
Action
4/8 eligible field(s) missing autocomplete or inputmode
REVIEW
4/8 eligible field(s) missing autocomplete or inputmode
Warning::
2 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: username.
Got: <input name="username">, <input name="username">
Warning::
2 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email" name="email">, <input type="email" name="email">
C
Tap Target Adequacy
Action
8 tap target(s) too small or too close together
REVIEW
8 tap target(s) too small or too close together
Warning::
8 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
404 Error Page
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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Pagina non trovata - SBLOB.IT ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
6 icon(s) detected
REVIEW
6 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
C
Lighthouse Accessibility Audits
Action
Score 78/100 — 5 failing, 15 passed
REVIEW
78

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
AGGIORNATA IN TEMPO REALE section.news-timeline > div.timeline-heading > div > p.timeline-kicker
Una selezione ordinata per freschezza, rilevanza e varietà delle fonti. section.news-timeline > div.timeline-heading > div > p.timeline-intro
Archivio div.int > section.news-timeline > div.timeline-heading > a.timeline-archive
strong-tech.com div.timeline-list > article.listato > div.txt > a.domain-link
02/10/2026 div.timeline-list > article.listato > div.txt > a.card-date
Leggi su strong-tech.com article.listato > div.txt > div.card-actions > a.leggi
EVENT a.card-link > div.img-container > div.img > span.type-badge
openwebinarworld.com div.timeline-list > article.listato > div.txt > a.domain-link
02/10/2026 div.timeline-list > article.listato > div.txt > a.card-date
Leggi su openwebinarworld.com article.listato > div.txt > div.card-actions > a.leggi
dievio.com div.timeline-list > article.listato > div.txt > a.domain-link
02/10/2026 div.timeline-list > article.listato > div.txt > a.card-date
Leggi su dievio.com article.listato > div.txt > div.card-actions > a.leggi
www.seiseralm.it div.timeline-list > article.listato > div.txt > a.domain-link
02/10/2026 div.timeline-list > article.listato > div.txt > a.card-date
Leggi su www.seiseralm.it article.listato > div.txt > div.card-actions > a.leggi
www.4isp.it div.timeline-list > article.listato > div.txt > a.domain-link
02/10/2026 div.timeline-list > article.listato > div.txt > a.card-date
Leggi su www.4isp.it article.listato > div.txt > div.card-actions > a.leggi
www.vs.ch div.timeline-list > article.listato > div.txt > a.domain-link
02/10/2026 div.timeline-list > article.listato > div.txt > a.card-date
Leggi su www.vs.ch article.listato > div.txt > div.card-actions > a.leggi
zanzaratigreonline.it div.timeline-list > article.listato > div.txt > a.domain-link
02/10/2026 div.timeline-list > article.listato > div.txt > a.card-date
Leggi su zanzaratigreonline.it article.listato > div.txt > div.card-actions > a.leggi
anra.it div.timeline-list > article.listato > div.txt > a.domain-link
02/10/2026 div.timeline-list > article.listato > div.txt > a.card-date
Leggi su anra.it article.listato > div.txt > div.card-actions > a.leggi
www.quinewsarezzo.it div.timeline-list > article.listato > div.txt > a.domain-link
02/10/2026 div.timeline-list > article.listato > div.txt > a.card-date
Leggi su www.quinewsarezzo.it article.listato > div.txt > div.card-actions > a.leggi
yale-herald.com div.timeline-list > article.listato > div.txt > a.domain-link
02/10/2026 div.timeline-list > article.listato > div.txt > a.card-date
Leggi su yale-herald.com article.listato > div.txt > div.card-actions > a.leggi
404 main.corpo > div.int > div.page-404 > h1
Torna alla home main.corpo > div.int > div.page-404 > a.leggi

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
Meyer Sound - Acheron Designer - Strong Technical Services article.listato > div.txt > h2 > a
Software, Komponenten und Prozesse auf Ressourceneffizienz getrimmt article.listato > div.txt > h2 > a
Dievio article.listato > div.txt > h2 > a
4ISP s.r.l. article.listato > div.txt > h2 > a
Votation cantonale - Deux objets soumis au vote de la population le 29 novembre… article.listato > div.txt > h2 > a
Sorveglianza delle zanzare in Europa: cosa fa l’Italia secondo il nuovo rapport… article.listato > div.txt > h2 > a
Hormuz, energia e inflazione: perché la crisi torna a pesare sui conti delle im… article.listato > div.txt > h2 > a
Benzina, gasolio, gpl, ecco dove risparmiare a Arezzo article.listato > div.txt > h2 > a
difnet.it footer.footer > div.int > p > a
difnet.it footer.footer > div.int > p > a

These are opportunities to improve the legibility of your content.

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
body > meta body > 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
🧘 PAUSA LETTURA footer.footer > div.int > div.f_links > a#sblob-pause-toggle
CONTATTI footer.footer > div.int > div.f_links > a
RIMOZIONE SITO footer.footer > div.int > div.f_links > a
PRIVACY footer.footer > div.int > div.f_links > a
🧘 PAUSA LETTURA footer.footer > div.int > div.f_links > a#sblob-pause-toggle
CONTATTI footer.footer > div.int > div.f_links > a
RIMOZIONE SITO footer.footer > div.int > div.f_links > a
PRIVACY footer.footer > div.int > div.f_links > a

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
EVENT 🆕 section.news-timeline > div.timeline-list > article.listato > a.card-link
○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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●ARIA IDs are unique
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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
○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.
○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.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A
Heading Hierarchy
14 headings
PASS
14 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 Accedi a SBLOB
  • H1 Le news del giorno
  • H2 Meyer Sound - Acheron Designer - Strong Technical Services
  • H2 Software, Komponenten und Prozesse auf Ressourceneffizienz getrimmt
  • H2 Dievio
  • H2 Seiser Alm Marketing Gen.
  • H2 4ISP s.r.l.
  • H2 Votation cantonale - Deux objets soumis au vote de la population le 29 novembre 2026
  • H2 Sorveglianza delle zanzare in Europa: cosa fa l’Italia secondo il nuovo rapporto ECDC
  • H2 Hormuz, energia e inflazione: perché la crisi torna a pesare sui conti delle imprese europee
  • H2 Benzina, gasolio, gpl, ecco dove risparmiare a Arezzo
  • H2 Same, Same (but different)
  • H2 Accedi a SBLOB
  • H1 404 duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+
Heading Text Quality
All 14 heading(s) have substantive, well-formed text
PASS
All 14 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
usernameinputNomenone
emailemailEmailnone
passwordpasswordPasswordnone
usernameinputNomenone
emailemailEmailnone
passwordpasswordPasswordnone
A+
Form Input Types
6 form control(s) checked, no type mismatches
PASS
6 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A
Form Input Quality
1 input-semantic issue(s) across 6 form control(s)
PASS
1 input-semantic issue(s) across 6 form control(s)
Info::
2 login form field(s) missing `autocomplete=username` (or `email`)
On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input name="username">, <input name="username">.
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+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: SBLOB
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name SBLOB ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name SBLOB Display Mode standalone Theme Color #007bff Background Color #0e0e0e Icons 2 icon(s)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 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.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Le news del giorno18.26:13.0:1
#000000
#EFEFEF
Pass
h1 40418.26:13.0:1
#000000
#EFEFEF
Pass
h2 Accedi a SBLOB18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Accedi a SBLOB18.26:13.0:1
#000000
#EFEFEF
Pass
title SBLOB - Aggregatore …8.03:14.5:1
#000000
#A0A0A0
Pass
a Tag8.03:14.5:1
#000000
#A0A0A0
Pass
a Date18.26:14.5:1
#000000
#EFEFEF
Pass
a Servizi18.26:14.5:1
#000000
#EFEFEF
Pass
button Accedi18.26:14.5:1
#000000
#EFEFEF
Pass
label Nome18.26:14.5:1
#000000
#EFEFEF
Pass
label Email18.26:14.5:1
#000000
#EFEFEF
Pass
label Password18.26:14.5:1
#000000
#EFEFEF
Pass
button Accedi18.26:14.5:1
#000000
#EFEFEF
Pass
button Crea un account18.26:14.5:1
#000000
#EFEFEF
Pass
p Aggiornata in tempo …18.26:14.5:1
#000000
#EFEFEF
Pass
p Una selezione ordina…18.26:14.5:1
#000000
#EFEFEF
Pass
a Archivio18.26:14.5:1
#000000
#EFEFEF
Pass
span 🆕18.26:14.5:1
#000000
#EFEFEF
Pass
a strong-tech.com18.26:14.5:1
#000000
#EFEFEF
Pass
a 02/10/202618.26:14.5:1
#000000
#EFEFEF
Pass

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

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

Send Feedback