Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 2 REVIEW 7 FIX

Alt Text Quality

Action

6 of 106 images have issues

FIX

6 of 106 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image-in-link without alt text

An image inside a link with no alt creates an empty link.

4 image(s) with generic alt text

59 decorative image(s) correctly marked

41 image(s) with good alt text

106 images 41 good alt text 59 decorative 4 generic 2 missing

Issue	Count
missing	2 image(s)
generic	4 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Link & Button Quality

Action

10 issue(s) across 358 links and 10 buttons

FIX

10 issue(s) across 358 links and 10 buttons

6 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /eu-en; /eu-en; a#main-content-link; https://www.facebook.com/OANDAGroup; https://www.youtube.com/@oandagroup/; https://twitter.com/OANDAsupport

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /eu-fr ("Continue")

15 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: /eu-en/onboarding/?from=HP_UP; javascript:void(0);; javascript:void(0);; /eu-en/platform; https://hub.oanda.com/eu-en; https://help.oanda.com/eu/en/home.htm; /eu-en/platform; https://hub.oanda.com/eu-en; https://help.oanda.com/eu/en/home.htm; https://www.oanda.com/eu-en/mobile-app (+5 more)

3 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.custom-btn--primary (#304 on page); button.custom-btn--primary (#707 on page); button.custom-btn--primary (#749 on page)

336 link(s) with descriptive text

358 links

6 empty

1 generic text

15 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
/eu-en/onboarding/?from=HP_UP	Open account Trading	new tab	Add '(opens in new tab)' to text
javascript:void(0);	Demo Open demo account	new tab	Add '(opens in new tab)' to text
javascript:void(0);	Language switcher popup	new tab	Add '(opens in new tab)' to text
/eu-en/platform	Trade online	new tab	Add '(opens in new tab)' to text
https://hub.oanda.com/eu-en	My account	new tab	Add '(opens in new tab)' to text
https://help.oanda.com/eu/en/home.htm	Help	new tab	Add '(opens in new tab)' to text
/eu-en/platform	Trade online	new tab	Add '(opens in new tab)' to text
https://hub.oanda.com/eu-en	My account	new tab	Add '(opens in new tab)' to text
https://help.oanda.com/eu/en/home.htm	Help	new tab	Add '(opens in new tab)' to text
/eu-en	(empty)	empty	Add link text or aria-label
/eu-en	(empty)	empty	Add link text or aria-label
	(empty)	empty	Add link text or aria-label
https://www.oanda.com/eu-en/mobile-app	Find out more	new tab	Add '(opens in new tab)' to text
https://www.oanda.com/eu-en/invest/tradi…	Find out more	new tab	Add '(opens in new tab)' to text
https://www.oanda.com/eu-en/etf	Find out more	new tab	Add '(opens in new tab)' to text
https://www.oanda.com/eu-en/stocks	Find out more	new tab	Add '(opens in new tab)' to text
https://www.oanda.com/eu-en/tradingview	Find out more	new tab	Add '(opens in new tab)' to text
https://www.oanda.com/eu-en/interest-rat…	Find out more	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/OANDAGroup	(empty)	empty	Add link text or aria-label
https://www.youtube.com/@oandagroup/	(empty)	empty	Add link text or aria-label
https://twitter.com/OANDAsupport	(empty)	empty	Add link text or aria-label
/eu-fr	Continue	generic text	Replace with descriptive text
Before: Continue Suggested: Eu Fr
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

343 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/eu-en; /eu-en; a#main-content-link; https://www.facebook.com/OANDAGroup; https://www.youtube.com/@oandagroup/; https://twitter.com/OANDAsupport

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

/eu-fr ("Continue")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Add '(opens in new tab)' to link text or aria-label.

/eu-en/onboarding/?from=HP_UP; javascript:void(0);; javascript:void(0);; /eu-en/platform; https://hub.oanda.com/eu-en; https://help.oanda.com/eu/en/home.htm; /eu-en/platform; https://hub.oanda.com/eu-en; https://help.oanda.com/eu/en/home.htm; https://www.oanda.com/eu-en/mobile-app (+5 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button.custom-btn--primary (#304 on page); button.custom-btn--primary (#707 on page); button.custom-btn--primary (#749 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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 Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

6 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 6 <nav> element(s)

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.

Landmark Structure

9 landmarks

REVIEW

9 landmarks

<main> landmark present

6 <nav> landmark(s) found

3 of 6 <nav> elements are unlabeled

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

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

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Heading Hierarchy

48 headings

PASS

48 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H3 Select your language
H1 (empty)
H1 Trade in a different league duplicate H1
H2 Trade in a different league
H2 The smart choice for smart traders
H3 Access 4000+ global instruments — all in one app
H3 Trade CFDs easily
H3 ETFs: 0 EUR commission on 10 trades per month
H3 Trade global shares
H3 Smarter trading with OANDA and TradingView
H3 Earn interest
H3 A broker you can trust
H2 Trading resources
H3 Daily market news
H3 Investing reports and guides
H3 Blog
H2 4000+ financial instruments
H2 Popular
H2 Top movers
H2 Forex
H2 Indices CFDs
H2 Shares
H2 Shares
H2 Shares
H2 Shares
H2 Shares
H2 Shares
H2 Shares CFDs
H2 Shares CFDs
H2 Shares CFDs
H2 Shares CFDs
H2 Shares CFDs
H2 Shares CFDs
H2 Shares CFDs
H2 Shares CFDs
H2 Shares CFDs
H2 Shares CFDs
H2 Shares CFDs
H2 Shares CFDs
H2 ETF CFDs
H2 Commodities CFDs
H2 Cryptocurrencies CFDs
H2 ETFs
H2 ETFs
H2 ETFs
H2 ETFs
H2 ETFs
H2 FAQ

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

Form Accessibility

1 of 9 controls have issues

PASS

1 of 9 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="search">

8 control(s) properly labeled

9 controls

8 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#edit-email--2	email	email	for/id
#edit-phoneprefix--2	text	phone_prefix	for/id
#edit-phone--2	text	phone	for/id
#edit-password--2	password	Password	for/id
#edit-check-all-agreements--2	checkbox		none
#edit-privacy-0--2	checkbox		none
#edit-email-agreement--2	checkbox		none
#edit-mobile-agreement--2	checkbox		none
input	search	(Search for instruments)	placeholder only

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

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

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Trade in a different…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Trading resources	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 4000+ financial inst…	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Popular	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Top movers	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Forex	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Indices CFDs	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Shares	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Shares	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Shares	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Shares	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Shares	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Shares	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Shares CFDs	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Shares CFDs	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Shares CFDs	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Shares CFDs	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Shares CFDs	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Shares CFDs	18.76:1	3.0:1	#000000	#F2F2F2	Pass
h2 Shares CFDs	18.76:1	3.0:1	#000000	#F2F2F2	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.

Lighthouse Accessibility Audits

Score 94/100 — 3 failing, 33 passed

PASS

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
Find out more `div.paragraph > div > div.element-link > a.link`
Find out more `div.paragraph > div > div.element-link > a.link`
Find out more `div.paragraph > div > div.element-link > a.link`
Find out more `div.paragraph > div > div.element-link > a.link`
Find out more `div.paragraph > div > div.element-link > a.link`
Find out more `div.paragraph > div > div.element-link > a.link`
1.174 `tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell`
1.175 `tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy`
1.351 `tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell`
1.351 `tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy`
-0.07 % `tr.border-0 > td.change-column > a.fc-primary-1 > span.instrument-change`
159.274 `tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell`
-0.10 % `tr.border-0 > td.change-column > a.fc-primary-1 > span.instrument-change`
0.780 `tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell`
0.781 `tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy`
0.716 `tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell`
0.716 `tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy`
0.591 `tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell`
0.591 `tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy`
-1.11 % `tr.border-0 > td.change-column > a.fc-primary-1 > span.instrument-change`
4740.010 `tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell`
4740.740 `tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy`
77.390 `tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell`
77.454 `tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy`
-0.84 % `tr.border-0 > td.change-column > a.fc-primary-1 > span.instrument-change`
76301.000 `tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell`
76363.000 `tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy`
2322.700 `tr.border-0 > td.py-2 > a.fc-primary-1 > span.instrument-sell`
2328.050 `tr.border-0 > td.p-2 > a.fc-primary-1 > span.instrument-buy`
-2.50 % `tr.border-0 > td.change-column > a.fc-primary-1 > span.instrument-change`
-1.55 % `tr.border-0 > td.change-column > a.fc-primary-1 > span.instrument-change`

These are opportunities to improve the legibility of your content.

Names and labels

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.node__content > div.paragraph > div.paragraph > a.d-block `div.node__content > div.paragraph > div.paragraph > a.d-block`
div.node__content > div.paragraph > div.paragraph > a.d-block `div.node__content > div.paragraph > div.paragraph > a.d-block`
div.node__content > div.paragraph > div.paragraph > a.d-block `div.node__content > div.paragraph > div.paragraph > a.d-block`

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.

Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Name of instrument Change (%) Sell Buy US500 0.16 % 7137.300 7138.000 DE30 … `div.row > div#myTabContent > div#popular-155401741 > table.quotes-table`

○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

●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

●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 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

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●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.

○`[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

○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.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`<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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.