Skip to content
https://helmi.fm

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
7
REVIEW
5
PASS
12
INFO
0
Checks
24
12 PASS 5 REVIEW 7 FIX
D
Landmark Structure
Action
36 landmarks
FIX
36 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
12 <nav> landmark(s) found
Warning::
12 of 12 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 MAIN (missing!) 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

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

F
Document Language
Action
Missing <html lang> attribute (WCAG 3.1.1)
FIX
Missing <html lang> attribute (WCAG 3.1.1)
Critical::
Missing <html lang> attribute (WCAG 3.1.1)
Without `<html lang="...">`, screen readers default to the user's system language even when reading content in a different one -- words get pronounced wrong (English text read with French phonetics, etc.). Add a BCP-47 language tag to the <html> root element.
D
Iframe Accessibility
Action
15/15 iframe(s) missing title; 0 placeholder(s)
FIX
15/15 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="about:blank")
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.tumblr.com/dashboard/iframe/consent")
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://assets.tumblr.com/assets/html/like_iframe.html?_v=c96f30edcf75919c3976e…")
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://assets.tumblr.com/assets/html/like_iframe.html?_v=c96f30edcf75919c3976e…")
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://assets.tumblr.com/assets/html/like_iframe.html?_v=c96f30edcf75919c3976e…")
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://assets.tumblr.com/assets/html/like_iframe.html?_v=c96f30edcf75919c3976e…")
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://assets.tumblr.com/assets/html/like_iframe.html?_v=c96f30edcf75919c3976e…")
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://assets.tumblr.com/assets/html/like_iframe.html?_v=c96f30edcf75919c3976e…")
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://assets.tumblr.com/assets/html/like_iframe.html?_v=c96f30edcf75919c3976e…")
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://assets.tumblr.com/assets/html/like_iframe.html?_v=c96f30edcf75919c3976e…")
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://assets.tumblr.com/assets/html/like_iframe.html?_v=c96f30edcf75919c3976e…")
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://assets.tumblr.com/assets/html/like_iframe.html?_v=c96f30edcf75919c3976e…")
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://assets.tumblr.com/assets/html/like_iframe.html?_v=c96f30edcf75919c3976e…")
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://assets.tumblr.com/analytics.html?_v=9f5febfd57a8a649c598d888f2d9e062#ht…")
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.tumblr.com/dashboard/iframe/monetization?tumblelog=helmi&src=https%…")
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.
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: #35465d
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.

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::
12 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 12 <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.
D
Lighthouse Accessibility Audits
Action
Score 55/100 — 6 failing, 7 passed
FIX
55

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
Fundstücke aus dem täglichen Streifzug durch das Web header#header > div.blog-title-wrapper > div.title-group > span.description
Instagram div.post-wrapper > section.post > section.inline-meta > a.meta-item
Photo div.post-wrapper > section.post > section.inline-meta > a.meta-item
1 note section.inline-meta > div.date-note-wrapper > span > a.meta-item
Instagram div.post-wrapper > section.post > section.inline-meta > a.meta-item
Photo div.post-wrapper > section.post > section.inline-meta > a.meta-item
Instagram div.post-wrapper > section.post > section.inline-meta > a.meta-item
Photo div.post-wrapper > section.post > section.inline-meta > a.meta-item
Instagram div.post-wrapper > section.post > section.inline-meta > a.meta-item
Photo div.post-wrapper > section.post > section.inline-meta > a.meta-item
Instagram div.post-wrapper > section.post > section.inline-meta > a.meta-item
Photo div.post-wrapper > section.post > section.inline-meta > a.meta-item
Instagram div.post-wrapper > section.post > section.inline-meta > a.meta-item
Photo div.post-wrapper > section.post > section.inline-meta > a.meta-item
Instagram div.post-wrapper > section.post > section.inline-meta > a.meta-item
Photo div.post-wrapper > section.post > section.inline-meta > a.meta-item
Instagram div.post-wrapper > section.post > section.inline-meta > a.meta-item
Photo div.post-wrapper > section.post > section.inline-meta > a.meta-item
Instagram div.post-wrapper > section.post > section.inline-meta > a.meta-item
Photo div.post-wrapper > section.post > section.inline-meta > a.meta-item
Instagram div.post-wrapper > section.post > section.inline-meta > a.meta-item
Photo div.post-wrapper > section.post > section.inline-meta > a.meta-item

These are opportunities to improve the legibility of your content.

