Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 7 REVIEW 6 FIX

Alt Text Quality

Action

26 of 29 images have issues

FIX

26 of 29 images have issues

26 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

4 image-in-link without alt text

An image inside a link with no alt creates an empty link.

3 decorative image(s) correctly marked

29 images 3 decorative 26 missing

Issue	Count
missing	26 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

404 Error Page

Action

HTTP 403, bare page

FIX

HTTP 403, bare page

Unexpected status code: HTTP 403

Expected HTTP 404 but received 403. This may confuse search engine crawlers.

Got: HTTP 403

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 403 ✗Page Title Access Denied ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

4 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 4 <nav> element(s)

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.

Landmark Structure

7 landmarks

REVIEW

7 landmarks

<main> landmark present

4 <nav> landmark(s) found

4 of 4 <nav> elements are unlabeled

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

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

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

Link & Button Quality

2 issue(s) across 30 links and 14 buttons

REVIEW

2 issue(s) across 30 links and 14 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /news/fiat-topolino-compasso-doro-adi-2026 ("Read more")

7 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.pinacoteca-agnelli.it/en/casa-fiat/%20; #; https://www.facebook.com/Fiat/; https://twitter.com/fiat; https://www.youtube.com/fiat; https://www.instagram.com/fiat/; https://www.linkedin.com/company/fiatauto/

21 link(s) with descriptive text

30 links

1 empty

1 generic text

7 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
/news/fiat-topolino-compasso-doro-adi-20…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Fiat Topolino Compasso Doro Adi 2026
/news/new-fiat-500-dolcevita-special-ser…	FIAT unveils the New 500 Dolce…	img no alt	Add alt attribute to the image
/news/stellantis-upgrades-connected-serv…	Stellantis Upgrades Its Connec…	img no alt	Add alt attribute to the image
/news/fiat-accelerates-europe-25-sales-g…	FIAT Accelerates Across Europe…	img no alt	Add alt attribute to the image
/news/fiat-wallpaper-milano-design-week-…	FIAT × Wallpaper* at Milano D…	img no alt	Add alt attribute to the image
https://www.pinacoteca-agnelli.it/en/cas…	Discover more	new tab	Add '(opens in new tab)' to text
#	darktheme	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Fiat/	facebook	new tab	Add '(opens in new tab)' to text
https://twitter.com/fiat	Twitter	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/fiat	Youtube	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/fiat/	Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/fiataut…	LinkedIn	new tab	Add '(opens in new tab)' to text

35 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

Why this matters

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

Generic link text like 'click here' doesn't describe the destination.

/news/fiat-topolino-compasso-doro-adi-2026 ("Read more")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://www.pinacoteca-agnelli.it/en/casa-fiat/%20; #; https://www.facebook.com/Fiat/; https://twitter.com/fiat; https://www.youtube.com/fiat; https://www.instagram.com/fiat/; https://www.linkedin.com/company/fiatauto/

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

Document Language

Action

Lang attribute "en-CORPORATE" is malformed

REVIEW

Lang attribute "en-CORPORATE" is malformed

<html lang="en-CORPORATE"> is not a valid BCP-47 tag

Language attribute is present but doesn't parse as a valid BCP-47 tag (e.g., 'english' instead of 'en', or 'us' which is a region not a language). Screen readers may ignore invalid values and fall back to the system locale.

Mobile-Readable Font Sizes

Action

83% of visible text renders at >= 12 CSS px (7 below threshold)

REVIEW

83% of visible text renders at >= 12 CSS px (7 below threshold)

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: <span> 11.0px ("Choose your country"); <span> 11.0px ("Privacy"); <span> 11.0px ("Legal notes"); <span> 11.0px ("Data Act"); <span> 11.0px ("Terms and conditions").

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 7 fail WCAG AA

REVIEW

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

13 pass 7 fail WCAG AA 13 pass AA only

h1 Fiat Grande Panda

1.35:1

#000000

#1D252B

needs 3.0:1 (large text)

32px · above the fold

h2 Fiat key drivers

2.21:1

#000000

#434649

needs 3.0:1 (large text)

24px · above the fold

h2 Discover our news

2.02:1

#000000

#4D3D2C

needs 3.0:1 (large text)

24px · above the fold

h2 FIAT Topolino wins the XXIX Premio Compa…

1.95:1

#000000

#483C26

