Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 6 REVIEW 6 FIX

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: tel.

Got: <input type="tel">

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: tel.

Got: <input type="tel">

Mobile-Readable Font Sizes

Action

49% of visible text renders at >= 12 CSS px (170 below threshold)

FIX

49% of visible text renders at >= 12 CSS px (170 below threshold)

170 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: <div> 9.0px ("متصل"); <div> 10.0px ("🔒 بياناتك آمنة ولن تُشارك مع أحد"); <div> 10.0px ("سيتم إنشاء رقم عميل فريد من 6 أرقام — لا..."); <div> 10.0px ("يمكنك التصفح الآن، والتسجيل مطلوب فقط لل..."); <p> 10.0px ("ALMAJED PHONE").

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

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.

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

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.

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Form Accessibility

7 of 7 controls have issues

REVIEW

7 of 7 controls have issues

7 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="text">; <input type="tel">; <input type="text">

7 controls

0 labeled

7 placeholder only

0 unlabeled

Control	Type	Label	Method
input	text	(مثال: أحمد محمد علي)	placeholder only
input	text	(مثال: قنقنان)	placeholder only
input	text	(لحج)	placeholder only
input	text	(القبيطة)	placeholder only
input	text	(مثال: سوق الربوع - أمام محل البهارات)	placeholder only
input	tel	(مثال: 737849748)	placeholder only
input	text	(ابحث عن منتجك...)	placeholder only

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Tap Target Adequacy

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

REVIEW

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

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

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

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

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

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

#000000

#2F2F30

needs 3.0:1 (large text)

32px · mid-page

h2 مرحباً بك!

1.55:1

#000000

#2E2E2F

needs 3.0:1 (large text)

24px · top of page (header area)

h2 🎧 سماعة الرأس اللاس…

1.59:1

#000000

#303031

needs 3.0:1 (large text)

24px · bottom of viewport · over background image/gradient

h2 جميع المنتجات

1.59:1

#000000

#303031

needs 3.0:1 (large text)

24px · bottom of viewport

h2 هواتف

1.59:1

#000000

#303031

needs 3.0:1 (large text)

24px · bottom of viewport

h2 سماعات

1.59:1

#000000

#303031

needs 3.0:1 (large text)

24px · bottom of viewport

h2 كشافات

1.59:1

#000000

#303031

needs 3.0:1 (large text)

24px · bottom of viewport

h2 حامل

1.59:1

#000000

#303031

needs 3.0:1 (large text)

24px · bottom of viewport

h2 راديواء

1.59:1

#000000

#303031

needs 3.0:1 (large text)

24px · bottom of viewport

h2 سيفرات

1.59:1

#000000

#303031

needs 3.0:1 (large text)

24px · bottom of viewport

h2 مكبر صوت

1.59:1

#000000

#303031

needs 3.0:1 (large text)

24px · bottom of viewport

h2 ذواكر

1.59:1

#000000

#303031

needs 3.0:1 (large text)

24px · bottom of viewport

h2 لوحة باور بنك

1.59:1

#000000

#303031

needs 3.0:1 (large text)

24px · bottom of viewport

h2 شرائح

1.59:1

#000000

#303031

needs 3.0:1 (large text)

24px · bottom of viewport

h3 هاتف نوكيا 1208) شريحة

1.59:1

#000000

#303031

needs 3.0:1 (large text)

19px · bottom of viewport

h3 هاتف نوكيا 105 (Nokia 105)

1.59:1

#000000

#303031

needs 3.0:1 (large text)

19px · bottom of viewport

h3 سماعة الأعمال اللاس�…

1.59:1

#000000

#303031

needs 3.0:1 (large text)

19px · bottom of viewport

h3 🎧 سماعة الرأس اللاس…

1.59:1

#000000

#303031

needs 3.0:1 (large text)

19px · bottom of viewport

h3 🎧 سماعة البلوتوث ال…

1.59:1

#000000

#303031

needs 3.0:1 (large text)

19px · bottom of viewport

h3 🎧 سماعة البلوتوث ال…

1.59:1

#000000

#303031

needs 3.0:1 (large text)

19px · bottom of viewport

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
h1 الماجد فون	1.57:1	3.0:1	#000000	#2F2F30	Fail
h2 مرحباً بك!	1.55:1	3.0:1	#000000	#2E2E2F	Fail
h2 🎧 سماعة �…	1.59:1	3.0:1	#000000	#303031	Fail
h2 جميع المنت�…	1.59:1	3.0:1	#000000	#303031	Fail
h2 هواتف	1.59:1	3.0:1	#000000	#303031	Fail
h2 سماعات	1.59:1	3.0:1	#000000	#303031	Fail
h2 كشافات	1.59:1	3.0:1	#000000	#303031	Fail
h2 حامل	1.59:1	3.0:1	#000000	#303031	Fail
h2 راديواء	1.59:1	3.0:1	#000000	#303031	Fail
h2 سيفرات	1.59:1	3.0:1	#000000	#303031	Fail
h2 مكبر صوت	1.59:1	3.0:1	#000000	#303031	Fail
h2 ذواكر	1.59:1	3.0:1	#000000	#303031	Fail
h2 لوحة باور ب…	1.59:1	3.0:1	#000000	#303031	Fail
h2 شرائح	1.59:1	3.0:1	#000000	#303031	Fail
h3 هاتف نوكيا …	1.59:1	3.0:1	#000000	#303031	Fail
h3 هاتف نوكيا …	1.59:1	3.0:1	#000000	#303031	Fail
h3 سماعة الأ…	1.59:1	3.0:1	#000000	#303031	Fail
h3 🎧 سماعة �…	1.59:1	3.0:1	#000000	#303031	Fail
h3 🎧 سماعة �…	1.59:1	3.0:1	#000000	#303031	Fail
h3 🎧 سماعة �…	1.59:1	3.0:1	#000000	#303031	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.

Lighthouse Accessibility Audits

Score 83/100 — 3 failing, 17 passed

REVIEW

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
⚠️ 5 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
⚠️ 2 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
⚠️ 2 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
👁️ عرض التفاصيل `div.flex-shrink-0 > div.group > div.p-3 > button.w-full`
👁️ عرض التفاصيل `div.flex-shrink-0 > div.group > div.p-3 > button.w-full`
👁️ عرض التفاصيل `div.flex-shrink-0 > div.group > div.p-3 > button.w-full`
⚠️ 4 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
⚠️ 4 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
⚠️ 3 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
SKU: 764338 `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
👁️ عرض التفاصيل `div.flex-shrink-0 > div.group > div.p-3 > button.w-full`
⚠️ 1 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
⚠️ 2 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
⚠️ 3 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
⚠️ 2 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
SKU: 231122 `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
📦 10 قطعة `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
👁️ عرض التفاصيل `div.flex-shrink-0 > div.group > div.p-3 > button.w-full`
⚠️ 5 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
⚠️ 2 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
⚠️ 2 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
⚠️ 2 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
⚠️ 2 متبقية فقط `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
SKU: 798272 `div.flex-shrink-0 > div.group > div.p-3 > p.text-[10px]`
👁️ عرض التفاصيل `div.flex-shrink-0 > div.group > div.p-3 > button.w-full`

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

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
الشريحة 1 `div.min-h-screen > div.mx-auto > div.flex > button.rounded-full`
الشريحة 2 `div.min-h-screen > div.mx-auto > div.flex > button.rounded-full`
الشريحة 3 `div.min-h-screen > div.mx-auto > div.flex > button.rounded-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-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

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

●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 have a discernible name

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Image elements do not have `[alt]` attributes that are redundant text.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

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

○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

○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

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

A+

Heading Hierarchy

41 headings

PASS

41 headings

Single H1 present

H2 مرحباً بك!
H1 الماجد فون
H2 🎧 سماعة الرأس اللاسلكية الأنيقة (JBL TUNE 2961 / Pure Bass Wireless)
H2 جميع المنتجات(26)
H2 هواتف(2)
H3 هاتف نوكيا 1208) شريحة
H3 هاتف نوكيا 105 (Nokia 105)
H2 سماعات(7)
H3 سماعة الأعمال اللاسلكية الذكية (Business Headset - Model: M1)
H3 🎧 سماعة الرأس اللاسلكية الأنيقة (JBL TUNE 2961 / Pure Bass Wireless)
H3 🎧 سماعة البلوتوث المكتبي والأعمال Mini Headset (موديل M11)
H3 🎧 سماعة البلوتوث اللاسلكية الذكية M5 MINI
H3 سماعات سلك LT
H3 سماعات سلك العادي
H3 🎧 سماعات أذن سلكية LT بمنفذ Type-C (عالية الجودة)
H2 كشافات(1)
H3 🔦 كشاف الرأس فائق الإضاءة (FENIX FX-6622 - 50W)
H2 حامل(1)
H3 حامل الهواتف والأجهزة اللوحية المكتبي (Alloy Phone Stand - NO.K72)
H2 راديواء(1)
H3 راديواء ومشغل صوت
H2 سيفرات(1)
H3 سيفرات HD
H2 مكبر صوت(4)
H3 مكبر صوت GREATNICE GTS
H3 🔊 رفيقك المثالي في كل مكان! مكبر صوت GREATNICE GTS-1961
H3 مكبر صوت KTS-1057اللاسلكي
H3 مبكر صوت محمول صغير
H2 ذواكر(4)
H3 كرت ذاكرة ميكرو Micro SD سعة 4GB فئة Class 10
H3 كرت XTREME سعة 8 جيجابايت
H3 فلاش ميموري SanDisk Ultra Dual Drive m3.0 بسعة 64 جيجابايت
H3 بطاقة ذاكرة SanDisk Ultra بسعة 32 جيجابايت
H2 لوحة باور بنك(4)
H3 لوحة ومتحكم ذكي RL-SNSKP-AK31
H3 لوحة باور بنك نحيفة بمؤشرات LED رقم V2.3
H3 لوحة باور بنك HSY-E02-CP07 V1.2 مع كشاف
H3 بوردة باور بنك مزدوجة المنافذ (شحن ذكي)
H2 شرائح(1)
H3 شرائح يمن موبايل 78
H3 متجر الماجد فون

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 31 images OK

PASS

All 31 images OK

31 image(s) with good alt text

31 images 31 good alt text

All images have appropriate alt text.

Link & Button Quality

19 links, 81 buttons — all OK

PASS

19 links, 81 buttons — all OK

2 link(s) open in new tab without warning

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

Got: https://amjad-direct-link.base44.app/; https://www.2dec.net/rate.html

17 link(s) with descriptive text

19 links

0 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://amjad-direct-link.base44.app/	تحويل الملفات ال…	new tab	Add '(opens in new tab)' to text
https://www.2dec.net/rate.html	اسعار الصرفاسعا�…	new tab	Add '(opens in new tab)' to text

98 links and buttons have descriptive text

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

https://amjad-direct-link.base44.app/; https://www.2dec.net/rate.html

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

7 form control(s) checked, no type mismatches

PASS

7 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

7 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

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+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: الماجد فون | Al-Majed Phone

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name الماجد فون | Al-Majed Phone ✓192×192 icon ✓512×512 icon ✓Start URL https://majed-phone-hub.base44.app ✓Display Mode standalone ✓

Name الماجد فون | Al-Majed Phone Display Mode standalone Theme Color #000000 Background Color #ffffff Icons 2 icon(s)

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

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.

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