Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 3 REVIEW 6 FIX

Mobile-Readable Font Sizes

Action

66% of visible text renders at >= 12 CSS px (40 below threshold)

FIX

66% of visible text renders at >= 12 CSS px (40 below threshold)

40 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: <button> 11.0px ("Menu"); <p> 11.0px ("Real-asset private markets"); <dt> 11.0px ("Stage"); <dt> 11.0px ("Investors"); <dt> 11.0px ("Base").

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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 Missing

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

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

No <nav> landmark found

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

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 Democratize — The Global Marketplace for Tokenised Real Assets ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h1 Real-asset deals, structured for

1.36:1

#000000

#1B2438

needs 3.0:1 (large text)

32px · mid-page

h2 Real-asset deals with a hard asset under…

1.36:1

#000000

#1B2438

needs 3.0:1 (large text)

24px · bottom of viewport

h2 See the platform blueprint

1.36:1

#000000

#1B2438

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Two sides of every deal

1.36:1

#000000

#1B2438

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The infrastructure for a new investment …

1.36:1

#000000

#1B2438

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Institutions first is how the assets rea…

1.36:1

#000000

#1B2438

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What to hold lightly

1.36:1

#000000

#1B2438

needs 3.0:1 (large text)

24px · bottom of viewport

h3 For asset owners and sponsors

1.36:1

#000000

#1B2438

needs 3.0:1 (large text)

19px · bottom of viewport

h3 For professional investors

1.36:1

#000000

#1B2438

needs 3.0:1 (large text)

19px · bottom of viewport

span Exchange

1.36:1

#000000

#1B2438

needs 4.5:1 (normal text)

16px · top of page (header area)

a Marketplace

1.36:1

#000000

#1B2438

needs 4.5:1 (normal text)

16px · top of page (header area)

button Intelligence

1.36:1

#000000

#1B2438

needs 4.5:1 (normal text)

16px · above the fold

span ▼

1.36:1

#000000

#1B2438

needs 4.5:1 (normal text)

16px · above the fold

button Invest

1.36:1

#000000

#1B2438

needs 4.5:1 (normal text)

16px · above the fold

span ▼

1.36:1

#000000

#1B2438

needs 4.5:1 (normal text)

16px · above the fold

button Issue

1.36:1

#000000

#1B2438

needs 4.5:1 (normal text)

16px · above the fold

span ▼

1.36:1

#000000

#1B2438

needs 4.5:1 (normal text)

16px · above the fold

button Platform

1.36:1

#000000

#1B2438

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Real-asset deals, st…	1.36:1	3.0:1	#000000	#1B2438	Fail
h2 Real-asset deals wit…	1.36:1	3.0:1	#000000	#1B2438	Fail
h2 See the platform blu…	1.36:1	3.0:1	#000000	#1B2438	Fail
h2 Two sides of every d…	1.36:1	3.0:1	#000000	#1B2438	Fail
h2 The infrastructure f…	1.36:1	3.0:1	#000000	#1B2438	Fail
h2 Institutions first i…	1.36:1	3.0:1	#000000	#1B2438	Fail
h2 What to hold lightly	1.36:1	3.0:1	#000000	#1B2438	Fail
h3 For asset owners and…	1.36:1	3.0:1	#000000	#1B2438	Fail
h3 For professional inv…	1.36:1	3.0:1	#000000	#1B2438	Fail
title Democratize \| Real-a…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Democratize	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Exchange	1.36:1	4.5:1	#000000	#1B2438	Fail
a Marketplace	1.36:1	4.5:1	#000000	#1B2438	Fail
button Intelligence	1.36:1	4.5:1	#000000	#1B2438	Fail
span ▼	1.36:1	4.5:1	#000000	#1B2438	Fail
button Invest	1.36:1	4.5:1	#000000	#1B2438	Fail
span ▼	1.36:1	4.5:1	#000000	#1B2438	Fail
button Issue	1.36:1	4.5:1	#000000	#1B2438	Fail
span ▼	1.36:1	4.5:1	#000000	#1B2438	Fail
button Platform	1.36:1	4.5:1	#000000	#1B2438	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.

A+

Heading Hierarchy

9 headings

PASS

9 headings

Single H1 present

H1 Real-asset deals, structured for institutional capital.
H2 Real-asset deals with a hard asset underneath
H2 See the platform blueprint
H2 Two sides of every deal
H3 For asset owners and sponsors
H3 For professional investors
H2 The infrastructure for a new investment economy
H2 Institutions first is how the assets reach everyone
H2 What to hold lightly

A+

Heading Text Quality

All 9 heading(s) have substantive, well-formed text

PASS

All 9 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 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+

Link & Button Quality

20 links, 6 buttons — all OK

PASS

20 links, 6 buttons — all OK

20 link(s) with descriptive text

20 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

26 links and buttons have descriptive text

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+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Lighthouse Accessibility Audits

Score 96/100 — 2 failing, 24 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
Each deal sits in an SPV with an independent trustee. `section.py-14 > div.mt-8 > div.tile > p.type-body`
Ownership held on a digital register kept by a transfer agent. `section.py-14 > div.mt-8 > div.tile > p.type-body`
DEMONSTRATION LOTS `section.rule-top > div.card-champagne-light > div.max-w-2xl > p.eyebrow`
A clickable demonstration of the marketplace, asset records and portfolio tools… `section.rule-top > div.card-champagne-light > div.max-w-2xl > p.type-body`
Off-market real-asset deals. `div.type-body > ul.space-y-3 > li.type-body > span`
Independent trustee oversight. `div.type-body > ul.space-y-3 > li.type-body > span`
A standard asset record. `div.type-body > ul.space-y-3 > li.type-body > span`
A digital register. `div.type-body > ul.space-y-3 > li.type-body > span`

These are opportunities to improve the legibility of your content.

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
DEMOCRATIZE EXCHANGE `body > header.sticky > div.mx-auto > a.flex`

○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

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

●Elements use only permitted ARIA attributes

●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

●Definition list items are wrapped in `<dl>` elements

●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

●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

○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

○Links are distinguishable without relying on color.

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

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

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