Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 5 REVIEW 7 FIX

Alt Text Quality

Action

17 of 28 images have issues

FIX

17 of 28 images have issues

14 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 image(s) with filename as alt text

11 decorative image(s) correctly marked

28 images 11 decorative 3 generic 14 missing

Issue	Count
missing	14 image(s)
filename	3 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

Mobile-Readable Font Sizes

Action

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

FIX

68% 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 ("skipToContentData"); <span> 11.0px ("skipToNavigationData"); <span> 11.0px ("DISCOVER MORE"); <a> 11.0px ("PRIVACY INFORMATIVE"); <a> 11.0px ("LEGAL NOTES").

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

6 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 6 <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

11 landmarks

REVIEW

11 landmarks

<main> landmark present

6 <nav> landmark(s) found

5 of 6 <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

1 issue(s) across 68 links and 35 buttons

REVIEW

1 issue(s) across 68 links and 35 buttons

1 link(s) with no accessible text

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

Got: /

29 link(s) open in new tab without warning

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

Got: /lancia-new-era; /lancia-pu-ra-hpe; /design-lab; /icons; https://www.facebook.com/Lancia; https://www.instagram.com/lancia_official/; https://www.youtube.com/@lancia; https://www.linkedin.com/company/lanciaofficial; https://twitter.com/lancia_official; /models/gamma (+19 more)

38 link(s) with descriptive text

68 links

1 empty

0 generic text

29 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
/lancia-new-era	New Era	new tab	Add '(opens in new tab)' to text
/lancia-pu-ra-hpe	PU + RA HPE Concept	new tab	Add '(opens in new tab)' to text
/design-lab	Design Lab	new tab	Add '(opens in new tab)' to text
/icons	Icons	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Lancia	https://www.facebook.com/Lanci…	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/lancia_officia…	https://www.instagram.com/lanc…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@lancia	https://www.youtube.com/@lanci…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/lanciao…	https://www.linkedin.com/compa…	new tab	Add '(opens in new tab)' to text
https://twitter.com/lancia_official	https://twitter.com/lancia_off…	new tab	Add '(opens in new tab)' to text
/models/gamma	New Lancia Gamma	new tab	Add '(opens in new tab)' to text
/models/ypsilon-turbo-100	Ypsilon Turbo 100	new tab	Add '(opens in new tab)' to text
/models/ypsilon-hybrid	Ypsilon Hybrid	new tab	Add '(opens in new tab)' to text
/models/ypsilon-electric	Ypsilon Electric	new tab	Add '(opens in new tab)' to text
/models/lancia-ypsilon-hf-280	Ypsilon HF 280	new tab	Add '(opens in new tab)' to text
/models/lancia-ypsilon-hf-line	Ypsilon HF Line	new tab	Add '(opens in new tab)' to text
/ibrido-e-elettrico/electric-mobility	THE ADVANTAGES OF ELECTRIC	new tab	Add '(opens in new tab)' to text
/ibrido-e-elettrico/vantaggi-auto-ibride	ADVANTAGES OF HYBRID	new tab	Add '(opens in new tab)' to text
/connected-services	Connected Services	new tab	Add '(opens in new tab)' to text
/120-anniversary	120 Anniversary	new tab	Add '(opens in new tab)' to text
/lancia-new-era	NEW ERA	new tab	Add '(opens in new tab)' to text
/lancia-pu-ra-hpe	PU+RA HPE CONCEPT	new tab	Add '(opens in new tab)' to text
/design-lab	DESIGN LAB	new tab	Add '(opens in new tab)' to text
/icons	ICONS	new tab	Add '(opens in new tab)' to text
/heritage	HERITAGE	new tab	Add '(opens in new tab)' to text
/eberhard	Eberhard	new tab	Add '(opens in new tab)' to text
/lancia-corse-news/lancia-corse-ypsilon-…	Range Ypsilon HF	new tab	Add '(opens in new tab)' to text
/lancia-corse	Trofeo Lancia	new tab	Add '(opens in new tab)' to text
/lancia-corse-news/lancia-wrc2	WRC2	new tab	Add '(opens in new tab)' to text
/lancia-corse-news/erc	ERC	new tab	Add '(opens in new tab)' to text

73 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

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

/lancia-new-era; /lancia-pu-ra-hpe; /design-lab; /icons; https://www.facebook.com/Lancia; https://www.instagram.com/lancia_official/; https://www.youtube.com/@lancia; https://www.linkedin.com/company/lanciaofficial; https://twitter.com/lancia_official; /models/gamma (+19 more)

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.

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

