Skip to content
https://wdr.de

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
F
Heading Hierarchy
Action
67 headings, 10 skip(s)
FIX
67 headings, 10 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 WDR - Nachrichten und Geschichten aus NRW
  • H2 Premium Teaser
  • H4 Gericht erlaubt Demos Castortransport von Jülich nach Ahaus läuft skipped
  • H4 Korruptionsverdacht Razzia bei Telekom-Tochter in Bonn
  • H4 Tödliches Gas im Hotel So gefährlich ist Aluminiumphosphid
  • H4 Unfall mit E-Scooter Armin Laschet (CDU) bricht sich die Schulter
  • H4 Frühjahrsputz an NRW-Bahnhöfen Bahnkunden klagen über Urin und Müll
  • H4 NRW ändert Verordnung Abschleppkosten dürfen wieder erhoben werden
  • H2 Banner Teaser
  • H4 Mehr Regionales, neues Design Unser neues Angebot für Web und App skipped
  • H2 Das Neueste für NRW
  • H4 Bau für Hospiz- und Palliativzentrum beginnt Menschen können in Paderborn dauerhaft oder kurzzeitig im Hospiz leben skipped
  • H4 Streit um Krispy Kebab Bielefelder Döner-Unternehmen wehrt sich gegen KFC
  • H4 Sorge vor Kerosin-Mangel Werden Sommerferien-Flüge teurer?
  • H4 Milliarden ohne Zugriff Mehrheit für Spenden von Geld auf vergessenen Konten
  • H4 Casting von Regisseur aus Enger Tahsims "Mama bitte lern Deutsch!" als Film
  • H4 Prozessstart in Paderborn Mordanschlag mit Giftspritze
  • H4 Austausch über Brandverletzungen Aus dem Ukraine-Krieg in den Dortmunder OP
  • H4 Klares Ergebnis AfD-Bezirksbürgermeister Sontowski abgewählt
  • H2 Wetter in NRW
  • H2 Verkehrslage in NRW
  • H2 Die größten NRW-Städte auf einen Blick
  • H4 Köln skipped
  • H4 Düsseldorf
  • H4 Dortmund
  • H4 Essen
  • H4 Duisburg
  • H4 Bochum
  • H4 Wuppertal
  • H4 Bielefeld
  • H4 Bonn
  • H4 Münster
  • H2 Meistgeklickt
  • H3 Teaser
  • H3 Teaser
  • H2 Politik in NRW
  • H4 Kosten für Rettungsdienst Wüst wirft Krankenkassen Erpressung vor skipped
  • H4 Sparpläne im Sozialbereich Kritik an möglichen Kürzungen bei Kinder- und Jugendhilfe
  • H4 Facebook-Hetze in Siegen Drohungen gegen Ex-Bürgermeister Mues
  • H2 Wirtschaft
  • H4 Hoffnung auf Halbmast Wuppertaler Traditionsfirma Fahnen Herold insolvent skipped
  • H4 "Alles wird teurer" Was sagen Menschen in Duisburg und am Niederrhein?
  • H4 Digitales Dating Dortmund bietet Netzwerk für Schüler und Betriebe
  • H2 Sport
  • H4 Vor dem Pokal-Halbfinale gegen Bayern Bayer Leverkusen hofft auf die "magische Nacht" skipped
  • H4 Vor Marathon in Düsseldorf Ex-Profi Sonja Oberem - "Laufen hat sich zum Lifestyle entwickelt"
  • H4 Aus im Halbfinale Kölner Haie scheitern erneut an Berlin
  • H2 Freizeit
  • H4 Schäden in Millionenhöhe Velbert will Schloss Hardenberg wieder aufbauen skipped
  • H4 Sorge vor Flugausfällen Urlauber im Kreis Heinsberg planen um
  • H4 Neuzugang im Duisburger Zoo Warum Koala Kiri jetzt nach Duisburg zieht
  • H2 Kultur
  • H4 Kinopremiere in Essen "Vier von Hier" in der Lichtburg skipped
  • H4 Festival droht das Aus 15.000 Unterschriften für "Hai in den Mai"
  • H4 Geheim-Shows und Radtour So spektakulär waren Prince’ Köln-Konzerte
  • H2 NRW-Regionen im Überblick
  • H3 Mit einem Klick in deine Region
  • H2 NRW in Bildern
  • H2 Weitere WDR-Angebote
  • H4 Lach- und Sachgeschichten skipped
  • H4 Wissenschaft statt Bauchgefühl
  • H4 Zusammen sind wir der Westen
  • H4 Wir sind Heimat
  • H2 WDR auf anderen Plattformen:
  • H3 Der WDR
  • H3 Service
  • H2 Globale Links

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
4 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 4 <nav> element(s)
Back to Top
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.
B
Form Accessibility
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Warning::
3 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="search" name="q">; <input type="search" name="q">; <input type="text" name="_query" id="_query">
3 controls
0 labeled
3 placeholder only
0 unlabeled
ControlTypeLabelMethod
qsearch(im WDR suchen)placeholder only
qsearch(im WDR suchen)placeholder only
#_querytext(PLZ oder Ort eingeben)placeholder only

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

<input type="search" name="q">; <input type="search" name="q">; <input type="text" name="_query" id="_query">

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

C
404 Error Page
Action
HTTP 410, custom page
REVIEW
HTTP 410, custom page
Warning::
Unexpected status code: HTTP 410
Expected HTTP 404 but received 410. This may confuse search engine crawlers.
Got: HTTP 410
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 410 ✗Page Title Seite nicht gefunden, Fehler HTTP 404 - Fehlerseite ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Warning::
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
BANNER header NAV "Navigation" MAIN ASIDE "Mobile Navigation" CONTENTINFO footer

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

A
Alt Text Quality
All 88 images OK
PASS
All 88 images OK
Info::
3 image(s) with alt text over 125 characters
Info::
85 image(s) with good alt text
88 images 85 good alt text
IssueCount
too long3 image(s)
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /assets-v5.174.4/css/merged_print.css
Print Stylesheet ✓ Print Optimized
Print stylesheet /assets-v5.174.4/css/merged_print.css ✓Inline @media print Not detected ✗
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 WDR - Nachrichten un…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Premium Teaser21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Banner Teaser21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Das Neueste für NRW21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Die größten NRW-St…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Meistgeklickt21.00:13.0:1
#000000
#FFFFFF
Pass
h2 NRW-Regionen im Übe…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 NRW in Bildern21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Weitere WDR-Angebote21.00:13.0:1
#000000
#FFFFFF
Pass
h2 WDR auf anderen Plat…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Globale Links21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Teaser21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Teaser21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Mit einem Klick in d…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Der WDR21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Service21.00:13.0:1
#000000
#FFFFFF
Pass
title WDR - Nachrichten un…21.00:14.5:1
#000000
#FFFFFF
Pass
a zum Inhalt21.00:14.5:1
#000000
#FFFFFF
Pass
a zur Navigation21.00:14.5:1
#000000
#FFFFFF
Pass
a zur Suche21.00:14.5:1
#000000
#FFFFFF
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.

A
Lighthouse Accessibility Audits
Score 90/100 — 3 failing, 25 passed
PASS
90

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
Der WDR div.section > div.content > nav.navGroups > div.navGroup
Service div.section > div.content > nav.navGroups > div.navGroup

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.

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
Gericht erlaubt Demos Castortransport von Jülich nach Ahaus am Abend div.teaser > div.textCon > a.teaserlink > h4.headline
Unser neues Angebot für Web und App div.teaser > a.teaserlink > div.textCon > h4.headline
Bau für Hospiz- und Palliativzentrum beginnt Menschen können in Paderborn dauer… div.teaser > div.textCon > a.teaserlink > h4.headline
Köln div.teaser > a.teaserlink > div.textCon > h4.headline
Kosten für Rettungsdienst Wüst wirft Krankenkassen Erpressung vor div.teaser > div.textCon > a.teaserlink > h4.headline
Hoffnung auf Halbmast Wuppertaler Traditionsfirma Fahnen Herold insolvent div.teaser > div.textCon > a.teaserlink > h4.headline
Vor dem Pokal-Halbfinale gegen Bayern Bayer Leverkusen hofft auf die "magische … div.teaser > div.textCon > a.teaserlink > h4.headline
Schäden in Millionenhöhe Velbert will Schloss Hardenberg wieder aufbauen div.teaser > div.textCon > a.teaserlink > h4.headline
Kinopremiere in Essen "Vier von Hier" in der Lichtburg div.teaser > div.textCon > a.teaserlink > h4.headline
Lach- und Sachgeschichten div.teaser > a.teaserlink > div.textCon > h4.headline

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Suchen fieldset > div.inputComponent > div.inputFieldWrapper > button.submit

These items highlight common accessibility best practices.

○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
●Background and foreground colors have a sufficient contrast ratio
●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
●`[lang]` attributes have a valid value
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[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.
○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.
○`<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.

Send Feedback