Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 5 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #012169

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

8 landmarks

REVIEW

8 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

Heading Hierarchy

Action

40 headings, 1 skip(s)

REVIEW

40 headings, 1 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 PayPal for You
H3 Shopping & Rewards
H3 Send & Receive
H3 Manage Your Money
H2 PayPal Open
H3 Business Types
H3 Accept Payments
H3 Risk & Operations
H3 Financial Services
H2 PayPal Ads
H2 Pay, send, and save smarter
H2 Shop in stores and online
H2 Get cash back on the brands you love
H3 01234567%cash back
H3 +012345%cash back
H2 Pay now or pay over time.
H2 It’s your choice.
H3 Pay in 4
H3 interest-free
H3 payments
H3 Pay Monthly in 3,
H3 6, 12, or 24
H3 payments
H3 Pay Monthly
H3 in store5
H3 Pay with the PayPal Cashback Mastercard®
H3 Special financing with the PayPal Credit Card
H2 Safety and privacy are built in
H2 Securely send money to just about anyone, anywhere8
H3 Send
H3 Receive
H3 Split
H3 Pool
H2 Make your money
H2 work harder.
H2 It’s easy. Really easy.
H2 Get 3.50% APY12 with your PayPal Savings account
H2 Crypto the easy way
H2 All in thePayPalapp
H4 If you accept cookies, we’ll use them to improve and customize your experience and enable our partners to show you personalized PayPal ads when you visit other sites. Manage cookies and learn more skipped

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found - PayPal ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

9 icon(s) detected

REVIEW

9 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h2 Pay, send, and save smarter

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Shop in stores and online

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get cash back on the brands you love

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Pay now or pay over time.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 It’s your choice.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Safety and privacy are built in

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Securely send money to just about anyone…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Make your money

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 work harder.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 It’s easy. Really easy.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Get 3.50% APY

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 with your PayPal Savings account

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Crypto the easy way

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Pay in 4

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 interest-free

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 payments

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Pay Monthly in 3,

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 6, 12, or 24

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 payments

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Pay Monthly

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Pay, send, and save …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Shop in stores and …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Get cash back on the…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Pay now or pay over�…	1.00:1	3.0:1	#000000	#000000	Fail
h2 It’s your choice.	1.00:1	3.0:1	#000000	#000000	Fail
h2 Safety and privacy a…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Securely send money …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Make your money	1.00:1	3.0:1	#000000	#000000	Fail
h2 work harder.	1.00:1	3.0:1	#000000	#000000	Fail
h2 It’s easy. Really …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Get 3.50% APY	1.00:1	3.0:1	#000000	#000000	Fail
h2 with your PayPal Sav…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Crypto the easy way	1.00:1	3.0:1	#000000	#000000	Fail
h3 Pay in 4	1.00:1	3.0:1	#000000	#000000	Fail
h3 interest-free	1.00:1	3.0:1	#000000	#000000	Fail
h3 payments	1.00:1	3.0:1	#000000	#000000	Fail
h3 Pay Monthly in 3,	1.00:1	3.0:1	#000000	#000000	Fail
h3 6, 12, or 24	1.00:1	3.0:1	#000000	#000000	Fail
h3 payments	1.00:1	3.0:1	#000000	#000000	Fail
h3 Pay Monthly	1.00:1	3.0:1	#000000	#000000	Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+

Alt Text Quality

All 6 images OK

PASS

All 6 images OK

6 image(s) with good alt text

6 images 6 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

1 issue(s) across 117 links and 15 buttons

PASS

1 issue(s) across 117 links and 15 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://www.paypal.com/us/digital-wallet/ways-to-pay/credit-services/paypal-credit ("Learn More")

2 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.synchronycredit.com/gecrbterms/html/PayPalCashbackRewardsTerms.htm; https://www.synchronybankterms.com/gecrbterms/html/PayPalCashbackApplyTerms_combo.htm

114 link(s) with descriptive text

117 links

0 empty

1 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.paypal.com/us/digital-wallet…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Paypal Credit
https://www.synchronycredit.com/gecrbter…	Rewards Program Terms	new tab	Add '(opens in new tab)' to text
https://www.synchronybankterms.com/gecrb…	See Terms & Rates	new tab	Add '(opens in new tab)' to text

129 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://www.paypal.com/us/digital-wallet/ways-to-pay/credit-services/paypal-credit ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

https://www.synchronycredit.com/gecrbterms/html/PayPalCashbackRewardsTerms.htm; https://www.synchronybankterms.com/gecrbterms/html/PayPalCashbackApplyTerms_combo.htm

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Lighthouse Accessibility Audits

Score 98/100 — 2 failing, 24 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
If you accept cookies, we’ll use them to improve and customize your experience … `div.CookieBanner_container_wrapper > div.CookieBanner_content_wrapper > div#ccpaCookieContent_wrapper > h4#cookieTitle`

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Send `div.carousel > div > div.page-nav-container > button.carousel-indicator`
Receive `div.carousel > div > div.page-nav-container > button.carousel-indicator`
Split `div.carousel > div > div.page-nav-container > button.carousel-indicator`
Pool `div.carousel > div > div.page-nav-container > button.carousel-indicator`
United States `div._container_1jad8_1335 > div._row_1jad8_1149 > div._links-container_1jad8_1152 > a.glnv-base-link`

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.