Skip to content
https://tumblr.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
2
REVIEW
7
PASS
4
INFO
0
Checks
13
4 PASS 7 REVIEW 2 FIX
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::
Hamburger menu detected (responsive design)
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
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 ASIDE 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

B
Heading Hierarchy
No headings
REVIEW
No headings
Warning::
No headings found
Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

B
Alt Text Quality
3 of 7 images have issues
REVIEW
3 of 7 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
3 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
7 images 1 good alt text 3 decorative 3 missing
IssueCount
missing3 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

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::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Not found. ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✓
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color width=device-width, initial-scale=1 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA
title Trending topics on Tumblr
1.19:1
#000000
on
#001935
needs 4.5:1 (normal text)
16px · top of page (header area)
div Join over
1.19:1
#000000
on
#001935
needs 4.5:1 (normal text)
16px · top of page (header area)
strong 100 million
2.65:1
#000000
on
#405367
needs 3.0:1 (large text)
16px · top of page (header area) · over background image/gradient
div people using
1.19:1
#000000
on
#001935
needs 4.5:1 (normal text)
16px · top of page (header area)
strong Tumblr
1.19:1
#000000
on
#001935
needs 3.0:1 (large 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
title Trending topics on T…1.19:14.5:1
#000000
#001935
Fail
div Join over1.19:14.5:1
#000000
#001935
Fail
strong 100 million2.65:13.0:1
#000000
#405367
Fail
div people using1.19:14.5:1
#000000
#001935
Fail
strong Tumblr1.19:13.0:1
#000000
#001935
Fail
div to find their8.11:14.5:1
#000000
#98A2AD
Pass
strong communities21.00:13.0:1
#000000
#FFFFFF
Pass
div and make21.00:14.5:1
#000000
#FFFFFF
Pass
strong friends21.00:13.0:1
#000000
#FFFFFF
Pass
span Sign up21.00:14.5:1
#000000
#FFFFFF
Pass
span Log in21.00:14.5:1
#000000
#FFFFFF
Pass
a Trending21.00:14.5:1
#000000
#FFFFFF
Pass
a Staff Picks21.00:14.5:1
#000000
#FFFFFF
Pass
a Videos21.00:14.5:1
#000000
#FFFFFF
Pass
span More21.00:14.5:1
#000000
#FFFFFF
Pass
span #atla21.00:14.5:1
#000000
#FFFFFF
Pass
span #tomodachi life21.00:14.5:1
#000000
#FFFFFF
Pass
span #good omens21.00:14.5:1
#000000
#FFFFFF
Pass
span #music21.00:14.5:1
#000000
#FFFFFF
Pass
span #dc21.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.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 6 failing, 18 passed
REVIEW
78

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

When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label `progressbar` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
main.YDpaw > div.j8ha0 > div.gG278 > div.LQ3tN main.YDpaw > div.j8ha0 > div.gG278 > div.LQ3tN

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
6 badges div.l4Qpd > div.cPL5a > div.W0XIT > span.R7jci
1 badge div.l4Qpd > div.cPL5a > div.W0XIT > span.R7jci
4 badges div.l4Qpd > div.cPL5a > div.W0XIT > span.R7jci

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.

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
100 million div.IvzMP > div.xw7_H > div.hhVNo > strong
Tumblr div.IvzMP > div.xw7_H > div.hhVNo > strong
communities div.IvzMP > div.xw7_H > div.hhVNo > strong
friends div.IvzMP > div.xw7_H > div.hhVNo > strong
the-big-moodApr 6#posts#food119942.1K main.YDpaw > div.j8ha0 > div.zAlrA > div.rZlUD
moxrhodesMar 20#wwe#cody rhodes#my gifs#tw blood4139408 main.YDpaw > div.j8ha0 > div.zAlrA > div.rZlUD
goth-queenMar 30#goth#gothic#fashion#alternative#soft grunge#grunge131.3K2.7K main.YDpaw > div.j8ha0 > div.zAlrA > div.rZlUD
romehboApr 2a misogynistic society is so threatened by the concept of trans wom… main.YDpaw > div.j8ha0 > div.zAlrA > div.rZlUD

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
span.EvhBA > figure.DdFPj > div._0MuRn > img.nLowv span.EvhBA > figure.DdFPj > div._0MuRn > img.nLowv
span.EvhBA > figure.DdFPj > div._0MuRn > img.nLowv span.EvhBA > figure.DdFPj > div._0MuRn > img.nLowv
span.EvhBA > figure.DdFPj > div._0MuRn > img.nLowv span.EvhBA > figure.DdFPj > div._0MuRn > img.nLowv
span.EvhBA > figure.DdFPj > div._0MuRn > img.nLowv span.EvhBA > figure.DdFPj > div._0MuRn > img.nLowv

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.

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
ariadne-mouse div.cPL5a > div.W0XIT > div.d7ZC6 > a.BSUG4
thoughtkick div.cPL5a > div.W0XIT > div.d7ZC6 > a.BSUG4
#lit div.qYXF9 > div.hAFp3 > div.mwjNz > a.KSDLH
frog-memes div.cPL5a > div.W0XIT > div.d7ZC6 > a.BSUG4
animentality div.cPL5a > div.W0XIT > div.d7ZC6 > a.BSUG4
havingapoemwithyou div.cPL5a > div.W0XIT > div.d7ZC6 > a.BSUG4
ALT button.TRX6J > span.EvhBA > figure.DdFPj > button.Dt_Mi
undying-princess div.cPL5a > div.W0XIT > div.d7ZC6 > a.BSUG4

These items highlight common accessibility best practices.

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
70 div.rtfvT > span.Vcrhu > span.Vcrhu > button#:r0:
232 span.Vcrhu > span.Vcrhu > div.pG5KN > button.VmbqY
1K div.rtfvT > span.Vcrhu > span.Vcrhu > button#:r1:
2.4K span.Vcrhu > span.Vcrhu > div.pG5KN > button.VmbqY
63 footer.gm9gb > div.ndAE7 > div.rtfvT > button.VmbqY
5.3K div.rtfvT > span.Vcrhu > span.Vcrhu > button#:r2:
12K span.Vcrhu > span.Vcrhu > div.pG5KN > button.VmbqY
2 footer.gm9gb > div.ndAE7 > div.rtfvT > button.VmbqY
717 div.rtfvT > span.Vcrhu > span.Vcrhu > button#:r3:
3K span.Vcrhu > span.Vcrhu > div.pG5KN > button.VmbqY
ALT span > div.GzjsW > div.CQmeg > button.TRX6J
2 footer.gm9gb > div.ndAE7 > div.rtfvT > button.VmbqY
606 div.rtfvT > span.Vcrhu > span.Vcrhu > button#:r4:
1.2K span.Vcrhu > span.Vcrhu > div.pG5KN > button.VmbqY
81 footer.gm9gb > div.ndAE7 > div.rtfvT > button.VmbqY
27K div.rtfvT > span.Vcrhu > span.Vcrhu > button#:r5:
41K span.Vcrhu > span.Vcrhu > div.pG5KN > button.VmbqY
○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
●`[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
●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
●No element has a `[tabindex]` value greater than 0
●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
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○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
○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
○Heading elements appear in a sequentially-descending order
○`<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.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○`[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.
○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.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A
Favicon & Branding
13 icon(s) detected
PASS
13 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Tumblr
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Tumblr ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Tumblr Display Mode standalone Theme Color #36465d Background Color #36465d Icons 9 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback