Skip to content
https://westernunion.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (missing!) CONTENTINFO footer

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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
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::
Hamburger menu detected (responsive design)
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 69/100 — 9 failing, 19 passed
FIX
69

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Colombia Enviar a div.col > div.row > div.col > div.wuds-dropdown
Envía dinero a prácticamente cualquier lugar div.col > div.w-100 > div.bdr-thin-tp > div#Enva-dinero-a-prcticamente-cualquier-lugar
Recogida en efectivo, incluso al enviar por Internet div.col > div.w-100 > div.bdr-thin-tp > div#Recogida-en-efectivo-incluso-al-enviar-por-Internet
Transferencias de dinero directas al banco div.col > div.w-100 > div.bdr-thin-tp > div#Transferencias-de-dinero-directas-al-banco
Registro gratuito div.col > div.w-100 > div.bdr-thin-tp > div#Registro-gratuito
España Tu ubicación div.wu-footer-corridor-section > div.row > div.col > div#footer-country-dropdown

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ES div#header-content > header.wu-header > div.wu-header__container > nav#main-wunav

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Western Union Logo div#header-content > header.wu-header > div.wu-header__container > a.wu-logo

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.

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
el estado de tu transferencia div.row > div.text-M-left > p.font-body-01 > a
de agente de Western Union div.row > div.text-M-left > p.font-body-01 > a

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
¿No puedes encontrar lo que estás buscando? footer.wu-footer > div.wu-footer__page-links-section > div.wu-footer__page-links-section__title > h5.font-header-h5

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#body-component > section.app > div > img.hero-banner__app-img

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.row > ul.d-flex > li.d-flex > a div.row > ul.d-flex > li.d-flex > a
div.row > ul.d-flex > li.d-flex > a div.row > ul.d-flex > li.d-flex > a
div.row > ul.d-flex > li.d-flex > a div.row > ul.d-flex > li.d-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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > ul.d-flex > li.d-flex > a div.row > ul.d-flex > li.d-flex > a
div.row > ul.d-flex > li.d-flex > a div.row > ul.d-flex > li.d-flex > a
instagram div.row > ul.d-flex > li.d-flex > a
div.row > ul.d-flex > li.d-flex > a div.row > ul.d-flex > li.d-flex > a

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 html

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-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
●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
●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
●No element has a `[tabindex]` value greater than 0
●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 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
○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.
○Elements with visible text labels have matching accessible names.
○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.
C
Form Accessibility
Action
3 of 9 controls have issues
REVIEW
3 of 9 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <select>
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="number" name="wu-input" id="wu-input-EUR">
Info::
6 control(s) properly labeled
9 controls
6 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#input-fieldinputEnviar importefor/id
#footer-link-Money-Transfer-1checkboxEnviar dinerofor/id
#footer-link-Money-Transfer-2checkboxSoportefor/id
#footer-link-Money-Transfer-3checkboxEnlaces rápidosfor/id
#footer-link-Money-Transfer-4checkboxLegalfor/id
#input-field-footerinputTu ubicaciónfor/id
#wu-input-EURnumber(200.00)placeholder only
selectselect(none)none
selectselect(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select>; <select>

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="number" name="wu-input" id="wu-input-EUR">

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
Info::
Navigation links present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
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 Envía dinero desde España con Western …
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Transfiere dinero como tú prefieras
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ¡Ahora puedes verificar tu identidad de…
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Cómodas formas de recibir dinero
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Descarga la aplicación de transferencia…
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ¿Qué puedes hacer con Western Union?
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ¡Transfiere dinero al extranjero en wes…
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ¿Listo para enviar dinero desde España…
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Enviar en línea
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Enviar con nuestra aplicación
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Enviar en persona
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Recogida de efectivo
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cuenta bancaria
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cartera móvil
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Tarjeta bancaria
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Enviar dinero al extranjero
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Realizar el seguimiento de una transfere…
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Comprobar el precio de las transferencia…
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Buscar ubicaciones de agente
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Envía dinero a prácticamente cualquier…
2.04:1
#000000
on
#533C27
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Envía dinero desde …2.04:13.0:1
#000000
#533C27
Fail
h2 Transfiere dinero co…2.04:13.0:1
#000000
#533C27
Fail
h2 ¡Ahora puedes verif…2.04:13.0:1
#000000
#533C27
Fail
h2 Cómodas formas de r…2.04:13.0:1
#000000
#533C27
Fail
h2 Descarga la aplicaci…2.04:13.0:1
#000000
#533C27
Fail
h2 ¿Qué puedes hacer …2.04:13.0:1
#000000
#533C27
Fail
h2 ¡Transfiere dinero …2.04:13.0:1
#000000
#533C27
Fail
h2 ¿Listo para enviar …2.04:13.0:1
#000000
#533C27
Fail
h3 Enviar en línea2.04:13.0:1
#000000
#533C27
Fail
h3 Enviar con nuestra a…2.04:13.0:1
#000000
#533C27
Fail
h3 Enviar en persona2.04:13.0:1
#000000
#533C27
Fail
h3 Recogida de efectivo2.04:13.0:1
#000000
#533C27
Fail
h3 Cuenta bancaria2.04:13.0:1
#000000
#533C27
Fail
h3 Cartera móvil2.04:13.0:1
#000000
#533C27
Fail
h3 Tarjeta bancaria2.04:13.0:1
#000000
#533C27
Fail
h3 Enviar dinero al ext…2.04:13.0:1
#000000
#533C27
Fail
h3 Realizar el seguimie…2.04:13.0:1
#000000
#533C27
Fail
h3 Comprobar el precio …2.04:13.0:1
#000000
#533C27
Fail
h3 Buscar ubicaciones d…2.04:13.0:1
#000000
#533C27
Fail
h3 Envía dinero a prá…2.04:13.0:1
#000000
#533C27
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
Heading Hierarchy
25 headings, 1 skip(s)
PASS
25 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Envía dinero desde España con Western Union
  • H2 Transfiere dinero como tú prefieras
  • H3 Enviar en línea
  • H3 Enviar con nuestra aplicación
  • H3 Enviar en persona
  • H2 ¡Ahora puedes verificar tu identidad de forma más rápida!
  • H2 Cómodas formas de recibir dinero
  • H3 Recogida de efectivo
  • H3 Cuenta bancaria
  • H3 Cartera móvil2
  • H3 Tarjeta bancaria
  • H2 Descarga la aplicación de transferencias de dinero en la que puedes confiar
  • H2 ¿Qué puedes hacer con Western Union?
  • H3 Enviar dinero al extranjero
  • H3 Realizar el seguimiento de una transferencia
  • H3 Comprobar el precio de las transferencias
  • H3 Buscar ubicaciones de agente
  • H2 ¡Transfiere dinero al extranjero en westernunion.com y tus destinatarios podrán retirar el dinero en efectivo!
  • H3 Envía dinero a prácticamente cualquier lugar
  • H3 Recogida en efectivo, incluso al enviar por Internet
  • H3 Transferencias de dinero directas al banco
  • H3 Registro gratuito
  • H2 ¿Listo para enviar dinero desde España?
  • H5 ¿No puedes encontrar lo que estás buscando? skipped
  • H5 Transferimos a todo el mundo

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
1 of 12 images have issues
PASS
1 of 12 images have issues
Warning::
1 image(s) with generic alt text
Info::
3 decorative image(s) correctly marked
Info::
8 image(s) with good alt text
12 images 8 good alt text 3 decorative 1 generic
IssueCount
generic1 image(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback