Skip to content
https://xe.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #ffffff
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Warning::
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
BANNER header MAIN CONTENTINFO footer

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

B
Form Accessibility
2 of 5 controls have issues
REVIEW
2 of 5 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">; <input type="text">
Info::
3 control(s) properly labeled
5 controls
3 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
emailemailEmail addressaria-label
inputtextReceiving amountaria-label
inputtextReceiving amountaria-label
inputtext(Type to search...)placeholder only
inputtext(Type to search...)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text">; <input type="text">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404: This page could not be found. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Xe
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Xe ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode standalone ✓
Name Xe Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
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
h1 International money transfers and global…
1.15:1
#000000
on
#040E43
needs 3.0:1 (large text)
32px · mid-page
h2 Global currency conversions
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
24px · bottom of viewport
h2 International money transfers made easy
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Xe for business
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Sign up for free
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Get a quote
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Add your recipient
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Verify your identity
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Confirm the quote
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Track your transfer
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
19px · bottom of viewport
h3 International transfers
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Rate alerts
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Historical currency rates
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
19px · bottom of viewport
h3 IBAN calculator
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Currency email updates
1.16:1
#000000
on
#161616
needs 3.0:1 (large text)
19px · bottom of viewport
title Xe: Currency Exchange Rates and Internat…
1.15:1
#000000
on
#040E43
needs 4.5:1 (normal text)
16px · top of page (header area)
a Get the App
1.15:1
#000000
on
#040E43
needs 4.5:1 (normal text)
16px · top of page (header area)
div Toggle menu
1.15:1
#000000
on
#040E43
needs 4.5:1 (normal text)
16px · top of page (header area)
a Personal
1.15:1
#000000
on
#040E43
needs 4.5:1 (normal text)
16px · top of page (header area)
a Business
1.15:1
#000000
on
#040E43
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 International money …1.15:13.0:1
#000000
#040E43
Fail
h2 Global currency conv…1.16:13.0:1
#000000
#161616
Fail
h2 International money …1.16:13.0:1
#000000
#161616
Fail
h2 Xe for business1.16:13.0:1
#000000
#161616
Fail
h3 Sign up for free1.16:13.0:1
#000000
#161616
Fail
h3 Get a quote1.16:13.0:1
#000000
#161616
Fail
h3 Add your recipient1.16:13.0:1
#000000
#161616
Fail
h3 Verify your identity1.16:13.0:1
#000000
#161616
Fail
h3 Confirm the quote1.16:13.0:1
#000000
#161616
Fail
h3 Track your transfer1.16:13.0:1
#000000
#161616
Fail
h3 International transf…1.16:13.0:1
#000000
#161616
Fail
h3 Rate alerts1.16:13.0:1
#000000
#161616
Fail
h3 Historical currency …1.16:13.0:1
#000000
#161616
Fail
h3 IBAN calculator1.16:13.0:1
#000000
#161616
Fail
h3 Currency email updat…1.16:13.0:1
#000000
#161616
Fail
title Xe: Currency Exchang…1.15:14.5:1
#000000
#040E43
Fail
a Get the App1.15:14.5:1
#000000
#040E43
Fail
div Toggle menu1.15:14.5:1
#000000
#040E43
Fail
a Personal1.15:14.5:1
#000000
#040E43
Fail
a Business1.15:14.5:1
#000000
#040E43
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.

B
Lighthouse Accessibility Audits
Score 81/100 — 7 failing, 23 passed
REVIEW
81

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.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
It looks like you're in the US. Visit the US site for the best experience. Swi… main.__className_f367f3 > div.pointer-events-none > div.pointer-events-auto > div

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.py-6 > div.mt-4 > div.flex > button.size-4 div.py-6 > div.mt-4 > div.flex > button.size-4
div.py-6 > div.mt-4 > div.flex > button.size-4 div.py-6 > div.mt-4 > div.flex > button.size-4
div.py-6 > div.mt-4 > div.flex > button.size-4 div.py-6 > div.mt-4 > div.flex > button.size-4
div.py-6 > div.mt-4 > div.flex > button.size-4 div.py-6 > div.mt-4 > div.flex > button.size-4
div.py-6 > div.mt-4 > div.flex > button.size-4 div.py-6 > div.mt-4 > div.flex > button.size-4
div.py-6 > div.mt-4 > div.flex > button.size-4 div.py-6 > div.mt-4 > div.flex > button.size-4
div.py-6 > div.mt-4 > div.flex > button.size-4 div.py-6 > div.mt-4 > div.flex > button.size-4
div.py-6 > div.mt-4 > div.flex > button.size-4 div.py-6 > div.mt-4 > div.flex > button.size-4
div.py-6 > div.mt-4 > div.flex > button.size-4 div.py-6 > div.mt-4 > div.flex > button.size-4

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
footer.flex > div.flex > div.flex > a footer.flex > div.flex > div.flex > a

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
135824 div > p.text-lg > span > span.text-xe-neutral-700

These are opportunities to improve the legibility of your content.

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
Everything allways work like promised div.flex > div.min-w-0 > div.grid > h4.text-lg

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 Sign up for free It only takes a few minutes—all you need is an email addres… div.overflow-hidden > div.flex > div.min-w-0 > li.grid
2 Get a quote Choose your destination country, send & recipient currency, and … div.overflow-hidden > div.flex > div.min-w-0 > li.grid
3 Add your recipient Provide your recipient's payment information (you'll need… div.overflow-hidden > div.flex > div.min-w-0 > li.grid
4 Verify your identity For some transfers, we may need identifying documents t… div.overflow-hidden > div.flex > div.min-w-0 > li.grid
5 Confirm the quote Confirm and fund your transfer with a bank account, credit… div.overflow-hidden > div.flex > div.min-w-0 > li.grid
6 Track your transfer See where your money is and when it arrives to your reci… div.overflow-hidden > div.flex > div.min-w-0 > li.grid

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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
Download the app div.grid > div.flex > div.mt-6 > a.polymorphic-btn
Explore Xe for business div.z-10 > div.flex > div.mt-6 > a.polymorphic-btn
○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
●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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○Links are distinguishable without relying on color.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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
○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.
A
Heading Hierarchy
31 headings, 1 skip(s)
PASS
31 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 International money transfers and global currency conversions
  • H2 Global currency conversions
  • H2 International money transfers made easy
  • H2 Live exchange rates
  • H3 Compare 100+ currencies in real time & find the right moment to transfer funds
  • H2 How to send money online with Xe
  • H3 Sign up for free
  • H3 Get a quote
  • H3 Add your recipient
  • H3 Verify your identity
  • H3 Confirm the quote
  • H3 Track your transfer
  • H3 Manage your currencies on the go with the Xe app
  • H2 Xe currency tools
  • H3 FX insights, advanced indicators, live news feeds & customizable dashboards
  • H3 International transfers
  • H3 Rate alerts
  • H3 Historical currency rates
  • H3 IBAN calculator
  • H3 Currency email updates
  • H2 Xe currency data API
  • H3 Providing commercial grade exchange rates to 3000+ companies worldwide
  • H4 The world's most trusted source for currency data
  • H2 Xe is trusted by millions around the globe
  • H4 Everything allways work like promised skipped
  • H4 The service is easy to use and keeps me…
  • H4 It’s easy to use….
  • H2 Xe for business
  • H2 Send money destinations
  • H3 Connecting the world
  • H2 Simplifying money transfers

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

A+
Alt Text Quality
All 49 images OK
PASS
All 49 images OK
Info::
26 decorative image(s) correctly marked
Info::
23 image(s) with good alt text
49 images 23 good alt text 26 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback