PayPal paypal.com
Accessibility score
League position
8thof 10
Issues found
5
Audits passed
51
Accessibility score over time
weekly scans · last 6 months- Good · 90+
- Needs improvement · 70–89
- Poor · Below 70
This month's scan
Issues found
SeriousElements must meet minimum color contrast ratio thresholds2 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
<span class="brand-moment-content-headline heading-text-style heading-text-size-display-1">pay securely</span>
Fix any of the following:
- Element has insufficient color contrast of 1.79 (foreground color: #ffffff, background color: #60cdff, font size: 108.2pt (144.215px), font weight: bold). Expected contrast ratio of 3:1
<a id="manageCookiesLink" href="https://www.paypal.com/myaccount/privacy/cookiePrefs?locale=en_NZ" pagename="Send & Request Money, Shop, Manage Payments & More | PayPal NZ|managecookies" pa-marked="1">Manage your cookies and learn more.</a>
Fix any of the following:
- Element has insufficient color contrast of 4.27 (foreground color: #0070e0, background color: #f0f2f9, font size: 12.0pt (16px), font weight: normal). Expected contrast ratio of 4.5:1
SeriousElements must have their visible text as part of their accessible name1 element
Interactive widgets that support name from content must have aria-label or aria-labelledby values that match their visible text. Mismatches confuse voice control users who speak the visible label but activate a different function based on the hidden accessible name.
Failing Elements
<a data-testid="country-selector-trigger" href="#" class="glnv-base-link glnv-footer-link group glnv-country-selector-link" aria-disabled="false" aria-label="Change country or region">
Fix any of the following:
- Text inside the element is not included in the accessible name
SeriousFocused elements must not be entirely hidden by author-created content7 elements
Keyboard users have no pointer to show where they are. The focus indicator is their only cue, and a sticky header, footer, cookie banner, or other author-created overlay that completely hides the focused control strands them with no idea what will activate next.
Failing Elements
<a target="_self" href="/nz/webapps/mpp/about" class="glnv-base-link glnv-footer-link glnv-footer-captio..." aria-disabled="false">
<a target="_self" href="https://newsroom.paypal-corp.com/" class="glnv-base-link glnv-footer-link glnv-footer-captio..." aria-disabled="false">
<a target="_self" href="https://careers.pypl.com/home/" class="glnv-base-link glnv-footer-link glnv-footer-captio..." aria-disabled="false">
<a target="_self" href="/nz/webapps/mpp/accessibility" class="glnv-base-link glnv-footer-link glnv-footer-captio..." aria-disabled="false">
<a target="_self" href="https://www.paypal.com/privacy-center" class="glnv-base-link glnv-footer-link glnv-footer-captio..." aria-disabled="false">
<a target="_self" href="https://www.paypal.com/myaccount/privacy/cookiePre..." class="glnv-base-link glnv-footer-link glnv-footer-captio..." aria-disabled="false">
<a target="_self" href="/nz/webapps/mpp/ua/legalhub-full" class="glnv-base-link glnv-footer-link glnv-footer-captio..." aria-disabled="false">
ModerateHeading levels should only increase by one1 element
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Failing Elements
<h4 class="styles_text-title_medium__awycp4g CookieBanner_text" data-ppui-info="title-text" id="cookieTitle">
Fix any of the following:
- Heading order invalid
ModerateAll page content should be contained by landmarks2 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.
Failing Elements
<div slot="glnv-footer-after" class="glnv-shadow-dom-slot">
Fix any of the following:
- Some page content is not contained by landmarks
<div id="ccpaCookieContent_wrapper" class="CookieContent_wrapper">
Fix any of the following:
- Some page content is not contained by landmarks
Passed audits51 across 1 page
[role="img"] and [role="image"] elements must have alternative text5 elements
Screen readers cannot convert visual images with role="img" into text without an accessible alternative. All users with visual disabilities, from complete blindness to low vision and color blindness, require text alternatives to access the information that images convey.
Audit Elements
<div class="qr-code-image-container qr-code-appearance-default" role="img" aria-label="QR Code to scan for the PayPal app">
<div class="featured-split-section-view-media-container ppcmsnodeweb-5mr7i0" role="img" aria-label="UI of phone with sunglasses and PayPal button for checkout">
<div class="featured-split-section-view-media-container ppcmsnodeweb-1f5f95k" role="img" aria-label="Person smiling and looking at phone with overlay of digital wallet">
<div class="ppcmsnodeweb-18byuhn" role="img" aria-label="Person looking at their phone and smiling">
<div class="qr-code-image-container qr-code-appearance-default" role="img" aria-label="QrCode">
<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-NZ" dir="ltr" class="js">
<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-NZ" dir="ltr" class="js">
<li> elements must be contained in a <ul> or <ol>21 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="glnv-main-menu-nav-item" data-testid="main-menu-link-Wg7yYgPK0Gvc3dB0tqPsNF" id="Wg7yYgPK0Gvc3dB0tqPsNF_nav_item">
<li class="glnv-main-menu-nav-item" data-testid="main-menu-link-7GA39JFhU7ad9iV6NynwRT" id="7GA39JFhU7ad9iV6NynwRT_nav_item">
<li class="glnv-main-menu-nav-item" data-testid="main-menu-link-4LliMTTihLAYq7k6YQRtfj" id="4LliMTTihLAYq7k6YQRtfj_nav_item">
<li class="glnv-main-menu-nav-item" data-testid="main-menu-link-4PlzP8ap2C3eK7qumILoNH" id="4PlzP8ap2C3eK7qumILoNH_nav_item">
<li>
Showing first 5 of 21 audited elements.
<ul> and <ol> must only directly contain <li>, <script> or <template> elements7 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.
Audit Elements
<ul class="flex lg:items-center max-lg:flex-col max-lg:pt-4">
<ul class="flex lg:items-center max-lg:flex-col">
<ul>
<ul class="glnv-footer-nav-list">
<ul class="flex flex-wrap p-0 max-md:w-full">
Showing first 5 of 7 audited elements.
All page content should be contained by landmarks2075 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 class="document-body-root" data-hosted-by="ppcmsnodeweb" dir="ltr" data-source="1">
<div><!-- [globalnav:fragment:regionalbanner] --></div>
<div id="globalnav-header" data-nav-version="rebrand" data-nav-sub-version="v2" data-glnv-source="service"><div id="shadow-host-header" translate="no" class="glnv-shadow-host notranslate"></div></div>
<div id="shadow-host-header" translate="no" class="glnv-shadow-host notranslate"></div>
Showing first 5 of 2075 audited elements.
All touch targets must be 24px large, or leave sufficient space34 elements
Touch targets must be large enough or spaced far enough apart to be activated without accidentally hitting adjacent controls. This helps users on mobile devices, people with hand tremors or mobility impairments, users in shaking environments like public transit, and anyone using one hand or large fingers to interact with the interface.
Audit Elements
<a data-testid="header-logo" href="/nz/home" class="glnv-base-link block..." aria-disabled="false" style="background-image: ur...">
<button role="button" aria-expanded="false" id="Wg7yYgPK0Gvc3dB0tqPsNF" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<button role="button" aria-expanded="false" id="7GA39JFhU7ad9iV6NynwRT" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<a role="link" id="4LliMTTihLAYq7k6YQRtfj" href="https://developer.paypal.com/home" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Developer">Developer</span></a>
<a role="link" id="4PlzP8ap2C3eK7qumILoNH" href="/nz/cshelp/personal" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Help">Help</span></a>
Showing first 5 of 34 audited elements.
Alternative text of images should not be repeated as text1 element
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="Friends smiling outs..." aria-hidden="false" sizes="100vw" src="https://www.paypalob..." srcset="https://www.paypalob..." fetchpriority="high">
ARIA attributes must be used as specified for the element's role41 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
<a data-testid="header-logo" href="/nz/home" class="glnv-base-link block..." aria-disabled="false" style="background-image: ur...">
<button role="button" aria-expanded="false" id="Wg7yYgPK0Gvc3dB0tqPsNF" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<button role="button" aria-expanded="false" id="7GA39JFhU7ad9iV6NynwRT" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<a role="link" id="4LliMTTihLAYq7k6YQRtfj" href="https://developer.paypal.com/home" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Developer">Developer</span></a>
<a role="link" id="4PlzP8ap2C3eK7qumILoNH" href="/nz/cshelp/personal" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Help">Help</span></a>
Showing first 5 of 41 audited elements.
ARIA attributes must conform to valid names41 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
<a data-testid="header-logo" href="/nz/home" class="glnv-base-link block..." aria-disabled="false" style="background-image: ur...">
<button role="button" aria-expanded="false" id="Wg7yYgPK0Gvc3dB0tqPsNF" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<button role="button" aria-expanded="false" id="7GA39JFhU7ad9iV6NynwRT" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<a role="link" id="4LliMTTihLAYq7k6YQRtfj" href="https://developer.paypal.com/home" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Developer">Developer</span></a>
<a role="link" id="4PlzP8ap2C3eK7qumILoNH" href="/nz/cshelp/personal" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Help">Help</span></a>
Showing first 5 of 41 audited elements.
ARIA attributes must conform to valid values41 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
<a data-testid="header-logo" href="/nz/home" class="glnv-base-link block..." aria-disabled="false" style="background-image: ur...">
<button role="button" aria-expanded="false" id="Wg7yYgPK0Gvc3dB0tqPsNF" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<button role="button" aria-expanded="false" id="7GA39JFhU7ad9iV6NynwRT" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<a role="link" id="4LliMTTihLAYq7k6YQRtfj" href="https://developer.paypal.com/home" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Developer">Developer</span></a>
<a role="link" id="4PlzP8ap2C3eK7qumILoNH" href="/nz/cshelp/personal" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Help">Help</span></a>
Showing first 5 of 41 audited elements.
ARIA hidden element must not be focusable or contain focusable elements24 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 width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" aria-hidden="true" focusable="false" class="max-lg:hidden"><path d="M22.0264 9.00293L12 19.0283L1.97461 9.00293L3.38867 7.58887L12 16.2002L20.6123 7.58887L22.0264 9.00293Z" fill="black"></path></svg>
<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" aria-hidden="true" focusable="false" class="lg:hidden max-lg:size-4 icon-rotate">
<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" aria-hidden="true" focusable="false" class="size-4"><path d="M19 12.0029L8.97363 22.0293L7.55957 20.6152L16.1719 12.0029L7.55957 3.3916L8.97363 1.97754L19 12.0029Z" fill="black"></path></svg>
<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" aria-hidden="true" focusable="false" class="size-3"><path d="M19 12.0029L8.97363 22.0293L7.55957 20.6152L16.1719 12.0029L7.55957 3.3916L8.97363 1.97754L19 12.0029Z" fill="black"></path></svg>
<svg width="24" height="24" viewBox="0 0 24 24" fill="none" xmlns="http://www.w3.org/2000/svg" aria-hidden="true" focusable="false" class="size-3"><path d="M19 12.0029L8.97363 22.0293L7.55957 20.6152L16.1719 12.0029L7.55957 3.3916L8.97363 1.97754L19 12.0029Z" fill="black"></path></svg>
Showing first 5 of 24 audited elements.
ARIA role should be appropriate for the element18 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
<button role="button" aria-expanded="false" id="Wg7yYgPK0Gvc3dB0tqPsNF" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<button role="button" aria-expanded="false" id="7GA39JFhU7ad9iV6NynwRT" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<a role="link" id="4LliMTTihLAYq7k6YQRtfj" href="https://developer.paypal.com/home" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Developer">Developer</span></a>
<a role="link" id="4PlzP8ap2C3eK7qumILoNH" href="/nz/cshelp/personal" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Help">Help</span></a>
<div class="document-body" data-testid="document-body-element" role="main">
Showing first 5 of 18 audited elements.
ARIA roles used must conform to valid values15 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
<button role="button" aria-expanded="false" id="Wg7yYgPK0Gvc3dB0tqPsNF" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<button role="button" aria-expanded="false" id="7GA39JFhU7ad9iV6NynwRT" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<a role="link" id="4LliMTTihLAYq7k6YQRtfj" href="https://developer.paypal.com/home" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Developer">Developer</span></a>
<a role="link" id="4PlzP8ap2C3eK7qumILoNH" href="/nz/cshelp/personal" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Help">Help</span></a>
<div class="document-body" data-testid="document-body-element" role="main">
Showing first 5 of 15 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 class=" ccpaCookieBanner-acceptedAll" style="overflow: auto;">
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="glnv-root glnv-base-..." data-building-block="organism" data-theme="paypal60" style="max-height: 5.5rem;">
Buttons must have discernible text6 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 role="button" aria-expanded="false" id="Wg7yYgPK0Gvc3dB0tqPsNF" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<button role="button" aria-expanded="false" id="7GA39JFhU7ad9iV6NynwRT" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<button type="button" class="text-group-item-header" tabindex="0" id="tab-1" role="tab" aria-selected="true" aria-controls="featured-tab-content-1 featured-media-1" pa-marked="1">
<button type="button" class="text-group-item-header" tabindex="0" id="tab-2" role="tab" aria-selected="false" aria-controls="featured-tab-content-2 featured-media-2" pa-marked="1">
<button class="styles_button_base__..." data-ppui-info="" id="acceptAllButton" tab-index="0" pagename="Send & Request Money..." pa-marked="1">
Showing first 5 of 6 audited elements.
Certain ARIA roles must be contained by particular parents2 elements
ARIA roles with missing required parent elements cannot function as intended for assistive technology users. Parent-child relationships convey essential hierarchy and context, like showing where an item sits within a tree structure. Without proper parents, this critical relationship information is lost.
Audit Elements
<button type="button" class="text-group-item-header" tabindex="0" id="tab-1" role="tab" aria-selected="true" aria-controls="featured-tab-content-1 featured-media-1" pa-marked="1">
<button type="button" class="text-group-item-header" tabindex="0" id="tab-2" role="tab" aria-selected="false" aria-controls="featured-tab-content-2 featured-media-2" pa-marked="1">
Certain ARIA roles must contain particular children1 element
ARIA roles missing required child elements cannot perform their intended accessibility functions. Children provide essential context, like how a treeitem relates to its parent container and siblings. Without proper children, assistive technologies cannot convey this structural information to users.
Audit Elements
<div class="text-group-tabs-portal" role="tablist">
Content must reflow without two-dimensional scrolling3 elements
People who zoom to 400% or use a narrow viewport must be able to scroll in one direction only. A layout that still requires horizontal scrolling at 320 CSS pixels forces magnified readers to pan left and right line by line, which makes the page close to unusable.
Audit Elements
<div class="brand-moment-content-text" style="will-change: transform; transform: translateX(615....">
<div class="brand-moment-content-text" style="will-change: transform; transform: translateX(237....">
<div role="presentation" class="carousel-track" style="transition-duration: 0ms; transform: translateX(0p...">
Contentinfo 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.
Audit Elements
<footer data-building-block="organism" class="glnv-root glnv-base-font pb-[3.75rem] pt-[2.813rem] lg:pt-[4vw] lg:pb-[4vw] black" data-theme="paypal60" id="footer">
Deprecated ARIA roles must not be used15 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
<button role="button" aria-expanded="false" id="Wg7yYgPK0Gvc3dB0tqPsNF" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<button role="button" aria-expanded="false" id="7GA39JFhU7ad9iV6NynwRT" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<a role="link" id="4LliMTTihLAYq7k6YQRtfj" href="https://developer.paypal.com/home" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Developer">Developer</span></a>
<a role="link" id="4PlzP8ap2C3eK7qumILoNH" href="/nz/cshelp/personal" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Help">Help</span></a>
<div class="document-body" data-testid="document-body-element" role="main">
Showing first 5 of 15 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-NZ" dir="ltr" class="js">
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="glnv-root glnv-base-..." data-building-block="organism" data-theme="paypal60" style="max-height: 5.5rem;">
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 data-building-block="organism" class="glnv-root glnv-base-font pb-[3.75rem] pt-[2.813rem] lg:pt-[4vw] lg:pb-[4vw] black" data-theme="paypal60" id="footer">
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 class="document-body" data-testid="document-body-element" role="main">
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-NZ" dir="ltr" class="js">
Elements marked as presentational should be consistently ignored1 element
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 xmlns="http://www.w3.org/2000/svg" viewBox="0 0 167 56" fill="none" role="presentation" class="_phone-frame-logo-image_1ojo8_26">
Elements must meet minimum color contrast ratio thresholds29 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="glnv-nav-link-text" data-text="Personal">Personal</span>
<span class="glnv-nav-link-text" data-text="Business">Business</span>
<span class="glnv-nav-link-text" data-text="Developer">Developer</span>
<span class="glnv-nav-link-text" data-text="Help">Help</span>
<p class="body-text-style body-text-size-body-large-bold">Get the PayPal app</p>
Showing first 5 of 29 audited elements.
Elements must only use permitted ARIA attributes41 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
<a data-testid="header-logo" href="/nz/home" class="glnv-base-link block..." aria-disabled="false" style="background-image: ur...">
<button role="button" aria-expanded="false" id="Wg7yYgPK0Gvc3dB0tqPsNF" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<button role="button" aria-expanded="false" id="7GA39JFhU7ad9iV6NynwRT" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<a role="link" id="4LliMTTihLAYq7k6YQRtfj" href="https://developer.paypal.com/home" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Developer">Developer</span></a>
<a role="link" id="4PlzP8ap2C3eK7qumILoNH" href="/nz/cshelp/personal" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Help">Help</span></a>
Showing first 5 of 41 audited elements.
Elements must only use supported ARIA attributes41 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
<a data-testid="header-logo" href="/nz/home" class="glnv-base-link block..." aria-disabled="false" style="background-image: ur...">
<button role="button" aria-expanded="false" id="Wg7yYgPK0Gvc3dB0tqPsNF" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<button role="button" aria-expanded="false" id="7GA39JFhU7ad9iV6NynwRT" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<a role="link" id="4LliMTTihLAYq7k6YQRtfj" href="https://developer.paypal.com/home" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Developer">Developer</span></a>
<a role="link" id="4PlzP8ap2C3eK7qumILoNH" href="/nz/cshelp/personal" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Help">Help</span></a>
Showing first 5 of 41 audited elements.
Elements should not have tabindex greater than zero2 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
<button type="button" class="text-group-item-header" tabindex="0" id="tab-1" role="tab" aria-selected="true" aria-controls="featured-tab-content-1 featured-media-1" pa-marked="1">
<button type="button" class="text-group-item-header" tabindex="0" id="tab-2" role="tab" aria-selected="false" aria-controls="featured-tab-content-2 featured-media-2" pa-marked="1">
Focused elements must not be entirely hidden by author-created content31 elements
Keyboard users have no pointer to show where they are. The focus indicator is their only cue, and a sticky header, footer, cookie banner, or other author-created overlay that completely hides the focused control strands them with no idea what will activate next.
Audit Elements
<a data-testid="header-logo" href="/nz/home" class="glnv-base-link block indent-[-999em] bg-no-repeat ..." aria-disabled="false" style="background-image: url("https://www.paypalobje...">
<button role="button" aria-expanded="false" id="Wg7yYgPK0Gvc3dB0tqPsNF" class="glnv-base-link glnv-base-header-link glnv-link gln..." aria-disabled="false">
<button role="button" aria-expanded="false" id="7GA39JFhU7ad9iV6NynwRT" class="glnv-base-link glnv-base-header-link glnv-link gln..." aria-disabled="false">
<a role="link" id="4LliMTTihLAYq7k6YQRtfj" href="https://developer.paypal.com/home" class="glnv-base-link glnv-base-header-link glnv-link gln..." aria-disabled="false">
<a role="link" id="4PlzP8ap2C3eK7qumILoNH" href="/nz/cshelp/personal" class="glnv-base-link glnv-base-header-link glnv-link gln..." aria-disabled="false">
Showing first 5 of 31 audited elements.
Heading levels should only increase by one10 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h1 class="text-group-headline heading-text-style heading-text-size-headline-2">Send and request</h1>
<h1 class="text-group-headline heading-text-style heading-text-size-headline-2">money</h1>
<h2 class="text-group-headline heading-text-style heading-text-size-headline-4">Check out your way</h2>
<h3 class="text-group-headline heading-text-style heading-text-size-headline-4">Load your digital wallet</h3>
<h2 class="text-group-headline heading-text-style heading-text-size-headline-4">Security that’s</h2>
Showing first 5 of 10 audited elements.
Headings should not be empty11 elements
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h1 class="text-group-headline heading-text-style heading-text-size-headline-2">Send and request</h1>
<h1 class="text-group-headline heading-text-style heading-text-size-headline-2">money</h1>
<h2 class="text-group-headline heading-text-style heading-text-size-headline-4">Check out your way</h2>
<h3 class="text-group-headline heading-text-style heading-text-size-headline-4">Load your digital wallet</h3>
<h2 class="text-group-headline heading-text-style heading-text-size-headline-4">Security that’s</h2>
Showing first 5 of 11 audited elements.
IDs used in ARIA and labels must be unique6 elements
Duplicate IDs break the accessibility of ARIA elements, form labels, and table headers. When IDs are duplicated, assistive technologies and scripts only reference the first instance, causing subsequent elements with the same ID to be ignored or incorrectly associated.
Audit Elements
<div id="featured-media-1" class="media-item media-item-media-size-3-4 media-item-layout-default media-active ppcmsnodeweb-1f8sh49">
<div id="featured-media-2" class="media-item media-item-media-size-3-4 media-item-layout-default media-next ppcmsnodeweb-1f8sh49">
<button type="button" class="text-group-item-header" tabindex="0" id="tab-1" role="tab" aria-selected="true" aria-controls="featured-tab-content-1 featured-media-1" pa-marked="1">
<button type="button" class="text-group-item-header" tabindex="0" id="tab-2" role="tab" aria-selected="false" aria-controls="featured-tab-content-2 featured-media-2" pa-marked="1">
<div class="text-group-item-info content-active" aria-hidden="false" id="featured-tab-content-1" role="tabpanel" aria-labelledby="tab-1" style="opacity: 1;">
Showing first 5 of 6 audited elements.
Images must have alternative text1 element
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="Friends smiling outs..." aria-hidden="false" sizes="100vw" src="https://www.paypalob..." srcset="https://www.paypalob..." fetchpriority="high">
Inline text spacing must be adjustable with custom stylesheets11 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 class=" ccpaCookieBanner-acceptedAll" style="overflow: auto;">
<header class="glnv-root glnv-base-..." data-building-block="organism" data-theme="paypal60" style="max-height: 5.5rem;">
<div class="box-inherit relative lg:bg-primary lg:py-0 xl:max-w-screen xl:ps-0 xl:pe-0 xl:gap-clamp-default xl:grid xl:grid-cols-lg xl:relative xl-plus:grid-cols-xxl 2xl:grid-cols-header-2xl" style="max-height: 5.5rem; min-height: 5.5rem; transition: min-height 0.3s; overflow: hidden;">
<a data-testid="header-logo" href="/nz/home" class="glnv-base-link block..." aria-disabled="false" style="background-image: ur...">
<div class="_hero-homepage-stack-ppe-grid-content_1btgq_122 ppcmsnodeweb-ltk1x" style="--top-content-translate:0vh">
Showing first 5 of 11 audited elements.
Interactive controls must not be nested13 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 role="button" aria-expanded="false" id="Wg7yYgPK0Gvc3dB0tqPsNF" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<button role="button" aria-expanded="false" id="7GA39JFhU7ad9iV6NynwRT" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<img alt="Friends smiling outs..." aria-hidden="false" sizes="100vw" src="https://www.paypalob..." srcset="https://www.paypalob..." fetchpriority="high">
<div class="qr-code-image-container qr-code-appearance-default" role="img" aria-label="QR Code to scan for the PayPal app">
<div class="featured-split-section-view-media-container ppcmsnodeweb-5mr7i0" role="img" aria-label="UI of phone with sunglasses and PayPal button for checkout">
Showing first 5 of 13 audited elements.
Interactive elements must have a visible focus indicator39 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<a data-testid="header-logo" href="/nz/home" class="glnv-base-link block indent-[-999em] bg-no-repeat ..." aria-disabled="false" style="background-image: url("https://www.paypalobje...">
<button role="button" aria-expanded="false" id="Wg7yYgPK0Gvc3dB0tqPsNF" class="glnv-base-link glnv-base-header-link glnv-link gln..." aria-disabled="false">
<button role="button" aria-expanded="false" id="7GA39JFhU7ad9iV6NynwRT" class="glnv-base-link glnv-base-header-link glnv-link gln..." aria-disabled="false">
<a role="link" id="4LliMTTihLAYq7k6YQRtfj" href="https://developer.paypal.com/home" class="glnv-base-link glnv-base-header-link glnv-link gln..." aria-disabled="false">
<a role="link" id="4PlzP8ap2C3eK7qumILoNH" href="/nz/cshelp/personal" class="glnv-base-link glnv-base-header-link glnv-link gln..." aria-disabled="false">
Showing first 5 of 39 audited elements.
Keyboard focus must be able to leave every component it can enter0 elements
Keyboard users move through a page with Tab, Shift+Tab, arrow keys and Escape. When focus enters a component and none of those keys lets it leave, the rest of the page becomes unreachable and the only way out is to reload or abandon it.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination5 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="glnv-root glnv-base-..." data-building-block="organism" data-theme="paypal60" style="max-height: 5.5rem;">
<nav id="main-menu" class="flex flex-1 h-12 max...">
<div class="document-body" data-testid="document-body-element" role="main">
<nav class="_hero-segment-control-group_1rcd2_1 paypal60" aria-label="Personal and Business page">
<footer data-building-block="organism" class="glnv-root glnv-base-font pb-[3.75rem] pt-[2.813rem] lg:pt-[4vw] lg:pb-[4vw] black" data-theme="paypal60" id="footer">
Links must be distinguishable without relying on color3 elements
People with low vision or color blindness cannot visually distinguish links from surrounding text without sufficient color contrast (3:1 ratio minimum). When link colors are too similar to regular text, users with visual impairments cannot identify which text is clickable.
Audit Elements
<a href="https://www.paypal.com/nz/legalhub/paypal/useragreement-full" target="_self" rel="" class="html-text-renderer-link multi-line-text-paragraph" data-pa-click="{"link":"Disclosure-Link--User Agreement","event_name":"text_link_clicked"}" pa-marked="1"><a href="https://www.paypal.com/nz/digital-wallet/paypal-consumer-fees" target="_self" rel="" class="html-text-renderer-link multi-line-text-paragraph" data-pa-click="{"link":"Disclosure-Link--See fees","event_name":"text_link_clicked"}" pa-marked="1"><a id="manageCookiesLink" href="https://www.paypal.com/myaccount/privacy/cookiePrefs?locale=en_NZ" pagename="Send & Request Money, Shop, Manage Payments & More | PayPal NZ|managecookies" pa-marked="1">Manage your cookies and learn more.</a>
Links must have discernible text31 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 data-testid="header-logo" href="/nz/home" class="glnv-base-link block..." aria-disabled="false" style="background-image: ur...">
<a role="link" id="4LliMTTihLAYq7k6YQRtfj" href="https://developer.paypal.com/home" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Developer">Developer</span></a>
<a role="link" id="4PlzP8ap2C3eK7qumILoNH" href="/nz/cshelp/personal" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Help">Help</span></a>
<a id="ul-btn" data-cta-type="login" href="/signin" class="glnv-base-link glnv-..." aria-disabled="false">
<a id="signup-button" data-cta-type="signup" href="/nz/webapps/mpp/acco..." class="glnv-base-link glnv-..." aria-disabled="false">
Showing first 5 of 31 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
<div class="document-body" data-testid="document-body-element" role="main">
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-NZ" dir="ltr" class="js">
Page 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.
Audit Elements
<html lang="en-NZ" dir="ltr" class="js">
Required ARIA attributes must be provided15 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
<button role="button" aria-expanded="false" id="Wg7yYgPK0Gvc3dB0tqPsNF" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<button role="button" aria-expanded="false" id="7GA39JFhU7ad9iV6NynwRT" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-nav-link-submenu glnv-main-menu-nav-link" aria-disabled="false">
<a role="link" id="4LliMTTihLAYq7k6YQRtfj" href="https://developer.paypal.com/home" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Developer">Developer</span></a>
<a role="link" id="4PlzP8ap2C3eK7qumILoNH" href="/nz/cshelp/personal" class="glnv-base-link glnv-base-header-link glnv-link glnv-nav-link group glnv-main-menu-nav-link" aria-disabled="false"><span class="glnv-nav-link-text" data-text="Help">Help</span></a>
<div class="document-body" data-testid="document-body-element" role="main">
Showing first 5 of 15 audited elements.
Text must remain readable when spacing is increased0 elements
People with low vision and dyslexia increase line height, letter spacing, word spacing, and paragraph spacing so they can read. Fixed-height boxes and overflow: hidden containers clip or overlap that text, which is a loss of content under WCAG 1.4.12.
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 name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
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 name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
How does your site stack up against PayPal?
Run the same automated WCAG 2.2 checks we run on the scoreboard.
More in Banking & Finance
- Chase100 out of 100, good
- Citibank95 out of 100, good
- HSBC95 out of 100, good
- Barclays85 out of 100, needs improvement
- Capital One85 out of 100, needs improvement
- Charles Schwab85 out of 100, needs improvement
- Wells Fargo85 out of 100, needs improvement
- Fidelity58 out of 100, poor
- Bank of America31 out of 100, poor