Skip to content
https://safaqat.om

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
4
REVIEW
6
PASS
14
INFO
0
Checks
24
14 PASS 6 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #0e2a56
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
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.
B
Mobile Keyboard & Autofill
1/4 eligible field(s) missing autocomplete or inputmode
REVIEW
1/4 eligible field(s) missing autocomplete or inputmode
Info::
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" name="email" id="f-email">
C
Tabindex Anti-Patterns
Action
0 positive, 8 -1-on-focusable
REVIEW
0 positive, 8 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button id="svx-tab-g2">
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.)
Info::
tabindex="-1" on naturally-focusable <button id="svx-tab-g3">
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.)
Info::
tabindex="-1" on naturally-focusable <button id="svx-tab-g4">
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.)
Info::
tabindex="-1" on naturally-focusable <button id="svx-tab-g5">
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.)
Info::
tabindex="-1" on naturally-focusable <button>
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.)
Info::
tabindex="-1" on naturally-focusable <button>
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.)
Info::
tabindex="-1" on naturally-focusable <button>
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.)
Info::
tabindex="-1" on naturally-focusable <input>
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.)
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
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.37:1
#000000
on
#18253C
needs 3.0:1 (large text)
32px · above the fold
h2 المناقصات الحصرية
1.42:1
#000000
on
#1B283E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 بدأنا بمجموعة واتساب
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 خدماتنا
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 منصاتنا الرقمية
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ماذا يقول عملاؤنا؟
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 الأخبار
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 المؤسسون
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 تواصل معنا
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 إمكانية الوصول
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 رؤيتنا
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 هدفنا
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 قيمنا
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 ما أنجزناه
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 العقود
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 منصة صفقات
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 منصة تمكين
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 منصة تعاقد
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 الأخبار المميزة
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 صفقات توقّع اتفاقية تØ…
1.39:1
#000000
on
#19263E
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 المناقصات Ø…1.37:13.0:1
#000000
#18253C
Fail
h2 المناقصات Ø…1.42:13.0:1
#000000
#1B283E
Fail
h2 بدأنا بمجمÙ…1.39:13.0:1
#000000
#19263E
Fail
h2 خدماتنا1.39:13.0:1
#000000
#19263E
Fail
h2 منصاتنا الØ…1.39:13.0:1
#000000
#19263E
Fail
h2 ماذا يقول ع…1.39:13.0:1
#000000
#19263E
Fail
h2 الأخبار1.39:13.0:1
#000000
#19263E
Fail
h2 المؤسسون1.39:13.0:1
#000000
#19263E
Fail
h2 تواصل معنا1.39:13.0:1
#000000
#19263E
Fail
h2 إمكانية الÙ…1.39:13.0:1
#000000
#19263E
Fail
h3 رؤيتنا1.39:13.0:1
#000000
#19263E
Fail
h3 هدفنا1.39:13.0:1
#000000
#19263E
Fail
h3 قيمنا1.39:13.0:1
#000000
#19263E
Fail
h3 ما أنجزناه1.39:13.0:1
#000000
#19263E
Fail
h3 العقود1.39:13.0:1
#000000
#19263E
Fail
h3 منصة صفقات1.39:13.0:1
#000000
#19263E
Fail
h3 منصة تمكين1.39:13.0:1
#000000
#19263E
Fail
h3 منصة تعاقد1.39:13.0:1
#000000
#19263E
Fail
h3 الأخبار الÙ…1.39:13.0:1
#000000
#19263E
Fail
h3 صفقات توقّØ…1.39:13.0:1
#000000
#19263E
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
10 landmarks
PASS
10 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Warning::
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
BANNER header NAV "القائمة الرئيسية" MAIN ASIDE CONTENTINFO footer

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
50 headings
PASS
50 headings
Info::
Single H1 present
  • H1 المناقصات صارت أسهل
  • H2 المناقصات الحصرية
  • H2 بدأنا بمجموعة واتساب
  • H3 رؤيتنا
  • H3 هدفنا
  • H3 قيمنا
  • H3 ما أنجزناه
  • H2 خدماتنا
  • H3 العقود
  • H2 منصاتنا الرقمية
  • H3 منصة صفقات
  • H3 منصة تمكين
  • H3 منصة تعاقد
  • H2 ماذا يقول عملاؤنا؟
  • H2 الأخبار
  • H3 الأخبار المميزة
  • H3 صفقات توقّع اتفاقية تعاون لثلاث سنوات مع وزارة الأوقاف والشؤون الدينية
  • H3 جميع الأخبار
  • H3 صفقات توقّع اتفاقية تعاون لثلاث سنوات مع وزارة الأوقاف والشؤون الدينية
  • H3 تتويج صفقات في جائزة الرؤية الاقتصادية ٢٠٢٥
  • H3 المعتصم السيفي ينضم إلى برنامج القيادة للشركات الناشئة
  • H3 عام البدايات
  • H4 المشاركة في كومكس
  • H2 المؤسسون
  • H3 المعتصم السيفي
  • H3 سليمان السيفي
  • H3 ماجد السيفي
  • H3 إبراهيم السيفي
  • H3 فريق العمل
  • H4 غصين الخصيبي
  • H4 بثينة البادرية
  • H4 فاطمة الوضاحية
  • H4 صفاء الحاتمية
  • H4 محمد المقبالي
  • H4 نزار العدوي
  • H4 غصين الخصيبي
  • H4 بثينة البادرية
  • H4 فاطمة الوضاحية
  • H4 صفاء الحاتمية
  • H4 محمد المقبالي
  • H4 نزار العدوي
  • H2 تواصل معنا
  • H3 اطلب خدمة
  • H3 تم استلام طلبك
  • H4 الشركة
  • H4 المنصات
  • H4 تابعنا
  • H2 إمكانية الوصول
  • H3 القراءة والرؤية
  • H3 الحركة والمؤشر
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
50 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: 50 all-caps heading(s)
A+
Alt Text Quality
All 47 images OK
PASS
All 47 images OK
Info::
14 decorative image(s) correctly marked
Info::
33 image(s) with good alt text
47 images 33 good alt text 14 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 7 controls labeled
PASS
All 7 controls labeled
Info::
7 control(s) properly labeled
7 controls
7 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#f-nameinputالاسم*for/id
#f-orginputالجهة(اختياري)for/id
#f-ccselectرمز الدولةaria-label
#f-phonetelرقم الهاتف*for/id
#f-emailemailالبريد الإلكتروني(اختياري)for/id
#f-svcselectالخدمة المطلوبة(اختياري)for/id
#f-msgtextareaتفاصيل المشروع*for/id
A+
Form Input Types
7 form control(s) checked, no type mismatches
PASS
7 form control(s) checked, no type mismatches
Info::
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
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "ar"
PASS
Lang attribute set to "ar"
Info::
<html lang="ar"> is set and valid
Got: ar
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 284 visible text node(s) render at >= 12 CSS pixels
PASS
All 284 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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 — 1 failing, 31 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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
صفقات body > header#header > div.container > a.brand
○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
●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
●`[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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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 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.
○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.
○`<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.
○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.

Send Feedback