https://masar-is9-accounting.ramlhlwlalamal.chatgpt.site

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

Favicon & Branding

Action

2 icon(s) detected

FIX

2 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

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

✗ favicon.ico Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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 ✗

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

No <nav> landmark found

No banner (header) landmark

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

Mobile-Readable Font Sizes

Action

75% of visible text renders at >= 12 CSS px (9 below threshold)

REVIEW

75% of visible text renders at >= 12 CSS px (9 below threshold)

9 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> 11.0px ("إدارة متكاملة. دقة في الحسابات. ذكاء الأ..."); <span> 10.0px ("مساحة عملك. بصلاحياتك."); <span> 11.0px ("بوابة الدخول"); <span> 11.0px ("أو ادخل بطريقة أخرى"); <span> 9.0px ("APEX IS9 ERP").

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 404: This page could not be found. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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 Not set ✗Dark theme-color Not set ✗CSS indicators 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

h1 كل تفاصيل أعمالك.

1.55:1

#000000

#342653

needs 3.0:1 (large text)

32px · above the fold

h2 ابدأ يومك بثقة

1.26:1

#000000

#1E193A

needs 3.0:1 (large text)

24px · bottom of viewport

title APEX IS9 ERP | نظام إدارة ال�…

1.61:1

#000000

#362956

needs 4.5:1 (normal text)

16px · top of page (header area)

b APEX

1.62:1

#000000

#372957

needs 3.0:1 (large text)

16px · top of page (header area)

span IS9

1.62:1

#000000

#382957

needs 4.5:1 (normal text)

16px · top of page (header area)

b ERP

1.61:1

#000000

#382857

needs 3.0:1 (large text)

16px · top of page (header area)

span إدارة متكاملة. دقة في �…

1.61:1

#000000

#372858

needs 4.5:1 (normal text)

16px · above the fold

small نظام متكامل لإدارة مو�…

1.60:1

#000000

#372857

needs 4.5:1 (normal text)

16px · above the fold

p رؤية أوضح. إدارة أذكى.

1.58:1

#000000

#362755

needs 4.5:1 (normal text)

16px · above the fold

em برؤية واحدة.

1.52:1

#000000

#322552

needs 4.5:1 (normal text)

16px · above the fold

p إدارة متكاملة للمخزون…

1.51:1

#000000

#312550

needs 4.5:1 (normal text)

16px · above the fold

p قرارات أوضح، وخطوة وا�…

1.49:1

#000000

#30244F

needs 4.5:1 (normal text)

16px · above the fold

b المخزون والمستودعات

1.47:1

#000000

#2F234E

needs 3.0:1 (large text)

16px · above the fold

small من الرول إلى آخر متر

1.45:1

#000000

#2E224D

needs 4.5:1 (normal text)

16px · mid-page

b المالية والحسابات

1.43:1

#000000

#2D214B

needs 3.0:1 (large text)

16px · mid-page

small كل حركة، في مكانها الص…

1.42:1

#000000

#2C2149

needs 4.5:1 (normal text)

16px · mid-page

b الفروع وفريق العمل

1.40:1

#000000

#2A2047

needs 3.0:1 (large text)

16px · mid-page

small ترابط في العمل، ووضوح …

1.39:1

#000000

#292046

needs 4.5:1 (normal text)

16px · mid-page

span مساحة عملك. بصلاحياتك.

1.37:1

#000000

#271F45

needs 4.5:1 (normal text)

16px · mid-page

span بوابة الدخول

1.35:1

#000000

#261E43

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 كل تفاصيل أ…	1.55:1	3.0:1	#000000	#342653	Fail
h2 ابدأ يومك ب…	1.26:1	3.0:1	#000000	#1E193A	Fail
title APEX IS9 ERP \| نظ�…	1.61:1	4.5:1	#000000	#362956	Fail
b APEX	1.62:1	3.0:1	#000000	#372957	Fail
span IS9	1.62:1	4.5:1	#000000	#382957	Fail
b ERP	1.61:1	3.0:1	#000000	#382857	Fail
span إدارة متكا�…	1.61:1	4.5:1	#000000	#372858	Fail
small نظام متكام�…	1.60:1	4.5:1	#000000	#372857	Fail
p رؤية أوضح. �…	1.58:1	4.5:1	#000000	#362755	Fail
em برؤية واحد�…	1.52:1	4.5:1	#000000	#322552	Fail
p إدارة متكا�…	1.51:1	4.5:1	#000000	#312550	Fail
p قرارات أوض�…	1.49:1	4.5:1	#000000	#30244F	Fail
b المخزون وا�…	1.47:1	3.0:1	#000000	#2F234E	Fail
small من الرول إل…	1.45:1	4.5:1	#000000	#2E224D	Fail
b المالية وا�…	1.43:1	3.0:1	#000000	#2D214B	Fail
small كل حركة، في…	1.42:1	4.5:1	#000000	#2C2149	Fail
b الفروع وفر�…	1.40:1	3.0:1	#000000	#2A2047	Fail
small ترابط في ال…	1.39:1	4.5:1	#000000	#292046	Fail
span مساحة عملك.…	1.37:1	4.5:1	#000000	#271F45	Fail
span بوابة الدخ�…	1.35:1	4.5:1	#000000	#261E43	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+

Heading Hierarchy

2 headings

PASS

2 headings

Single H1 present

H1 كل تفاصيل أعمالك.برؤية واحدة.
H2 ابدأ يومك بثقة

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 decorative image(s) correctly marked

2 images 2 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
select	select	لغة النظام	aria-label
username	input	اسم المستخدم	none
password	password	رمز الدخول أو كلمة المرور	none
input	checkbox		none

A+

Link & Button Quality

2 links, 6 buttons — all OK

PASS

2 links, 6 buttons — all OK

2 link(s) with descriptive text

2 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

8 links and buttons have descriptive text

A+

Form Input Types

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

4 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

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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

2 mobile-depth signal(s) detected

PASS

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

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 100/100 — 0 failing, 25 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

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●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

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

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

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