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 8 REVIEW 5 FIX

Landmark Structure

Action

4 landmarks

FIX

4 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

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

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

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 ✗

Heading Hierarchy

16 headings

REVIEW

16 headings

No H1 heading found

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H2 The Essence of Living
H2 Selected Prime Residences
H2 (empty)
H3 Villa Stern Sotogrande
H3 Villa Oak Sotogrande
H3 Apartment Alcazaba Beach 5201, Estepona
H3 Villa NARA, Sotogrande
H3 Villa DUNE The 15, Sotogrande
H2 A dialogue between Switzerland, art and nature
H2 Reflections from Our Clients
H3 Private Family, Switzerland
H3 Private Property Owner, Austria
H3 International Private Investor
H2 Request a private consultation
H2 Contacts
H2 Contact

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Form Accessibility

Action

4 of 9 controls have issues

REVIEW

4 of 9 controls have issues

4 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">

5 control(s) properly labeled

9 controls

5 labeled

0 placeholder only

4 unlabeled

Control	Type	Label	Method
#CybotCookiebotDialogBodyLevelButtonNecessary	checkbox	Necessary	for/id
#CybotCookiebotDialogBodyLevelButtonPreferences	checkbox	Preferences	for/id
#CybotCookiebotDialogBodyLevelButtonStatistics	checkbox	Statistics	for/id
#CybotCookiebotDialogBodyLevelButtonMarketing	checkbox	Marketing	for/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformation	checkbox	Do not sell or share my personal information	for/id
#CybotCookiebotDialogBodyLevelButtonPreferencesInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonStatisticsInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonMarketingInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonNecessaryInline	checkbox	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

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

Link & Button Quality

Action

6 issue(s) across 58 links and 20 buttons

REVIEW

6 issue(s) across 58 links and 20 buttons

6 link(s) with no accessible text

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

Got: https://sandrasliving.swiss/; javascript:void(0);; https://sandrasliving.swiss/; javascript:void(0);; https://sandrasliving.swiss/; #

8 link(s) open in new tab without warning

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

Got: https://www.cookiebot.com/en/what-is-behind-powered-by-cookiebot/?utm_source=…; [#DSR_FORM_URL#]; https://www.cookiebot.com; https://sandrasliving.swiss/sceda-immobile/?immobile=2209; https://sandrasliving.swiss/sceda-immobile/?immobile=2238; https://sandrasliving.swiss/sceda-immobile/?immobile=2410; https://sandrasliving.swiss/sceda-immobile/?immobile=2290; https://sandrasliving.swiss/sceda-immobile/?immobile=2334

44 link(s) with descriptive text

58 links

6 empty