REVIEW

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

11 pass 9 fail WCAG AA 11 pass AA only

title Lancia: the classy city car - official s…

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · top of page (header area)

span skipToContentData

3.66:1

#000000

#666666

needs 4.5:1 (normal text)

16px · top of page (header area)

span Models

3.05:1

#000000

#545B63

needs 4.5:1 (normal text)

16px · top of page (header area)

span Choose your country

3.20:1

#000000

#585E65

needs 4.5:1 (normal text)

16px · top of page (header area)

span Choose your country

1.66:1

#000000

#2D352C

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span skipToNavigationData

1.25:1

#000000

#1E1E10

needs 4.5:1 (normal text)

16px · above the fold

span Models

1.22:1

#000000

#201A18

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

span All Motorizations

1.55:1

#000000

#272F37

needs 4.5:1 (normal text)

16px · above the fold

span (active )

2.24:1

#000000

#444748

needs 4.5:1 (normal text)

16px · above the fold

2 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
h1 The New Lancia Gamma	3.66:1	3.0:1	#000000	#666666	Pass
h1 Crafted in Italia.	3.66:1	3.0:1	#000000	#666666	Pass
h1 Designed for tomorro…	3.66:1	3.0:1	#000000	#666666	Pass
h2 Naturally Eye-catchi…	3.66:1	3.0:1	#000000	#666666	Pass
h2 Unleash the instinct	3.66:1	3.0:1	#000000	#666666	Pass
h2 Elegance of a Master…	3.66:1	3.0:1	#000000	#666666	Pass
h2 Discover the engines	3.66:1	3.0:1	#000000	#666666	Pass
h2 Free2Move Charge	3.66:1	3.0:1	#000000	#666666	Pass
h2 Lancia Ypsilon Range	3.66:1	3.0:1	#000000	#666666	Pass
h2 Lancia Corse: a lega…	3.66:1	3.0:1	#000000	#666666	Pass
h3 LANCIA YPSILON EDIZI…	3.66:1	3.0:1	#000000	#666666	Pass
title Lancia: the classy c…	3.66:1	4.5:1	#000000	#666666	Fail
span skipToContentData	3.66:1	4.5:1	#000000	#666666	Fail
span Models	3.05:1	4.5:1	#000000	#545B63	Fail
span Choose your country	3.20:1	4.5:1	#000000	#585E65	Fail
span Choose your country	1.66:1	4.5:1	#000000	#2D352C	Fail
span skipToNavigationData	1.25:1	4.5:1	#000000	#1E1E10	Fail
span Models	1.22:1	4.5:1	#000000	#201A18	Fail
span All Motorizations	1.55:1	4.5:1	#000000	#272F37	Fail
span (active )	2.24:1	4.5:1	#000000	#444748	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 Hierarchy

9 headings

PASS

9 headings

Single H1 present

H1 The New Lancia Gamma Crafted in Italia. Designed for tomorrow.
H2 Naturally Eye-catching
H2 Unleash the instinct
H2 Elegance of a Masterpiece
H2 Discover the engines
H2 Free2Move Charge
H2 Lancia Ypsilon Range
H2 Lancia Corse: a legacy reignited
H3 LANCIA YPSILON EDIZIONE LIMITATA CASSINA

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+

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

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

PASS

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

No tabindex anti-patterns detected

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

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.

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 22 passed

PASS

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

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.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`
div.cvRow > div.cvTextImage__image > picture > img.lazy `div.cvRow > div.cvTextImage__image > picture > img.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`
div#cvFooter > div.cvContainer > div.cvFooter__social > a `div#cvFooter > div.cvContainer > div.cvFooter__social > a`
div#cvFooter > div.cvContainer > div.cvFooter__social > a `div#cvFooter > div.cvContainer > div.cvFooter__social > a`
div#cvFooter > div.cvContainer > div.cvFooter__social > a `div#cvFooter > div.cvContainer > div.cvFooter__social > a`
div#cvFooter > div.cvContainer > div.cvFooter__social > a `div#cvFooter > div.cvContainer > div.cvFooter__social > a`
div#cvFooter > div.cvContainer > div.cvFooter__social > a `div#cvFooter > div.cvContainer > div.cvFooter__social > a`

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

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

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

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

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

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