Skip to content
https://www.treccani.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
5
REVIEW
8
PASS
11
INFO
0
Checks
24
11 PASS 8 REVIEW 5 FIX
F
Heading Hierarchy
Action
79 headings, 5 skip(s)
FIX
79 headings, 5 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (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: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Prima Pagina
  • H5 wellerismo skipped
  • H5 Allarme bomba in 300 scuole italiane, Meloni convoca vertice a Palazzo Chigi
  • H5 Droni colpiscono il porto russo di Ust-Luga sul Baltico, incendio in corso
  • H5 G7 Esteri a Parigi: al centro Ucraina, Iran e guerra ibrida
  • H2 Ultimi dai magazine
  • H5 Memorie vive, all’hotel Campo Imperatore skipped
  • H5 Il dialetto tursitano di Albino Pierro
  • H5 La memoria (sconveniente) degli alberi
  • H2 Approfondimenti
  • H5 QUALI GARANZIE DI SICUREZZA PER L’UCRAINA? skipped
  • H5 GREEN JOBS E TRANSIZIONE ECOLOGICA
  • H5 Nvidia indaga sul suo CEO: il caso Jensen Huang e la presunta spia cinese
  • H2 La galassia treccani
  • H3 MASTER
  • H3 BORSE DI STUDIO
  • H3 MASTER
  • H3 EDULIA
  • H3 Migrant Child
  • H3 IN CLASSE CON TRECCANI SCUOLA
  • H3 EFFETTO MATILDA
  • H3 ECOSISPIEGA
  • H3 MANUALE DI GRAMMATICA PER LA SCUOLA SECONDARIA DI I GRADO
  • H3 PENSARE BENE
  • H3 Intelligenza artificiale: progetto per le scuole
  • H3 Club Treccani
  • H3 POSTER
  • H3 TRECCANI EMPORIUM
  • H3 LO SPORT, A PAROLE TUE
  • H3 REGGILIBRO E KIT DA DISEGNO
  • H3 LA TRECCANI DEI RAGAZZI
  • H3 NEGOZI TRECCANI
  • H3 TRECCANI SCUOLA
  • H3 TRECCANI LIBRI
  • H3 Maranza Le parole della neopolitica
  • H3 Novità Treccani
  • H4 NUOVE USCITE
  • H2 DIZIONARIO BIOGRAFICO E TEMATICO DELLE DONNE IN ITALIA
  • H2 Recensioni
  • H3 L’italiano popolare contemporaneo
  • H3 Il pesce lampada
  • H3 L’Internazionale del rifiuto di Mikkel Bolt Rasmussen
  • H3 L’italiano per scelta. I nuovi italiani tra cinema, musica, social e letteratura
  • H3 Il mondo e la terra. Come preservarli? di David Van Reybrouck
  • H3 Lettere
  • H3 Maledette. Le diverse dal XVII secolo ai nostri giorni
  • H3 Veglia di George Saunders
  • H3 Giuseppe Tomasi di Lampedusa, Il Gattopardo raccontato alle ragazze e ai ragazzi
  • H3 Il seduttore, di Ernst Weiss
  • H3 Semplicità degli uomini
  • H3 Giacomo Puccini scrittore. La lingua dell’epistolario e delle poesie
  • H3 A Londra con Freddie Mercury
  • H3 Guerra alla Terra di Danilo Zagaria
  • H3 Storie della lingua. L’italiano in dieci lezioni
  • H3 Bristol di Jean Echenoz
  • H3 L’eterno ritorno di ’Ndrja Cambrìa. «Itinerario all’uomo» in Horcynus Orca di Stefano D’Arrigo
  • H3 Interrogare la sfinge di Renzo Guolo
  • H3 Brava Giulia, di Anna Toscano
  • H3 Coinquilini bestiali di Nicola Bressi
  • H3 Il testo poetico Metodi strumenti esempi d’analisi linguistica
  • H3 Le sei donne che amarono Picasso, di Sue Roe
  • H3 «Illusione»: storia di una parola
  • H3 Picca
  • H3 Assoluzione di Jeff VanderMeer
  • H3 Un saper leggero di Xavier Nueno
  • H3 Come sono, suona di Susan Rogers e Ogi Ogas
  • H4 Vuoi accedere al Sapere Treccani Senza Limiti?
  • H2 enciclopedia
  • H4 I LIBRI DI TRECCANI skipped
  • H1 Tommaso D’Aquino
  • H3 di Martin Grabmann, Franz Pelster skipped
  • H3 Introduzione di Pasquale Porro
  • H4 LA SCUOLA DEL TASCABILE
  • H2 OGGI, 11 novembre
  • H3 I non servati voti e i molti errori
  • H3 Lalla Romano
  • H3 La sovrabbondanza di avvenimenti genera la sensazione che la storia stia accelerando, ma paradossalmente rischiamo di perdere il senso del futuro
  • H3 Abbiamo a cuore la tua privacy
  • H3 Gestisci le opzioni

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
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-vc8xjt
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

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: #000
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::
4 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 4 <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
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <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

B
Iframe Accessibility
3/4 iframe(s) missing title; 0 placeholder(s)
REVIEW
3/4 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Treccani
Info::
192x192 icon present
Info::
512x512 icon present
PWA Install Criteria Not Installable
Name Treccani ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode browser ✗
Name Treccani Display Mode browser Theme Color #000 Background Color #000 Icons 4 icon(s)
B
PWA Depth
2 PWA signal(s) surfaced
REVIEW
2 PWA signal(s) surfaced
Warning::
Manifest declares display="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).
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA 1 pass AA only
h1 Tommaso D’Aquino
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Ultimi dai magazine
1.07:1
#000000
on
#080C0D
needs 3.0:1 (large text)
24px · mid-page
h2 Approfondimenti
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
24px · bottom of viewport
h2 La galassia treccani
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
24px · bottom of viewport
h2 DIZIONARIO BIOGRAFICO E TEMATICO DELLE D…
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Recensioni
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
24px · bottom of viewport
h2 enciclopedia
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
24px · bottom of viewport
h2 OGGI, 11 novembre
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
24px · bottom of viewport
h3 MASTER
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
19px · bottom of viewport
h3 BORSE DI STUDIO
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
19px · bottom of viewport
h3 MASTER
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
19px · bottom of viewport
h3 EDULIA
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Migrant Child
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
19px · bottom of viewport
h3 IN CLASSE CON TRECCANI SCUOLA
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
19px · bottom of viewport
h3 EFFETTO MATILDA
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
19px · bottom of viewport
h3 ECOSISPIEGA
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
19px · bottom of viewport
h3 MANUALE DI GRAMMATICA PER LA SCUOLA SECO…
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
19px · bottom of viewport
h3 PENSARE BENE
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Intelligenza artificiale: progetto per l…
1.01:1
#000000
on
#020204
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Tommaso D’Aquino1.01:13.0:1
#000000
#020204
Fail
h2 Prima Pagina3.66:13.0:1
#000000
#666666
Pass
h2 Ultimi dai magazine1.07:13.0:1
#000000
#080C0D
Fail
h2 Approfondimenti1.01:13.0:1
#000000
#020204
Fail
h2 La galassia treccani1.01:13.0:1
#000000
#020204
Fail
h2 DIZIONARIO BIOGRAFIC…1.01:13.0:1
#000000
#020204
Fail
h2 Recensioni1.01:13.0:1
#000000
#020204
Fail
h2 enciclopedia1.01:13.0:1
#000000
#020204
Fail
h2 OGGI, 11 novembre1.01:13.0:1
#000000
#020204
Fail
h3 MASTER1.01:13.0:1
#000000
#020204
Fail
h3 BORSE DI STUDIO1.01:13.0:1
#000000
#020204
Fail
h3 MASTER1.01:13.0:1
#000000
#020204
Fail
h3 EDULIA1.01:13.0:1
#000000
#020204
Fail
h3 Migrant Child1.01:13.0:1
#000000
#020204
Fail
h3 IN CLASSE CON TRECCA…1.01:13.0:1
#000000
#020204
Fail
h3 EFFETTO MATILDA1.01:13.0:1
#000000
#020204
Fail
h3 ECOSISPIEGA1.01:13.0:1
#000000
#020204
Fail
h3 MANUALE DI GRAMMATIC…1.01:13.0:1
#000000
#020204
Fail
h3 PENSARE BENE1.01:13.0:1
#000000
#020204
Fail
h3 Intelligenza artific…1.01:13.0:1
#000000
#020204
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 89/100 — 3 failing, 25 passed
REVIEW
89

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.MuiContainer-root > div.MuiGrid-root > div.MuiGrid-root > button.MuiButtonBase-root div.MuiContainer-root > div.MuiGrid-root > div.MuiGrid-root > button.MuiButtonBase-root

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#mainContent > main.Index_main__hJDvk > div.MuiBox-root > img.MuiBox-root div#mainContent > main.Index_main__hJDvk > div.MuiBox-root > img.MuiBox-root

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.

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
WELLERISMO a.MuiTypography-root > div.Card_card__jLcEy > div.MuiBox-root > h5.MuiTypography-root
MEMORIE VIVE, ALL’HOTEL CAMPO IMPERATORE a.MuiTypography-root > div.Card_card__jLcEy > div.MuiBox-root > h5.MuiTypography-root
QUALI GARANZIE DI SICUREZZA PER L’UCRAINA? a.MuiTypography-root > div.Card_card__jLcEy > div.MuiBox-root > h5.MuiTypography-root
I LIBRI DI TRECCANI div > div.MuiGrid-root > div.MuiGrid-root > h4.MuiTypography-root
di Martin Grabmann, Franz Pelster div > div.MuiGrid-root > div.MuiGrid-root > h3.MuiTypography-root

These are opportunities to improve keyboard navigation in your application.

○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○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
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
1 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 145 chars
Got: 1 >120-char heading(s)
Info::
23 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: 23 all-caps heading(s)
A
Alt Text Quality
1 of 71 images have issues
PASS
1 of 71 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
65 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
71 images 5 good alt text 65 decorative 1 missing
IssueCount
missing1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#searchtextSearcharia-label
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "search" should use type="search" (currently type="text")
Field name "search" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 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+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -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.)
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 306 visible text node(s) render at >= 12 CSS pixels
PASS
All 306 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback