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

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-u351st

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Favicon & Branding

Action

3 icon(s) detected

FIX

3 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

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://biermetstijl.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://biermetstijl.com/manifest.json

Manifest contains invalid JSON.

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: #24103a

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

3 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 3 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

Landmark Structure

11 landmarks

REVIEW

11 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

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

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

Heading Hierarchy

21 headings, 2 skip(s)

REVIEW

21 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Beveiligingsupdate MijnAccount, Mijndomein, Webhosting & Webmail; PHP-kwetsbaarheden ( CVE-2026-109618 / CVE-2026-109619 )
H2 Jouw veiligheid gaat voor
H2 Huidige Status
H4 Details van de verstoring skipped
H4 Updates en storingslog
H2 Details van de verstoring
H2 Preventieve uitschakeling ( besloten om 13:35 )
H2 Updates en statuslog
H3 Volgende statusupdate
H3 Statuslog
H2 Kom je er niet uit?
H3 Heeft dit je probleem opgelost?
H4 Op deze pagina
H3 Meer over dit onderwerp
H2 Misschien helpt dit je ook
H3 Gerelateerde artikelen
H2 Verwante artikelen
H2 Wat wordt jouw domein?
H4 Helpdesk skipped
H4 Contact
H4 Meer

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Form Accessibility

Action

4 of 10 controls have issues

REVIEW

4 of 10 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">

6 control(s) properly labeled

10 controls

6 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
#footer-domain-query	text	Kies je domeinnaam	for/id
#CybotCookiebotDialogBodyLevelButtonStatisticsInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonMarketingInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonNecessaryInline	checkbox	(none)	none
#CybotCookiebotDialogBodyLevelButtonPreferencesInline	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

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 4 fail WCAG AA

REVIEW

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

16 pass 4 fail WCAG AA

title Beveiligingsupdate MijnAccount, Mijndome…

2.30:1

#000000

#8B1E16

needs 4.5:1 (normal text)

16px · top of page (header area)

a Consent

2.30:1

#000000

#8B1E16

needs 4.5:1 (normal text)

16px · top of page (header area)

a Details

2.30:1

#000000

#8B1E16

needs 4.5:1 (normal text)

16px · top of page (header area)

