Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 3 REVIEW 5 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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 ✗

Link & Button Quality

Action

6 issue(s) across 19 links and 0 buttons

REVIEW

6 issue(s) across 19 links and 0 buttons

6 link(s) with generic text

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

Got: https://venmo.com/pay/start/ ("Learn more"); https://venmo.com/stash-rewards ("Learn more"); https://venmo.com/send-receive/start ("Learn more"); https://venmo.com/business/start ("Learn more"); https://venmo.com/about/crypto/ ("Learn more"); https://help.venmo.com/hc/en-us/articles/360021199834-Customer-Identification… ("Learn more")

6 link(s) open in new tab without warning

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

Got: https://venmo.com/legal/us-user-agreement/#rewards; https://venmo.com/legal/us-user-agreement#rewards; https://www.synchronybankterms.com/gecrbterms/html/VenmoApplyTerms_combo.htm; https://venmo.com/resources/our-fees/#longform; https://venmo.com/legal/crypto-terms/; https://www.paxos.com/terms-and-conditions/stablecoin-terms-conditions

7 link(s) with descriptive text

19 links

0 empty

6 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://venmo.com/pay/start/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Start
https://venmo.com/legal/us-user-agreemen…	Venmo Stash bundle terms and e…	new tab	Add '(opens in new tab)' to text
https://venmo.com/stash-rewards	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Stash Rewards
https://venmo.com/send-receive/start	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Start
https://venmo.com/business/start	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Start
https://venmo.com/about/crypto/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Crypto
https://venmo.com/legal/us-user-agreemen…	Venmo Stash bundle terms and e…	new tab	Add '(opens in new tab)' to text
https://help.venmo.com/hc/en-us/articles…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: 360021199834 Customer Identification Document Requirements
https://www.synchronybankterms.com/gecrb…	Terms & Rates	new tab	Add '(opens in new tab)' to text
https://venmo.com/resources/our-fees/#lo…	Venmo	new tab	Add '(opens in new tab)' to text
https://venmo.com/legal/crypto-terms/	Venmo’s disclosure	new tab	Add '(opens in new tab)' to text
https://www.paxos.com/terms-and-conditio…	Paxos US Dollar-Backed Stablec…	new tab	Add '(opens in new tab)' to text

7 links and buttons have descriptive text

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

https://venmo.com/pay/start/ ("Learn more"); https://venmo.com/stash-rewards ("Learn more"); https://venmo.com/send-receive/start ("Learn more"); https://venmo.com/business/start ("Learn more"); https://venmo.com/about/crypto/ ("Learn more"); https://help.venmo.com/hc/en-us/articles/360021199834-Customer-Identification… ("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://venmo.com/legal/us-user-agreement/#rewards; https://venmo.com/legal/us-user-agreement#rewards; https://www.synchronybankterms.com/gecrbterms/html/VenmoApplyTerms_combo.htm; https://venmo.com/resources/our-fees/#longform; https://venmo.com/legal/crypto-terms/; https://www.paxos.com/terms-and-conditions/stablecoin-terms-conditions

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

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Venmo | Page Not Found ✓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

Heading Hierarchy

13 headings

PASS

13 headings

Multiple H1 headings (3 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 Pay friends.
H1 Pay for duplicate H1
H1 everything. duplicate H1
H2 Meet Venmo
H2 Stash rewards.
H2 Venmo everything, online and in-store.
H3 The Venmo Debit Card.
H3 Check out with Venmo.
H3 The Venmo Credit Card.
H2 Venmo your friends.
H2 Grow a business.
H2 Purchase crypto.
H2 Get the Venmo app.

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Pay friends.	17.32:1	3.0:1	#000000	#E3EAF2	Pass
h1 Pay for	17.90:1	3.0:1	#000000	#DEEFFF	Pass
h1 everything.	17.90:1	3.0:1	#000000	#DEEFFF	Pass
h2 Meet Venmo	17.90:1	3.0:1	#000000	#DEEFFF	Pass
h2 Stash rewards.	17.90:1	3.0:1	#000000	#DEEFFF	Pass
h2 Venmo everything, on…	17.74:1	3.0:1	#000000	#DDEEFE	Pass
h2 Venmo your friends.	17.58:1	3.0:1	#000000	#DCEDFD	Pass
h2 Grow a business.	17.58:1	3.0:1	#000000	#DCEDFD	Pass
h2 Purchase crypto.	17.58:1	3.0:1	#000000	#DCEDFD	Pass
h2 Get the Venmo app.	17.58:1	3.0:1	#000000	#DCEDFD	Pass
h3 The Venmo Debit Card…	17.10:1	3.0:1	#000000	#D9EAFA	Pass
h3 Check out with Venmo…	17.58:1	3.0:1	#000000	#DCEDFD	Pass
h3 The Venmo Credit Car…	17.58:1	3.0:1	#000000	#DCEDFD	Pass
title Pay Friends \| Paymen…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Easily send money to…	17.90:1	4.5:1	#000000	#DEEFFF	Pass
a Learn more	17.90:1	4.5:1	#000000	#DEEFFF	Pass
p Scan to download the…	17.90:1	4.5:1	#000000	#DEEFFF	Pass
a Download Venmo	17.90:1	4.5:1	#000000	#DEEFFF	Pass
div *Venmo purchase rest…	17.90:1	4.5:1	#000000	#DEEFFF	Pass
p Do more Stash, get m…	17.90:1	4.5:1	#000000	#DEEFFF	Pass

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

Lighthouse Accessibility Audits

Score 94/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.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.document-body > section._wrapper_1wuz2_1 > div._sticky-qr-stealth_1wuz2_10 > a#sticky-qr-badge `div.document-body > section._wrapper_1wuz2_1 > div._sticky-qr-stealth_1wuz2_10 > a#sticky-qr-badge`

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js `html.js`

These items highlight common accessibility best practices.

○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.

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[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.

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

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

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

○`[lang]` attributes have a valid value

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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

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

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

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