Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 5 REVIEW 2 FIX

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

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)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

10 landmarks

REVIEW

10 landmarks

<main> landmark present

4 <nav> landmark(s) found

2 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

Tap Target Adequacy

Action

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

REVIEW

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

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

Mobile-Readable Font Sizes

Action

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

REVIEW

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

39 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 ("10"); <div> 11.0px ("10"); <div> 11.0px ("100"); <div> 11.0px ("10"); <div> 11.0px ("18").

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 Gively - Marketplace solidaire française | Vendre, louer, services solidaires & dons aux associations ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: light only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #1da1f2

Detection limited to meta tags and inline styles

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

Dark Mode✓ Dark Mode Supported

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

Detection limited to meta tags and inline styles.

A+

Heading Hierarchy

6 headings

PASS

6 headings

Single H1 present

H1 La marketplace solidaire : seconde main, location & services
H2 Pourquoi Gively n'est pas une marketplace comme les autres
H3 Économie circulaire
H3 Économie solidaire
H3 Économie locale
H3 Impact environnemental

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 12 images OK

PASS

All 12 images OK

12 image(s) with good alt text

12 images 12 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	text	Que cherchez-vous ?	aria-label
input	text	Ville ou code postal	aria-label

Link & Button Quality

29 links, 32 buttons — all OK

PASS

29 links, 32 buttons — all OK

8 link(s) open in new tab without warning

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

Got: https://www.cressoccitanie.org/Gively-la-marketplace-solidaire-toulousaine-qu…; https://www.latribune.fr/article/economie/agroconso/74001216842877/a-toulouse…; https://www.touleco.fr/Article-Market-Place-Solidaire,51793; https://www.pressreader.com/france/la-tribune-france/20260604/281741276094201; https://melles750.fr/articles/2026/2026-05-20-gively-plateforme-toulousaine-s…; https://www.linkedin.com/company/assomart/; https://www.instagram.com/gively.fr; https://www.facebook.com/share/1D1dQsnkLa/

21 link(s) with descriptive text

29 links

0 empty

0 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.cressoccitanie.org/Gively-la…	Vu dans la presse« Gively s'…	new tab	Add '(opens in new tab)' to text
https://www.latribune.fr/article/economi…	Vu dans la presse« Vendre ou…	new tab	Add '(opens in new tab)' to text
https://www.touleco.fr/Article-Market-Pl…	Vu dans la presse« Acheter d…	new tab	Add '(opens in new tab)' to text
https://www.pressreader.com/france/la-tr…	Vu dans la presse« Retrouvez…	new tab	Add '(opens in new tab)' to text
https://melles750.fr/articles/2026/2026-…	Vu dans la presse« L'une des…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/assomar…	Gively sur LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/gively.fr	Gively sur Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/share/1D1dQsnkL…	Gively sur Facebook	new tab	Add '(opens in new tab)' to text

53 links and buttons have descriptive text

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

https://www.cressoccitanie.org/Gively-la-marketplace-solidaire-toulousaine-qu…; https://www.latribune.fr/article/economie/agroconso/74001216842877/a-toulouse…; https://www.touleco.fr/Article-Market-Place-Solidaire,51793; https://www.pressreader.com/france/la-tribune-france/20260604/281741276094201; https://melles750.fr/articles/2026/2026-05-20-gively-plateforme-toulousaine-s…; https://www.linkedin.com/company/assomart/; https://www.instagram.com/gively.fr; https://www.facebook.com/share/1D1dQsnkLa/

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

A+

Form Input Types

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

2 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 "fr"

PASS

Lang attribute set to "fr"

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

Got: fr

A+

Tabindex Anti-Patterns

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

PASS

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

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

Favicon & Branding

25 icon(s) detected

PASS

25 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Gively - Marketplace Solidaire

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Gively - Marketplace Solidaire ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Gively - Marketplace Solidaire Display Mode standalone Theme Color #1DA1F2 Background Color #ffffff Icons 19 icon(s)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Service worker registration detected

The page calls `navigator.serviceWorker.register(...)` -- the prerequisite for any real PWA capability (offline support, push notifications, background sync, Cache API). This is a positive signal; whether the registered worker actually does what you want is a separate question (check DevTools > Application > Service Workers).

A+

Mobile UX Depth

3 mobile-depth signal(s) detected

PASS

3 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

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.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 La marketplace solid…	18.60:1	3.0:1	#000000	#E3F4FB	Pass
h2 Pourquoi Gively n'es…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Économie circulaire	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Économie solidaire	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Économie locale	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Impact environnement…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Gively — Seconde m…	20.52:1	4.5:1	#000000	#F9FDFF	Pass
title Gively - Marketplace…	20.52:1	4.5:1	#000000	#F9FDFF	Pass
span Gively	15.55:1	4.5:1	#0F172A	#E0F2FD	Pass
p Achetez, vendez et l…	18.29:1	4.5:1	#000000	#E0F2FD	Pass
p Une part de chaque t…	15.57:1	4.5:1	#0F172A	#E1F2FD	Pass
a Aller au contenu pri…	18.44:1	4.5:1	#000000	#E1F3FD	Pass
span Gively	18.44:1	4.5:1	#000000	#E1F3FD	Pass
a Rechercher	18.43:1	4.5:1	#000000	#E1F3FC	Pass
a Publier	18.46:1	4.5:1	#000000	#E2F3FC	Pass
a Associations	18.58:1	4.5:1	#000000	#E2F4FC	Pass
a Mon espace	18.58:1	4.5:1	#000000	#E2F4FC	Pass
a Connexion	18.58:1	4.5:1	#000000	#E2F4FC	Pass
span Gively	18.58:1	4.5:1	#000000	#E2F4FC	Pass
span seconde main, locati…	18.72:1	4.5:1	#000000	#E3F5FB	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.

