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

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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

Theme color only

FIX

Theme color 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: #0a0e1a

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 ModePartial Dark Mode

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

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

Action

4 landmarks

REVIEW

4 landmarks

No <main> landmark found

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

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

Form Accessibility

4 of 4 controls have issues

REVIEW

4 of 4 controls have issues

4 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" name="name">; <input type="email" name="email">; <input type="text" name="subject">; <textarea name="message">

4 controls

0 labeled

4 placeholder only

0 unlabeled

Control	Type	Label	Method
name	text	(Votre nom)	placeholder only
email	email	(Votre email)	placeholder only
subject	text	(Sujet)	placeholder only
message	textarea	(Votre message...)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Mobile Keyboard & Autofill

Action

1/3 eligible field(s) missing autocomplete or inputmode

REVIEW

1/3 eligible field(s) missing autocomplete or inputmode

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" name="email">

Mobile-Readable Font Sizes

Action

77% of visible text renders at >= 12 CSS px (67 below threshold)

REVIEW

77% of visible text renders at >= 12 CSS px (67 below threshold)

67 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: <small> 9.0px ("Software Architect"); <p> 11.5px ("À propos"); <span> 11.5px ("ans exp."); <span> 11.5px ("projets"); <span> 11.5px ("Recherche").

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 Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 John

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Architecte logiciel.

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 NASA Space Apps

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Mes services

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Mes projets

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Articles & Réflexions

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Travaillons ensemble

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Software Architect & M2 Researcher — s…

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Résoudre des défis spatiaux avec le co…

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Architecture Microservices

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Backend Spring Boot & Django

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Frontend React & Vue.js

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Recherche & Analyse Prédictive

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Tests & Qualité

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Conteneurisation & DevOps

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 NJILA

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Bibliothèque Centrale — Université d…

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 TMS SARL

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 BloodLink

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

19px · bottom of viewport

h3 TradeFlow

1.24:1

#000000

#181E1F

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 John	1.24:1	3.0:1	#000000	#181E1F	Fail
h2 Architecte logiciel.	1.24:1	3.0:1	#000000	#181E1F	Fail
h2 NASA Space Apps	1.24:1	3.0:1	#000000	#181E1F	Fail
h2 Mes services	1.24:1	3.0:1	#000000	#181E1F	Fail
h2 Mes projets	1.24:1	3.0:1	#000000	#181E1F	Fail
h2 Articles & Réflexio…	1.24:1	3.0:1	#000000	#181E1F	Fail
h2 Travaillons ensemble	1.24:1	3.0:1	#000000	#181E1F	Fail
h3 Software Architect &…	1.24:1	3.0:1	#000000	#181E1F	Fail
h3 Résoudre des défis…	1.24:1	3.0:1	#000000	#181E1F	Fail
h3 Architecture Microse…	1.24:1	3.0:1	#000000	#181E1F	Fail
h3 Backend Spring Boot …	1.24:1	3.0:1	#000000	#181E1F	Fail
h3 Frontend React & Vue…	1.24:1	3.0:1	#000000	#181E1F	Fail
h3 Recherche & Analyse …	1.24:1	3.0:1	#000000	#181E1F	Fail
h3 Tests & Qualité	1.24:1	3.0:1	#000000	#181E1F	Fail
h3 Conteneurisation & D…	1.24:1	3.0:1	#000000	#181E1F	Fail
h3 NJILA	1.24:1	3.0:1	#000000	#181E1F	Fail
h3 Bibliothèque Centra…	1.24:1	3.0:1	#000000	#181E1F	Fail
h3 TMS SARL	1.24:1	3.0:1	#000000	#181E1F	Fail
h3 BloodLink	1.24:1	3.0:1	#000000	#181E1F	Fail
h3 TradeFlow	1.24:1	3.0:1	#000000	#181E1F	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

36 headings

PASS

36 headings

Single H1 present

H1 JohnNGUEMBU
H2 Architecte logiciel.Chercheur. Pragmatique.
H3 Software Architect & M2 Researcher — systèmes distribués
H4 Backend
H4 Frontend
H4 Architecture & Systèmes
H4 Recherche & Analyse
H4 Tools & Databases
H2 NASA Space AppsChallenge
H3 Résoudre des défis spatiaux avec le code
H2 Mes services
H3 Architecture Microservices
H3 Backend Spring Boot & Django
H3 Frontend React & Vue.js
H3 Recherche & Analyse Prédictive
H3 Tests & Qualité
H3 Conteneurisation & DevOps
H2 Mes projets
H3 NJILA
H3 Bibliothèque Centrale — Université de Yaoundé I
H3 TMS SARL
H3 BloodLink
H3 TradeFlow
H3 Tempo Air Quality
H3 Blog Platform
H3 Keng Engineering
H3 Mamzy Color Kids
H3 TERRABIA
H2 Articles & Réflexions
H3 « Conception d'une approche prédictive d'analyse d'impact des changements dans les architectures microservices évolutives »
H3 Transactions distribuées en microservices : ce que révèle NJILA
H3 Construire BloodLink : une app mobile de don de sang en React Native + Expo
H3 Tempo Air Quality : collecter et visualiser des données environnementales avec Python
H3 48h au NASA Space Apps Challenge — ce que j'ai appris
H2 Travaillons ensemble
H3 Un projet ou une collaboration de recherche ?

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

