Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Link & Button Quality

Action

15 issue(s) across 212 links and 19 buttons

FIX

15 issue(s) across 212 links and 19 buttons

8 link(s) with no accessible text

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

Got: https://www.infosecurity-magazine.com/; https://www.infosecurity-magazine.com/; https://www.facebook.com/pages/Infosecurity-Magazine/210560332330063; https://x.com/InfosecurityMag; https://www.linkedin.com/company/infosecurity-magazine/; /; https://rxglobal.com/; https://www.relx.com/

2 link(s) open in new tab without warning

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

Got: https://privacy.reedexpo.com/en-gb.html; https://privacy.reedexpo.com/en-gb/cookie-policy.html

7 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.pullout-open (#103 on page); button.pullout-close (#113 on page); button.form-button (#120 on page); button (#242 on page); button.owl-prev (#334 on page); button.owl-next (#337 on page); button#interstitial-close

202 link(s) with descriptive text

212 links

8 empty

0 generic text

2 new tab

7 empty buttons

Element	Text	Issue	Suggested Fix
https://www.infosecurity-magazine.com/	(empty)	empty	Add link text or aria-label
https://www.infosecurity-magazine.com/	(empty)	empty	Add link text or aria-label
https://www.facebook.com/pages/Infosecur…	(empty)	empty	Add link text or aria-label
https://x.com/InfosecurityMag	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/infosec…	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
https://rxglobal.com/	(empty)	empty	Add link text or aria-label
https://www.relx.com/	(empty)	empty	Add link text or aria-label
https://privacy.reedexpo.com/en-gb.html	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://privacy.reedexpo.com/en-gb/cooki…	Cookie Policy	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

214 links and buttons have descriptive text

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

https://www.infosecurity-magazine.com/; https://www.infosecurity-magazine.com/; https://www.facebook.com/pages/Infosecurity-Magazine/210560332330063; https://x.com/InfosecurityMag; https://www.linkedin.com/company/infosecurity-magazine/; /; https://rxglobal.com/; https://www.relx.com/

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://privacy.reedexpo.com/en-gb.html; https://privacy.reedexpo.com/en-gb/cookie-policy.html

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.pullout-open (#103 on page); button.pullout-close (#113 on page); button.form-button (#120 on page); button (#242 on page); button.owl-prev (#334 on page); button.owl-next (#337 on page); button#interstitial-close

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Web Manifest

Action

Valid manifest

FIX

Valid manifest

Name present: Infosecurity Magazine

192x192 icon present

PWA Install Criteria Not Installable

Name Infosecurity Magazine ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗

Name Infosecurity Magazine Icons 6 icon(s)

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: #ffffff

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

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

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

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

1 <nav> landmark(s) 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

Form Accessibility

Action

3 of 7 controls have issues

REVIEW

3 of 7 controls have issues

3 control(s) without accessible label

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

Got: <input type="submit">; <input type="submit">; <input type="submit">

4 control(s) properly labeled

7 controls

4 labeled

0 placeholder only

3 unlabeled

Control	Type	Label	Method
q	search	Search keywords	aria-label
q	search	Search keywords	aria-label
signup	email	Email address	aria-label
signup	email	Email address	aria-label
input	submit	(none)	none
input	submit	(none)	none
input	submit	(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

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Infosecurity Magazine - Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

Favicon & Branding

21 icon(s) detected

REVIEW

21 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 Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 19 fail WCAG AA

REVIEW

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

1 pass 19 fail WCAG AA 1 pass AA only

h1 Infosecurity Magazine

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Don’t Miss Out!

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Latest News and Features

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Don’t miss out!

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Webinars Coming Up

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 White Papers

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 On-Demand Webinars

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What’s Hot on Infosecurity Magazine?

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Podcasts

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 More news and features

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Events Coming Up

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Next-Gen Infosec

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The magazine

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Advertisers

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Contributors

1.41:1

#000000

#1D244E

needs 3.0:1 (large text)

24px · bottom of viewport

title Infosecurity Magazine - Information Secu…

4.24:1

#000000

#7C61B6

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a Log In

3.02:1

#000000

#6F03F6

needs 4.5:1 (normal text)

16px · top of page (header area)

a News

1.53:1

#000000

#212959

needs 4.5:1 (normal text)

16px · top of page (header area)

a Magazine Features

1.62:1

#000000

#242D61

needs 4.5:1 (normal text)

16px · above the fold

1 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 Infosecurity Magazin…	1.41:1	3.0:1	#000000	#1D244E	Fail
h2 Don’t Miss Out!	1.41:1	3.0:1	#000000	#1D244E	Fail
h2 Latest News and Feat…	1.41:1	3.0:1	#000000	#1D244E	Fail
h2 Don’t miss out!	1.41:1	3.0:1	#000000	#1D244E	Fail
h2 Webinars Coming Up	1.41:1	3.0:1	#000000	#1D244E	Fail
h2 White Papers	1.41:1	3.0:1	#000000	#1D244E	Fail
h2 On-Demand Webinars	1.41:1	3.0:1	#000000	#1D244E	Fail
h2 What’s Hot on Info…	1.41:1	3.0:1	#000000	#1D244E	Fail
h2 Podcasts	1.41:1	3.0:1	#000000	#1D244E	Fail
h2 More news and featur…	1.41:1	3.0:1	#000000	#1D244E	Fail
h2 Events Coming Up	1.41:1	3.0:1	#000000	#1D244E	Fail
h2 Next-Gen Infosec	1.41:1	3.0:1	#000000	#1D244E	Fail
h2 The magazine	1.41:1	3.0:1	#000000	#1D244E	Fail
h2 Advertisers	1.41:1	3.0:1	#000000	#1D244E	Fail
h2 Contributors	1.41:1	3.0:1	#000000	#1D244E	Fail
title Infosecurity Magazin…	4.24:1	4.5:1	#000000	#7C61B6	Fail
a Log In	3.02:1	4.5:1	#000000	#6F03F6	Fail
a Sign Up	6.87:1	4.5:1	#000000	#A781E1	Pass
a News	1.53:1	4.5:1	#000000	#212959	Fail
a Magazine Features	1.62:1	4.5:1	#000000	#242D61	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.

Heading Hierarchy

78 headings

PASS

78 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

1 empty heading(s)

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

H2 Vercel Confirms Cyber Incident After Sophisticated Attacker Exploits Third‑Party Tool
H2 The Gentlemen Ransomware Expands With Rapid Affiliate Growth
H2 Unchecked AI Agents Cause Cybersecurity Incidents at Two Thirds of Firms
H2 Trojanized Android App Fuels New Wave of NFC Fraud
H2 UK Faces a Cyber ‘Perfect Storm’ Driven by Tech Advances and Nation State Threats, NCSC Warns
H2 Former Ransomware Negotiator Pleads Guilty to Working For BlackCat Cyber Gang
H1 Infosecurity Magazine
H2 Don’t Miss Out!
H2 Latest News and Features
H3 MacOS Native Tools Enable Stealthy Enterprise Attacks
H3 NCSC Unveils SilentGlass, a Plug-In Device to Protect Monitors from Cyber-Attacks
H3 UK Commits £90m for Cybersecurity and Pushes for ‘Resilience Pledge’
H3 Surge in Silent Subject Phishing Attacks Targets VIP Users
H3 Former Ransomware Negotiator Pleads Guilty to Working For BlackCat Cyber Gang
H3 Researchers Uncover ProxySmart Software Powering 90+ SIM Farms
H3 UK Faces a Cyber ‘Perfect Storm’ Driven by Tech Advances and Nation State Threats, NCSC Warns
H3 Trojanized Android App Fuels New Wave of NFC Fraud
H3 The Gentlemen Ransomware Expands With Rapid Affiliate Growth
H3 Unchecked AI Agents Cause Cybersecurity Incidents at Two Thirds of Firms
H2 Don’t miss out!
H3 Financial Services Under Pressure: Supply Chain Risk, Regulation and Operational Resilience
H2 Webinars Coming Up
H3 Behind the Curtain of Microsoft 365 Cybersecurity: Lessons from Overlooked Resilience Gaps
H3 Financial Services Under Pressure: Supply Chain Risk, Regulation and Operational Resilience
H2 White Papers
H3 The Customer Identity Buyer’s Guide
H3 How Leading Brands Stop Fraud & Prevent Threats
H3 The Digital Operational Resilience Act (DORA): A Comprehensive Guide to TPRM Compliance
H2 On-Demand Webinars
H2 What’s Hot on Infosecurity Magazine?
H3 Vercel Confirms Cyber Incident After Sophisticated Attacker Exploits Third‑Party Tool
H3 Hackers Leak Sexually Explicit Photos, Messages of WWE Star Paige
H3 ZionSiphon Malware Targets Water Infrastructure Systems
H3 Attackers Exploit DVR Command Injection Flaw to Deploy Mirai-Based Botnet
H3 NCSC Outlines Coordinated Plan to Boost NHS Cyber Resilience
H3 Commercial AI Models Show Rapid Gains in Vulnerability Research
H3 Systemic Flaw in MCP Protocol Could Expose 150 Million Downloads
H3 European Cybersecurity Agency ENISA Seeks Top-Tier Status in CVE Program
H3 AI Companies to Play Bigger Role in CVE Program, Says CISA
H3 AI Security Institute Advocates Security Best Practices After Mythos Test
H3 FIRST CEO Calls for Global CVE Collaboration amid AI Vulnerability Tsunami
H3 Hundreds of MCP Servers at Risk of RCE and Data Leaks
H3 Why Resilience‑Focused Cloud Design Is Your Best Defense Against Modern Attacks
H3 How To Enhance Security Operations with AI-Powered Defenses
H3 How to Harness Advanced Intelligence Capabilities to Strengthen Cyber Defence
H3 How to Recover From a Cyber-Attack: A Step-by-Step Playbook
H3 Securing M365 Data and Identity Systems Against Modern Adversaries
H3 How Trusted Time Strengthens Network Security
H3 AI Security and Governance Virtual Summit
H3 Exclusive Interview with OpenClaw's Security Advisor
H3 CDW's Walt Powell on CISO 3.0 and Translating Cyber Risk into Business Value
H3 AI Companies to Play Bigger Role in CVE Program, Says CISA
H3 When Agentic AI Becomes Your Riskiest Third Party
H3 How Security Leaders Can Safeguard Against Vibe Coding Security Risks
H2 Podcasts
H2 More news and features
H3 Vercel Confirms Cyber Incident After Sophisticated Attacker Exploits Third‑Party Tool
H3 North Korea Blamed for $290m KelpDAO Crypto Heist
H3 ZionSiphon Malware Targets Water Infrastructure Systems
H3 Formbook Malware Campaign Uses Multiple Obfuscation Techniques to Avoid Detection
H3 Attackers Exploit DVR Command Injection Flaw to Deploy Mirai-Based Botnet
H3 NCSC Outlines Coordinated Plan to Boost NHS Cyber Resilience
H3 Crypto Exchange Grinex Blames Western Spies for $13m Theft
H3 OpenClaw Exposes the Real Cybersecurity Risks of Agentic AI
H3 Commercial AI Models Show Rapid Gains in Vulnerability Research
H3 DDoS-For-Hire Services Disrupted by International Police Action in ‘Operation PowerOff’
H2 Events Coming Up
H3 AI Security and Governance Virtual Summit
H3 Infosecurity Europe 2026
H3 Women in Cybersecurity at Infosecurity Europe 2026
H2 Next-Gen Infosec
H3 How to Prevent Data Leakages
H3 Top Cloud Misconceptions that Could Damage Your Organization
H3 Improve Asset Visibility in OT Security With Hybrid AI-Cloud Approaches
H2 The magazine
H2 Advertisers
H2 Contributors
H1 (empty)

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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

A+

Alt Text Quality

All 47 images OK

PASS

All 47 images OK

27 decorative image(s) correctly marked

20 image(s) with good alt text

47 images 20 good alt text 27 decorative

All images have appropriate alt text.

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 29 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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#cphContent_phCarousel > div#owl-carousel > div.owl-nav > button.owl-prev `div#cphContent_phCarousel > div#owl-carousel > div.owl-nav > button.owl-prev`
div#cphContent_phCarousel > div#owl-carousel > div.owl-nav > button.owl-next `div#cphContent_phCarousel > div#owl-carousel > div.owl-nav > button.owl-next`

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

●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

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●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

●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

●Uses ARIA roles only on compatible elements

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

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

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

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

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