a [#IABV2SETTINGS#]

2.30:1

#000000

#8B1E16

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Beveiligingsupdate M…	20.39:1	3.0:1	#000000	#FBFCF9	Pass
h2 Kom je er niet uit?	20.39:1	3.0:1	#000000	#FBFCF9	Pass
h2 Misschien helpt dit …	20.39:1	3.0:1	#000000	#FBFCF9	Pass
h2 Verwante artikelen	20.39:1	3.0:1	#000000	#FBFCF9	Pass
h2 Wat wordt jouw domei…	20.39:1	3.0:1	#000000	#FBFCF9	Pass
h3 Heeft dit je problee…	20.39:1	3.0:1	#000000	#FBFCF9	Pass
h3 Meer over dit onderw…	20.39:1	3.0:1	#000000	#FBFCF9	Pass
h3 Gerelateerde artikel…	20.39:1	3.0:1	#000000	#FBFCF9	Pass
title Beveiligingsupdate M…	2.30:1	4.5:1	#000000	#8B1E16	Fail
a Consent	2.30:1	4.5:1	#000000	#8B1E16	Fail
a Details	2.30:1	4.5:1	#000000	#8B1E16	Fail
a [#IABV2SETTINGS#]	2.30:1	4.5:1	#000000	#8B1E16	Fail
a About	20.22:1	4.5:1	#000000	#FAFBF8	Pass
div This website uses co…	19.36:1	4.5:1	#000000	#F5F6F3	Pass
div We use cookies to pe…	17.55:1	4.5:1	#000000	#EAEBE8	Pass
div [#GPC_BANNER_ICON#]	15.99:1	4.5:1	#000000	#E0E1DE	Pass
div [#GPC_TOAST_TEXT#]	15.25:1	4.5:1	#000000	#DBDCD9	Pass
span Consent Selection	15.25:1	4.5:1	#000000	#DBDCD9	Pass
strong Necessary	15.25:1	3.0:1	#000000	#DBDCD9	Pass
strong Preferences	15.25:1	3.0:1	#000000	#DBDCD9	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.

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 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: - H1: 122 chars

Got: 1 >120-char heading(s)

A+

Alt Text Quality

1 of 29 images have issues

PASS

1 of 29 images have issues

1 image(s) with generic alt text

1 decorative image(s) correctly marked

27 image(s) with good alt text

29 images 27 good alt text 1 decorative 1 generic

Issue	Count
generic	1 image(s)

Link & Button Quality

115 links, 16 buttons — all OK

PASS

115 links, 16 buttons — all OK

30 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=…; https://www.cloudflare.com/privacypolicy/; https://business.safety.google/privacy/; https://legal.hubspot.com/privacy-policy; https://www.linkedin.com/legal/privacy-policy; https://admin.typeform.com/to/dwk6gt/; https://www.linkedin.com/legal/privacy-policy; https://admin.typeform.com/to/dwk6gt/; https://www.cloudflare.com/privacypolicy/; https://business.safety.google/privacy/ (+20 more)

85 link(s) with descriptive text

115 links

0 empty

0 generic text

30 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
https://www.cloudflare.com/privacypolicy…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://legal.hubspot.com/privacy-policy	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/legal/privacy-p…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://admin.typeform.com/to/dwk6gt/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/legal/privacy-p…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://admin.typeform.com/to/dwk6gt/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.cloudflare.com/privacypolicy…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://legal.hubspot.com/privacy-policy	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://privacy.microsoft.com/en-us/priv…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/legal/privacy-pol…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://admin.typeform.com/to/dwk6gt/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/policy.php/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://site.adform.com/privacy-center/p…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://elfsight.com/privacy-policy/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://legal.hubspot.com/privacy-policy	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://privacy.microsoft.com/en-US/priv…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://openai.com/policies/privacy-poli…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.redditinc.com/policies/priva…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.rudderstack.com/cookie-polic…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/legal/privacy-pol…	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://admin.typeform.com/to/dwk6gt/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://business.safety.google/privacy/	Learn more about this provider…	new tab	Add '(opens in new tab)' to text
https://www.mijndomein.zendesk.com	www.mijndomein.zendesk.com - o…	new tab	Add '(opens in new tab)' to text
https://mijnaccount.mijndomein.nl	mijnaccount.mijndomein.nl - op…	new tab	Add '(opens in new tab)' to text
https://www.mijndomein.nl	www.mijndomein.nl - opens in a…	new tab	Add '(opens in new tab)' to text
https://www.cookiebot.com	Cookiebot	new tab	Add '(opens in new tab)' to text
https://www.mijndomein.nl/producten/webh…	Bekijk de Mijndomein actie	img no alt	Add alt attribute to the image

101 links and buttons have descriptive text

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

https://www.cookiebot.com/en/what-is-behind-powered-by-cookiebot/?utm_source=…; https://www.cloudflare.com/privacypolicy/; https://business.safety.google/privacy/; https://legal.hubspot.com/privacy-policy; https://www.linkedin.com/legal/privacy-policy; https://admin.typeform.com/to/dwk6gt/; https://www.linkedin.com/legal/privacy-policy; https://admin.typeform.com/to/dwk6gt/; https://www.cloudflare.com/privacypolicy/; https://business.safety.google/privacy/ (+20 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

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "domeinnaam" should use type="search" (currently type="text")

Field name "domeinnaam" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.

A+

Form Input Quality

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

PASS

10 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 "nl"

PASS

Lang attribute set to "nl"

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

Got: nl

A+

Iframe Accessibility

All 3 iframe(s) have descriptive titles

PASS

All 3 iframe(s) have descriptive titles

All 3 iframe(s) have title attributes

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

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

PASS

All 83 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

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.

A+

Lighthouse Accessibility Audits

Score 96/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
Bijgewerkt 21 oktober 2026 `div.container > article.article > div.article-meta-row > span`
21 oktober 2026 `article.article > div.article-meta-row > span > time`
Gepubliceerd 21 oktober 2026 `div.container > article.article > div.article-meta-row > span`
21 oktober 2026 `article.article > div.article-meta-row > span > time`
± 3 min leestijd `div.container > article.article > div.article-meta-row > span`
© Mijndomein `footer.footer > div.container > div.footer-bottom > span`

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Details van de verstoring `div > ul > li.wysiwyg-list-bold > h4#h_01M5F1GKVWQ45KY06HTBA5Y3GM`
Helpdesk `div.container > div.footer-grid > div > h4`

These are opportunities to improve keyboard navigation in your application.

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
Ja `article.article > section.article-votes > div.article-vote-controls > button.article-vote-up`
Nee `article.article > section.article-votes > div.article-vote-controls > button.article-vote-down`

○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

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

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

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