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

Form Accessibility

Action

25 of 26 controls have issues

FIX

25 of 26 controls have issues

23 control(s) without accessible label

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

Got: <input type="text" name="1">; <input type="text" name="3">; <input type="text" name="71">; <input type="text" name="72">; <input type="text" name="73">; <input type="email" name="75">; <select name="98">; <select name="34">; <textarea name="69">; <input type="text" name="8"> (+13 more)

2 control(s) rely on placeholder only

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

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

1 control(s) properly labeled

26 controls

1 labeled

2 placeholder only

23 unlabeled

Control	Type	Label	Method
33	checkbox		none
input	text	(____ _______)	placeholder only
input	text	(Suchmaschinenoptimierung)	placeholder only
72	text	(none)	none
73	text	(none)	none
1	text	(none)	none
3	text	(none)	none
75	email	(none)	none
98	select	(none)	none
34	select	(none)	none
69	textarea	(none)	none
8	text	(none)	none
9	select	(none)	none
40	text	(none)	none
41	select	(none)	none
36	text	(none)	none
37	select	(none)	none
42	text	(none)	none
43	select	(none)	none
44	text	(none)	none
45	select	(none)	none
38	text	(none)	none
39	select	(none)	none
55	textarea	(none)	none
71	text	(none)	none
ba-honeypot	checkbox	(none)	none

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

<input type="text" name="1">; <input type="text" name="3">; <input type="text" name="71">; <input type="text" name="72">; <input type="text" name="73">; <input type="email" name="75">; <select name="98">; <select name="34">; <textarea name="69">; <input type="text" name="8"> (+13 more)

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

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

Web Manifest

Action

Valid manifest

FIX

Valid manifest

Name present: App

192x192 icon present

PWA Install Criteria Not Installable

Name App ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗

Name App 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: #000000

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

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)

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

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

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

Heading Hierarchy

26 headings, 2 skip(s)

REVIEW

26 headings, 2 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H3 → H6 (missing H4)

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

H1 Gewaltpräventionskursmit Raik Hennel
H3 Gefahr erkennen skipped
H3 Gefahrvermeidung
H3 Selbsbewußtsein steigern
H3 Was lernen die Kids?
H3 Das richtige Verhalten in den unterschiedlichsten Gefahrensituationen
H3 Schärfung des Bewusstseins für Gewalt. Was ist Gewalt? Unterschiede und Formen von Gewalt.
H3 Förderung der Konfliktlösungsfähigkeit – Kinder entwickeln nach dem Kurs diese Fähigkeit.
H3 Vermittlung von Strategien zur Deeskalation der Gefahrenssituation
H3 Anmeldung zum Kurs
H3 Nächster Kurs
H3 06.April & 13.Juli 2024 in Eggesin
H3 +++NEU+++ Jetzt auch in Tutow
H3 13.April 2024 in Tutow
H3 +++NEU+++ Jetzt auch in Tutow
H3 06.Juli 2024 in Tutow
H3 Kurz zu mir, was biete ich an:
H3 01. Gewaltpräventionskurs
H3 02. Gewaltpräventionskurse vor Ort
H3 01. Personal Training
H3 02. Kampfsporttraining
H3 01. Objektschutz
H3 02. Eventschutz
H3 03. Detektiv
H6 Say Hello skipped
H2 Starten Sie ein Projekt mit mir!

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

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 Fehler: 404 Seite nicht gefunden ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

11 icon(s) detected

REVIEW

11 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

PWA Depth

3 PWA signal(s) surfaced

REVIEW

3 PWA signal(s) surfaced

Manifest is missing `display` -- defaults to browser, no PWA UX

When `display` is `browser` (or unset, which is the spec default), the installed app opens in a regular browser tab -- no install prompt, no standalone window, no app-shell experience. The intended values for a PWA are `standalone` (most common; full-screen, no browser chrome) or `fullscreen` (games / immersive apps). `minimal-ui` is a middle ground (basic browser controls but no address bar).

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

Manifest is missing `theme_color`

Without `theme_color`, the install prompt and Android status bar fall back to a generic tint instead of your brand color. Add a hex color (e.g. `"theme_color": "#0066cc"`); for richer support, mirror it via `<meta name="theme-color" content="#0066cc">` so non-installed browsers also pick it up.

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 Gewaltpräventionskurs

1.00:1

#000000

needs 3.0:1 (large text)

32px · above the fold

h2 Starten Sie ein Projekt mit mir!

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Gefahr erkennen

1.00:1

#000000

needs 3.0:1 (large text)

19px · above the fold

h3 Gefahrvermeidung

1.00:1

#000000

needs 3.0:1 (large text)

19px · above the fold

h3 Selbsbewußtsein steigern

1.00:1

#000000

needs 3.0:1 (large text)

19px · above the fold

h3 Was lernen die Kids?

1.00:1

#000000

needs 3.0:1 (large text)

19px · mid-page

h3 Das richtige Verhalten in den unterschie…

1.00:1

#000000

needs 3.0:1 (large text)

19px · mid-page

h3 Schärfung des Bewusstseins für Gewalt.…

1.00:1

#000000

needs 3.0:1 (large text)

19px · mid-page

h3 Förderung der Konfliktlösungsfähigkei…

1.00:1

#000000

needs 3.0:1 (large text)

19px · mid-page

h3 Vermittlung von Strategien zur Deeskalat…

1.00:1

#000000

needs 3.0:1 (large text)

19px · mid-page

h3 Anmeldung zum Kurs

1.00:1

#000000

needs 3.0:1 (large text)

19px · mid-page

