Tumblrtumblr.com
Accessibility Score
Issues Found
Issues Found
SeriousARIA progressbar nodes must have an accessible name1 element
Screen reader users cannot determine what a role="progressbar" element is tracking without an accessible name. The name tells users what process or task is progressing.
Failing Elements
<div aria-busy="true" class="LQ3tN K6fAK OK2Wo" role="progressbar"><div class="OpTfa"></div><div class="OpTfa"></div><div class="OpTfa"></div></div>
Fix any of the following:
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
SeriousElements must only use permitted ARIA attributes2 elements
Using prohibited ARIA attributes prevents important information from reaching assistive technology users. It also causes assistive technologies to behave inconsistently as they attempt to compensate for the error.
Failing Elements
<span aria-label="1 badge" class="R7jci Kkrh1" style="--badge-size: 16px; --badge-spacing: 0px; --badges-total: 1;">
Fix all of the following:
- aria-label attribute cannot be used on a span with no valid role attribute.
<span aria-label="1 badge" class="R7jci Kkrh1" style="--badge-size: 16px; --badge-spacing: 0px; --badges-total: 1;">
Fix all of the following:
- aria-label attribute cannot be used on a span with no valid role attribute.
SeriousElements must meet minimum color contrast ratio thresholds7 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Failing Elements
<strong>100 million</strong>
Fix any of the following:
- Element has insufficient color contrast of 4.34 (foreground color: #ffffff, background color: #7c5cff, font size: 12.0pt (16px), font weight: bold). Expected contrast ratio of 4.5:1
<strong>Tumblr</strong>
Fix any of the following:
- Element has insufficient color contrast of 4.34 (foreground color: #ffffff, background color: #7c5cff, font size: 12.0pt (16px), font weight: bold). Expected contrast ratio of 4.5:1
<strong>communities</strong>
Fix any of the following:
- Element has insufficient color contrast of 4.34 (foreground color: #ffffff, background color: #7c5cff, font size: 12.0pt (16px), font weight: bold). Expected contrast ratio of 4.5:1
<strong>friends</strong>
Fix any of the following:
- Element has insufficient color contrast of 4.34 (foreground color: #ffffff, background color: #7c5cff, font size: 12.0pt (16px), font weight: bold). Expected contrast ratio of 4.5:1
<a class="jofje" data-login-wall-type="tags" data-login-wall-tag-...="hollanov" data-login-wall-dest...="/tagged/hollanov" data-login-wall-redi...="/tagged/hollanov" data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." href="/tagged/hollanov">
Fix any of the following:
- Element has insufficient color contrast of 3.25 (foreground color: #99a3ae, background color: #465236, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<a class="jofje" data-login-wall-type="tags" data-login-wall-tag-...="iron lung" data-login-wall-dest...="/tagged/iron%20lung" data-login-wall-redi...="/tagged/iron%20lung" data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." ...>
Fix any of the following:
- Element has insufficient color contrast of 4.16 (foreground color: #99a3ae, background color: #4d3b25, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
<a class="jofje" data-login-wall-type="tags" data-login-wall-tag-...="franco colapinto" data-login-wall-dest...="/tagged/franco%20col..." data-login-wall-redi...="/tagged/franco%20col..." data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." ...>
Fix any of the following:
- Element has insufficient color contrast of 3.73 (foreground color: #99a3ae, background color: #005035, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
SeriousLinks must have discernible text20 elements
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Failing Elements
<a class="yTeF1" data-login-wall-type="tags" data-login-wall-tag-...="heated rivalry" data-login-wall-dest...="/tagged/heated%20riv..." data-login-wall-redi...="/tagged/heated%20riv..." data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." ...>
Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
<a class="yTeF1" data-login-wall-type="tags" data-login-wall-tag-...="bloodymary" data-login-wall-dest...="/tagged/bloodymary" data-login-wall-redi...="/tagged/bloodymary" data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." href="/tagged/bloodymary">
Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
<a class="yTeF1" data-login-wall-type="tags" data-login-wall-tag-...="megan thee stallion" data-login-wall-dest...="/tagged/megan%20thee..." data-login-wall-redi...="/tagged/megan%20thee..." data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." ...>
Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
<a class="yTeF1" data-login-wall-type="tags" data-login-wall-tag-...="wlw" data-login-wall-dest...="/tagged/wlw" data-login-wall-redi...="/tagged/wlw" data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." href="/tagged/wlw">
Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
<a class="yTeF1" data-login-wall-type="tags" data-login-wall-tag-...="dc" data-login-wall-dest...="/tagged/dc" data-login-wall-redi...="/tagged/dc" data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." href="/tagged/dc">
Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
<a class="yTeF1" data-login-wall-type="tags" data-login-wall-tag-...="f1" data-login-wall-dest...="/tagged/f1" data-login-wall-redi...="/tagged/f1" data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." href="/tagged/f1">
Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
<a class="yTeF1" data-login-wall-type="tags" data-login-wall-tag-...="boku no hero academi..." data-login-wall-dest...="/tagged/boku%20no%20..." data-login-wall-redi...="/tagged/boku%20no%20..." data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." ...>
Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
<a class="yTeF1" data-login-wall-type="tags" data-login-wall-tag-...="supernatural" data-login-wall-dest...="/tagged/supernatural" data-login-wall-redi...="/tagged/supernatural" data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." ...>
Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
<a class="yTeF1" data-login-wall-type="tags" data-login-wall-tag-...="stranger things" data-login-wall-dest...="/tagged/stranger%20t..." data-login-wall-redi...="/tagged/stranger%20t..." data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." ...>
Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
<a class="yTeF1" data-login-wall-type="tags" data-login-wall-tag-...="boston bruins" data-login-wall-dest...="/tagged/boston%20bru..." data-login-wall-redi...="/tagged/boston%20bru..." data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." ...>
Fix all of the following:
- Element is in tab order and does not have accessible text
Fix any of the following:
- Element does not have text that is visible to screen readers
- aria-label attribute does not exist or is empty
- aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty
- Element has no title attribute
Showing first 10 of 20 failing elements.
Serious<ul> and <ol> must only directly contain <li>, <script> or <template> elements2 elements
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Failing Elements
<ul aria-label="Navigation menu" class="gM9qK" tabindex="-1">
Fix all of the following:
- List element has direct children that are not allowed: div
<ol class="nKYyP CXVtW">
Fix all of the following:
- List element has direct children that are not allowed: div
Serious<li> elements must be contained in a <ul> or <ol>10 elements
Lists require proper semantic hierarchy with ul or ol parent elements and li child elements. This structure allows screen readers to announce when users enter a list, how many items it contains, and which item they're currently on, providing essential context for understanding the content.
Failing Elements
<li data-index="1">
Fix any of the following:
- List item does not have a <ul>, <ol> parent element
<li data-index="2">
Fix any of the following:
- List item does not have a <ul>, <ol> parent element
<li data-index="3">
Fix any of the following:
- List item does not have a <ul>, <ol> parent element
<li data-index="4">
Fix any of the following:
- List item does not have a <ul>, <ol> parent element
<li data-index="5">
Fix any of the following:
- List item does not have a <ul>, <ol> parent element
<li data-index="6">
Fix any of the following:
- List item does not have a <ul>, <ol> parent element
<li data-index="7">
Fix any of the following:
- List item does not have a <ul>, <ol> parent element
<li data-index="8">
Fix any of the following:
- List item does not have a <ul>, <ol> parent element
<li data-index="9">
Fix any of the following:
- List item does not have a <ul>, <ol> parent element
<li data-index="10">
Fix any of the following:
- List item does not have a <ul>, <ol> parent element
SeriousElements should not have tabindex greater than zero9 elements
Using tabindex values greater than 0 creates unexpected tab orders that disorient users. It makes elements appear to be skipped when users tab past them, requires setting tabindex on every element to maintain order, and forces all tabindex items to be visited before any normal elements, breaking natural navigation flow.
Failing Elements
<div tabindex="2" style="margin-top: 0px;">
Fix any of the following:
- Element has a tabindex greater than 0
<div tabindex="4" style="margin-top: 0px;">
Fix any of the following:
- Element has a tabindex greater than 0
<div tabindex="6" style="margin-top: 0px;">
Fix any of the following:
- Element has a tabindex greater than 0
<div tabindex="8" style="margin-top: 0px;">
Fix any of the following:
- Element has a tabindex greater than 0
<div tabindex="1">
Fix any of the following:
- Element has a tabindex greater than 0
<div tabindex="3" style="margin-top: 0px;">
Fix any of the following:
- Element has a tabindex greater than 0
<div tabindex="5" style="margin-top: 0px;">
Fix any of the following:
- Element has a tabindex greater than 0
<div tabindex="7" style="margin-top: 0px;">
Fix any of the following:
- Element has a tabindex greater than 0
<div tabindex="9" style="margin-top: 0px;">
Fix any of the following:
- Element has a tabindex greater than 0
ModerateContentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Failing Elements
<footer class="m8mN_ _qHCt hG1qj" role="contentinfo" style="--element-height: 63px;">
Fix any of the following:
- The contentinfo landmark is contained in another landmark.
ModerateLandmarks should have a unique role or role/label/title (i.e. accessible name) combination1 element
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Failing Elements
<aside>
Fix any of the following:
- The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
ModeratePage should contain a level-one heading1 element
Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.
Failing Elements
<html lang="en-US" data-tumblr-ready="true">
Fix all of the following:
- Page must have a level-one heading
ModerateAll page content should be contained by landmarks1 element
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Failing Elements
<div class="hhVNo">Join over <strong>100 million</strong> people using <strong>Tumblr</strong> to find their <strong>communities</strong> and make <strong>friends</strong>.</div>
Fix any of the following:
- Some page content is not contained by landmarks
MinorAlternative text of images should not be repeated as text2 elements
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Failing Elements
<img alt="wlw" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/dd01669ae3d7c3950805b0bdbcb03bc0/3eb0fb61ffc43a21-94/s75x75_c1/cca186779a5b481979b842b51551a8e5c1b46af4.jpg 64w">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
<img alt="boku no hero academia" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/27d12eb904cbf344232636c20dc47afe/16a42be7a7db33a0-0b/s75x75_c1/91450f7f23627d5eb194d46d0e977320f3b76214.pnj 64w">
Fix all of the following:
- Element contains <img> element with alt text that duplicates existing text
Passed Audits
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html lang="en-US" data-tumblr-ready="true">
<html> element must have a valid value for the lang attribute1 element
Screen readers use language-specific sound libraries for proper pronunciation. Invalid language attributes cause screen readers to use the wrong library, making text sound like a confusing accent or completely unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<html lang="en-US" data-tumblr-ready="true">
<li> elements must be contained in a <ul> or <ol>8 elements
Lists require proper semantic hierarchy with ul or ol parent elements and li child elements. This structure allows screen readers to announce when users enter a list, how many items it contains, and which item they're currently on, providing essential context for understanding the content.
Audit Elements
<li class="Gav7q">
<li class="IYrO9 zxn0J" title="Explore">
<li class="IYrO9">
<li class="IYrO9">
<li class="kqme1">
<li class="kqme1">
<li class="kqme1">
<li class="kqme1">
<ul> and <ol> must only directly contain <li>, <script> or <template> elements1 element
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ul aria-label="Trending Blogs" class="PwJi6" style="height: 236px;">
All page content should be contained by landmarks4127 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<div id="root">
<div id="base-container">
<div class="Ty83o adsbygoogle Qrht9" data-testid="adBlockTest" id="adBanner"></div>
<div class="D5eCV Mpbf7">
<div class="c9lq9">
<div class="h_Erh">
<div class="FA5JM">
<div class="FnmoN">
<nav class="NkkDk">
<ul aria-label="Navigation menu" class="gM9qK" tabindex="-1">
Showing first 10 of 4127 audited elements.
Alternative text of images should not be repeated as text10 elements
Duplicating alternative text adjacent to an image or link forces screen readers to announce the same information twice. This redundancy is unnecessary and confusing, especially when image buttons repeat their labels in nearby text.
Audit Elements
<img alt="heated rivalry" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/261849764052c170e74a311bdeedcc90/3498b0a4b6b31edf-dc/s75x75_c1/ad0c6ac49cfddbd69ab2d6115c5344240d08201a.jpg 64w">
<img alt="bloodymary" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/596d0a199b09202dcda322ebe387b17a/467e39f1daae2ccc-5c/s75x75_c1/e19f11c0451ed6ba08ade8aafb6ee24e10d957cd.pnj 64w">
<img alt="megan thee stallion" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/0fa3d35aaad5d31991480fa3e77b55b4/ce7c6e1675e857dd-7b/s75x75_c1/ec9b60e313f17e7d5b9041ca51d7490e3c75659a.jpg 64w">
<img alt="dc" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/36d6e4942719a60c0bbb92707c2dbad7/4c3a2b3d1a79bc82-71/s75x75_c1/42e7588544e6ad7b691846adc9e60ec318c010ea.pnj 64w">
<img alt="f1" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/bfa080ea365047097f35c70881ac69a9/6e73550b83f85b8f-ab/s75x75_c1/b068a229f34bdd8f46868e27dabcf5ad6c2fab5f.pnj 64w">
<img alt="supernatural" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/04a44f68971394f5c830930810770a96/ab94196d2c246239-09/s75x75_c1/360d2b36129b1f5cc093e4dda7bc8a3fe929beaf.jpg 64w">
<img alt="Avatar" class="nLowv MbgAw" decoding="sync" loading="eager" sizes="37px" srcset="https://64.media.tum..." style="width: 37px; height:...">
<img alt="Avatar" class="nLowv MbgAw" decoding="sync" loading="eager" sizes="37px" srcset="https://64.media.tum..." style="width: 37px; height:...">
<img alt="Avatar" class="nLowv MbgAw" decoding="sync" loading="eager" sizes="37px" srcset="https://64.media.tum..." style="width: 37px; height:...">
<img alt="Avatar" class="nLowv MbgAw" decoding="sync" loading="eager" sizes="37px" srcset="https://64.media.tum..." style="width: 37px; height:...">
ARIA attributes must be used as specified for the element's role133 elements
Using ARIA attributes where they're not expected causes unpredictable behavior in assistive technologies. Following the ARIA specification ensures that screen readers and other tools can properly interpret and communicate your content's meaning to people with disabilities.
Audit Elements
<ul aria-label="Navigation menu" class="gM9qK" tabindex="-1">
<a aria-label="Home" href="/">
<a aria-current="page" class="tDT48" href="/explore/trending">
<button class="TRX6J UyyJb" aria-label="Change palette">
<button class="VmbqY ZWGnP Li_00 cqwPT Lp50M EF4A5" aria-label="Sign up" type="button"><span class="D4GNf">Sign up</span></button>
<button class="VmbqY ZWGnP Li_00 cqwPT zn53i EF4A5" aria-label="Log in" type="button"><span class="D4GNf">Log in</span></button>
<button class="VmbqY MuH6n Li_00 cqwPT Lp50M EF4A5" aria-label="Sign up" type="button"><span class="D4GNf">Sign up</span></button>
<button class="VmbqY MuH6n Li_00 cqwPT zn53i CKAFB" aria-label="Log in" type="button"><span class="D4GNf">Log in</span></button>
<button class="TRX6J KO5EN V7v4g m2bR1" aria-label="Scroll left">
<button class="TRX6J KO5EN TyF2z m2bR1" aria-label="Scroll right">
Showing first 10 of 133 audited elements.
ARIA attributes must conform to valid names133 elements
Misspelled or non-existent ARIA attributes cannot perform their intended accessibility function. Assistive technologies rely on correctly spelled, current ARIA attributes to convey proper user interface behaviors and structural information to people with disabilities.
Audit Elements
<ul aria-label="Navigation menu" class="gM9qK" tabindex="-1">
<a aria-label="Home" href="/">
<a aria-current="page" class="tDT48" href="/explore/trending">
<button class="TRX6J UyyJb" aria-label="Change palette">
<button class="VmbqY ZWGnP Li_00 cqwPT Lp50M EF4A5" aria-label="Sign up" type="button"><span class="D4GNf">Sign up</span></button>
<button class="VmbqY ZWGnP Li_00 cqwPT zn53i EF4A5" aria-label="Log in" type="button"><span class="D4GNf">Log in</span></button>
<button class="VmbqY MuH6n Li_00 cqwPT Lp50M EF4A5" aria-label="Sign up" type="button"><span class="D4GNf">Sign up</span></button>
<button class="VmbqY MuH6n Li_00 cqwPT zn53i CKAFB" aria-label="Log in" type="button"><span class="D4GNf">Log in</span></button>
<button class="TRX6J KO5EN V7v4g m2bR1" aria-label="Scroll left">
<button class="TRX6J KO5EN TyF2z m2bR1" aria-label="Scroll right">
Showing first 10 of 133 audited elements.
ARIA attributes must conform to valid values133 elements
ARIA attributes must contain correctly spelled values that match the attribute's expected options. Invalid values prevent the accessibility feature from working, making content inaccessible to assistive technology users who depend on these attributes for navigation and interaction.
Audit Elements
<ul aria-label="Navigation menu" class="gM9qK" tabindex="-1">
<a aria-label="Home" href="/">
<a aria-current="page" class="tDT48" href="/explore/trending">
<button class="TRX6J UyyJb" aria-label="Change palette">
<button class="VmbqY ZWGnP Li_00 cqwPT Lp50M EF4A5" aria-label="Sign up" type="button"><span class="D4GNf">Sign up</span></button>
<button class="VmbqY ZWGnP Li_00 cqwPT zn53i EF4A5" aria-label="Log in" type="button"><span class="D4GNf">Log in</span></button>
<button class="VmbqY MuH6n Li_00 cqwPT Lp50M EF4A5" aria-label="Sign up" type="button"><span class="D4GNf">Sign up</span></button>
<button class="VmbqY MuH6n Li_00 cqwPT zn53i CKAFB" aria-label="Log in" type="button"><span class="D4GNf">Log in</span></button>
<button class="TRX6J KO5EN V7v4g m2bR1" aria-label="Scroll left">
<button class="TRX6J KO5EN TyF2z m2bR1" aria-label="Scroll right">
Showing first 10 of 133 audited elements.
ARIA hidden element must not be focusable or contain focusable elements2 elements
Elements with aria-hidden="true" are removed from the accessibility API but remain keyboard-focusable, creating confusion about their visibility state. When users tab to these hidden elements, screen readers stay silent, leaving users unaware of what they've focused on or why nothing is being announced.
Audit Elements
<img alt="Badge image." class="sdOCZ" src="https://assets.tumbl..." srcset="https://assets.tumbl..." aria-hidden="true">
<img alt="Badge image." class="sdOCZ" src="https://assets.tumbl..." srcset="https://assets.tumbl..." aria-hidden="true">
ARIA role should be appropriate for the element118 elements
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Audit Elements
<svg class="GjGsN" height="20" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="98" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__logo-tumblr"></use></svg>
<svg height="24" role="presentation" width="22" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__explore"></use></svg>
<svg height="24" role="presentation" width="25" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__communities"></use></svg>
<svg height="24" role="presentation" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__palette"></use></svg>
<svg height="9" role="presentation" width="15" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(90deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
<svg height="9" role="presentation" width="15" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(270deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
<svg height="24" role="presentation" style="transform:rotate(90deg);transform-origin:center" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__caret-fat"></use></svg>
<svg height="24" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__masonry-view"></use></svg>
<svg height="23" role="presentation" style="--icon-color-primary:rgba(var(--white-on-dark), 0.40)" width="23" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__list-view"></use></svg>
<svg height="40" role="presentation" width="40" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(90deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
Showing first 10 of 118 audited elements.
ARIA roles used must conform to valid values98 elements
Invalid ARIA role values prevent assistive technologies from understanding and communicating the element's purpose to users. Without valid roles, screen readers cannot provide information about the element's features, properties, or how users should interact with it.
Audit Elements
<svg class="GjGsN" height="20" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="98" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__logo-tumblr"></use></svg>
<svg height="24" role="presentation" width="22" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__explore"></use></svg>
<svg height="24" role="presentation" width="25" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__communities"></use></svg>
<svg height="24" role="presentation" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__palette"></use></svg>
<svg height="9" role="presentation" width="15" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(90deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
<svg height="9" role="presentation" width="15" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(270deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
<svg height="24" role="presentation" style="transform:rotate(90deg);transform-origin:center" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__caret-fat"></use></svg>
<svg height="24" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__masonry-view"></use></svg>
<svg height="23" role="presentation" style="--icon-color-primary:rgba(var(--white-on-dark), 0.40)" width="23" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__list-view"></use></svg>
<svg height="40" role="presentation" width="40" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(90deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
Showing first 10 of 98 audited elements.
aria-hidden="true" must not be present on the document body1 element
Setting <body aria-hidden="true" hides all page content from assistive technologies while leaving it visible on screen. This creates a confusing experience where keyboard users can still tab to elements, but screen readers remain completely silent, providing no information about what's focused.
Audit Elements
<body id="tumblr" class="palette--trueBlue" style="--dashboard-tabs-header-height: 53px;">
Aside should not be contained in another landmark2 elements
Screen reader users can skip over complementary content like <aside> elements when they appear at the top level. Embedding asides within other landmarks may disable this navigation feature, forcing users to wade through ancillary content they want to skip.
Audit Elements
<aside>
<aside id="managed-icon-repository" style="width:0;height:0;overflow:hidden">
autocomplete attribute must be used correctly1 element
Missing or incorrect autocomplete values make forms inaccessible to screen reader users. Screen readers cannot provide adequate information about form fields without proper autocomplete attributes, preventing users from understanding what information is required and how to complete forms correctly.
Audit Elements
<input aria-label="Search" autocapitalize="on" autocomplete="off" class="j8Eiw Qqfho" name="q" placeholder="Search Tumblr" type="text" value="">
Buttons must have discernible text82 elements
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Audit Elements
<button class="TRX6J UyyJb" aria-label="Change palette">
<button class="VmbqY ZWGnP Li_00 cqwPT Lp50M EF4A5" aria-label="Sign up" type="button"><span class="D4GNf">Sign up</span></button>
<button class="VmbqY ZWGnP Li_00 cqwPT zn53i EF4A5" aria-label="Log in" type="button"><span class="D4GNf">Log in</span></button>
<button class="VmbqY MuH6n Li_00 cqwPT Lp50M EF4A5" aria-label="Sign up" type="button"><span class="D4GNf">Sign up</span></button>
<button class="VmbqY MuH6n Li_00 cqwPT zn53i CKAFB" aria-label="Log in" type="button"><span class="D4GNf">Log in</span></button>
<button class="TRX6J KO5EN V7v4g m2bR1" aria-label="Scroll left">
<button class="TRX6J KO5EN TyF2z m2bR1" aria-label="Scroll right">
<button class="TRX6J wl0Ka" tabindex="0">
<button class="TRX6J FSQZ7" aria-label="View in masonry"><span class="EvhBA" tabindex="-1"><svg height="24" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__masonry-view"></use></svg></span></button>
<button class="TRX6J FSQZ7" aria-label="View in list"><span class="EvhBA" tabindex="-1"><svg height="23" role="presentation" style="--icon-color-primary:rgba(var(--white-on-dark), 0.40)" width="23" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__list-view"></use></svg></span></button>
Showing first 10 of 82 audited elements.
Deprecated ARIA roles must not be used98 elements
Deprecated ARIA roles are not recognized by modern screen readers and assistive technologies. Using outdated roles means some users cannot access essential information or functionality on your site.
Audit Elements
<svg class="GjGsN" height="20" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="98" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__logo-tumblr"></use></svg>
<svg height="24" role="presentation" width="22" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__explore"></use></svg>
<svg height="24" role="presentation" width="25" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__communities"></use></svg>
<svg height="24" role="presentation" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__palette"></use></svg>
<svg height="9" role="presentation" width="15" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(90deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
<svg height="9" role="presentation" width="15" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(270deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
<svg height="24" role="presentation" style="transform:rotate(90deg);transform-origin:center" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__caret-fat"></use></svg>
<svg height="24" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__masonry-view"></use></svg>
<svg height="23" role="presentation" style="--icon-color-primary:rgba(var(--white-on-dark), 0.40)" width="23" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__list-view"></use></svg>
<svg height="40" role="presentation" width="40" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(90deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
Showing first 10 of 98 audited elements.
Document should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Audit Elements
<html lang="en-US" data-tumblr-ready="true">
Document should not have more than one banner landmark1 element
Multiple banner landmarks force screen reader users to sort through duplicate options to find header information. Each page should have only one banner landmark to enable quick, predictable navigation to the header without overwhelming users with unnecessary choices.
Audit Elements
<header class="DEkbl rtjhW">
Document should not have more than one contentinfo landmark1 element
Multiple contentinfo landmarks force screen reader users to sort through extra options to find footer information. Each page should have only one content info landmark to enable quick, predictable navigation without overwhelming users with duplicate structural markers.
Audit Elements
<footer aria-label="Post footer" class="gm9gb">
Document should not have more than one main landmark1 element
Multiple main landmarks confuse screen reader users about where the primary content is located. Each page should have only one main landmark so users can quickly and predictably navigate to the primary content area.
Audit Elements
<main class="YDpaw" style="min-height:100vh">
Documents must have <title> element to aid in navigation1 element
The page title is the first thing screen reader users hear when loading a page. Without a descriptive, unique title, users must read through the entire page to understand its contents and purpose, wasting valuable time on every page visit.
Audit Elements
<html lang="en-US" data-tumblr-ready="true">
Elements marked as presentational should be consistently ignored67 elements
Elements with role="none" or role="presentation" should be removed from the accessibility tree. Adding global ARIA attributes or making these elements focusable prevents their removal, leaving them accessible to screen readers when they should be ignored, creating unexpected and confusing behavior.
Audit Elements
<svg class="GjGsN" height="20" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="98" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__logo-tumblr"></use></svg>
<svg height="24" role="presentation" width="22" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__explore"></use></svg>
<svg height="24" role="presentation" width="25" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__communities"></use></svg>
<svg height="24" role="presentation" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__palette"></use></svg>
<svg height="9" role="presentation" width="15" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(90deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
<svg height="9" role="presentation" width="15" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(270deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
<svg height="24" role="presentation" style="transform:rotate(90deg);transform-origin:center" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__caret-fat"></use></svg>
<svg height="24" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__masonry-view"></use></svg>
<svg height="23" role="presentation" style="--icon-color-primary:rgba(var(--white-on-dark), 0.40)" width="23" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__list-view"></use></svg>
<svg height="40" role="presentation" width="40" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(90deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
Showing first 10 of 67 audited elements.
Elements must meet minimum color contrast ratio thresholds129 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Audit Elements
<span class="D4GNf">Sign up</span>
<span class="D4GNf">Log in</span>
<span class="D4GNf">Sign up</span>
<span class="D4GNf">Log in</span>
<a class="wl0Ka sSq2h" href="/explore/trending">Trending</a>
<a class="wl0Ka" href="/explore/staff-picks">Staff Picks</a>
<a class="wl0Ka" href="/explore/video">Videos</a>
<span>More</span>
<span class="CJe61">heated rivalry</span>
<span class="CJe61">bloodymary</span>
Showing first 10 of 129 audited elements.
Elements must only use permitted ARIA attributes111 elements
Using prohibited ARIA attributes prevents important information from reaching assistive technology users. It also causes assistive technologies to behave inconsistently as they attempt to compensate for the error.
Audit Elements
<ul aria-label="Navigation menu" class="gM9qK" tabindex="-1">
<a aria-label="Home" href="/">
<a aria-current="page" class="tDT48" href="/explore/trending">
<button class="TRX6J UyyJb" aria-label="Change palette">
<button class="VmbqY ZWGnP Li_00 cqwPT Lp50M EF4A5" aria-label="Sign up" type="button"><span class="D4GNf">Sign up</span></button>
<button class="VmbqY ZWGnP Li_00 cqwPT zn53i EF4A5" aria-label="Log in" type="button"><span class="D4GNf">Log in</span></button>
<button class="VmbqY MuH6n Li_00 cqwPT Lp50M EF4A5" aria-label="Sign up" type="button"><span class="D4GNf">Sign up</span></button>
<button class="VmbqY MuH6n Li_00 cqwPT zn53i CKAFB" aria-label="Log in" type="button"><span class="D4GNf">Log in</span></button>
<button class="TRX6J KO5EN V7v4g m2bR1" aria-label="Scroll left">
<button class="TRX6J KO5EN TyF2z m2bR1" aria-label="Scroll right">
Showing first 10 of 111 audited elements.
Elements must only use supported ARIA attributes133 elements
Using ARIA attributes in roles where they're not allowed can disable accessibility for entire sections of your application. Invalid attribute-role combinations create conflicts that cause assistive technologies to report incorrect or nonsensical information about your interface.
Audit Elements
<ul aria-label="Navigation menu" class="gM9qK" tabindex="-1">
<a aria-label="Home" href="/">
<a aria-current="page" class="tDT48" href="/explore/trending">
<button class="TRX6J UyyJb" aria-label="Change palette">
<button class="VmbqY ZWGnP Li_00 cqwPT Lp50M EF4A5" aria-label="Sign up" type="button"><span class="D4GNf">Sign up</span></button>
<button class="VmbqY ZWGnP Li_00 cqwPT zn53i EF4A5" aria-label="Log in" type="button"><span class="D4GNf">Log in</span></button>
<button class="VmbqY MuH6n Li_00 cqwPT Lp50M EF4A5" aria-label="Sign up" type="button"><span class="D4GNf">Sign up</span></button>
<button class="VmbqY MuH6n Li_00 cqwPT zn53i CKAFB" aria-label="Log in" type="button"><span class="D4GNf">Log in</span></button>
<button class="TRX6J KO5EN V7v4g m2bR1" aria-label="Scroll left">
<button class="TRX6J KO5EN TyF2z m2bR1" aria-label="Scroll right">
Showing first 10 of 133 audited elements.
Elements should not have tabindex greater than zero97 elements
Using tabindex values greater than 0 creates unexpected tab orders that disorient users. It makes elements appear to be skipped when users tab past them, requires setting tabindex on every element to maintain order, and forces all tabindex items to be visited before any normal elements, breaking natural navigation flow.
Audit Elements
<ul aria-label="Navigation menu" class="gM9qK" tabindex="-1">
<span class="EvhBA tDT48" tabindex="-1"><div class="kn4U3"><svg height="24" role="presentation" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__palette"></use></svg></div><div class="a132D"><span class="ZC1wz">Change palette</span><span class="jF6A2"></span></div></span>
<span class="EvhBA" tabindex="-1"><svg height="9" role="presentation" width="15" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(90deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg></span>
<span class="EvhBA" tabindex="-1"><svg height="9" role="presentation" width="15" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(270deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg></span>
<button class="TRX6J wl0Ka" tabindex="0">
<span class="EvhBA" tabindex="-1"><span class="WojaA"><span>More</span><span class="hXMYF"><svg height="24" role="presentation" style="transform:rotate(90deg);transform-origin:center" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__caret-fat"></use></svg></span></span></span>
<span class="EvhBA" tabindex="-1"><svg height="24" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__masonry-view"></use></svg></span>
<span class="EvhBA" tabindex="-1"><svg height="23" role="presentation" style="--icon-color-primary:rgba(var(--white-on-dark), 0.40)" width="23" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__list-view"></use></svg></span>
<span class="EvhBA GTDnP wOp1Q" tabindex="-1" style="left: 0px; padding-left: calc(50% - 310px);">
<span class="EvhBA GTDnP" tabindex="-1" style="right: 0px; padding-right: calc(50% - 310px);">
Showing first 10 of 97 audited elements.
Form elements must have labels1 element
Form labels are essential for screen reader users to understand what information each field requires. Without proper labels, screen readers cannot identify input expectations, fields don't receive focus when announced, and users with motor impairments lose the benefit of larger clickable areas that labels provide.
Audit Elements
<input aria-label="Search" autocapitalize="on" autocomplete="off" class="j8Eiw Qqfho" name="q" placeholder="Search Tumblr" type="text" value="">
Form elements should have a visible label1 element
The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.
Audit Elements
<input aria-label="Search" autocapitalize="on" autocomplete="off" class="j8Eiw Qqfho" name="q" placeholder="Search Tumblr" type="text" value="">
Form field must not have multiple label elements1 element
Multiple labels on the same form field cause inconsistent behavior across screen reader and browser combinations. Some will read the first label, others the last, and some will read both, creating confusion about what information the field requires.
Audit Elements
<input aria-label="Search" autocapitalize="on" autocomplete="off" class="j8Eiw Qqfho" name="q" placeholder="Search Tumblr" type="text" value="">
Images must have alternative text12 elements
Screen readers cannot translate images into text without alt attributes. Alternative text is essential for blind users and beneficial for users with low vision or color blindness, providing the same information that sighted users get from viewing the image.
Audit Elements
<img alt="heated rivalry" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/261849764052c170e74a311bdeedcc90/3498b0a4b6b31edf-dc/s75x75_c1/ad0c6ac49cfddbd69ab2d6115c5344240d08201a.jpg 64w">
<img alt="bloodymary" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/596d0a199b09202dcda322ebe387b17a/467e39f1daae2ccc-5c/s75x75_c1/e19f11c0451ed6ba08ade8aafb6ee24e10d957cd.pnj 64w">
<img alt="megan thee stallion" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/0fa3d35aaad5d31991480fa3e77b55b4/ce7c6e1675e857dd-7b/s75x75_c1/ec9b60e313f17e7d5b9041ca51d7490e3c75659a.jpg 64w">
<img alt="wlw" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/dd01669ae3d7c3950805b0bdbcb03bc0/3eb0fb61ffc43a21-94/s75x75_c1/cca186779a5b481979b842b51551a8e5c1b46af4.jpg 64w">
<img alt="dc" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/36d6e4942719a60c0bbb92707c2dbad7/4c3a2b3d1a79bc82-71/s75x75_c1/42e7588544e6ad7b691846adc9e60ec318c010ea.pnj 64w">
<img alt="f1" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/bfa080ea365047097f35c70881ac69a9/6e73550b83f85b8f-ab/s75x75_c1/b068a229f34bdd8f46868e27dabcf5ad6c2fab5f.pnj 64w">
<img alt="boku no hero academia" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/27d12eb904cbf344232636c20dc47afe/16a42be7a7db33a0-0b/s75x75_c1/91450f7f23627d5eb194d46d0e977320f3b76214.pnj 64w">
<img alt="supernatural" class="nLowv MbgAw" decoding="sync" loading="lazy" sizes="64px" srcset="https://64.media.tumblr.com/04a44f68971394f5c830930810770a96/ab94196d2c246239-09/s75x75_c1/360d2b36129b1f5cc093e4dda7bc8a3fe929beaf.jpg 64w">
<img alt="Avatar" class="nLowv MbgAw" decoding="sync" loading="eager" sizes="37px" srcset="https://64.media.tum..." style="width: 37px; height:...">
<img alt="Avatar" class="nLowv MbgAw" decoding="sync" loading="eager" sizes="37px" srcset="https://64.media.tum..." style="width: 37px; height:...">
Showing first 10 of 12 audited elements.
Inline text spacing must be adjustable with custom stylesheets125 elements
Single-spaced text makes it difficult for people with cognitive disabilities to track lines while reading. Providing line spacing between 1.5 to 2 helps these users start a new line more easily after finishing the previous one.
Audit Elements
<body id="tumblr" class="palette--trueBlue" style="--dashboard-tabs-header-height: 53px;">
<div class="FQkf4 tSe6h" style="width:98px;height:20px"><div class="FP6oS"></div><svg class="GjGsN" height="20" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="98" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__logo-tumblr"></use></svg></div>
<svg class="GjGsN" height="20" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="98" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__logo-tumblr"></use></svg>
<div class="IvzMP VC_rY hgN9e" style="background-color: rgb(124, 92, 255); color: rgb(255, 255, 255);">
<main class="YDpaw" style="min-height:100vh">
<div class="Dk06o" style="--offset:0px">
<svg height="24" role="presentation" style="transform:rotate(90deg);transform-origin:center" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__caret-fat"></use></svg>
<svg height="24" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__masonry-view"></use></svg>
<svg height="23" role="presentation" style="--icon-color-primary:rgba(var(--white-on-dark), 0.40)" width="23" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__list-view"></use></svg>
<div style="padding-left: calc(50% - 310px);"></div>
Showing first 10 of 125 audited elements.
Interactive controls must not be nested95 elements
Nested interactive elements create empty tab stops where screen readers remain silent. When users tab to a focusable element inside another interactive control, they receive no information about its name, role, or state, creating a confusing and broken navigation experience.
Audit Elements
<button class="TRX6J UyyJb" aria-label="Change palette">
<button class="VmbqY ZWGnP Li_00 cqwPT Lp50M EF4A5" aria-label="Sign up" type="button"><span class="D4GNf">Sign up</span></button>
<button class="VmbqY ZWGnP Li_00 cqwPT zn53i EF4A5" aria-label="Log in" type="button"><span class="D4GNf">Log in</span></button>
<button class="VmbqY MuH6n Li_00 cqwPT Lp50M EF4A5" aria-label="Sign up" type="button"><span class="D4GNf">Sign up</span></button>
<button class="VmbqY MuH6n Li_00 cqwPT zn53i CKAFB" aria-label="Log in" type="button"><span class="D4GNf">Log in</span></button>
<button class="TRX6J KO5EN V7v4g m2bR1" aria-label="Scroll left">
<button class="TRX6J KO5EN TyF2z m2bR1" aria-label="Scroll right">
<button class="TRX6J wl0Ka" tabindex="0">
<button class="TRX6J FSQZ7" aria-label="View in masonry"><span class="EvhBA" tabindex="-1"><svg height="24" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__masonry-view"></use></svg></span></button>
<button class="TRX6J FSQZ7" aria-label="View in list"><span class="EvhBA" tabindex="-1"><svg height="23" role="presentation" style="--icon-color-primary:rgba(var(--white-on-dark), 0.40)" width="23" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__list-view"></use></svg></span></button>
Showing first 10 of 95 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination3 elements
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<nav class="NkkDk">
<main class="YDpaw" style="min-height:100vh">
<footer class="m8mN_ _qHCt hG1qj" role="contentinfo" style="--element-height: 63px;">
Links must have discernible text107 elements
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Audit Elements
<a aria-label="Home" href="/">
<a aria-current="page" class="tDT48" href="/explore/trending">
<a class="tDT48" href="/communities/browse"><div class="kn4U3"><svg height="24" role="presentation" width="25" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__communities"></use></svg></div><div class="a132D"><span class="ZC1wz">Communities</span><span class="jF6A2"></span></div></a>
<a class="wl0Ka sSq2h" href="/explore/trending">Trending</a>
<a class="wl0Ka" href="/explore/staff-picks">Staff Picks</a>
<a class="wl0Ka" href="/explore/video">Videos</a>
<a class="jofje" data-login-wall-type="tags" data-login-wall-tag-...="hollanov" data-login-wall-dest...="/tagged/hollanov" data-login-wall-redi...="/tagged/hollanov" data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." href="/tagged/hollanov">
<a class="jofje" data-login-wall-type="tags" data-login-wall-tag-...="iron lung" data-login-wall-dest...="/tagged/iron%20lung" data-login-wall-redi...="/tagged/iron%20lung" data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." ...>
<a class="jofje" data-login-wall-type="tags" data-login-wall-tag-...="klay thompson" data-login-wall-dest...="/tagged/klay%20thomp..." data-login-wall-redi...="/tagged/klay%20thomp..." data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." ...>
<a class="jofje" data-login-wall-type="tags" data-login-wall-tag-...="dc fanart" data-login-wall-dest...="/tagged/dc%20fanart" data-login-wall-redi...="/tagged/dc%20fanart" data-login-wall-titl...="Seems we're out of f..." data-login-wall-text="But there's good new..." ...>
Showing first 10 of 107 audited elements.
Main landmark should not be contained in another landmark1 element
The main landmark must be at the top level and not nested inside other landmarks. This ensures screen reader users can quickly navigate to the primary content without searching through complex hierarchy, making page navigation simpler and more predictable.
Audit Elements
<main class="YDpaw" style="min-height:100vh">
Page must have means to bypass repeated blocks1 element
Keyboard-only users must tab through all navigation and header content before reaching the main content, which can take several minutes and cause physical pain for users with motor limitations. Bypass mechanisms like skip links allow these users to jump directly to main content, saving time and reducing fatigue.
Audit Elements
<html lang="en-US" data-tumblr-ready="true">
Required ARIA attributes must be provided98 elements
ARIA widget roles need required attributes to describe their current state. Without these attributes, screen readers cannot communicate essential information like whether a checkbox is checked or a slider's current value, leaving users unable to interact effectively with the widget.
Audit Elements
<svg class="GjGsN" height="20" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="98" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__logo-tumblr"></use></svg>
<svg height="24" role="presentation" width="22" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__explore"></use></svg>
<svg height="24" role="presentation" width="25" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__communities"></use></svg>
<svg height="24" role="presentation" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__palette"></use></svg>
<svg height="9" role="presentation" width="15" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(90deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
<svg height="9" role="presentation" width="15" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(270deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
<svg height="24" role="presentation" style="transform:rotate(90deg);transform-origin:center" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__caret-fat"></use></svg>
<svg height="24" role="presentation" style="--icon-color-primary:RGB(var(--white-on-dark))" width="24" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__masonry-view"></use></svg>
<svg height="23" role="presentation" style="--icon-color-primary:rgba(var(--white-on-dark), 0.40)" width="23" xmlns="http://www.w3.org/2000/svg"><use href="#managed-icon__list-view"></use></svg>
<svg height="40" role="presentation" width="40" xmlns="http://www.w3.org/2000/svg" style="transform: rotate(90deg); transform-origin: center center;"><use href="#managed-icon__caret-thin"></use></svg>
Showing first 10 of 98 audited elements.
Scrollable region must have keyboard access1 element
Scrollable regions must contain focusable elements or be focusable themselves to enable keyboard navigation. Without keyboard access, users cannot scroll to view content that extends beyond the visible area, making that content completely inaccessible to keyboard-only users.
Audit Elements
<div class="jxu4l">
Users should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Audit Elements
<meta content="width=device-width, initial-scale=1" name="viewport">
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta content="width=device-width, initial-scale=1" name="viewport">