1 heading(s) are over 120 characters -- likely a misformatted paragraph

Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 123 chars

Got: 1 >120-char heading(s)

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

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

Link & Button Quality

42 links, 22 buttons — all OK

PASS

42 links, 22 buttons — all OK

22 link(s) open in new tab without warning

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

Got: https://github.com/nguembu; https://www.linkedin.com/in/jaures-nguembu-040658335/; https://x.com/_Johnny_watson; https://www.instagram.com/i_am_johnny_watson/; https://github.com/nguembu/njila; https://tmsarl.netlify.app/; https://github.com/nguembu/BloodLink; https://github.com/nguembu/TradeFlow; https://github.com/nguembu/tempo_air_quality; https://github.com/nguembu/blogPlatform (+12 more)

20 link(s) with descriptive text

42 links

0 empty

0 generic text

22 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://github.com/nguembu	GitHub	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/jaures-nguem…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://x.com/_Johnny_watson	X / Twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/i_am_johnny_wa…	Instagram	new tab	Add '(opens in new tab)' to text
https://github.com/nguembu/njila	GitHub →	new tab	Add '(opens in new tab)' to text
https://tmsarl.netlify.app/	Live →	new tab	Add '(opens in new tab)' to text
https://github.com/nguembu/BloodLink	GitHub →	new tab	Add '(opens in new tab)' to text
https://github.com/nguembu/TradeFlow	GitHub →	new tab	Add '(opens in new tab)' to text
https://github.com/nguembu/tempo_air_qua…	GitHub →	new tab	Add '(opens in new tab)' to text
https://github.com/nguembu/blogPlatform	GitHub →	new tab	Add '(opens in new tab)' to text
https://keng-engineering-website.netlify…	Live →	new tab	Add '(opens in new tab)' to text
https://mamzy-color-kids.netlify.app/	Live →	new tab	Add '(opens in new tab)' to text
https://github.com/nguembu/TERRABIA	GitHub →	new tab	Add '(opens in new tab)' to text
https://github.com/nguembu/master-thesis…	Voir le dépôt de recherche �…	new tab	Add '(opens in new tab)' to text
https://github.com/nguembu/NJILA	Voir le dépôt de recherche �…	new tab	Add '(opens in new tab)' to text
https://github.com/nguembu/BloodLink	Voir le projet →	new tab	Add '(opens in new tab)' to text
https://github.com/nguembu/tempo_air_qua…	Voir le projet →	new tab	Add '(opens in new tab)' to text
https://github.com/nguembu	Voir mon GitHub →	new tab	Add '(opens in new tab)' to text
https://github.com/nguembu	GitHub	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/jaures-nguem…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://x.com/_Johnny_watson	X / Twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/i_am_johnny_wa…	Instagram	new tab	Add '(opens in new tab)' to text

42 links and buttons have descriptive text

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

https://github.com/nguembu; https://www.linkedin.com/in/jaures-nguembu-040658335/; https://x.com/_Johnny_watson; https://www.instagram.com/i_am_johnny_watson/; https://github.com/nguembu/njila; https://tmsarl.netlify.app/; https://github.com/nguembu/BloodLink; https://github.com/nguembu/TradeFlow; https://github.com/nguembu/tempo_air_quality; https://github.com/nguembu/blogPlatform (+12 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

A+

Form Input Types

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

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

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

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

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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

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.

Lighthouse Accessibility Audits

Score 91/100 — 3 failing, 24 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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Tous Microservices Web Backend Mobile E-commerce Corporate Bibliothèque `body > section#projects > div.container > div.filter-row`

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.

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
Disponible pour missions & collaborations `section#home > div.hero-inner > div > div.hero-tag`
À PROPOS `body > section#about > div.container > p.sec-label`
CE QUE JE FAIS `body > section#services > div.container > p.sec-label`
PORTFOLIO `body > section#projects > div.container > p.sec-label`
Tous `section#projects > div.container > div.filter-row > button.flt-btn`
PARTAGE DE CONNAISSANCES `body > section#blog > div.container > p.sec-label`
CONTACT `body > section#contact > div.container > p.sec-label`

These are opportunities to improve the legibility of your content.

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
John . dev SOFTWARE ARCHITECT `body > header#siteHeader > div.hdr > a.logo`

○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 have a discernible name

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

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

●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

●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

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

○Links are distinguishable without relying on color.

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

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