Skip to content
https://conad.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
5
REVIEW
7
PASS
12
INFO
0
Checks
24
12 PASS 7 REVIEW 5 FIX
D
Mobile Keyboard & Autofill
Action
1/1 eligible field(s) missing autocomplete or inputmode
FIX
1/1 eligible field(s) missing autocomplete or inputmode
Warning::
1 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: street-address.
Got: <input name="address" id="rc102-carrot-banner-762526476-search-field-address-input">
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: #ffffff
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::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

C
Heading Hierarchy
Action
21 headings, 1 skip(s)
REVIEW
21 headings, 1 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Bassi e Fissi
  • H3 Bassi e Fissi
  • H4 CONAD Mandorle Sgusciate 100 g
  • H4 CONAD Fagioli Corona 400 g
  • H4 CONAD Cono Caffè 6 coni 450 g
  • H4 CONAD Pasta di Semola di Grano Duro N°21 Tempestine 500 g
  • H4 CONAD Pomodorini 3 x 400 g
  • H4 CONAD Lavastoviglie Tabs Limone 100 x 12 g
  • H2 Scopri i valori che ci rendono unici
  • H2 HeyConad App, spesa, viaggi, assicurazioni e molto di più!
  • H3 La spesa a portata di click
  • H3 Prenota viaggi e vacanze online
  • H2 Le linee di prodotto per le tue esigenze
  • H2 I negozi specializzati
  • H2 Scopri consigli e ricette Bene Insieme
  • H5 Linguine con Crema di Mandorle, Speck e Pistacchi skipped
  • H5 Carciofi alla Romana Sapori & Dintorni: il gusto della Tradizione
  • H5 Orto sul Balcone: Guida su cosa Piantare Per un'Estate a Km 0!
  • H5 Svezzamento Primaverile: Guida alle Prime Pappe con Verdure sicure...
  • H2 Ultime news
  • H3 Personalizza la tua navigazione

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

B
Iframe Accessibility
2/3 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/3 iframe(s) missing title; 0 placeholder(s)
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.
C
Mobile-Readable Font Sizes
Action
80% of visible text renders at >= 12 CSS px (7 below threshold)
REVIEW
80% of visible text renders at >= 12 CSS px (7 below threshold)
Warning::
7 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: <div> 10.0px ("Equilibrio tra Gusto e Sostenibilità"); <div> 10.0px ("Prodotti Locali e Tradizioni Italiane"); <div> 10.0px ("Freschezza ed Eccellenza"); <div> 10.0px ("Viaggio nell'Eccellenza"); <div> 10.0px ("Per te che ami il sapore unico e origina...").
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 404 | Conad ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
14 icon(s) detected
REVIEW
14 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
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA
a Seleziona il punto vendita per scoprire …
4.22:1
#000000
on
#397889
needs 4.5:1 (normal text)
16px · above the fold
span Gestisci
4.22:1
#000000
on
#397889
needs 4.5:1 (normal text)
16px · above the fold
span Spesa Online
4.22:1
#000000
on
#397889
needs 4.5:1 (normal text)
16px · above the fold
span Assicurazioni
4.22:1
#000000
on
#397889
needs 4.5:1 (normal text)
16px · above the fold
span Viaggi
4.22:1
#000000
on
#397889
needs 4.5:1 (normal text)
16px · above the fold
span Sapori&
4.22:1
#000000
on
#397889
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Bassi e Fissi21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Scopri i valori che …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Le linee di prodotto…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Scopri consigli e ri…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ultime news21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Bassi e Fissi21.00:13.0:1
#000000
#FFFFFF
Pass
h3 La spesa a portata d…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Prenota viaggi e vac…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Personalizza la tua …21.00:13.0:1
#000000
#FFFFFF
Pass
title Conad.it: il sito uf…21.00:14.5:1
#000000
#FFFFFF
Pass
label Cosa stai cercando?21.00:14.5:1
#000000
#FFFFFF
Pass
span Ultimo negozio visit…19.42:14.5:1
#000000
#F8F6EF
Pass
span Negozio preferito:11.46:14.5:1
#000000
#ACC4C5
Pass
a Seleziona il punto v…4.22:14.5:1
#000000
#397889
Fail
span Gestisci4.22:14.5:1
#000000
#397889
Fail
span Spesa Online4.22:14.5:1
#000000
#397889
Fail
span Assicurazioni4.22:14.5:1
#000000
#397889
Fail
span Viaggi4.22:14.5:1
#000000
#397889
Fail
span Sapori&4.22:14.5:1
#000000
#397889
Fail
span Sostenibilità12.11:14.5:1
#000000
#B0C9D0
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.