needs 3.0:1 (large text)

24px · mid-page

title Fiat - Official Website

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · top of page (header area)

span Fiat

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · top of page (header area)

span GO TO FIAT

1.11:1

#000000

#0A1217

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Fiat Grande Panda	1.35:1	3.0:1	#000000	#1D252B	Fail
h2 Fiat key drivers	2.21:1	3.0:1	#000000	#434649	Fail
h2 Discover our news	2.02:1	3.0:1	#000000	#4D3D2C	Fail
h2 FIAT Topolino wins t…	1.95:1	3.0:1	#000000	#483C26	Fail
h2 Releases & events	3.66:1	3.0:1	#000000	#666666	Pass
h2 Visit Casa Fiat	3.66:1	3.0:1	#000000	#666666	Pass
h2 (FIAT)	3.66:1	3.0:1	#000000	#666666	Pass
h2 Family	3.66:1	3.0:1	#000000	#666666	Pass
h2 Italian symbol	3.66:1	3.0:1	#000000	#666666	Pass
h2 You don't need to se…	3.66:1	3.0:1	#000000	#666666	Pass
h2 Italiannes around th…	3.66:1	3.0:1	#000000	#666666	Pass
h3 New 500 hybrid	3.66:1	3.0:1	#000000	#666666	Pass
h3 New Topolino Vilebre…	3.66:1	3.0:1	#000000	#666666	Pass
h3 FIAT \| Grande Panda …	3.66:1	3.0:1	#000000	#666666	Pass
h3 500e Giorgio Armani …	3.66:1	3.0:1	#000000	#666666	Pass
h3 Happy birthday 500!	3.66:1	3.0:1	#000000	#666666	Pass
h3 Italy is our engine	3.66:1	3.0:1	#000000	#666666	Pass
title Fiat - Official Webs…	3.66:1	4.5:1	#000000	#666666	Fail
span Fiat	3.66:1	4.5:1	#000000	#666666	Fail
span GO TO FIAT	1.11:1	4.5:1	#000000	#0A1217	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.

Lighthouse Accessibility Audits

Score 84/100 — 3 failing, 22 passed

REVIEW

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.