Lighthouse Accessibility Audits

Score 93/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
Rechercher `div.container > form.flex > button.flex > span`
Vente `div.min-h-screen > div.container > div.flex > button.flex-1`
Location `div.min-h-screen > div.container > div.flex > button.flex-1`
Services `div.min-h-screen > div.container > div.flex > button.flex-1`
♥ 10% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 10% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 6% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 10% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 18% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 27% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 50% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 50% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
PRO `a.group > div.aspect-[4/3] > div.absolute > span.text-xs`
♥ 10% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 10% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 6% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 50% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 10% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 87% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 22% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 10% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 5% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 10% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 46% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
♥ 28% `div.snap-start > a.group > div.aspect-[4/3] > div.absolute`
13 juil. 2026 `div.grid > a.group > div.p-3 > p.text-[10px]`
Lire → `div.grid > a.group > div.p-3 > p.mt-1.5`
9 juil. 2026 `div.grid > a.group > div.p-3 > p.text-[10px]`
Lire → `div.grid > a.group > div.p-3 > p.mt-1.5`
19 juin 2026 `div.grid > a.group > div.p-3 > p.text-[10px]`
Lire → `div.grid > a.group > div.p-3 > p.mt-1.5`
22 mai 2026 `div.grid > a.group > div.p-3 > p.text-[10px]`
Lire → `div.grid > a.group > div.p-3 > p.mt-1.5`
VU DANS LA PRESSE `div.press-scroller > a.snap-center > div.flex-1 > p.text-[11px]`
VU DANS LA PRESSE `div.press-scroller > a.snap-center > div.flex-1 > p.text-[11px]`
VU DANS LA PRESSE `div.press-scroller > a.snap-center > div.flex-1 > p.text-[11px]`
VU DANS LA PRESSE `div.press-scroller > a.snap-center > div.flex-1 > p.text-[11px]`
VU DANS LA PRESSE `div.press-scroller > a.snap-center > div.flex-1 > p.text-[11px]`
CGU `footer.bg-white > div.container > nav.mt-2 > a.hover:text-slate-600`
CGV `footer.bg-white > div.container > nav.mt-2 > a.hover:text-slate-600`
Confidentialité `footer.bg-white > div.container > nav.mt-2 > a.hover:text-slate-600`
Mentions légales `footer.bg-white > div.container > nav.mt-2 > a.hover:text-slate-600`
Gérer les cookies `footer.bg-white > div.container > nav.mt-2 > button.hover:text-slate-600`
© 2026 Gively `div.min-h-screen > footer.bg-white > div.container > p.mt-2`
Accueil `nav.bottom-nav > div.flex > a.bottom-nav-item > span`
Politique de confidentialité `div.max-w-4xl > div.flex-1 > p.text-slate-500 > a.text-[#1DA1F2]`
Accepter `div.fixed > div.max-w-4xl > div.flex > button.px-4`

These are opportunities to improve the legibility of your content.

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
Voir la mention CRESS Occitanie `div.container > div.max-w-3xl > div.flex > button.h-1.5`
Voir la mention La Tribune `div.container > div.max-w-3xl > div.flex > button.h-1.5`
Voir la mention TOULÉCO `div.container > div.max-w-3xl > div.flex > button.h-1.5`
Voir la mention PressReader `div.container > div.max-w-3xl > div.flex > button.h-1.5`
Voir la mention Melles750 `div.container > div.max-w-3xl > div.flex > button.h-1.5`
Voir l'espace presse `div.container > div.max-w-3xl > div.text-center > a.text-[11px]`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Action Femmes Grand Sud TOULOUSE `div.min-h-screen > div.py-8 > div.flex > a.shrink-0`
Adie Toulouse `div.min-h-screen > div.py-8 > div.flex > a.shrink-0`
ARCEA Toulouse `div.min-h-screen > div.py-8 > div.flex > a.shrink-0`
Chats Libres Citoyens de Saint-Priest Saint-Priest `div.min-h-screen > div.py-8 > div.flex > a.shrink-0`
Jeunesse solidaire pour le volontariat et le développement France-Togo Nantes `div.min-h-screen > div.py-8 > div.flex > a.shrink-0`
Maison de la Culture Tunisienne Toulouse `div.min-h-screen > div.py-8 > div.flex > a.shrink-0`
SINGA Toulouse Toulouse `div.min-h-screen > div.py-8 > div.flex > a.shrink-0`
Action Femmes Grand Sud TOULOUSE `div.min-h-screen > div.py-8 > div.flex > a.shrink-0`
Adie Toulouse `div.min-h-screen > div.py-8 > div.flex > a.shrink-0`
ARCEA Toulouse `div.min-h-screen > div.py-8 > div.flex > a.shrink-0`
Chats Libres Citoyens de Saint-Priest Saint-Priest `div.min-h-screen > div.py-8 > div.flex > a.shrink-0`
Jeunesse solidaire pour le volontariat et le développement France-Togo Nantes `div.min-h-screen > div.py-8 > div.flex > a.shrink-0`
Maison de la Culture Tunisienne Toulouse `div.min-h-screen > div.py-8 > div.flex > a.shrink-0`
SINGA Toulouse Toulouse `div.min-h-screen > div.py-8 > div.flex > a.shrink-0`

○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

●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

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

●Links have a discernible name

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

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Identical links have the same purpose.

○`[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 the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

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

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

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