0 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.cookiebot.com/en/what-is-beh…	Cookiebot by Usercentrics - op…	new tab	Add '(opens in new tab)' to text
[#DSR_FORM_URL#]	[#DSR_FORM_URL_TEXT#]	new tab	Add '(opens in new tab)' to text
https://www.cookiebot.com	Cookiebot	new tab	Add '(opens in new tab)' to text
https://sandrasliving.swiss/	(empty)	empty	Add link text or aria-label
javascript:void(0);	(empty)	empty	Add link text or aria-label
https://sandrasliving.swiss/	(empty)	empty	Add link text or aria-label
javascript:void(0);	(empty)	empty	Add link text or aria-label
https://sandrasliving.swiss/sceda-immobi…	DISCOVER MORE	new tab	Add '(opens in new tab)' to text
https://sandrasliving.swiss/sceda-immobi…	DISCOVER MORE	new tab	Add '(opens in new tab)' to text
https://sandrasliving.swiss/sceda-immobi…	DISCOVER MORE	new tab	Add '(opens in new tab)' to text
https://sandrasliving.swiss/sceda-immobi…	DISCOVER MORE	new tab	Add '(opens in new tab)' to text
https://sandrasliving.swiss/sceda-immobi…	DISCOVER MORE	new tab	Add '(opens in new tab)' to text
https://sandrasliving.swiss/	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label

64 links and buttons have descriptive text

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

https://sandrasliving.swiss/; javascript:void(0);; https://sandrasliving.swiss/; javascript:void(0);; https://sandrasliving.swiss/; #

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.

https://www.cookiebot.com/en/what-is-behind-powered-by-cookiebot/?utm_source=…; [#DSR_FORM_URL#]; https://www.cookiebot.com; https://sandrasliving.swiss/sceda-immobile/?immobile=2209; https://sandrasliving.swiss/sceda-immobile/?immobile=2238; https://sandrasliving.swiss/sceda-immobile/?immobile=2410; https://sandrasliving.swiss/sceda-immobile/?immobile=2290; https://sandrasliving.swiss/sceda-immobile/?immobile=2334

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

Tabindex Anti-Patterns

0 positive, 4 -1-on-focusable

REVIEW

0 positive, 4 -1-on-focusable

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogPoweredbyCybot">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavDetails">

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavAdSettings">

tabindex="-1" on naturally-focusable <a id="CybotCookiebotDialogNavAbout">

Tap Target Adequacy

Action

8 tap target(s) too small or too close together

REVIEW

8 tap target(s) too small or too close together

8 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Pagina non trovata – Site ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

a [#IABV2SETTINGS#]

3.41:1

#000000

#686059

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 The Essence of Livin…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 Selected Prime Resid…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 A dialogue between S…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 Reflections from Our…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 Request a private co…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 Contacts	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h2 Contact	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Villa Stern Sotogran…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Villa Oak Sotogrande	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Apartment Alcazaba B…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Villa NARA, Sotogran…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Villa DUNE The 15, S…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Private Family, Swit…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 Private Property Own…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
h3 International Privat…	16.98:1	3.0:1	#000000	#E7E7E7	Pass
title Casa base – Site	19.95:1	4.5:1	#000000	#F9F9F9	Pass
a Consent	17.94:1	4.5:1	#000000	#EDEDED	Pass
a Details	9.82:1	4.5:1	#000000	#B3B1AE	Pass
a [#IABV2SETTINGS#]	3.41:1	4.5:1	#000000	#686059	Fail
a About	7.08:1	4.5:1	#000000	#9A949A	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 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

Alt Text Quality

2 of 22 images have issues

PASS

2 of 22 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image(s) with generic alt text

4 decorative image(s) correctly marked

16 image(s) with good alt text

22 images 16 good alt text 4 decorative 1 generic 1 missing

Issue	Count
missing	1 image(s)
generic	1 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

A+

Form Input Types

9 form control(s) checked, no type mismatches

PASS

9 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

9 form control(s) checked, no input-semantic issues

PASS

9 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "it-IT"

PASS

Lang attribute set to "it-IT"

<html lang="it-IT"> is set and valid

Got: it-IT

A+

Iframe Accessibility

All 2 iframe(s) have descriptive titles

PASS

All 2 iframe(s) have descriptive titles

All 2 iframe(s) have title attributes

A+

Mobile-Readable Font Sizes

All 76 visible text node(s) render at >= 12 CSS pixels

PASS

All 76 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

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 90/100 — 3 failing, 27 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.

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
The Essence of Living `div.wdt-elementor-container-fluid > div.elementor > div.elementor-element > h2.e-04ff0a4-b87f730`
Selected Prime Residences `div.wdt-elementor-container-fluid > div.elementor > div.elementor-element > h2.e-fecc567-bf3043b`
A dialogue between Switzerland, art and nature `div.elementor > div.elementor-element > div.elementor-element > h2.e-f5893d6-4d3d7f3`
01 `div.sl-timeline-step > div.sl-timeline-bubble > div.sl-timeline-front > strong`
DISCOVERY `div.sl-timeline-step > div.sl-timeline-bubble > div.sl-timeline-front > small`
02 `div.sl-timeline-step > div.sl-timeline-bubble > div.sl-timeline-front > strong`
SELECTION `div.sl-timeline-step > div.sl-timeline-bubble > div.sl-timeline-front > small`
03 `div.sl-timeline-step > div.sl-timeline-bubble > div.sl-timeline-front > strong`
VIEWINGS `div.sl-timeline-step > div.sl-timeline-bubble > div.sl-timeline-front > small`
04 `div.sl-timeline-step > div.sl-timeline-bubble > div.sl-timeline-front > strong`
YOUR HOME `div.sl-timeline-step > div.sl-timeline-bubble > div.sl-timeline-front > small`
Reflections from Our Clients `div.wdt-elementor-container-fluid > div.elementor > div.elementor-element > h2.e-586277e-a762ee5`
CONTACT US `div#wdt-button-26323d4 > a.wdt-button > div.wdt-button-text > span`
A contemporary and conscious approach to living, where nature and art come toge… `div.elementor-element > div.elementor-element > div.elementor-element > p`
Contacts `div.elementor-element > div.elementor-element > div.elementor-element > h2.elementor-heading-title`
sandra@sandrasliving.swiss `div.elementor-element > p > a > span.elementor-icon-list-text`
+41 79 386 60 52 `div.elementor-element > div.elementor-element > span.selectable-text > a`
Legal Notice \| `ul.elementor-icon-list-items > li.elementor-icon-list-item > a > span.elementor-icon-list-text`
Privacy Policy \| `ul.elementor-icon-list-items > li.elementor-icon-list-item > a > span.elementor-icon-list-text`
Terms & Services `ul.elementor-icon-list-items > li.elementor-icon-list-item > a > span.elementor-icon-list-text`
SANDRA S Living GmbH © All rights reserved. 2026 – Credits `div.elementor-element > div.elementor-element > p > span`
Credits `div.elementor-element > p > span > a`

These are opportunities to improve the legibility of your content.

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
div.elementor-element > div.elementor-widget-container > div#gsquare-f8e70f8 > a `div.elementor-element > div.elementor-widget-container > div#gsquare-f8e70f8 > a`
div.elementor-widget-container > div.wdt-header-menu > div.mobile-nav-container > a.menu-trigger `div.elementor-widget-container > div.wdt-header-menu > div.mobile-nav-container > a.menu-trigger`

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Scheda 1 `div.elementor-widget-container > section.sl-root > div.sl-showcase-dots > button.sl-showcase-dot`
Scheda 2 `div.elementor-widget-container > section.sl-root > div.sl-showcase-dots > button.sl-showcase-dot`
Scheda 3 `div.elementor-widget-container > section.sl-root > div.sl-showcase-dots > button.sl-showcase-dot`
Scheda 4 `div.elementor-widget-container > section.sl-root > div.sl-showcase-dots > button.sl-showcase-dot`
Scheda 5 `div.elementor-widget-container > section.sl-root > div.sl-showcase-dots > button.sl-showcase-dot`
Scheda 1 `div.elementor-widget-container > section.sl-root > div.sl-profile-dots > button.is-active`
Scheda 2 `div.elementor-widget-container > section.sl-root > div.sl-profile-dots > button`
Scheda 3 `div.elementor-widget-container > section.sl-root > div.sl-profile-dots > button`

These items highlight common accessibility best practices.

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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

●`[lang]` attributes have a valid value

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

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

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

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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Image elements do not have `[alt]` attributes that are redundant text.

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