Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 6 REVIEW 5 FIX

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 ✗

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

No <nav> landmark found

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

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

Heading Hierarchy

3 headings

REVIEW

3 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 CHOOSE YOUR COUNTRY TO GET STARTED
H3 Company
H3 Condizioni di utilizzo del sito

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

Link & Button Quality

24 issue(s) across 39 links and 0 buttons

REVIEW

24 issue(s) across 39 links and 0 buttons

24 link(s) with no accessible text

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

Got: a.cmp-teaser__cardLink (#53 on page); a.cmp-teaser__cardLink (#55 on page); a.cmp-teaser__cardLink (#57 on page); a.cmp-teaser__cardLink (#59 on page); a.cmp-teaser__cardLink (#65 on page); a.cmp-teaser__cardLink (#67 on page); a.cmp-teaser__cardLink (#69 on page); a.cmp-teaser__cardLink (#71 on page); a.cmp-teaser__cardLink (#77 on page); a.cmp-teaser__cardLink (#79 on page) (+14 more)

15 link(s) with descriptive text

39 links

24 empty

0 generic text

0 new tab

0 empty buttons

Text	Issue	Suggested Fix
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label
(empty)	empty	Add link text or aria-label

15 links and buttons have descriptive text

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

a.cmp-teaser__cardLink (#53 on page); a.cmp-teaser__cardLink (#55 on page); a.cmp-teaser__cardLink (#57 on page); a.cmp-teaser__cardLink (#59 on page); a.cmp-teaser__cardLink (#65 on page); a.cmp-teaser__cardLink (#67 on page); a.cmp-teaser__cardLink (#69 on page); a.cmp-teaser__cardLink (#71 on page); a.cmp-teaser__cardLink (#77 on page); a.cmp-teaser__cardLink (#79 on page) (+14 more)

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

Mobile-Readable Font Sizes

90% of visible text renders at >= 12 CSS px (1 below threshold)

REVIEW

90% of visible text renders at >= 12 CSS px (1 below threshold)

1 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> 11.0px ("Share").

Favicon & Branding

Action

7 icon(s) detected

REVIEW

7 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, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA 12 pass AA only

title Mopar EU | Genuine Mopar Car Parts & Acc…

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · top of page (header area)

p Corso G. Agnelli 200, 10135 Torino, Ital…

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · above the fold

p Registro Imprese Torino / Codice Fiscale…

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · above the fold

p Capitale Sociale Euro 850.000.000 i.v.

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · above the fold

p Società a unico socio

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · mid-page

p L'accesso a questo sito (il “Sito) com…

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · mid-page

p Nessuna responsabilità, di qualsivoglia…

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · mid-page

p Tutti i contenuti del Sito (notizie, fot…

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 CHOOSE YOUR COUNTRY …	3.66:1	3.0:1	#000000	#666666	Pass
h3 Company	3.66:1	3.0:1	#000000	#666666	Pass
h3 Condizioni di utiliz…	3.66:1	3.0:1	#000000	#666666	Pass
title Mopar EU \| Genuine M…	3.66:1	4.5:1	#000000	#666666	Fail
a SPAIN	5.74:1	4.5:1	#FFFFFF	#666666	Pass
a ITALY	5.74:1	4.5:1	#FFFFFF	#666666	Pass
a GERMANY	5.74:1	4.5:1	#FFFFFF	#666666	Pass
a BELGIUM	5.74:1	4.5:1	#FFFFFF	#666666	Pass
a FRANCE	5.74:1	4.5:1	#FFFFFF	#666666	Pass
a SPAIN	5.74:1	4.5:1	#FFFFFF	#666666	Pass
b Stellantis Europe S.…	3.66:1	3.0:1	#000000	#666666	Pass
p Corso G. Agnelli 200…	3.66:1	4.5:1	#000000	#666666	Fail
p Registro Imprese Tor…	3.66:1	4.5:1	#000000	#666666	Fail
p Capitale Sociale Eur…	3.66:1	4.5:1	#000000	#666666	Fail
p Società a unico soc…	3.66:1	4.5:1	#000000	#666666	Fail
p L'accesso a questo s…	3.66:1	4.5:1	#000000	#666666	Fail
b Accesso al Sito ed u…	3.66:1	3.0:1	#000000	#666666	Pass
p Nessuna responsabili…	3.66:1	4.5:1	#000000	#666666	Fail
b Contenuti del sito	3.66:1	3.0:1	#000000	#666666	Pass
p Tutti i contenuti de…	3.66:1	4.5:1	#000000	#666666	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.

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 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: 1 all-caps heading(s)

A+

Alt Text Quality

All 4 images OK

PASS

All 4 images OK

4 image(s) with good alt text

4 images 4 good alt text

All images have appropriate alt text.

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+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 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

2 mobile-depth signal(s) detected

PASS

2 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.

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 12 passed

PASS

100

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.

○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-hidden="true"]` is not present on the document `<body>`

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●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

●Links have a discernible name

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○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

○Elements use only permitted ARIA attributes

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

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

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

○Buttons have an accessible name

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

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

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

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