Skip to content
https://crypto.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
68
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
404 Error Page
Action
HTTP 404, custom page
FIX
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 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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::
1 navigation landmark(s) detected
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 1 <nav> element(s)
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.
C
Favicon & Branding
Action
10 icon(s) detected
REVIEW
10 icon(s) detected
Info::
favicon.ico present at site root
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'>.
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA
title Crypto.com España: Compra y vende cript…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Conectar
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · top of page (header area)
a Registrarse
1.08:1
#000000
on
#080D1B
needs 4.5:1 (normal text)
16px · top of page (header area)
span Descarga la aplicación
1.08:1
#000000
on
#080D1B
needs 4.5:1 (normal text)
16px · top of page (header area)
button Mercados
1.12:1
#000000
on
#0B1121
needs 4.5:1 (normal text)
16px · above the fold
button Particulares
1.17:1
#000000
on
#0E1729
needs 4.5:1 (normal text)
16px · above the fold
button Empresas
1.25:1
#000000
on
#121D31
needs 4.5:1 (normal text)
16px · above the fold
button Descubrir
1.32:1
#000000
on
#162239
needs 4.5:1 (normal text)
16px · above the fold
a Conectar
1.42:1
#000000
on
#1A2841
needs 4.5:1 (normal text)
16px · above the fold
a Registrarse
1.54:1
#000000
on
#1D2E49
needs 4.5:1 (normal text)
16px · above the fold
span Aplicación Crypto.com
1.80:1
#000000
on
#243958
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Todas tus criptomone…10.60:13.0:1
#000000
#B1B9C3
Pass
h2 Diseñado para cript…10.60:13.0:1
#000000
#B1B9C3
Pass
h2 Tu viaje cripto empi…10.60:13.0:1
#000000
#B1B9C3
Pass
h2 Tu acceso onchain de…10.60:13.0:1
#000000
#B1B9C3
Pass
h2 Una plataforma, múl…10.60:13.0:1
#000000
#B1B9C3
Pass
h3 Opera con facilidad …10.60:13.0:1
#000000
#B1B9C3
Pass
h3 Tarjeta Visa Crypto.…10.60:13.0:1
#000000
#B1B9C3
Pass
h3 Controla por complet…10.60:13.0:1
#000000
#B1B9C3
Pass
h3 Consigue Onchain Wal…10.60:13.0:1
#000000
#B1B9C3
Pass
title Crypto.com España: …1.00:14.5:1
#000000
#000000
Fail
a Conectar1.00:14.5:1
#000000
#000000
Fail
a Registrarse1.08:14.5:1
#000000
#080D1B
Fail
span Descarga la aplicaci…1.08:14.5:1
#000000
#080D1B
Fail
button Mercados1.12:14.5:1
#000000
#0B1121
Fail
button Particulares1.17:14.5:1
#000000
#0E1729
Fail
button Empresas1.25:14.5:1
#000000
#121D31
Fail
button Descubrir1.32:14.5:1
#000000
#162239
Fail
a Conectar1.42:14.5:1
#000000
#1A2841
Fail
a Registrarse1.54:14.5:1
#000000
#1D2E49
Fail
span Aplicación Crypto.c…1.80:14.5:1
#000000
#243958
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.

C
Lighthouse Accessibility Audits
Action
Score 72/100 — 8 failing, 21 passed
REVIEW
72

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

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.mx-auto > div.flex > div.flex > button.flex div.mx-auto > div.flex > div.flex > button.flex

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
Registrarse header.sticky > div.mx-auto > div.flex > a.flex
Registrarse div.h-auto > div.p-[32px_16px] > div.flex > a.flex
Descarga la app div.flex > div.flex > a.relative > p.text-[14px]
La cartera OnChain es un producto independiente y no está regulada conforme al … div.flex > p.max-w-[1100px] > div.payload-richtext > p
Easy & Fast a.flex-1 > div.group > div.flex > span.inline-flex
Aceptar todas las cookies div#onetrust-button-group-parent > div#onetrust-button-group > div.banner-actions-container > button#onetrust-accept-btn-handler

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
chat.crypto.com div.flex-col-reverse > div.w-full > p > a.text-[#1199FA]

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
Productos nav.custom-scrollbar > div.h-auto > div.py-[24px] > h5.p-[0px_16px_10px_16px]

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Popular Velo VELO -0.47% Pudgy Penguins PENGU +9.91% Wrapped Bitcoin WBTC +3.84… div.fixed > div.custom-scrollbar > div > ul.custom-scrollbar

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
Velo VELO -0.47% div > ul.custom-scrollbar > div.mb-[24px] > li
Pudgy Penguins PENGU +9.91% div > ul.custom-scrollbar > div.mb-[24px] > li
Wrapped Bitcoin WBTC +3.84% div > ul.custom-scrollbar > div.mb-[24px] > li
PAX Gold PAXG +0.42% div > ul.custom-scrollbar > div.mb-[24px] > li
B BlackRock USD In... BUIDL +0% div > ul.custom-scrollbar > div.mb-[24px] > li

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

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
Términos y condiciones para el EEE div.mt-[16px] > div.justify-start > div.ml-[-8px] > a.border-r-[1px]
Estado div.mt-[16px] > div.justify-start > div.ml-[-8px] > a.border-r-[1px]
Preferencias de cookies div.mt-[16px] > div.justify-start > div.ml-[-8px] > button#ot-sdk-btn

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
●Image elements have `[alt]` attributes
●Form elements have associated labels
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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 have a discernible name
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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 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
○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
○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.
○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.
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) 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 NAV 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

A+
Heading Hierarchy
11 headings
PASS
11 headings
Info::
Single H1 present
  • H5 Productos
  • H1 Todas tus criptomonedas en una app de confianza
  • H2 Diseñado para cripto, hecho para España
  • H2 Consulta precios en directo, movimientos del mercado y los tokens más destacados
  • H2 Tu viaje cripto empieza aquí
  • H3 Opera con facilidad y con comisiones muy bajas
  • H3 Tarjeta Visa Crypto.com
  • H2 Tu acceso onchain de confianza
  • H3 Controla por completo tus cripto y gestiona tus activos de forma segura
  • H3 Consigue Onchain Wallet
  • H2 Una plataforma, múltiples formas de operar
A+
Alt Text Quality
All 55 images OK
PASS
All 55 images OK
Info::
6 decorative image(s) correctly marked
Info::
49 image(s) with good alt text
55 images 49 good alt text 6 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#crypto-searchtextBuscar activosaria-label
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Crypto
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: minimal-ui
PWA Install Criteria ✓ Installable
Name Crypto ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode minimal-ui ✓
Name Crypto Display Mode minimal-ui Theme Color #061121 Background Color #ffffff Icons 8 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback