Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 3 FIX

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 ✗

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Favicon & Branding

Action

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

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

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

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+

Mobile-Readable Font Sizes

Font-size measurement not available for this scan

PASS

Font-size measurement not available for this scan

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Trading Titans

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Trading Titans ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name Trading Titans Display Mode standalone Theme Color #2563eb Background Color #0f172a Icons 5 icon(s)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

No HTML captured -- mobile-depth check is N/A

PASS

No HTML captured -- mobile-depth check is N/A

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 25 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
02 `div.grid > div.relative > div.rounded-2xl > div.absolute`
03 `div.grid > div.relative > div.rounded-2xl > div.absolute`
₹0Cr+ `div.grid > div.text-center > div.flex > div.text-xl`
+129.9% `div.group > div.flex > div.flex-1 > div.text-base`
+23.4% `div.group > div.flex > div.flex-1 > div.text-base`
+17.6% `div.group > div.flex > div.flex-1 > div.text-base`
+17.6% `div.group > div.flex > div.flex-1 > div.text-base`
+15.0% `div.group > div.flex > div.flex-1 > div.text-base`
+11.4% `div.group > div.flex > div.flex-1 > div.text-base`
LIVE RISK SCANNER `div.grid > div.lg:col-span-5 > div.flex > span.text-[10px]`
+₹4,500.00 `div.lg:col-span-5 > div.space-y-4 > div.flex > span.text-lg`
🛡️ Protected ₹50Cr+ Capital Across Dhan & Upstox Brokers `div.grid > div.lg:col-span-5 > div.space-y-4 > div.pt-2`
Trading Titans Premium `div.absolute > div.bg-[#0088cc] > div > div.text-white`
10,432 subscribers `div.absolute > div.bg-[#0088cc] > div > div.text-blue-100`
TODAY `div.absolute > div.p-3 > div.flex > span.bg-gray-400/20`
₹48,150 `div.bg-white > div.space-y-1.5 > div.flex > span.font-black`
High Accuracy Signal `div.p-3 > div.bg-white > div.mt-3 > span`
10:15 AM `div.p-3 > div.bg-white > div.mt-3 > span`
Join Channel to chat... `div.relative > div.absolute > div.absolute > div.flex-1`
ACCURACY `div.absolute > div.flex > div > div.text-[8px]`
RESPONSE `div.absolute > div.flex > div > div.text-[8px]`
Verified Audited P&L `div.max-w-7xl > div.mt-8 > div.flex > span`
Sub-Second Push Alerts `div.max-w-7xl > div.mt-8 > div.flex > span`
50,000+ Elite Community `div.max-w-7xl > div.mt-8 > div.flex > span`
© 2026 Trading Titans. All rights reserved. `div.max-w-7xl > div.border-t > div.flex > p`
Developed with ❤️ by Gurudeep Verma (Founder of Kashipixel) `div.max-w-7xl > div.border-t > div.flex > p.flex`
Privacy Policy `div.max-w-7xl > div.border-t > div.flex > a.hover:text-white`
Terms of Service `div.max-w-7xl > div.border-t > div.flex > a.hover:text-white`
Disclaimer `div.max-w-7xl > div.border-t > div.flex > a.hover:text-white`

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.space-y-4 > div.p-4 > input.w-full `div > div.space-y-4 > div.p-4 > input.w-full`
div > div.space-y-4 > div.p-4 > input.w-full `div > div.space-y-4 > div.p-4 > input.w-full`

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

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

●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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

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

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