A+
Heading Text Quality
All 21 heading(s) have substantive, well-formed text
PASS
All 21 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 120 images OK
PASS
All 120 images OK
Info::
120 image(s) with good alt text
120 images 120 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 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::
3 control(s) properly labeled
4 controls
3 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#rs51-header-1301092497-searchbar-search-field-rt069-search-inputinputCosa stai cercando?aria-label
#rs51-header-1301092497-menu-mob-search-search-field-q-inputinputCerca nel sitoaria-label
#rc102-carrot-banner-762526476-search-field-address-inputinputIndirizzo, CAP o cittàaria-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
3 input(s) using type=text where a specific type would help
PASS
3 input(s) using type=text where a specific type would help
Info::
Input "rt069-search" should use type="search" (currently type="text")
Field name "rt069-search" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "q" should use type="search" (currently type="text")
Field name "q" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "address" should use type="search" (currently type="text")
Field name "address" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
4 form control(s) checked, no input-semantic issues
PASS
4 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
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
10 explicit tabindex attribute(s) checked, no anti-patterns
PASS
10 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
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+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Conad, Persone oltre le cose
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Conad, Persone oltre le cose ✓192×192 icon ✓512×512 icon ✓Start URL https://www.conad.it ✓Display Mode standalone ✓
Name Conad, Persone oltre le cose Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 7 icon(s)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
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 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
Lighthouse Accessibility Audits
Score 91/100 — 3 failing, 24 passed
PASS
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.

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
Scopri di più div.rt100-hero__left > div.rt100-hero__ctaArea > a#rc100-hero-1876489418-cta-0-cta > span.rt002-cta__label
viaggi.conad.it  div.rt217-card-banner__textsWrapper > div#rc125-banner-carousel-170318333-banner-1-description > p > a
Vai al volantino section.rl1-layout__item > div#rc101-thumb-slider-1246884741 > a#rc101-thumb-slider-1246884741-cta-cta > span.rt002-cta__label
Primi Piatti div.rt202-card-elev-recipes__info > div.rt202-card-elev-recipes__up > a#rc105-collector-458710796-var6RecipesRow1-card-carousel-slider-0-linkCategory > div.rt202-card-elev-recipes__category
Mondo Conad div.rt200-card-elev-editorial__bottom > div > a#rc105-collector-458710796-var6EditorialsRow2-card-carousel-slider-0-linkCategory > div.rt200-card-elev-editorial__category
Vivere Sostenibile div.rt200-card-elev-editorial__bottom > div > a#rc105-collector-458710796-var6EditorialsRow2-card-carousel-slider-1-linkCategory > div.rt200-card-elev-editorial__category
News e Approfondimenti div.rt201-card-elev-news__bottom > div > a#rc105-collector-1061910916-news-card-carousel-slider-0-linkCategory > div.rt201-card-elev-news__category
News e Approfondimenti div.rt201-card-elev-news__bottom > div > a#rc105-collector-1061910916-news-card-carousel-slider-1-linkCategory > div.rt201-card-elev-news__category
Richiamo Prodotto div#rc105-collector-1061910916-news-card-carousel-slider-2 > div.rt201-card-elev-news__bottom > div > div.rt201-card-elev-news__category
Leggi richiamo div.rt201-card-elev-news__bottom > div > a#rc105-collector-1061910916-news-card-carousel-slider-2-ctaLink-cta > span.rt002-cta__label
News e Approfondimenti div.rt201-card-elev-news__bottom > div > a#rc105-collector-1061910916-news-card-carousel-slider-3-linkCategory > div.rt201-card-elev-news__category
News e Approfondimenti div.rt201-card-elev-news__bottom > div > a#rc105-collector-1061910916-news-card-carousel-slider-4-linkCategory > div.rt201-card-elev-news__category
News e Approfondimenti div.rt201-card-elev-news__bottom > div > a#rc105-collector-1061910916-news-card-carousel-slider-5-linkCategory > div.rt201-card-elev-news__category
News e Approfondimenti div.rt201-card-elev-news__bottom > div > a#rc105-collector-1061910916-news-card-carousel-slider-6-linkCategory > div.rt201-card-elev-news__category
Richiamo Prodotto div#rc105-collector-1061910916-news-card-carousel-slider-7 > div.rt201-card-elev-news__bottom > div > div.rt201-card-elev-news__category
Leggi richiamo div.rt201-card-elev-news__bottom > div > a#rc105-collector-1061910916-news-card-carousel-slider-7-ctaLink-cta > span.rt002-cta__label
Accedi div > div.rt132-login-banner__ctas > a#rc132-login-banner-575859007-login-cta > span.rt002-cta__label

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Linguine con Crema di Mandorle, Speck e Pistacchi div.rt202-card-elev-recipes__info > div.rt202-card-elev-recipes__up > a#rc105-collector-458710796-var6RecipesRow1-card-carousel-slider-0-link-2 > h5.rt202-card-elev-recipes__title

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header#rs51-header-1301092497 > div#rs51-header-1301092497-topbar > div.rt054-topbar__container > a.rt054-topbar__next header#rs51-header-1301092497 > div#rs51-header-1301092497-topbar > div.rt054-topbar__container > a.rt054-topbar__next

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.

○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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 are distinguishable without relying on color.
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback