Buttons missing accessible name
CriticalButtons must have discernible text for screen reader users.
WCAG 4.1.24 element(s) affected
<button><button><button><button>
How to fix
Add text content, aria-label, or title to all <button> elements.
Accessibility audit of venmo.com — scanned on Feb 20, 2026
Finance9 issues found across 3 categories
Buttons must have discernible text for screen reader users.
WCAG 4.1.2<button><button><button><button>Add text content, aria-label, or title to all <button> elements.
Video content must have captions for deaf and hard-of-hearing users.
WCAG 1.2.2<video> "//videos.ctfassets.net/gkyt4bl1j2fs/176XGHpVphvQPk4FesazHF/0"<video> "//videos.ctfassets.net/gkyt4bl1j2fs/3vDJQSZdJqYvq8q7k8A1Kn/a"Add closed captions or subtitles to all video content.
Headings should follow a logical order (h1 → h2 → h3) without skipping levels.
WCAG 1.3.1<h6> "*Venmo purchase restrictions apply" (after h2)<h6> "Venmo Stash terms and exclusions apply. Max $100 c" (after h2)Restructure headings to follow sequential order. Don't skip from h1 to h3.
Element IDs must be unique to ensure correct assistive technology behavior.
WCAG 4.1.1id="Home | Hero | Video | Pause | Paused"id="Home | Hero | Video | Play"id="Hide on Desktop"id="Home | Pay Friends | Content | Text | Formatting"id="Hide on Mobile"Make each id attribute value unique within the page.
Elements with tabindex > 0 disrupt natural tab order and confuse keyboard users.
WCAG 2.4.3<li tabindex="7"><li tabindex="7"><li tabindex="4"><li tabindex="1"><li tabindex="2">Remove positive tabindex values. Use tabindex="0" or tabindex="-1" only.
Pages should have a mechanism to bypass repeated navigation blocks.
WCAG 2.4.1No skip navigation link foundAdd a 'Skip to main content' link as the first focusable element on the page.
Interactive elements must have visible focus indicators for keyboard users.
WCAG 2.4.7<div style="...outline:none...">Ensure :focus styles are visible. Don't use outline: none without a replacement.
Links must have descriptive text that indicates their purpose. Generic text like 'click here' or 'read more' does not help screen reader users understand where the link goes.
WCAG 2.4.4<a href="/pay/start/">learn more</a><a href="https://help.venmo.com/hc/en-us/articles/360021199834-Custom">learn more</a>Replace generic link text with descriptive text, e.g., 'Read our accessibility guide' instead of 'Read more'.
List items must be contained within <ul>, <ol>, or <dl> elements.
WCAG 1.3.1<li> inside <div>Ensure <li> elements are direct children of <ul> or <ol>.
Here are the most impactful changes venmo.com should make to improve accessibility:
Add text content, aria-label, or title to all <button> elements.
Add closed captions or subtitles to all video content.
Remove positive tabindex values. Use tabindex="0" or tabindex="-1" only.
venmo.com scored 19/100 (grade F) on our accessibility audit. This score reflects automated checks against WCAG 2.1 Level AA criteria.
Our scan found 9 accessibility issues on venmo.com. Full WCAG compliance requires addressing all critical and major issues identified above.
The European Accessibility Act requires websites to meet WCAG 2.1 AA standards. Check the detailed report above to see venmo.com's compliance status.
See the full issue list above with severity levels, affected elements, and recommended fixes for venmo.com.
Get a free accessibility report for your website in seconds.