h3 Nächster Kurs

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 06.April & 13.Juli 2024 in Eggesin

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 +++NEU+++ Jetzt auch in Tutow

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 13.April 2024 in Tutow

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 +++NEU+++ Jetzt auch in Tutow

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 06.Juli 2024 in Tutow

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Kurz zu mir, was biete ich an:

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 01. Gewaltpräventionskurs

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 02. Gewaltpräventionskurse vor Ort

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Gewaltpräventionsku…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Starten Sie ein Proj…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Gefahr erkennen	1.00:1	3.0:1	#000000	#000000	Fail
h3 Gefahrvermeidung	1.00:1	3.0:1	#000000	#000000	Fail
h3 Selbsbewußtsein ste…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Was lernen die Kids?	1.00:1	3.0:1	#000000	#000000	Fail
h3 Das richtige Verhalt…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Schärfung des Bewus…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Förderung der Konfl…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Vermittlung von Stra…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Anmeldung zum Kurs	1.00:1	3.0:1	#000000	#000000	Fail
h3 Nächster Kurs	1.00:1	3.0:1	#000000	#000000	Fail
h3 06.April & 13.Juli 2…	1.00:1	3.0:1	#000000	#000000	Fail
h3 +++NEU+++ Jetzt auch…	1.00:1	3.0:1	#000000	#000000	Fail
h3 13.April 2024 in Tut…	1.00:1	3.0:1	#000000	#000000	Fail
h3 +++NEU+++ Jetzt auch…	1.00:1	3.0:1	#000000	#000000	Fail
h3 06.Juli 2024 in Tuto…	1.00:1	3.0:1	#000000	#000000	Fail
h3 Kurz zu mir, was bie…	1.00:1	3.0:1	#000000	#000000	Fail
h3 01. Gewaltpräventio…	1.00:1	3.0:1	#000000	#000000	Fail
h3 02. Gewaltpräventio…	1.00:1	3.0:1	#000000	#000000	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 Text Quality

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

PASS

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

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

Alt Text Quality

3 of 7 images have issues

PASS

3 of 7 images have issues

3 image(s) with generic alt text

4 image(s) with good alt text

7 images 4 good alt text 3 generic

Issue	Count
generic	3 image(s)

Link & Button Quality

36 links, 0 buttons — all OK

PASS

36 links, 0 buttons — all OK

5 link(s) open in new tab without warning

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

Got: https://www.facebook.com/gesafehennel; https://www.instagram.com/raik_hennel/; https://gesafe-hennel.de; https://www.facebook.com/gesafehennel; https://www.instagram.com/raik_hennel/

31 link(s) with descriptive text

36 links

0 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/gesafehennel	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/raik_hennel/	Instagram	new tab	Add '(opens in new tab)' to text
https://gesafe-hennel.de	Datenschutzerklärung	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/gesafehennel	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/raik_hennel/	Instagram	new tab	Add '(opens in new tab)' to text

31 links and buttons have descriptive text

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

https://www.facebook.com/gesafehennel; https://www.instagram.com/raik_hennel/; https://gesafe-hennel.de; https://www.facebook.com/gesafehennel; https://www.instagram.com/raik_hennel/

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

26 form control(s) checked, no type mismatches

PASS

26 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

PASS

Lang attribute set to "de-de"

<html lang="de-de"> is set and valid

Got: de-de

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

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+

Mobile-Readable Font Sizes

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

PASS

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

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

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 95/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
01 `div.sppb-addon-content > div.sppb-blocknumber > div.pull-left > span.sppb-blocknumber-number`
02 `div.sppb-addon-content > div.sppb-blocknumber > div.pull-left > span.sppb-blocknumber-number`
03 `div.sppb-addon-content > div.sppb-blocknumber > div.pull-left > span.sppb-blocknumber-number`
04 `div.sppb-addon-content > div.sppb-blocknumber > div.pull-left > span.sppb-blocknumber-number`
+++NEU+++ Jetzt auch in Tutow `div#sppb-addon-wrapper-obI76FKzADSVEU7SMgv-- > div#sppb-addon-obI76FKzADSVEU7SMgv-- > div.sppb-addon > h3.sppb-addon-title`
+++NEU+++ Jetzt auch in Tutow `div#sppb-addon-wrapper-mgJYQYvx4GGVqW1gC4DB- > div#sppb-addon-mgJYQYvx4GGVqW1gC4DB- > div.sppb-addon > h3.sppb-addon-title`
Wichtig! `div#sppb-addon-wrapper-gIbQKBtMycfm_6GcMgY-z > div#sppb-addon-gIbQKBtMycfm_6GcMgY-z > div.sppb-addon > div.sppb-addon-title`
Social Media `div#sppb-addon-wrapper-1675322460978 > div#sppb-addon-1675322460978 > div.sppb-addon > div.sppb-addon-title`
Say Hello `div#sppb-addon-wrapper-bwZPyyBgUW-c5xtkOJVz3 > div#sppb-addon-bwZPyyBgUW-c5xtkOJVz3 > div.sppb-addon > h6.sppb-addon-title`
© 2026 GESAFE - RAIK HENNEL Designed By DTB `div.row > div#sp-footer2 > div.sp-column > span.sp-copyright`

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
Gefahr erkennen `div#sppb-addon-wrapper-1675675268913 > div#sppb-addon-1675675268913 > div.sppb-addon > h3.sppb-addon-title`
Say Hello `div#sppb-addon-wrapper-bwZPyyBgUW-c5xtkOJVz3 > div#sppb-addon-bwZPyyBgUW-c5xtkOJVz3 > div.sppb-addon > h6.sppb-addon-title`

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
facebook Facebook `div.sppb-addon > ul.sppb-icons-group-list > li#icon-16753224609781 > a`
Instagram Instagram `div.sppb-addon > ul.sppb-icons-group-list > li#icon-16753224609782 > a`

○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

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

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○Form elements have associated labels

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

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