Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 6 REVIEW 4 FIX

Mobile-Readable Font Sizes

Action

50% of visible text renders at >= 12 CSS px (2 below threshold)

FIX

50% of visible text renders at >= 12 CSS px (2 below threshold)

2 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> 10.0px ("BTC"); <div> 11.0px ("Connecting to secure quantitative stream...").

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: #08090c

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.

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 ✗

Heading Hierarchy

Action

4 headings, 1 skip(s)

REVIEW

4 headings, 1 skip(s)

No H1 heading found

Every page should have one H1 that describes the page content.

Heading level skipped: H2 → H4 (missing H3)

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

H2 SECURITY AND RELIABLE
H4 Trading Guide skipped
H4 Receive red envelope
H3 Trending Stocks

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

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

Link & Button Quality

Action

3 issue(s) across 56 links and 4 buttons

REVIEW

3 issue(s) across 56 links and 4 buttons

4 link(s) open in new tab without warning

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

Got: https://t.me/ALORA_33; https://t.me/ALORA_33; https://t.me/Apextradingcripto; https://t.me/ALORA_33

3 button(s) with no accessible text

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

Got: button.h-1.5 (#136 on page); button.h-1.5 (#137 on page); button.h-1.5 (#138 on page)

52 link(s) with descriptive text

56 links

0 empty

0 generic text

4 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
https://t.me/ALORA_33	Telegram Support (@ALORA_33)	new tab	Add '(opens in new tab)' to text
https://t.me/ALORA_33	Support	new tab	Add '(opens in new tab)' to text
https://t.me/Apextradingcripto	Telegram Channel	new tab	Add '(opens in new tab)' to text
https://t.me/ALORA_33	Live Support (@ALORA_33)	new tab	Add '(opens in new tab)' to text
<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

53 links and buttons have descriptive text

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

https://t.me/ALORA_33; https://t.me/ALORA_33; https://t.me/Apextradingcripto; https://t.me/ALORA_33

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.h-1.5 (#136 on page); button.h-1.5 (#137 on page); button.h-1.5 (#138 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

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 Btcminex - Cryptocurrency Trend Forecasting & Quantitative Exchange ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

6 icon(s) detected

REVIEW

6 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

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: Btcminex - Cryptocurrency Trend Forecasting Exchange

No 192x192 icon

A 192px icon is required for PWA installation.

Display mode: standalone

PWA Install Criteria Not Installable

Name Btcminex - Cryptocurrency Trend Forecasting Exchange ✓192×192 icon ✗512×512 icon ✗Start URL / ✓Display Mode standalone ✓

Name Btcminex - Cryptocurrency Trend Forecasting Exchange Display Mode standalone Theme Color #08090c Background Color #050608 Icons 1 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h2 SECURITY AND RELIABLE

1.04:1

#000000

#050608

needs 3.0:1 (large text)

24px · mid-page · over background image/gradient

h3 Trending Stocks

1.04:1

#000000

#050608

needs 3.0:1 (large text)

19px · bottom of viewport

title Btcminex - Cryptocurrency Trend Forecast…

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · top of page (header area)

span BTC

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · top of page (header area)

div BTCMINEX

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · top of page (header area)

div Connecting to secure quantitative stream…

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · above the fold

span BTCM

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · above the fold

span Btcminex

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · above the fold

span Crypto Forecast

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · above the fold

a Home

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · above the fold

a Quotes

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · above the fold

a Trade

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · above the fold

a Team

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · above the fold

a Bonus

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · above the fold

a Assets

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · mid-page

span Recharge

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · mid-page

span Withdraw

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · mid-page

span English

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · mid-page

span TOP GRADE ENCRYPTION

1.04:1

#000000

#050608

needs 4.5:1 (normal text)

16px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 SECURITY AND RELIABL…	1.04:1	3.0:1	#000000	#050608	Fail
h3 Trending Stocks	1.04:1	3.0:1	#000000	#050608	Fail
title Btcminex - Cryptocur…	1.04:1	4.5:1	#000000	#050608	Fail
a Skip to main content	1.04:1	4.5:1	#000000	#050608	Fail
span BTC	1.04:1	4.5:1	#000000	#050608	Fail
div BTCMINEX	1.04:1	4.5:1	#000000	#050608	Fail
div Connecting to secure…	1.04:1	4.5:1	#000000	#050608	Fail
span BTCM	1.04:1	4.5:1	#000000	#050608	Fail
span Btcminex	1.04:1	4.5:1	#000000	#050608	Fail
span Crypto Forecast	1.04:1	4.5:1	#000000	#050608	Fail
a Home	1.04:1	4.5:1	#000000	#050608	Fail
a Quotes	1.04:1	4.5:1	#000000	#050608	Fail
a Trade	1.04:1	4.5:1	#000000	#050608	Fail
a Team	1.04:1	4.5:1	#000000	#050608	Fail
a Bonus	1.04:1	4.5:1	#000000	#050608	Fail
a Assets	1.04:1	4.5:1	#000000	#050608	Fail
span Recharge	1.04:1	4.5:1	#000000	#050608	Fail
span Withdraw	1.04:1	4.5:1	#000000	#050608	Fail
span English	1.04:1	4.5:1	#000000	#050608	Fail
span TOP GRADE ENCRYPTION	1.04:1	4.5:1	#000000	#050608	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+

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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

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

3 mobile-depth signal(s) detected

PASS

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

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

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+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 10 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.

Best practices

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.h-full `html.h-full`

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-hidden="true"]` is not present on the document `<body>`

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

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

●Background and foreground colors have a sufficient contrast ratio

●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

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○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 use only permitted ARIA attributes

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

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○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

○Heading elements appear in a sequentially-descending order

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○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

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

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