Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLink & Button QualityAction4 issue(s) across 53 links and 19 buttonsFIX
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://www.youtube.com/@GuidaDifensiva | (empty) | empty | Add link text or aria-label |
| https://www.guidadifensiva.org/defensive… | Inizia qui la Guida Difensiva. | new tab | Add '(opens in new tab)' to text |
| https://www.guidadifensiva.org/defensive… | La Guida Difensiva è un metod… | new tab | Add '(opens in new tab)' to text |
| https://www.guidadifensiva.org/defensive… | i corsi | new tab | Add '(opens in new tab)' to text |
| https://www.youtube.com/@GuidaDifensiva | (empty) | empty | Add link text or aria-label |
| https://join.chat/en/powered/?utm_medium… | Powered by Joinchat | new tab | Add '(opens in new tab)' to text |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
Links without text are announced as raw URLs by screen readers.
https://www.youtube.com/@GuidaDifensiva; https://www.youtube.com/@GuidaDifensiva
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
https://www.guidadifensiva.org/defensive-driving-usa/; https://www.guidadifensiva.org/defensive-driving-usa/; https://www.guidadifensiva.org/defensive-driving-usa/; https://join.chat/en/powered/?utm_medium=widget&utm_source=www.guidadifensiva…
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
Icon-only buttons need an aria-label so screen readers can announce them.
button.toggle (#246 on page); button.toggle (#292 on page)
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
CLandmark StructureAction7 landmarksREVIEW
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.
Learn more ▾ ▴
Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.
Source: WCAG 2.1 SC 2.4.1
CHeading HierarchyAction11 headings, 1 skip(s)REVIEW
- H2 Conosci
- H2 #OnTheSafeSide
- H2 Conosci
- H2 #OnTheSafeSide
- H2 Conosci
- H2 #OnTheSafeSide
- H6 Creare sicurezza skipped
- H2 CREARE PROPRIE COMPETENZE PRIMA DI AFFIDARSI ALLA TECNOLOGIA
- H2 Guidare in totale sicurezza
- H3 828284,868384
- H3 8486,808080
Every page should have one H1 that describes the page content.
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.
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
BAlt Text Quality2 of 8 images have issuesREVIEW
| Issue | Count |
|---|---|
| missing | 2 image(s) |
Images without alt text are invisible to screen readers.
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
BMobile-Readable Font Sizes96% of visible text renders at >= 12 CSS px (1 below threshold)REVIEW
B404 Error PageHTTP 404, custom pageREVIEW
BFavicon & Branding4 icon(s) detectedREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 10 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
4 contrast failures on background images/gradients
These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h2 Conosci | 20.12:1 | 3.0:1 | #000000 | #FAFAFA | Pass |
| h2 #OnTheSafeSide | 20.12:1 | 3.0:1 | #000000 | #FAFAFA | Pass |
| h2 Conosci | 20.12:1 | 3.0:1 | #000000 | #FAFAFA | Pass |
| h2 #OnTheSafeSide | 20.12:1 | 3.0:1 | #000000 | #FAFAFA | Pass |
| h2 Conosci | 20.12:1 | 3.0:1 | #000000 | #FAFAFA | Pass |
| h2 #OnTheSafeSide | 20.12:1 | 3.0:1 | #000000 | #FAFAFA | Pass |
| h2 Guidare in totale si… | 20.12:1 | 3.0:1 | #000000 | #FAFAFA | Pass |
| title Home page - Guida Di… | 1.53:1 | 4.5:1 | #000000 | #4E1E1D | Fail |
| p We value your privac… | 1.61:1 | 4.5:1 | #212121 | #742A21 | Fail |
| p We use cookies to en… | 3.17:1 | 4.5:1 | #000000 | #9F3D26 | Fail |
| button Customise | 1.59:1 | 4.5:1 | #1863DC | #E0672B | Fail |
| button Reject All | 3.18:1 | 4.5:1 | #1863DC | #F8BB62 | Fail |
| button Accept All | 1.31:1 | 4.5:1 | #FFFFFF | #F9DF98 | Fail |
| span Customise Consent Pr… | 9.31:1 | 4.5:1 | #212121 | #FAB957 | Pass |
| p We use cookies to he… | 6.15:1 | 4.5:1 | #000000 | #D76E27 | Pass |
| p The cookies that are… | 5.04:1 | 4.5:1 | #000000 | #BE6426 | Pass |
| button Show more | 1.14:1 | 4.5:1 | #1863DC | #AB5F2A | Fail |
| button Necessary | 3.77:1 | 4.5:1 | #212121 | #B66628 | Fail |
| span Always Active | 2.54:1 | 4.5:1 | #008000 | #472A14 | Fail |
| p Necessary cookies ar… | 2.36:1 | 4.5:1 | #000000 | #6A3F2E | 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.
BLighthouse Accessibility AuditsScore 87/100 — 5 failing, 25 passedREVIEW
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Menu div.header-titles-wrapper > button.toggle > span.toggle-inner > span.toggle-text |
These are opportunities to improve the legibility of your content.
Navigation
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Creare sicurezza div.row > div.col-xl-6 > div.about-module > h6.subtitle |
These are opportunities to improve keyboard navigation in your application.
Names and labels
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.about-wrap > div.about-img-holder > div.card__image > img div.about-wrap > div.about-img-holder > div.card__image > img |
div.about-wrap > div.about-img-holder > div.card__image > img div.about-wrap > div.about-img-holder > div.card__image > img |
Including a skip link can help users skip to the main content to save time. Learn more about skip links.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Skip to the content body.home > a.skip-link |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Best practices
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.