Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureActionNo landmarksFIX
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>.
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.
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
F404 Error PageActionSoft 404 detectedFIX
The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.
DWeb ManifestActionNot foundFIX
No web manifest found.
DPrint StylesheetActionNo print stylesFIX
BFavicon & Branding17 icon(s) detectedREVIEW
BDark Mode SupportDark mode detectedREVIEW
Detection limited to meta tags and inline styles.
CColor Contrast (Screenshot)Action20 text elements analyzed, 1 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
1 contrast failures on background images/gradients
These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Fast, secure money t… | 19.26:1 | 3.0:1 | #000000 | #F5F5F5 | Pass |
| h1 Flexible and conveni… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Transfer to bank acc… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Send to mobile walle… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Send cash for pickup… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Reload mobile phones | 19.57:1 | 3.0:1 | #000000 | #F5F7FA | Pass |
| h1 Be there, even if yo… | 1.07:1 | 3.0:1 | #FFFFFF | #F5F7FA | Fail |
| h1 Your transfers, our … | 19.57:1 | 3.0:1 | #000000 | #F5F7FA | Pass |
| h1 Up front fees and ra… | 19.57:1 | 3.0:1 | #000000 | #F5F7FA | Pass |
| h1 Send with confidence | 18.89:1 | 3.0:1 | #000000 | #F1F3F6 | Pass |
| h1 Support when you nee… | 18.89:1 | 3.0:1 | #000000 | #F1F3F6 | Pass |
| h1 Trusted by millions | 18.89:1 | 3.0:1 | #000000 | #F1F3F6 | Pass |
| h1 Wherever life takes … | 18.89:1 | 3.0:1 | #000000 | #F1F3F6 | Pass |
| title Xoom, a PayPal Servi… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Send Money | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Transfer Money | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Send to Wallets | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Send Cash | 19.57:1 | 4.5:1 | #000000 | #F5F7FA | Pass |
| a Reload Phones | 19.57:1 | 4.5:1 | #000000 | #F5F7FA | Pass |
| p When sending money t… | 18.89:1 | 4.5:1 | #000000 | #F1F3F6 | 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.
AHeading Hierarchy13 headingsPASS
- H1 Fast, secure money transfers
- H1 Flexible and convenient options for your transfers duplicate H1
- H1 Transfer to bank accounts and debit cards duplicate H1
- H1 Send to mobile wallets, UPI, and PIX duplicate H1
- H1 Send cash for pickup and delivery duplicate H1
- H1 Reload mobile phones duplicate H1
- H1 Be there, even if you can’t be there. duplicate H1
- H1 Your transfers, our priority duplicate H1
- H1 Up front fees and rates duplicate H1
- H1 Send with confidence duplicate H1
- H1 Support when you need it duplicate H1
- H1 Trusted by millions duplicate H1
- H1 Wherever life takes you, stay connected with the Xoom app. duplicate H1
A page should have only one H1. Multiple H1s dilute the document outline.
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 QualityAll 9 images OKPASS
A+Form AccessibilityNo form controlsPASS
A+Link & Button Quality10 links, 0 buttons — all OKPASS
A+Lighthouse Accessibility AuditsScore 98/100 — 1 failing, 23 passedPASS
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.
Best practices
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.