Skip to content
https://ledger.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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::
3 navigation landmark(s) detected
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 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
2 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

C
Form Accessibility
Action
6 of 25 controls have issues
REVIEW
6 of 25 controls have issues
Critical::
6 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <select>; <select>; <select>; <select>; <select>
Info::
19 control(s) properly labeled
25 controls
19 labeled
0 placeholder only
6 unlabeled
ControlTypeLabelMethod
#block-11radioWhat is a crypto wallet?for/id
#block-21radioHow do crypto wallets work?for/id
#block-31radioWhat are the different types of crypto wallets?for/id
#block-41radioWhy do I need a hardware wallet?for/id
#block-51radioHow to get a crypto wallet?for/id
#block-1checkboxWhat is a crypto wallet?for/id
#block-2checkboxHow do crypto wallets work?for/id
#block-3checkboxWhat are the different types of crypto wallets?for/id
#block-4checkboxWhy do I need a hardware wallet?for/id
#block-5checkboxHow to get a crypto wallet?for/id
#footer-mailemailEnter your emailfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#vendor-search-handlertextVendor list searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none

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

<select>; <select>; <select>; <select>; <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

B
404 Error Page
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 ✓Page Title Page not found | Ledger ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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 Missing
✓ Multiple Sizes Present
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 Ledger Signers & Crypto Wallets
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Go beyond exchanges and software wallets
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get cashback. Use crypto daily
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Your phone alone isn’t secure
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Only Ledger signers keep you safe. Don…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Manage 15,000+ crypto daily
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Countless happy customers
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 FAQ
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Your Cookies preferences !
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Privacy Preference Center
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Privacy Preference Center
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
24px · bottom of viewport
h3 More clarity
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 More choice
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 More control
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ledger Stax™
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ledger Flex™
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ledger Nano™
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ledger Nano™
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Bitcoin, Ethereum, Solana, XRP, stableco…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
h3 One crypto app to rule all. Total ease a…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Ledger Signers & Cry…1.00:13.0:1
#000000
#000000
Fail
h2 Go beyond exchanges …1.00:13.0:1
#000000
#000000
Fail
h2 Get cashback. Use cr…1.00:13.0:1
#000000
#000000
Fail
h2 Your phone alone isn…1.00:13.0:1
#000000
#000000
Fail
h2 Only Ledger signers …1.00:13.0:1
#000000
#000000
Fail
h2 Manage 15,000+ crypt…1.00:13.0:1
#000000
#000000
Fail
h2 Countless happy cust…1.00:13.0:1
#000000
#000000
Fail
h2 FAQ1.00:13.0:1
#000000
#000000
Fail
h2 Your Cookies prefere…1.00:13.0:1
#000000
#000000
Fail
h2 Privacy Preference C…1.00:13.0:1
#000000
#000000
Fail
h2 Privacy Preference C…1.00:13.0:1
#000000
#000000
Fail
h3 More clarity1.00:13.0:1
#000000
#000000
Fail
h3 More choice1.00:13.0:1
#000000
#000000
Fail
h3 More control1.00:13.0:1
#000000
#000000
Fail
h3 Ledger Stax™1.00:13.0:1
#000000
#000000
Fail
h3 Ledger Flex™1.00:13.0:1
#000000
#000000
Fail
h3 Ledger Nano™1.00:13.0:1
#000000
#000000
Fail
h3 Ledger Nano™1.00:13.0:1
#000000
#000000
Fail
h3 Bitcoin, Ethereum, S…1.00:13.0:1
#000000
#000000
Fail
h3 One crypto app to ru…1.00:13.0:1
#000000
#000000
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 84/100 — 4 failing, 23 passed
REVIEW
84

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.

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
Discover the Ledger Wallet app div.flexbox > div.content > div.cta-section > a.button
50+ div.ledger-wallet-scrolly__step > div.ledger-wallet-scrolly__content > div.ledger-wallet-scrolly__icons > span.color-neutral-500

These are opportunities to improve the legibility of your content.

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
20%+ global crypto secured 8+ million signers sold Zero
hacks div.row > div.flexbox > div.content > ul.icons-container

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

These items highlight common accessibility best practices.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English Français Türkçe Deutsch Português Español Русский 简体中文 日本語 한국어 العربية … div.navigation-sections-mobile__secondary > div.header-language-selector > div.language-select > select.activeLanguage

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.

○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
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●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.
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●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 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
○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.
A+
Heading Hierarchy
36 headings
PASS
36 headings
Info::
Single H1 present
Info::
1 hidden heading(s) (aria-hidden)
  • H1 Ledger Signers & Crypto Wallets
  • H2 Go beyond exchanges and software wallets
  • H3 More clarity
  • H3 More choice
  • H3 More control
  • H2 Get cashback. Use crypto daily
  • H2 Your phone alone isn’t secure
  • H2 Only Ledger signers keep you safe. Don’t be a victim of identity theft or wallet drains.
  • H3 Ledger Stax™
  • H3 Ledger Flex™
  • H3 Ledger Nano™ Gen5
  • H3 Ledger Nano™ Classics
  • H2 Manage 15,000+ crypto daily
  • H3 Bitcoin, Ethereum, Solana, XRP, stablecoins... you name it, it’s here.
  • H3 One crypto app to rule all. Total ease and control.
  • H3 Where crypto meets cash
  • H3 Maximum flexibility & speed
  • H2 Countless happy customers
  • H2 FAQ
  • H3 Discover what security feels like
  • H3 Stay in touch
  • H3 Subscribe to our newsletter
  • H2 Your Cookies preferences !
  • H2 Privacy Preference Center
  • H2 Privacy Preference Center hidden
  • H3 Your Privacy
  • H3 Strictly Necessary Cookies
  • H3 Performance Cookies
  • H3 Functional Cookies
  • H3 Targeting Cookies
  • H4 Your Privacy
  • H4 Strictly Necessary Cookies
  • H4 Performance Cookies
  • H4 Functional Cookies
  • H4 Targeting Cookies
  • H3 Vendors List
A+
Alt Text Quality
All 119 images OK
PASS
All 119 images OK
Info::
62 decorative image(s) correctly marked
Info::
57 image(s) with good alt text
119 images 57 good alt text 62 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