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 4 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-hvzo5y

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://Orixafi.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://Orixafi.com/manifest.json

Manifest contains invalid JSON.

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: #070912

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Mobile Keyboard & Autofill

Action

1/3 eligible field(s) missing autocomplete or inputmode

REVIEW

1/3 eligible field(s) missing autocomplete or inputmode

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" id="authEmail">

Mobile-Readable Font Sizes

Action

73% of visible text renders at >= 12 CSS px (11 below threshold)

REVIEW

73% of visible text renders at >= 12 CSS px (11 below threshold)

11 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: <small> 10.0px ("فحص وتحليل مخاطر العملات الرقمية"); <div> 9.5px ("مساحة العمل"); <div> 9.5px ("المزايا المتقدمة"); <span> 9.0px ("PRO"); <div> 9.5px ("تعرّف علينا").

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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

h1 ماسح أمان العملات وال�…

1.10:1

#000000

#0B0F1C

needs 3.0:1 (large text)

32px · bottom of viewport

h2 افحص أمان أي توكن

1.10:1

#000000

#0B0F1C

needs 3.0:1 (large text)

24px · bottom of viewport

h3 دخول

1.10:1

#000000

#0B0F1C

needs 3.0:1 (large text)

19px · bottom of viewport

title Orixa | AI Crypto Security Scanner & Sma…

1.09:1

#000000

#0A0E1C

needs 4.5:1 (normal text)

16px · top of page (header area)

a انتقل إلى المحتوى الر�…

1.10:1

#000000

#0B0F1E

needs 4.5:1 (normal text)

16px · top of page (header area)

b Orixa

1.10:1

#000000

#0A0F1D

needs 3.0:1 (large text)

16px · top of page (header area)

small فحص وتحليل مخاطر العم�…

1.10:1

#000000

#0B0F1C

needs 4.5:1 (normal text)

16px · top of page (header area)

div مساحة العمل

1.10:1

#000000

#0B0F1C

needs 4.5:1 (normal text)

16px · above the fold

span فحص

1.10:1

#000000

#0B0F1C

needs 4.5:1 (normal text)

16px · above the fold

span اللوحة

1.10:1

#000000

#0B0F1C

needs 4.5:1 (normal text)

16px · above the fold

span المراقبة

1.10:1

#000000

#0B0F1C

needs 4.5:1 (normal text)

16px · above the fold

span السجل

1.10:1

#000000

#0B0F1C

needs 4.5:1 (normal text)

16px · above the fold

span التنبيهات

1.10:1

#000000

#0B0F1C

needs 4.5:1 (normal text)

16px · above the fold

span استكشاف

1.10:1

#000000

#0B0F1C

needs 4.5:1 (normal text)

16px · above the fold

div المزايا المتقدمة

1.10:1

#000000

#0B0F1C

needs 4.5:1 (normal text)

16px · above the fold

span أدوات Pro

1.10:1

#000000

#0B0F1C

needs 4.5:1 (normal text)

16px · above the fold

span PRO

1.10:1

#000000

#0B0F1C

needs 4.5:1 (normal text)

16px · mid-page

span الخطط

1.10:1

#000000

#0B0F1C

needs 4.5:1 (normal text)

16px · mid-page

span الأمان

1.10:1

#000000

#0B0F1C

needs 4.5:1 (normal text)

16px · mid-page

div تعرّف علينا

1.10:1

#000000

#0B0F1C

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 ماسح أمان ا…	1.10:1	3.0:1	#000000	#0B0F1C	Fail
h2 افحص أمان أ…	1.10:1	3.0:1	#000000	#0B0F1C	Fail
h3 دخول	1.10:1	3.0:1	#000000	#0B0F1C	Fail
title Orixa \| AI Crypto Se…	1.09:1	4.5:1	#000000	#0A0E1C	Fail
a انتقل إلى ا…	1.10:1	4.5:1	#000000	#0B0F1E	Fail
b Orixa	1.10:1	3.0:1	#000000	#0A0F1D	Fail
small فحص وتحليل …	1.10:1	4.5:1	#000000	#0B0F1C	Fail
div مساحة العم�…	1.10:1	4.5:1	#000000	#0B0F1C	Fail
span فحص	1.10:1	4.5:1	#000000	#0B0F1C	Fail
span اللوحة	1.10:1	4.5:1	#000000	#0B0F1C	Fail
span المراقبة	1.10:1	4.5:1	#000000	#0B0F1C	Fail
span السجل	1.10:1	4.5:1	#000000	#0B0F1C	Fail
span التنبيهات	1.10:1	4.5:1	#000000	#0B0F1C	Fail
span استكشاف	1.10:1	4.5:1	#000000	#0B0F1C	Fail
div المزايا ال�…	1.10:1	4.5:1	#000000	#0B0F1C	Fail
span أدوات Pro	1.10:1	4.5:1	#000000	#0B0F1C	Fail
span PRO	1.10:1	4.5:1	#000000	#0B0F1C	Fail
span الخطط	1.10:1	4.5:1	#000000	#0B0F1C	Fail
span الأمان	1.10:1	4.5:1	#000000	#0B0F1C	Fail
div تعرّف علين�…	1.10:1	4.5:1	#000000	#0B0F1C	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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) 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

A+

Heading Hierarchy

3 headings

PASS

3 headings

Single H1 present

H1 ماسح أمان العملات والعقود الذكية من Orixa
H2 افحص أمان أي توكن
H3 دخول

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 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: 2 all-caps heading(s)

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 5 controls labeled

PASS

All 5 controls labeled

5 control(s) properly labeled

5 controls

5 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#scChain	select	شبكة البلوكشين	aria-label
#scAddr	input	عنوان العقد أو التوكن	aria-label
#authEmail	email	Email address	for/id
#authPass	password	Password	for/id
#twofaCode	input	Two-factor authentication code	for/id

Link & Button Quality

5 links, 26 buttons — all OK

PASS

5 links, 26 buttons — all OK

4 link(s) open in new tab without warning

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

Got: /pricing; /terms; /privacy; /refunds

1 link(s) with descriptive text

5 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/pricing	الأسعار	new tab	Add '(opens in new tab)' to text
/terms	شروط الخدمة	new tab	Add '(opens in new tab)' to text
/privacy	سياسة الخصوصية	new tab	Add '(opens in new tab)' to text
/refunds	سياسة الاسترداد	new tab	Add '(opens in new tab)' to text

27 links and buttons have descriptive text

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

/pricing; /terms; /privacy; /refunds

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

A+

Form Input Types

5 form control(s) checked, no type mismatches

PASS

5 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

5 form control(s) checked, no input-semantic issues

PASS

5 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Document Language

Lang attribute set to "ar"

PASS

Lang attribute set to "ar"

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

Got: ar

A+

Tabindex Anti-Patterns

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

PASS

2 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

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

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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 26 passed

PASS

100

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.

○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

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

●Select elements have associated label elements.

●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

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

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

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

○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

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