Skip to content
https://etoro.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 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
Info::
No banner (header) landmark
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 (missing!) 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
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://etoro.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://etoro.com/manifest.json

Manifest contains invalid JSON.

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::
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.
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 - File or directory not found. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA
h1 Yep, it's
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Low fees,
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Diversify your portfolio
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Crypto trading at its best
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Copy top investors
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Investing courses, podcasts, and webinar…
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Your funds are held in top-tier institut…
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trusted worldwide
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sponsor of your favourite teams
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Trade Local, Trade Global
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
19px · bottom of viewport
h3 It’s time for loud investing
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Social
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Reliable
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Secured
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Global
1.02:1
#000000
on
#000021
needs 3.0:1 (large text)
19px · bottom of viewport
title Invest With eToro™ | Stocks, Crypto & …
3.75:1
#000000
on
#66667A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Press Alt+1 for screen-reader mode, Alt+…
3.75:1
#000000
on
#66667A
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Yep, it's1.02:13.0:1
#000000
#000021
Fail
h2 Low fees,1.02:13.0:1
#000000
#000021
Fail
h2 Diversify your portf…1.02:13.0:1
#000000
#000021
Fail
h2 Crypto trading at it…1.02:13.0:1
#000000
#000021
Fail
h2 Copy top investors1.02:13.0:1
#000000
#000021
Fail
h2 Investing courses, p…1.02:13.0:1
#000000
#000021
Fail
h2 Your funds are held …1.02:13.0:1
#000000
#000021
Fail
h2 Trusted worldwide1.02:13.0:1
#000000
#000021
Fail
h2 Sponsor of your favo…1.02:13.0:1
#000000
#000021
Fail
h3 Trade Local, Trade G…1.02:13.0:1
#000000
#000021
Fail
h3 It’s time for loud…1.02:13.0:1
#000000
#000021
Fail
h3 Social1.02:13.0:1
#000000
#000021
Fail
h3 Reliable1.02:13.0:1
#000000
#000021
Fail
h3 Secured1.02:13.0:1
#000000
#000021
Fail
h3 Global1.02:13.0:1
#000000
#000021
Fail
title Invest With eToro™…3.75:14.5:1
#000000
#66667A
Fail
span Press Alt+1 for scre…3.75:14.5:1
#000000
#66667A
Fail
a Accessibility Screen…11.86:14.5:1
#000000
#C2C2CA
Pass
button Cookie Settings21.00:14.5:1
#000000
#FFFFFF
Pass
div eToro is a multi-ass…21.00:14.5:1
#000000
#FFFFFF
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.

B
Lighthouse Accessibility Audits
Score 84/100 — 7 failing, 24 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
Sign Up div.etoro-menu-2025 > div.navigation > div.nav-for-mobile > a.e-signup
Download the App div.etoro-menu-2025 > div.navigation > div.nav-for-mobile > a.download_app
Join eToro div.text-box > div#cover-content > div.cv_info > a.cv_cta
3.55%* annual interest div.in-text-box > div > h2 > strong
Join eToro div.text-box > div.in-text-box > div.cta-group > a.e-cta
Learn More div.text-box > div.in-text-box > div.cta-group > a.e-cta-alt
Explore Top Markets div.col > div.text-box > div.in-text-box > a.e-cta-alt
Invest in Crypto div.col > div.text-box > div.in-text-box > a.e-cta-alt
Start Learning Now div.academy_block > div.e-container > div.center > a.e-cta-alt
Join Now div.site-content > div.site-content--flow > div.sticky-cta-wrapper > a.cv_cta
eToro (Europe) Ltd., a Financial Services Company authorised and regulated by t… div.footer__bottom > div.footer__disclaimer > div.footer__disclaimer-content > p.section
Finnish tax laws page div.footer__disclaimer > div.footer__disclaimer-content > p.section > a
Past performance is not an indication of future results General Risk Disclosure… div.footer__bottom > div.footer__disclaimer > div.footer__disclaimer-content > p.section
General Risk Disclosure div.footer__disclaimer > div.footer__disclaimer-content > p.section > a
Terms & Conditions div.footer__disclaimer > div.footer__disclaimer-content > p.section > a
Select Your Language body.en-gb > div#language-switcher > div.in > div.title

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
Find Us On div.footer__top > div.footer-row > div.footer__social > h4

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
body.en-gb > img#wpNavProAdded body.en-gb > img#wpNavProAdded

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
eToro div#e-header > div.etoro-menu-2025 > div.logo > a.brand

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
Submit Search div.nav-inner > div.search_box > form.search-form > button.search_icon

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.home html.home

These items highlight common accessibility best practices.

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
English div.navigation > div.nav-wrapper > div.nav-inner > button.e-lang-choose
○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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.
○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
24 headings, 1 skip(s)
PASS
24 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 Yep, it's all in one app
  • H2 Low fees, no surprises
  • H2 Earn up to 3.55%* annual interest
  • H2 Diversify your portfolio
  • H2 Crypto trading at its best
  • H2 Copy top investors
  • H2 Investing courses, podcasts, and webinars
  • H3 Trade Local, Trade Global
  • H3 It’s time for loud investing
  • H2 Your funds are held in top-tier institutions
  • H2 Trusted worldwide
  • H3 Social
  • H3 Reliable
  • H3 Secured
  • H3 Global
  • H2 Sponsor of your favourite teams
  • H4 Find Us On skipped
  • H4 Popular Instruments
  • H4 Support
  • H4 Learn more
  • H4 Download our app from the stores
  • H4 About Us
  • H4 Privacy and Regulation
  • H4 Partners and Promotions

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 69 images OK
PASS
All 69 images OK
Info::
10 decorative image(s) correctly marked
Info::
59 image(s) with good alt text
69 images 59 good alt text 10 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
ssearchSearch for:aria-label
ssearchSearch for:aria-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback