Pinterestpinterest.com
Accessibility Score
Issues Found
Issues Found
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 class="en" lang="en">
Fix all of the following:
- Page must have a level-one heading
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 class="en" lang="en">
<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 class="en" lang="en">
All page content should be contained by landmarks57 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 data-reactcontainer="true" id="__PWS_ROOT__">
<div class="ADXRXN">
<header class="ADXRXN">
<a class="etmDmh i7jpet zlD4hU Q3hcOU DodKMr KQwCbH itw4K9 g0I6wi udPABh be_g_n ap8aAM" href="#" rel="" tabindex="0">
<div data-test-id="hiddenSkipToContentContainer" class="ADXRXN R6_ngo TfR6nu WTrvgR _VU9d3 kXGpvW mGqjhp" style="height: 1px; width: 1px;">
<div class="ADXRXN YTYZ7l"><div class="H2DtUH KwViV7 FE_3R1 Tjcf3c kF2VEF sSBu24" style="height: 75px; width: 100%;"><div class="lIkAnG eMU5i5 YfEt3H v_eFe4 qnEc35 hxKTA7 rszMzv">Skip to content</div></div></div>
<div class="H2DtUH KwViV7 FE_3R1 Tjcf3c kF2VEF sSBu24" style="height: 75px; width: 100%;"><div class="lIkAnG eMU5i5 YfEt3H v_eFe4 qnEc35 hxKTA7 rszMzv">Skip to content</div></div>
<div class="lIkAnG eMU5i5 YfEt3H v_eFe4 qnEc35 hxKTA7 rszMzv">Skip to content</div>
<div data-test-id="unauth-header" class="ADXRXN bnBtRO mJ2PyB n62I2n" style="left: 0px; transition: left 200ms; z-index: 671;">
<nav aria-label="Main" class="ADXRXN BVzdUh Tjcf3c _xSIdT ecEhnF qJUqe1 sSBu24 zEVE_X" style="height: 80px; width: 100%;">
Showing first 10 of 57 audited elements.
ARIA attributes must be used as specified for the element's role2 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
<nav aria-label="Main" class="ADXRXN BVzdUh Tjcf3c _xSIdT ecEhnF qJUqe1 sSBu24 zEVE_X" style="height: 80px; width: 100%;">
<a aria-label="Pinterest home" class="etmDmh i7jpet zlD4hU Q3hcOU g81vm9 hlFz_k itw4K9 g0I6wi udPABh be_g_n ap8aAM" href="/" rel="" tabindex="0" target="_self">
ARIA attributes must conform to valid names2 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
<nav aria-label="Main" class="ADXRXN BVzdUh Tjcf3c _xSIdT ecEhnF qJUqe1 sSBu24 zEVE_X" style="height: 80px; width: 100%;">
<a aria-label="Pinterest home" class="etmDmh i7jpet zlD4hU Q3hcOU g81vm9 hlFz_k itw4K9 g0I6wi udPABh be_g_n ap8aAM" href="/" rel="" tabindex="0" target="_self">
ARIA attributes must conform to valid values2 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
<nav aria-label="Main" class="ADXRXN BVzdUh Tjcf3c _xSIdT ecEhnF qJUqe1 sSBu24 zEVE_X" style="height: 80px; width: 100%;">
<a aria-label="Pinterest home" class="etmDmh i7jpet zlD4hU Q3hcOU g81vm9 hlFz_k itw4K9 g0I6wi udPABh be_g_n ap8aAM" href="/" rel="" tabindex="0" target="_self">
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
<svg aria-hidden="true" aria-label="Pinterest logo" fill="none" height="18" role="img" viewBox="0 0 98 18" width="98" xmlns="http://www.w3.org/2000/svg">
<iframe aria-hidden="true" id="epik_localstore" src="https://ct.pinterest.com/ct.html" title="iframe to send EPIK" style="display: none;"></iframe>
ARIA role should be appropriate for the element2 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 aria-hidden="true" aria-label="Pinterest logo" fill="none" height="18" role="img" viewBox="0 0 98 18" width="98" xmlns="http://www.w3.org/2000/svg">
<div id="mweb-unauth-container" role="main" class="ADXRXN"><div data-layout-shift-boundary-id="UnauthHomePageContainer" class="ADXRXN "></div></div>
ARIA roles used must conform to valid values1 element
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
<div id="mweb-unauth-container" role="main" class="ADXRXN"><div data-layout-shift-boundary-id="UnauthHomePageContainer" class="ADXRXN "></div></div>
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 style="margin:0">
Banner landmark should not be contained in another landmark1 element
Banner landmarks must be top-level to effectively designate the header portion of the page. Nested banner landmarks fail to provide the structural information screen reader users need to navigate efficiently through the page layout.
Audit Elements
<header class="ADXRXN">
Buttons must have discernible text2 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="G0yGFD ap8aAM Q3hcOU gwpqhu itmoZr GaMK1V PRly_u y0ni1V" tabindex="0" type="button"><div class="oxThCB"><div class="lIkAnG eMU5i5 o5UlW_ hL1e7w">Log in</div></div></button>
<button class="G0yGFD ap8aAM Q3hcOU j0pMjI itmoZr GaMK1V PRly_u y0ni1V" tabindex="0" type="button"><div class="oxThCB"><div class="WuRgKB eMU5i5 o5UlW_ hL1e7w">Sign up</div></div></button>
Deprecated ARIA roles must not be used1 element
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
<div id="mweb-unauth-container" role="main" class="ADXRXN"><div data-layout-shift-boundary-id="UnauthHomePageContainer" class="ADXRXN "></div></div>
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 class="en" lang="en">
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="ADXRXN">
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
<div id="mweb-unauth-container" role="main" class="ADXRXN"><div data-layout-shift-boundary-id="UnauthHomePageContainer" class="ADXRXN "></div></div>
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 class="en" lang="en">
Elements must meet minimum color contrast ratio thresholds8 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
<div class="WuRgKB eMU5i5 o5UlW_ hL1e7w">Explore</div>
<div class="WuRgKB eMU5i5 o5UlW_ hL1e7w">Shop</div>
<div class="WuRgKB eMU5i5 o5UlW_ hL1e7w">About</div>
<div class="WuRgKB eMU5i5 o5UlW_ hL1e7w">Businesses</div>
<div class="WuRgKB eMU5i5 o5UlW_ hL1e7w">Create</div>
<div class="WuRgKB eMU5i5 o5UlW_ hL1e7w">News</div>
<div class="lIkAnG eMU5i5 o5UlW_ hL1e7w">Log in</div>
<div class="WuRgKB eMU5i5 o5UlW_ hL1e7w">Sign up</div>
Elements 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.
Audit Elements
<nav aria-label="Main" class="ADXRXN BVzdUh Tjcf3c _xSIdT ecEhnF qJUqe1 sSBu24 zEVE_X" style="height: 80px; width: 100%;">
<a aria-label="Pinterest home" class="etmDmh i7jpet zlD4hU Q3hcOU g81vm9 hlFz_k itw4K9 g0I6wi udPABh be_g_n ap8aAM" href="/" rel="" tabindex="0" target="_self">
Elements must only use supported ARIA attributes2 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
<nav aria-label="Main" class="ADXRXN BVzdUh Tjcf3c _xSIdT ecEhnF qJUqe1 sSBu24 zEVE_X" style="height: 80px; width: 100%;">
<a aria-label="Pinterest home" class="etmDmh i7jpet zlD4hU Q3hcOU g81vm9 hlFz_k itw4K9 g0I6wi udPABh be_g_n ap8aAM" href="/" rel="" tabindex="0" target="_self">
Elements should not have tabindex greater than zero10 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
<a class="etmDmh i7jpet zlD4hU Q3hcOU DodKMr KQwCbH itw4K9 g0I6wi udPABh be_g_n ap8aAM" href="#" rel="" tabindex="0">
<a aria-label="Pinterest home" class="etmDmh i7jpet zlD4hU Q3hcOU g81vm9 hlFz_k itw4K9 g0I6wi udPABh be_g_n ap8aAM" href="/" rel="" tabindex="0" target="_self">
<a class="etmDmh i7jpet zlD4hU Q3hcOU RLsYhV G0yGFD ap8aAM iMxAxK VogH1o itmoZr bknC6k PRly_u y0ni1V" data-test-id="ideas-tab" href="/ideas" rel="" tabindex="0"><div class="WuRgKB eMU5i5 o5UlW_ hL1e7w">Explore</div></a>
<a class="etmDmh i7jpet zlD4hU Q3hcOU RLsYhV G0yGFD ap8aAM iMxAxK VogH1o itmoZr bknC6k PRly_u y0ni1V" data-test-id="shopping-tab" href="/shopping/" rel="" tabindex="0"><div class="WuRgKB eMU5i5 o5UlW_ hL1e7w">Shop</div></a>
<a class="etmDmh i7jpet zlD4hU Q3hcOU RLsYhV G0yGFD ap8aAM iMxAxK VogH1o itmoZr bknC6k PRly_u y0ni1V" href="/_/_/about/" rel="noopener noreferrer" tabindex="0" target="_blank">
<a class="etmDmh i7jpet zlD4hU..." href="/_/_/business/?utm_c..." rel="noopener noreferrer" tabindex="0" target="_blank">
<a class="etmDmh i7jpet zlD4hU Q3hcOU RLsYhV G0yGFD ap8aAM iMxAxK VogH1o itmoZr bknC6k PRly_u y0ni1V" href="/_/_/create/" rel="noopener noreferrer" tabindex="0" target="_blank">
<a class="etmDmh i7jpet zlD4hU..." href="/_/_/blog/?utm_sourc..." rel="noopener noreferrer" tabindex="0" target="_blank">
<button class="G0yGFD ap8aAM Q3hcOU gwpqhu itmoZr GaMK1V PRly_u y0ni1V" tabindex="0" type="button"><div class="oxThCB"><div class="lIkAnG eMU5i5 o5UlW_ hL1e7w">Log in</div></div></button>
<button class="G0yGFD ap8aAM Q3hcOU j0pMjI itmoZr GaMK1V PRly_u y0ni1V" tabindex="0" type="button"><div class="oxThCB"><div class="WuRgKB eMU5i5 o5UlW_ hL1e7w">Sign up</div></div></button>
Inline text spacing must be adjustable with custom stylesheets14 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 style="margin:0">
<div data-test-id="unauth-header" class="ADXRXN bnBtRO mJ2PyB n62I2n" style="left: 0px; transition: left 200ms; z-index: 671;">
<nav aria-label="Main" class="ADXRXN BVzdUh Tjcf3c _xSIdT ecEhnF qJUqe1 sSBu24 zEVE_X" style="height: 80px; width: 100%;">
<div data-test-id="ideas-tab" class="ADXRXN C6J6UC g8WGSl" style="height: 48px; min-width: 60px;">
<div data-test-id="shopping-tab" class="ADXRXN C6J6UC g8WGSl" style="height: 48px; min-width: 60px;">
<div data-test-id="header-about-button" class="ADXRXN LbyOQL M9Ye1t Nt6yCq iqoOXP" style="margin-inline: 0px;">
<div class="ADXRXN gEQpi5" style="display: inline;"><div class="ADXRXN iWgz2P sA6yWk">; Opens a new tab</div></div>
<div data-test-id="header-business-button" class="ADXRXN LbyOQL M9Ye1t Nt6yCq iqoOXP" style="margin-inline: 0px;">
<div class="ADXRXN gEQpi5" style="display: inline;"><div class="ADXRXN iWgz2P sA6yWk">; Opens a new tab</div></div>
<div data-test-id="header-create-button" class="ADXRXN LbyOQL M9Ye1t Nt6yCq iqoOXP" style="margin-inline: 0px;">
Showing first 10 of 14 audited elements.
Interactive controls must not be nested2 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="G0yGFD ap8aAM Q3hcOU gwpqhu itmoZr GaMK1V PRly_u y0ni1V" tabindex="0" type="button"><div class="oxThCB"><div class="lIkAnG eMU5i5 o5UlW_ hL1e7w">Log in</div></div></button>
<button class="G0yGFD ap8aAM Q3hcOU j0pMjI itmoZr GaMK1V PRly_u y0ni1V" tabindex="0" type="button"><div class="oxThCB"><div class="WuRgKB eMU5i5 o5UlW_ hL1e7w">Sign up</div></div></button>
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
<header class="ADXRXN">
<nav aria-label="Main" class="ADXRXN BVzdUh Tjcf3c _xSIdT ecEhnF qJUqe1 sSBu24 zEVE_X" style="height: 80px; width: 100%;">
<div id="mweb-unauth-container" role="main" class="ADXRXN"><div data-layout-shift-boundary-id="UnauthHomePageContainer" class="ADXRXN "></div></div>
Links must have discernible text8 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 class="etmDmh i7jpet zlD4hU Q3hcOU DodKMr KQwCbH itw4K9 g0I6wi udPABh be_g_n ap8aAM" href="#" rel="" tabindex="0">
<a aria-label="Pinterest home" class="etmDmh i7jpet zlD4hU Q3hcOU g81vm9 hlFz_k itw4K9 g0I6wi udPABh be_g_n ap8aAM" href="/" rel="" tabindex="0" target="_self">
<a class="etmDmh i7jpet zlD4hU Q3hcOU RLsYhV G0yGFD ap8aAM iMxAxK VogH1o itmoZr bknC6k PRly_u y0ni1V" data-test-id="ideas-tab" href="/ideas" rel="" tabindex="0"><div class="WuRgKB eMU5i5 o5UlW_ hL1e7w">Explore</div></a>
<a class="etmDmh i7jpet zlD4hU Q3hcOU RLsYhV G0yGFD ap8aAM iMxAxK VogH1o itmoZr bknC6k PRly_u y0ni1V" data-test-id="shopping-tab" href="/shopping/" rel="" tabindex="0"><div class="WuRgKB eMU5i5 o5UlW_ hL1e7w">Shop</div></a>
<a class="etmDmh i7jpet zlD4hU Q3hcOU RLsYhV G0yGFD ap8aAM iMxAxK VogH1o itmoZr bknC6k PRly_u y0ni1V" href="/_/_/about/" rel="noopener noreferrer" tabindex="0" target="_blank">
<a class="etmDmh i7jpet zlD4hU..." href="/_/_/business/?utm_c..." rel="noopener noreferrer" tabindex="0" target="_blank">
<a class="etmDmh i7jpet zlD4hU Q3hcOU RLsYhV G0yGFD ap8aAM iMxAxK VogH1o itmoZr bknC6k PRly_u y0ni1V" href="/_/_/create/" rel="noopener noreferrer" tabindex="0" target="_blank">
<a class="etmDmh i7jpet zlD4hU..." href="/_/_/blog/?utm_sourc..." rel="noopener noreferrer" tabindex="0" target="_blank">
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
<div id="mweb-unauth-container" role="main" class="ADXRXN"><div data-layout-shift-boundary-id="UnauthHomePageContainer" class="ADXRXN "></div></div>
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 class="en" lang="en">
Required ARIA attributes must be provided1 element
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
<div id="mweb-unauth-container" role="main" class="ADXRXN"><div data-layout-shift-boundary-id="UnauthHomePageContainer" class="ADXRXN "></div></div>
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" id="viewport" 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" id="viewport" name="viewport">