ARIA

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
New 500 hybrid Whoever you are – human or android – when you drive a Fiat 500,… `div.cvTechnology__wrapper > div.cvTechnology__sections > div.ID17-TechnologyItem > div.cvTechnology__sectionWrapper`
New Topolino Vilebrequin Collector’s Edition Get ready to spend the summer wit… `div.cvTechnology__wrapper > div.cvTechnology__sections > div.ID17-TechnologyItem > div.cvTechnology__sectionWrapper`
FIAT \| Grande Panda - Everyday life, easier. Happiness is holding hands and go… `div.cvTechnology__wrapper > div.cvTechnology__sections > div.ID17-TechnologyItem > div.cvTechnology__sectionWrapper`
500e Giorgio Armani Collectors Edition Two absolute icons - Giorgio Armani and… `div.cvTechnology__wrapper > div.cvTechnology__sections > div.ID17-TechnologyItem > div.cvTechnology__sectionWrapper`
Happy birthday 500! Italian design recognised the world over, for 67 years. `div.cvTechnology__wrapper > div.cvTechnology__sections > div.ID17-TechnologyItem > div.cvTechnology__sectionWrapper`
Italy is our engine Love is the driving force behind everything, and love for … `div.cvTechnology__wrapper > div.cvTechnology__sections > div.ID17-TechnologyItem > div.cvTechnology__sectionWrapper`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.swiper-wrapper > div.ID06-CanvasMediaItem > picture.cvCanvasMedia__image > img.slider-lazy `div.swiper-wrapper > div.ID06-CanvasMediaItem > picture.cvCanvasMedia__image > img.slider-lazy`
div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy `div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy`
div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy `div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy`
div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy `div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy`
div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy `div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy`
div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy `div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy`
div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy `div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy`
div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy `div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy`
div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy `div.cvContainer > div.cvContentGrid__cards > div.ID04-ContentGridItem > img.lazy`
div.cvRow > div.cvTextImage__image > picture > img.lazy `div.cvRow > div.cvTextImage__image > picture > img.lazy`
div.cvTechnology__sectionWrapper > div.cvTechnology__sectionMedia > picture.cvTechnology__image > img.lazy `div.cvTechnology__sectionWrapper > div.cvTechnology__sectionMedia > picture.cvTechnology__image > img.lazy`
div.cvTechnology__sectionWrapper > div.cvTechnology__sectionMedia > picture.cvTechnology__image > img.lazy `div.cvTechnology__sectionWrapper > div.cvTechnology__sectionMedia > picture.cvTechnology__image > img.lazy`
div.cvTechnology__sectionWrapper > div.cvTechnology__sectionMedia > picture.cvTechnology__image > img.lazy `div.cvTechnology__sectionWrapper > div.cvTechnology__sectionMedia > picture.cvTechnology__image > img.lazy`
div.cvTechnology__sectionWrapper > div.cvTechnology__sectionMedia > picture.cvTechnology__image > img.lazy `div.cvTechnology__sectionWrapper > div.cvTechnology__sectionMedia > picture.cvTechnology__image > img.lazy`
div.cvTechnology__sectionWrapper > div.cvTechnology__sectionMedia > picture.cvTechnology__image > img.lazy `div.cvTechnology__sectionWrapper > div.cvTechnology__sectionMedia > picture.cvTechnology__image > img.lazy`
div.cvTechnology__sectionWrapper > div.cvTechnology__sectionMedia > picture.cvTechnology__image > img.lazy `div.cvTechnology__sectionWrapper > div.cvTechnology__sectionMedia > picture.cvTechnology__image > img.lazy`
div.cvRow > div.cvTextImage__image > picture > img.lazy `div.cvRow > div.cvTextImage__image > picture > img.lazy`
div.cvRow > div.cvTextImage__image > picture > img.lazy `div.cvRow > div.cvTextImage__image > picture > img.lazy`
div.cvGalleryFullscreen__text > div.cvGalleryFullscreen__image > picture.cvGalleryFullscreen__picture > img.slider-lazy `div.cvGalleryFullscreen__text > div.cvGalleryFullscreen__image > picture.cvGalleryFullscreen__picture > img.slider-lazy`
div.cvGalleryFullscreen__text > div.cvGalleryFullscreen__image > picture.cvGalleryFullscreen__picture > img.slider-lazy `div.cvGalleryFullscreen__text > div.cvGalleryFullscreen__image > picture.cvGalleryFullscreen__picture > img.slider-lazy`
div.cvGalleryFullscreen__text > div.cvGalleryFullscreen__image > picture.cvGalleryFullscreen__picture > img.slider-lazy `div.cvGalleryFullscreen__text > div.cvGalleryFullscreen__image > picture.cvGalleryFullscreen__picture > img.slider-lazy`
div.cvGalleryFullscreen__text > div.cvGalleryFullscreen__image > picture.cvGalleryFullscreen__picture > img.slider-lazy `div.cvGalleryFullscreen__text > div.cvGalleryFullscreen__image > picture.cvGalleryFullscreen__picture > img.slider-lazy`

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
div.wl-header > div.wl-header__logo-container > div.wlb-button-wrapper > a.wlb-button-wrapper--element `div.wl-header > div.wl-header__logo-container > div.wlb-button-wrapper > a.wlb-button-wrapper--element`

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●`[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

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●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

○`<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

○Links are distinguishable without relying on color.

○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

○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

16 headings

PASS

16 headings

Single H1 present

H1 Fiat Grande Panda
H2 Fiat key drivers
H2 Discover our news
H2 FIAT Topolino wins the XXIX Premio Compasso d’Oro ADI.
H2 Releases & events
H3 New 500 hybrid
H3 New Topolino Vilebrequin Collector’s Edition
H3 FIAT | Grande Panda - Everyday life, easier.
H3 500e Giorgio Armani Collectors Edition
H3 Happy birthday 500!
H3 Italy is our engine
H2 Visit Casa Fiat
H2 (FIAT)RED Family
H2 Italian symbol
H2 You don't need to set foot in Italy to experience dolce vita. Just get into a Fiat!
H2 Italiannes around the world

A+

Heading Text Quality

All 16 heading(s) have substantive, well-formed text

PASS

All 16 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Tabindex Anti-Patterns

42 explicit tabindex attribute(s) checked, no anti-patterns

PASS

42 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

All 7 iframe(s) have descriptive titles

PASS

All 7 iframe(s) have descriptive titles

All 7 iframe(s) have title attributes

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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