Accessibility

F

Heading Hierarchy

Action

62 headings, 5 skip(s)

FIX

62 headings, 5 skip(s)

Multiple H1 headings (5 found)

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

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H5 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 A New Era of Trading
H1 Trade Smarter, Faster, Safer. duplicate H1
H1 Where Markets Come Alive. duplicate H1
H1 Knowledge Powers Every Decision. duplicate H1
H1 We're Here Whenever You Need Us. duplicate H1
H2 Trusted stock broker at DSE since 2005
H4 PSL at a Glance skipped
H3 2005
H3 33K+
H3 DSE
H2 Building the future of smart investing
H3 Our Vision
H3 Our Mission
H3 Integrity
H3 Innovation
H3 Client Focus
H3 Excellence
H2 How we deliver consistent value
H3 Market Research & Insight
H3 Technology-Driven Execution
H3 Risk Management
H3 Client-Centric Support
H3 98%
H3 24/7
H3 100%
H3 0.2s
H2 Board of Directors
H4 Dr. Md. Zahirul Islam skipped
H4 Dr. Md. Abu Syed Tito
H4 Khaleda Noor Runa
H4 Dr. Shafinaz Islam
H2 Smarter, faster and more secure online trading
H3 Real-Time Market Data
H3 Secure Trading Platform
H3 Smart Investment Tools
H3 Mobile Trading
H3 Fast Order Execution
H3 Dedicated Support
H2 Powerful trading features
H3 Advanced Trading Terminal
H3 Real-Time Market Data
H3 Smart Watchlist
H3 Portfolio Management
H3 Market Depth Analysis
H3 Secure Transactions
H2 How to start trading
H3 Open BO Account
H3 Download the App
H3 Add Funds
H3 Start Trading
H2 Trade smarter from anywhere
H4 Android App skipped
H4 iOS App
H2 What our investors say
H5 Mahmudul Hasan skipped
H5 Jannatur Rubaiya
H5 Dr. A. Mamun
H2 Ready to invest with confidence?
H5 Quick Links skipped
H5 Services
H5 Head Office
H5 Regulatory Authorities

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

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

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

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

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

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

D

Dark Mode Support

Action

Theme color only

FIX

Theme color only

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

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

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

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 1 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

B

Link & Button Quality

1 issue(s) across 61 links and 12 buttons

REVIEW

1 issue(s) across 61 links and 12 buttons

1 link(s) with generic text

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

Got: /financial-knowledge.php ("Learn More")

13 link(s) open in new tab without warning

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

Got: https://oms.prilinkbd.com/login; https://oms.prilinkbd.com/login; https://play.google.com/store/apps/details?id=com.prilinkbd.tradesmart; https://apps.apple.com/us/app/trade-smart-by-prilink/id6775389934; https://www.facebook.com/prilink202; https://www.linkedin.com/in/prilinkbd/; https://www.youtube.com/@prilinkbd3165; https://wa.me/8801712705251; https://play.google.com/store/apps/details?id=com.prilinkbd.tradesmart; https://www.dse.com.bd (+3 more)

47 link(s) with descriptive text

61 links

0 empty

1 generic text

13 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://oms.prilinkbd.com/login	Login to Trade	new tab	Add '(opens in new tab)' to text
https://oms.prilinkbd.com/login	Login to Trade	new tab	Add '(opens in new tab)' to text
/financial-knowledge.php	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Financial Knowledge.Php
https://play.google.com/store/apps/detai…	Get it onGoogle Play	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/us/app/trade-smar…	Download onApp Store	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/prilink202	Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/in/prilinkbd/	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@prilinkbd3165	YouTube	new tab	Add '(opens in new tab)' to text
https://wa.me/8801712705251	WhatsApp	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	TradeSmart App	new tab	Add '(opens in new tab)' to text
https://www.dse.com.bd	Dhaka Stock Exchange (DSE)	new tab	Add '(opens in new tab)' to text
https://www.sec.gov.bd	Bangladesh Securities & Exchan…	new tab	Add '(opens in new tab)' to text
https://www.cdbl.com.bd	Central Depository Bangladesh …	new tab	Add '(opens in new tab)' to text
https://www.bb.org.bd	Bangladesh Bank	new tab	Add '(opens in new tab)' to text

59 links and buttons have descriptive text

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

/financial-knowledge.php ("Learn More")

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.

https://oms.prilinkbd.com/login; https://oms.prilinkbd.com/login; https://play.google.com/store/apps/details?id=com.prilinkbd.tradesmart; https://apps.apple.com/us/app/trade-smart-by-prilink/id6775389934; https://www.facebook.com/prilink202; https://www.linkedin.com/in/prilinkbd/; https://www.youtube.com/@prilinkbd3165; https://wa.me/8801712705251; https://play.google.com/store/apps/details?id=com.prilinkbd.tradesmart; https://www.dse.com.bd (+3 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

C

Tap Target Adequacy

Action

5 tap target(s) too small or too close together

REVIEW

5 tap target(s) too small or too close together

5 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

B

Mobile-Readable Font Sizes

92% of visible text renders at >= 12 CSS px (14 below threshold)

REVIEW

92% of visible text renders at >= 12 CSS px (14 below threshold)

14 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 11.5px ("History of Prilink Securities Limited"); <small> 11.5px ("TREC holder since"); <small> 11.5px ("Valued clients"); <small> 11.5px ("TREC holder"); <span> 11.5px ("Our Vision").

C

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

B

Favicon & Branding

5 icon(s) detected

REVIEW

5 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

C

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

B

Lighthouse Accessibility Audits

Score 85/100 — 5 failing, 22 passed

REVIEW

85

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
5 out of 5 stars `div.row > div.col-lg-4 > div.tm-card > div.tm-stars`
5 out of 5 stars `div.row > div.col-lg-4 > div.tm-card > div.tm-stars`
5 out of 5 stars `div.row > div.col-lg-4 > div.tm-card > div.tm-stars`

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
GET IT ON `div.tm-store-card > a.tm-store-btn > span > small`
DOWNLOAD ON `div.tm-store-card > a.tm-store-btn > span > small`
Disclaimer: Stock market investments are subject to market risks. Read all mark… `footer.site-footer > div.footer-bottom > div.container > p.mb-0`

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
+880 1712 705251 `div.row > div.col-lg-4 > p.mb-0 > 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
PSL at a Glance `div.col-lg-6 > div.tm-profile-panel > div.tm-profile-head > h4`
Dr. Md. Zahirul Islam `div.row > div.col-lg-3 > div.tm-card > h4`
Android App `div.row > div.col-md-6 > div.tm-store-card > h4`
Mahmudul Hasan `div.tm-card > div.tm-client > div > h5`
QUICK LINKS `div.container > div.row > div.col-lg-2 > h5`

These are opportunities to improve keyboard navigation in your application.

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
Go to slide 1 `main#main > section#heroCarousel > div.hero-dots > button.hero-dot`
Go to slide 2 `main#main > section#heroCarousel > div.hero-dots > button.hero-dot`
Go to slide 3 `main#main > section#heroCarousel > div.hero-dots > button.hero-dot`
Go to slide 4 `main#main > section#heroCarousel > div.hero-dots > button.hero-dot`
Go to slide 5 `main#main > section#heroCarousel > div.hero-dots > button.hero-dot`

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

●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

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

●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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●Skip links are focusable.

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

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○No element has a `[tabindex]` value greater than 0

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

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 1 all-caps heading(s)

A+

Alt Text Quality

All 6 images OK

PASS

All 6 images OK

6 image(s) with good alt text

6 images 6 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

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
h1 A New Era of Trading	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Trade Smarter, Faste…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Where Markets Come A…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Knowledge Powers Eve…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 We're Here Whenever …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Trusted stock broker…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Building the future …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 How we deliver consi…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Board of Directors	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Smarter, faster and …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Powerful trading fea…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 How to start trading	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Trade smarter from a…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What our investors s…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Ready to invest with…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 2005	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 33K+	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 DSE	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Our Vision	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Our Mission	21.00:1	3.0: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.