Names and labels

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
body.index-page > iframe.tmblr-iframe body.index-page > iframe.tmblr-iframe
div.controls-wrapper > div.control > div#like_button_182186811792 > iframe#like_iframe_182186811792 div.controls-wrapper > div.control > div#like_button_182186811792 > iframe#like_iframe_182186811792
div.controls-wrapper > div.control > div#like_button_182158360967 > iframe#like_iframe_182158360967 div.controls-wrapper > div.control > div#like_button_182158360967 > iframe#like_iframe_182158360967
div.controls-wrapper > div.control > div#like_button_182004925452 > iframe#like_iframe_182004925452 div.controls-wrapper > div.control > div#like_button_182004925452 > iframe#like_iframe_182004925452
div.controls-wrapper > div.control > div#like_button_181557201397 > iframe#like_iframe_181557201397 div.controls-wrapper > div.control > div#like_button_181557201397 > iframe#like_iframe_181557201397
div.controls-wrapper > div.control > div#like_button_181554298642 > iframe#like_iframe_181554298642 div.controls-wrapper > div.control > div#like_button_181554298642 > iframe#like_iframe_181554298642
div.controls-wrapper > div.control > div#like_button_181528950452 > iframe#like_iframe_181528950452 div.controls-wrapper > div.control > div#like_button_181528950452 > iframe#like_iframe_181528950452
div.controls-wrapper > div.control > div#like_button_181463041512 > iframe#like_iframe_181463041512 div.controls-wrapper > div.control > div#like_button_181463041512 > iframe#like_iframe_181463041512
div.controls-wrapper > div.control > div#like_button_181463040597 > iframe#like_iframe_181463040597 div.controls-wrapper > div.control > div#like_button_181463040597 > iframe#like_iframe_181463040597
div.controls-wrapper > div.control > div#like_button_181452959737 > iframe#like_iframe_181452959737 div.controls-wrapper > div.control > div#like_button_181452959737 > iframe#like_iframe_181452959737
div.controls-wrapper > div.control > div#like_button_181397012622 > iframe#like_iframe_181397012622 div.controls-wrapper > div.control > div#like_button_181397012622 > iframe#like_iframe_181397012622
body.index-page > iframe#ga_target body.index-page > iframe#ga_target

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.header-wrapper > header#header > div.header-image-wrapper > a.header-image div.header-wrapper > header#header > div.header-image-wrapper > a.header-image
helmi header#header > div.blog-title-wrapper > figure.avatar-wrapper > a.user-avatar
div.controls-wrapper > div.control > nav.pop > a.share div.controls-wrapper > div.control > nav.pop > a.share
section.post-controls > div.controls-wrapper > div.control > a.reblog_button section.post-controls > div.controls-wrapper > div.control > a.reblog_button
div.controls-wrapper > div.control > nav.pop > a.share div.controls-wrapper > div.control > nav.pop > a.share
section.post-controls > div.controls-wrapper > div.control > a.reblog_button section.post-controls > div.controls-wrapper > div.control > a.reblog_button
div.controls-wrapper > div.control > nav.pop > a.share div.controls-wrapper > div.control > nav.pop > a.share
section.post-controls > div.controls-wrapper > div.control > a.reblog_button section.post-controls > div.controls-wrapper > div.control > a.reblog_button
div.controls-wrapper > div.control > nav.pop > a.share div.controls-wrapper > div.control > nav.pop > a.share
section.post-controls > div.controls-wrapper > div.control > a.reblog_button section.post-controls > div.controls-wrapper > div.control > a.reblog_button
div.controls-wrapper > div.control > nav.pop > a.share div.controls-wrapper > div.control > nav.pop > a.share
section.post-controls > div.controls-wrapper > div.control > a.reblog_button section.post-controls > div.controls-wrapper > div.control > a.reblog_button
div.controls-wrapper > div.control > nav.pop > a.share div.controls-wrapper > div.control > nav.pop > a.share
section.post-controls > div.controls-wrapper > div.control > a.reblog_button section.post-controls > div.controls-wrapper > div.control > a.reblog_button
div.controls-wrapper > div.control > nav.pop > a.share div.controls-wrapper > div.control > nav.pop > a.share
section.post-controls > div.controls-wrapper > div.control > a.reblog_button section.post-controls > div.controls-wrapper > div.control > a.reblog_button
div.controls-wrapper > div.control > nav.pop > a.share div.controls-wrapper > div.control > nav.pop > a.share
section.post-controls > div.controls-wrapper > div.control > a.reblog_button section.post-controls > div.controls-wrapper > div.control > a.reblog_button
div.controls-wrapper > div.control > nav.pop > a.share div.controls-wrapper > div.control > nav.pop > a.share
section.post-controls > div.controls-wrapper > div.control > a.reblog_button section.post-controls > div.controls-wrapper > div.control > a.reblog_button
div.controls-wrapper > div.control > nav.pop > a.share div.controls-wrapper > div.control > nav.pop > a.share
section.post-controls > div.controls-wrapper > div.control > a.reblog_button section.post-controls > div.controls-wrapper > div.control > a.reblog_button

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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-hidden="true"]` is not present on the document `<body>`
Image elements have `[alt]` attributes
Document has a `<title>` element
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
`[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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
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 a valid value for its `[lang]` attribute
`<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.
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.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
B
Alt Text Quality
1 of 13 images have issues
REVIEW
1 of 13 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
2 image(s) with alt text over 125 characters
Info::
10 image(s) with good alt text
13 images 10 good alt text 1 missing
IssueCount
missing1 image(s)
too long2 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

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 Daily Helmi Custom Styling Navigation Homepage Link Search Form
C
Favicon & Branding
Action
4 icon(s) detected
REVIEW
4 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA 4 pass AA only
title Daily Helmi
1.79:1
#000000
on
#4A3139
needs 4.5:1 (normal text)
16px · top of page (header area)
div 1.5M ratings
2.50:1
#000000
on
#544A58
needs 4.5:1 (normal text)
16px · top of page (header area)
div 277k ratings
3.43:1
#000000
on
#725C65
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Sounds perfect
3.97:1
#000000
on
#537172
needs 4.5:1 (normal text)
16px · above the fold
span Fundstücke aus dem täglichen Streifzug…
1.38:1
#474E50
on
#4E656C
needs 4.5:1 (normal text)
16px · above the fold
a Posts
4.11:1
#000000
on
#806962
needs 4.5:1 (normal text)
16px · above the fold

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Daily Helmi4.29:13.0:1
#000000
#75706D
Pass
h2 See, that’s what t…3.25:13.0:1
#000000
#476367
Pass
title Daily Helmi1.79:14.5:1
#000000
#4A3139
Fail
div 1.5M ratings2.50:14.5:1
#000000
#544A58
Fail
div 277k ratings3.43:14.5:1
#000000
#725C65
Fail
a Sounds perfect3.97:14.5:1
#000000
#537172
Fail
a Wahhhh, I don’t wa…5.57:14.5:1
#000000
#578B9B
Pass
a Daily Helmi6.24:14.5:1
#000000
#898F74
Pass
span Fundstücke aus dem …1.38:14.5:1
#474E50
#4E656C
Fail
a Posts4.11:14.5:1
#000000
#806962
Fail
a Likes20.12:14.5:1
#000000
#FAFAFA
Pass
a Noch Fragen?20.12:14.5:1
#000000
#FAFAFA
Pass
a Dein Beitrag20.12:14.5:1
#000000
#FAFAFA
Pass
a Archive20.12:14.5:1
#000000
#FAFAFA
Pass
p Rasenfunk Hauptstadt…20.12:14.5:1
#000000
#FAFAFA
Pass
a Instagram19.98:14.5:1
#000000
#FAF9F9
Pass
a Photo20.12:14.5:1
#000000
#FAFAFA
Pass
a 1 note20.12:14.5:1
#000000
#FAFAFA
Pass
a Jan 21st, 201920.12:14.5:1
#000000
#FAFAFA
Pass
a Open in app20.12:14.5:1
#000000
#FAFAFA
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
Heading Hierarchy
3 headings
PASS
3 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Daily Helmi
  • H2 See, that’s what the app is perfect for.
  • H1 Daily Helmi duplicate H1

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

A+
Heading Text Quality
All 3 heading(s) have substantive, well-formed text
PASS
All 3 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 38 visible text node(s) render at >= 12 CSS pixels
PASS
All 38 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A
Web Manifest
Valid manifest
PASS
Valid manifest
Info::
Name present: Tumblr
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Tumblr 192×192 icon 512×512 icon Start URL Display Mode standalone
Name Tumblr Display Mode standalone Theme Color #001936 Background Color #001936 Icons 2 icon(s)
A+
PWA Depth
1 PWA signal(s) surfaced
PASS
1 PWA signal(s) surfaced
Info::
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).
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
iOS smart-banner opt-in present (`apple-itunes-app`)
The page declares a companion iOS app via `<meta name="apple-itunes-app" content="app-id=...">`. iOS Safari shows a smart banner offering to open the page in the app, with an unobtrusive 'X' to dismiss. Recommended when you have a published companion app.
Info::
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback