Skip to content
https://www.madcoinvlog.de

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
8
REVIEW
8
PASS
8
INFO
0
Checks
24
8 PASS 8 REVIEW 8 FIX
D
Landmark Structure
Action
4 landmarks
FIX
4 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
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 MAIN (missing!) ASIDE CONTENTINFO footer

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

F
Alt Text Quality
Action
16 of 33 images have issues
FIX
16 of 33 images have issues
Critical::
16 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
12 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
9 decorative image(s) correctly marked
Info::
8 image(s) with good alt text
33 images 8 good alt text 9 decorative 16 missing
IssueCount
missing16 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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
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
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
43 headings, 2 skip(s)
REVIEW
43 headings, 2 skip(s)
Warning::
Multiple H1 headings (5 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 Montag, 27. April 2026
  • H3 BlockDAG X1 und BDAG: Vom großen Krypto-Versprechen zum massiven Betrugsverdacht?
  • H2 Freitag, 27. März 2026
  • H3 BlockDAG (BDAG) steigt plötzlich – was steckt dahinter?
  • H1 Stand: 27. März 2026 15.50h | Redaktion: MadCoinVlog | Christian Schennen - madtrax
  • H3 🚀 Nach enormen Abfall, jetzt Rekordanstieg mit knapp 300 % Gewinn skipped
  • H2 Donnerstag, 26. März 2026
  • H3 GoMining Miner Wars: Odyssey Clan sucht aktive Miner für Block-Gewinn
  • H3 🎯 Ziel: Block-Gewinn & Klassenerhalt
  • H2 Mittwoch, 11. März 2026
  • H3 BlockDAG X1 Mining erklärt: Warum dein BDAG Guthaben schwankt und wann Auszahlungen möglich sind
  • H1 Stand: 11. März 2026 | Redaktion: MadCoinVlog | Verifizierungsteam | Christian Schennen duplicate H1
  • H2 Dienstag, 10. März 2026
  • H3 Ethereum im Fokus: Warum ETH aktuell stärker gefragt ist als viele andere Kryptowährungen
  • H1 Stand: 10. März 2026 | Redaktion: MadCoinVlog | Christian Schennen duplicate H1
  • H2 Montag, 9. März 2026
  • H3 Bitcoin heute: Warum der BTC-Kurs trotz Börsenstress stabil bleibt
  • H2 Donnerstag, 26. Februar 2026
  • H3 1000TH Bitcoin Miner geschenkt, beim Kauf dieser Mega Uhr
  • H2 Montag, 26. Januar 2026
  • H3 Kapitalflucht und steigende Zinsen: Warum der Bitcoin-Markt aktuell schwächelt
  • H3 Viele Coins verlieren an Wert: Was jetzt wirklich dahintersteckt – und wie du richtig reagierst
  • H1 (empty)
  • H2 Sonntag, 25. Januar 2026
  • H3 GoMining mit 5% Cashback Bitcoins minen - den Rest Deines Lebens!
  • H3 Warum Bitcoins kaufen, wenn man sie auch so bekommen kann?
  • H2 Freitag, 23. Januar 2026
  • H3 Viele Coins verlieren an Wert
  • H1 Stand: 27. März 2026 15.50h | Redaktion: MadCoinVlog | Christian Schennen - madtrax duplicate H1
  • H3 Viele Coins verlieren an Wert: Was jetzt wirklich dahintersteckt – und wie du richtig reagierst skipped
  • H2 Empfohlene Beiträge
  • H3 BlockDAG X1 und BDAG: Vom großen Krypto-Versprechen zum massiven Betrugsverdacht?
  • H2 Beliebteste Beiträge
  • H2 Serverstandort Deutschland - MadCoinVlog.de hostet by All-Inkl
  • H2 MadCoinVlog durchsuchen
  • H2 Menü
  • H2 Labels
  • H2 Abonnieren von MadCoinVlog
  • H2 Blog-Archiv
  • H2 Follower
  • H2 Übersetzer
  • H2 Gesamtzahl der Seitenaufrufe
  • H2 Wikipedia

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

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

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

C
Form Accessibility
Action
9 of 10 controls have issues
REVIEW
9 of 10 controls have issues
Critical::
9 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="q">; <input type="submit">; <input type="text" id="Wikipedia1_wikipedia-search-input">; <input type="submit">; <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">
Info::
1 control(s) properly labeled
10 controls
1 labeled
0 placeholder only
9 unlabeled
ControlTypeLabelMethod
selectselectWidget de tradução de idiomasaria-label
inputsubmit(none)none
qtext(none)none
#Wikipedia1_wikipedia-search-inputtext(none)none
inputsubmit(none)none
#goog-gt-votingInputSrcLangtext(none)none
#goog-gt-votingInputTrgLangtext(none)none
#goog-gt-votingInputSrcTexttext(none)none
#goog-gt-votingInputTrgTexttext(none)none
#goog-gt-votingInputVotetext(none)none

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

<input type="text" name="q">; <input type="submit">; <input type="text" id="Wikipedia1_wikipedia-search-input">; <input type="submit">; <input type="text" name="sl" id="goog-gt-votingInputSrcLang">; <input type="text" name="tl" id="goog-gt-votingInputTrgLang">; <input type="text" name="query" id="goog-gt-votingInputSrcText">; <input type="text" name="gtrans" id="goog-gt-votingInputTrgText">; <input type="text" name="vote" id="goog-gt-votingInputVote">

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

C
Iframe Accessibility
Action
4/9 iframe(s) missing title; 0 placeholder(s)
REVIEW
4/9 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="#")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://www.blogger.com/followers/frame/1243776478934316194?colors=Cgt0cmFuc3Bh…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="https://googleads.g.doubleclick.net/pagead/html/r20260805/r20190131/zrt_lookup.…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
C
Tap Target Adequacy
Action
6 tap target(s) too small or too close together
REVIEW
6 tap target(s) too small or too close together
Warning::
6 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
Mobile-Readable Font Sizes
99% of visible text renders at >= 12 CSS px (2 below threshold)
REVIEW
99% of visible text renders at >= 12 CSS px (2 below threshold)
Info::
2 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.0px ("MadCoinVlog.de | App: BlockDAG X1 | Mark..."); <span> 10.0px ("Stand: 26. März 2026 | Redaktion: MadCoi...").
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title MadCoinVlog – Bitcoin & Kryptowährungen verständlich erklärt ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA 1 pass AA only
h2 Empfohlene Beiträge
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Beliebteste Beiträge
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Serverstandort Deutschland - MadCoinVlog…
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 MadCoinVlog durchsuchen
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Menü
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Labels
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Abonnieren von MadCoinVlog
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Blog-Archiv
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Follower
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Übersetzer
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Gesamtzahl der Seitenaufrufe
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Wikipedia
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
24px · bottom of viewport
h3 🎯 Ziel: Block-Gewinn & Klassenerhalt
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Viele Coins verlieren an Wert: Was jetzt…
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Warum Bitcoins kaufen, wenn man sie auch…
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Viele Coins verlieren an Wert: Was jetzt…
1.14:1
#000000
on
#141414
needs 3.0:1 (large text)
19px · bottom of viewport
a BlockDAG X1 und BDAG: Vom großen Krypto…
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Empfohlene Beiträge1.14:13.0:1
#000000
#141414
Fail
h2 Beliebteste Beiträg…1.14:13.0:1
#000000
#141414
Fail
h2 Serverstandort Deuts…1.14:13.0:1
#000000
#141414
Fail
h2 MadCoinVlog durchsuc…1.14:13.0:1
#000000
#141414
Fail
h2 Menü1.14:13.0:1
#000000
#141414
Fail
h2 Labels1.14:13.0:1
#000000
#141414
Fail
h2 Abonnieren von MadCo…1.14:13.0:1
#000000
#141414
Fail
h2 Blog-Archiv1.14:13.0:1
#000000
#141414
Fail
h2 Follower1.14:13.0:1
#000000
#141414
Fail
h2 Übersetzer1.14:13.0:1
#000000
#141414
Fail
h2 Gesamtzahl der Seite…1.14:13.0:1
#000000
#141414
Fail
h2 Wikipedia1.14:13.0:1
#000000
#141414
Fail
h3 🎯 Ziel: Block-Gew…1.14:13.0:1
#000000
#141414
Fail
h3 Viele Coins verliere…1.14:13.0:1
#000000
#141414
Fail
h3 Warum Bitcoins kaufe…1.14:13.0:1
#000000
#141414
Fail
h3 Viele Coins verliere…1.14:13.0:1
#000000
#141414
Fail
title MadCoinVlog – Bitc…8.23:14.5:1
#000000
#A2A2A3
Pass
span Montag, 27. April 20…7.79:14.5:1
#000000
#9A9EA3
Pass
a BlockDAG X1 und BDAG…3.66:14.5:1
#000000
#666666
Fail
strong MadCoinVlog-Analyse:3.66:13.0:1
#000000
#666666
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.

C
Lighthouse Accessibility Audits
Action
Score 75/100 — 7 failing, 23 passed
REVIEW
75

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
Montag, 27. April 2026 div.blog-posts > div.date-outer > h2.date-header > span
weiterlesen div.post-outer > div.post > div.jump-link > a.jump-link
Freitag, 27. März 2026 div.blog-posts > div.date-outer > h2.date-header > span
weiterlesen div.post-outer > div.post > div.jump-link > a.jump-link
Donnerstag, 26. März 2026 div.blog-posts > div.date-outer > h2.date-header > span
weiterlesen div.post-outer > div.post > div.jump-link > a.jump-link
Mittwoch, 11. März 2026 div.blog-posts > div.date-outer > h2.date-header > span
weiterlesen div.post-outer > div.post > div.jump-link > a.jump-link
Dienstag, 10. März 2026 div.blog-posts > div.date-outer > h2.date-header > span
weiterlesen div.post-outer > div.post > div.jump-link > a.jump-link
Montag, 9. März 2026 div.blog-posts > div.date-outer > h2.date-header > span
weiterlesen div.post-outer > div.post > div.jump-link > a.jump-link
Donnerstag, 26. Februar 2026 div.blog-posts > div.date-outer > h2.date-header > span
weiterlesen div.post-outer > div.post > div.jump-link > a.jump-link
Montag, 26. Januar 2026 div.blog-posts > div.date-outer > h2.date-header > span
weiterlesen div.post-outer > div.post > div.jump-link > a.jump-link
Sonntag, 25. Januar 2026 div.blog-posts > div.date-outer > h2.date-header > span
weiterlesen div.post-outer > div.post > div.jump-link > a.jump-link
Freitag, 23. Januar 2026 div.blog-posts > div.date-outer > h2.date-header > span
weiterlesen div.post-outer > div.post > div.jump-link > a.jump-link
Marktlage: Breiter Rückgang bei Bitcoin, Ethereum und Altcoins. Hinter der Bewe… ul > li > div.item-content > div.item-snippet
Als Bitcoin im Januar 2009 erstmals öffentlich in Erscheinung trat, nahm kaum j… ul > li > div.item-content > div.item-snippet
Neben dem Bitcoin ist eines der berühmtesten Coins der Ethereum Coin (ETH) , do… ul > li > div.item-content > div.item-snippet
Gold div#Label2 > div.widget-content > span.label-size > a
Markenbotschafter div#Label2 > div.widget-content > span.label-size > a
Silber div#Label2 > div.widget-content > span.label-size > a
Visa div#Label2 > div.widget-content > span.label-size > a
April 2026 (1) div#ArchiveList > div#BlogArchive1_ArchiveList > ul.flat > li.archivedate
März 2026 (5) div#ArchiveList > div#BlogArchive1_ArchiveList > ul.flat > li.archivedate
Februar 2026 (1) div#ArchiveList > div#BlogArchive1_ArchiveList > ul.flat > li.archivedate
Januar 2026 (10) div#ArchiveList > div#BlogArchive1_ArchiveList > ul.flat > li.archivedate
Selecione o idioma Abecásio Achinês Acholi Afar Africâner Aimará Albanês Alur A… div#footer-1 > div#Translate1 > div#google_translate_element > div.skiptranslate
Tradutor div#google_translate_element > div.skiptranslate > span > a.VIpgJd-ZVi9od-l4eHX-hSRGPd

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
strong > div.separator > a > img strong > div.separator > a > img
div > div.separator > a > img div > div.separator > a > img
div > div.separator > a > img div > div.separator > a > img
div#SW_READER_LIST_CLOSED_Subscribe2POST > div.top > span.inner > img.subscribe-dropdown-arrow div#SW_READER_LIST_CLOSED_Subscribe2POST > div.top > span.inner > img.subscribe-dropdown-arrow
div#SW_READER_LIST_CLOSED_Subscribe2COMMENT > div.top > span.inner > img.subscribe-dropdown-arrow div#SW_READER_LIST_CLOSED_Subscribe2COMMENT > div.top > span.inner > img.subscribe-dropdown-arrow
div.wikipedia-searchtable > span > a.wikipedia-search-wiki-link > img.wikipedia-icon div.wikipedia-searchtable > span > a.wikipedia-search-wiki-link > img.wikipedia-icon

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wikipedia-searchtable > span.wikipedia-search-bar > span.wikipedia-input-box > input#Wikipedia1_wikipedia-search-input div.wikipedia-searchtable > span.wikipedia-search-bar > span.wikipedia-input-box > input#Wikipedia1_wikipedia-search-input

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div > div#followers-iframe-container > iframe#I0_1786304280847 div > div > div#followers-iframe-container > iframe#I0_1786304280847

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > strong > div.separator > a div > strong > div.separator > a
div > div > div.separator > a div > div > div.separator > a
div#post-body-3004705060273047292 > div > div.separator > a div#post-body-3004705060273047292 > div > div.separator > a
li > div.item-content > div.item-thumbnail > a li > div.item-content > div.item-thumbnail > a
li > div.item-content > div.item-thumbnail > a li > div.item-content > div.item-thumbnail > a
li > div.item-content > div.item-thumbnail > a li > div.item-content > div.item-thumbnail > a
form#Wikipedia1_wikipedia-search-form > div.wikipedia-searchtable > span > a.wikipedia-search-wiki-link

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.

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
🚀 Nach enormen Abfall, jetzt Rekordanstieg mit knapp 300 % Gewinn div.post > div#post-body-4901593896635718050 > article > h3
Viele Coins verlieren an Wert: Was jetzt wirklich dahintersteckt – und wie du r… article > div > div > h3

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
BTC div#Label2 > div.widget-content > span.label-size > a
GoMining div#Label2 > div.widget-content > span.label-size > a
VSN div#Label2 > div.widget-content > span.label-size > a
Vision div#Label2 > div.widget-content > span.label-size > a
Markenbotschafter div#Label2 > div.widget-content > span.label-size > a
Silber div#Label2 > div.widget-content > span.label-size > a

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Input buttons have discernible text.
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●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.
●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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●All heading elements contain content.
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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 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
○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
○Buttons have an accessible name
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Skip links are focusable.
○`<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>`.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Heading Text Quality
All 43 heading(s) have substantive, well-formed text
PASS
All 43 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Form Input Types
2 input(s) using type=text where a specific type would help
PASS
2 input(s) using type=text where a specific type would help
Info::
Input "Wikipedia1_wikipedia-search-input" should use type="search" (currently type="text")
Field name "Wikipedia1_wikipedia-search-input" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "query" should use type="search" (currently type="text")
Field name "query" 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
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "de"
PASS
Lang attribute set to "de"
Info::
<html lang="de"> is set and valid
Got: de
A+
Tabindex Anti-Patterns
2 explicit tabindex attribute(s) checked, no anti-patterns
PASS
2 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback