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 9 REVIEW 3 FIX

Mobile-Readable Font Sizes

Action

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

FIX

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

50 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> 9.1px ("ابدأ رحلتك"); <span> 9.1px ("ابدأ رحلتك"); <span> 9.1px ("اكتشف البرنامج"); <span> 9.1px ("اكتشف البرنامج"); <h3> 10.2px ("اختر صح").

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

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 2 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Heading Text Quality

3 heading-text-quality issue(s) detected

REVIEW

3 heading-text-quality issue(s) detected

3 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "01" - H3: "02" - H3: "03"

Got: 3 ≤2-char heading(s)

3 heading(s) are over 120 characters -- likely a misformatted paragraph

Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H1: 157 chars - H2: 164 chars - H2: 144 chars

Got: 3 >120-char heading(s)

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

Alt Text Quality

7 of 11 images have issues

REVIEW

7 of 11 images have issues

3 image(s) with filename as alt text

4 image(s) with generic alt text

4 image(s) with good alt text

11 images 4 good alt text 7 generic

Issue	Count
filename	3 image(s)
generic	4 image(s)

Link & Button Quality

1 issue(s) across 51 links and 8 buttons

REVIEW

1 issue(s) across 51 links and 8 buttons

8 link(s) open in new tab without warning

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

Got: https://www.youtube.com/; #; #; https://www.youtube.com/; #; #; https://innovi.biz; https://www.motolink.sa/ar/terms-conditions

1 button(s) with no accessible text

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

Got: button.close-button (#98 on page)

43 link(s) with descriptive text

51 links

0 empty

0 generic text

8 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.youtube.com/	youtube	new tab	Add '(opens in new tab)' to text
#	tiktok	new tab	Add '(opens in new tab)' to text
#	snapchat	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/	youtube	new tab	Add '(opens in new tab)' to text
#	tiktok	new tab	Add '(opens in new tab)' to text
#	snapchat	new tab	Add '(opens in new tab)' to text
https://innovi.biz	INNOVI.	new tab	Add '(opens in new tab)' to text
https://www.motolink.sa/ar/terms-conditi…	الشروط والأحكام	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

50 links and buttons have descriptive text

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

https://www.youtube.com/; #; #; https://www.youtube.com/; #; #; https://innovi.biz; https://www.motolink.sa/ar/terms-conditions

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.close-button (#98 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

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Favicon & Branding

Action

6 icon(s) detected

REVIEW

6 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓

Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

color-scheme meta tag present

The site declares support for light and dark color schemes via <meta name='color-scheme'>.

Got: dark

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta dark ✓Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

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

h3 اختر صح

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 عادات البايكر الآمن

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 التدريب العملي

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 إقرأ الطريق

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 القيادة الجماعية

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

h3 التدريب مع المرشد

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

title موتولينك

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · top of page (header area)

span الرئيسية

1.06:1

#000000

#0A0A0A

needs 4.5:1 (normal text)

16px · top of page (header area)

span البرنامج التدريبي

1.04:1

#000000

#060606

needs 4.5:1 (normal text)

16px · top of page (header area)

span مجتمع موتولينك

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

span عن موتولينك

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span تواصل معنا

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span اختر اللغة

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a English

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a العربية

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

a اردو

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span الرئيسية

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span البرنامج التدريبي

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span مجتمع موتولينك

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

span عن موتولينك

1.00:1

#000000

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h3 اختر صح	1.00:1	3.0:1	#000000	#000000	Fail
h3 عادات البا�…	1.00:1	3.0:1	#000000	#000000	Fail
h3 التدريب ال�…	1.00:1	3.0:1	#000000	#000000	Fail
h3 إقرأ الطري�…	1.00:1	3.0:1	#000000	#000000	Fail
h3 القيادة ال�…	1.00:1	3.0:1	#000000	#000000	Fail
h3 التدريب مع …	1.00:1	3.0:1	#000000	#000000	Fail
title موتولينك	1.06:1	4.5:1	#000000	#0A0A0A	Fail
span الرئيسية	1.06:1	4.5:1	#000000	#0A0A0A	Fail
span البرنامج ا�…	1.04:1	4.5:1	#000000	#060606	Fail
span مجتمع موتو�…	1.00:1	4.5:1	#000000	#000000	Fail
span عن موتولين�…	1.00:1	4.5:1	#000000	#000000	Fail
span تواصل معنا	1.00:1	4.5:1	#000000	#000000	Fail
span اختر اللغة	1.00:1	4.5:1	#000000	#000000	Fail
a English	1.00:1	4.5:1	#000000	#000000	Fail
a العربية	1.00:1	4.5:1	#000000	#000000	Fail
a اردو	1.00:1	4.5:1	#000000	#000000	Fail
span الرئيسية	1.00:1	4.5:1	#000000	#000000	Fail
span البرنامج ا�…	1.00:1	4.5:1	#000000	#000000	Fail
span مجتمع موتو�…	1.00:1	4.5:1	#000000	#000000	Fail
span عن موتولين�…	1.00:1	4.5:1	#000000	#000000	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.

Heading Hierarchy

19 headings, 1 skip(s)

PASS

19 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H5 (missing H3)

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

H1 ابدأ شغفك بالدراجات بخطوة صح
H2 أكثر من مجرد تدريب على قيادة الدراجة
H2 رحلتك التدريبية مع موتولينك
H3 اختر صح
H3 01
H3 عادات البايكر الآمن
H3 02
H3 التدريب العملي
H3 03
H3 إقرأ الطريق
H3 04
H3 القيادة الجماعية
H3 05
H3 التدريب مع المرشد
H3 06
H2 ماذا ستتعلم في برنامج موتولينك ؟
H2 لماذا موتولينك ؟
H2 كل رحلة تبدأ بقرار… ورحلتك تبدأ مع موتولينك.
H5 تحقق من رقم جوالك skipped

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

A+

Form Accessibility

All 16 controls labeled

PASS

All 16 controls labeled

16 control(s) properly labeled

16 controls

16 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#identifier	text	البريد الإلكتروني أو رقم الجوال	for/id
#first_name	text	الاسم الأول	for/id
#last_name	text	اسم العائلة	for/id
#reg_phone	text	رقم الجوال	for/id
#email	text	البريد الإلكتروني (اختياري)	for/id
#city_id	select	المدينة	for/id
#gender_male	radio	ذكر	for/id
#gender_female	radio	أنثى	for/id
#address	text	العنوان (اختياري)	for/id
#accept_terms	checkbox	أوافق على الشروط والأحكام	for/id
otp-box-0	text	الرقم 1	aria-label
otp-box-1	text	الرقم 2	aria-label
otp-box-2	text	الرقم 3	aria-label
otp-box-3	text	الرقم 4	aria-label
otp-box-4	text	الرقم 5	aria-label
otp-box-5	text	الرقم 6	aria-label

Form Input Types

2 input(s) using type=text where a specific type would help

PASS

2 input(s) using type=text where a specific type would help

Input "phone" should use type="tel" (currently type="text")

Field name "phone" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.

Input "email" should use type="email" (currently type="text")

Field name "email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

All 2 eligible field(s) carry autocomplete/inputmode

PASS

All 2 eligible field(s) carry autocomplete/inputmode

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

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

tabindex="-1" on naturally-focusable <a id="register-tab">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

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

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 — 1 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
بواسطة INNOVI. `div.container > div.row > div.col-md-auto > p.rbt-link-hover`

These are opportunities to improve the legibility of your content.

○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

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

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

○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

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