Skip to content
https://samanaiq.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
73
GRADE
C
FIX
7
REVIEW
5
PASS
12
INFO
0
Checks
24
12 PASS 5 REVIEW 7 FIX
D
Mobile-Readable Font Sizes
Action
40% of visible text renders at >= 12 CSS px (113 below threshold)
FIX
40% of visible text renders at >= 12 CSS px (113 below threshold)
Warning::
113 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 ("93 منتج"); <span> 11.0px ("42 منتج"); <span> 11.0px ("منتج"); <span> 11.0px ("16"); <span> 11.0px ("منتج").
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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
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: #c8506b
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
Landmark Structure
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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

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

C
Form Accessibility
Action
3 of 4 controls have issues
REVIEW
3 of 4 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search">; <input type="text" name="search" id="mobileSearchInput">
Info::
1 control(s) properly labeled
4 controls
1 labeled
2 placeholder only
1 unlabeled
ControlTypeLabelMethod
#pagiJumpInputnumberرقم الصفحةfor/id
#mobileSearchInputtext(ابحث عن منتج...)placeholder only
searchtext(ابحث عن منتج...)placeholder only
selectselect(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select>

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

<input type="text" name="search">; <input type="text" name="search" id="mobileSearchInput">

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

B
Tap Target Adequacy
2 tap target(s) too small or too close together
REVIEW
2 tap target(s) too small or too close together
Info::
2 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.
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 404 — الصفحة غير موجودة | SAMANA ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Lighthouse Accessibility Audits
Action
Score 76/100 — 5 failing, 20 passed
REVIEW
76

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header.site-header > div.header-mobile > div.hm-actions > button.mob-btn header.site-header > div.header-mobile > div.hm-actions > button.mob-btn
main > section#heroSlider > div.hero-dots > button.hero-dot main > section#heroSlider > div.hero-dots > button.hero-dot
main > section#heroSlider > div.hero-dots > button.hero-dot main > section#heroSlider > div.hero-dots > button.hero-dot
body.js-anim > main > section#heroSlider > button.hero-arrow body.js-anim > main > section#heroSlider > button.hero-arrow
body.js-anim > main > section#heroSlider > button.hero-arrow body.js-anim > main > section#heroSlider > button.hero-arrow
body.js-anim > div#cartSidebar > div.cart-header-bar > button.cart-close body.js-anim > div#cartSidebar > div.cart-header-bar > button.cart-close

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
الأحدث الأقدم السعر: الأقل السعر: الأعلى الاسم div.wrapper > div.sort-bar > div > select.sort-select

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.js-anim > a.wa-float body.js-anim > a.wa-float
div#productsGrid > article.p-card > div.p-card-img > a div#productsGrid > article.p-card > div.p-card-img > a
div#productsGrid > article.p-card > div.p-card-img > a div#productsGrid > article.p-card > div.p-card-img > a
div#productsGrid > article.p-card > div.p-card-img > a div#productsGrid > article.p-card > div.p-card-img > a
div#productsGrid > article.p-card > div.p-card-img > a div#productsGrid > article.p-card > div.p-card-img > a
div#productsGrid > article.p-card > div.p-card-img > a div#productsGrid > article.p-card > div.p-card-img > a
div#productsGrid > article.p-card > div.p-card-img > a div#productsGrid > article.p-card > div.p-card-img > a
div#productsGrid > article.p-card > div.p-card-img > a div#productsGrid > article.p-card > div.p-card-img > a
div#productsGrid > article.p-card > div.p-card-img > a div#productsGrid > article.p-card > div.p-card-img > a
div#productsGrid > article.p-card > div.p-card-img > a div#productsGrid > article.p-card > div.p-card-img > a
div#productsGrid > article.p-card > div.p-card-img > a div#productsGrid > article.p-card > div.p-card-img > a
div#productsGrid > article.p-card > div.p-card-img > a div#productsGrid > article.p-card > div.p-card-img > a
div#productsGrid > article.p-card > div.p-card-img > a div#productsGrid > article.p-card > div.p-card-img > a
div.wrapper > div.pagi-sec > div.pagi > a.pagi-btn div.wrapper > div.pagi-sec > div.pagi > a.pagi-btn
div.wrapper > div.pagi-sec > div.pagi > a.pagi-btn div.wrapper > div.pagi-sec > div.pagi > a.pagi-btn

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

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
EN header.site-header > div.header-mobile > div.hm-actions > button#langToggleBtnMobile
بحث header.site-header > div.mobile-search-wrap > form#mobileSearchForm > button.msb-submit
93 منتج div.branch-scroll > a.branch-card-sh > div.branch-card-sh__body > span.branch-card-sh__count
42 منتج div.branch-scroll > a.branch-card-sh > div.branch-card-sh__body > span.branch-card-sh__count
© 2026 SAMANA — جميع الحقوق محفوظة | تطوير سمانة body.js-anim > footer.site-footer > div.footer-bottom > p
SAMANA footer.site-footer > div.footer-bottom > p > a
دخول body.js-anim > nav.mob-bottom-nav > a.mob-nav-item > span

These are opportunities to improve the legibility of your content.

Best practices

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
main > section#heroSlider > div.hero-dots > button.hero-dot main > section#heroSlider > div.hero-dots > button.hero-dot
main > section#heroSlider > div.hero-dots > button.hero-dot main > section#heroSlider > div.hero-dots > button.hero-dot

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
●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.
●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 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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[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
○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.
○`[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
○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.
A+
Heading Hierarchy
17 headings
PASS
17 headings
Info::
Single H1 present
  • H1 سمانه — متجر عبائات نسائية فاخرة في السماوة | عبي عراقية بتصاميم عصرية ومحتشمة مع توصيل لجميع المحافظات
  • H2 سمانه دعائي 7
  • H2 دعائي 2
  • H2 تسوقي حسب القسم
  • H2 مختاراتنا لكِ
  • H3 حجاب شيفون ساده
  • H3 وحيدة
  • H3 سمر
  • H3 اثر
  • H3 اثر
  • H3 لارا
  • H2 فروعنا اختر فرعك الأقرب
  • H2 الأقسام
  • H2 جميع المنتجات
  • H2 موقع المتجر
  • H3 سلة التسوق
  • H3 الانتقال إلى صفحة
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
14 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: 14 all-caps heading(s)
A+
Alt Text Quality
All 9 images OK
PASS
All 9 images OK
Info::
9 image(s) with good alt text
9 images 9 good alt text
All images have appropriate alt text.
A
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
Info::
Input "search" should use type="search" (currently type="text")
Field name "search" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
Info::
Input "search" should use type="search" (currently type="text")
Field name "search" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
4 form control(s) checked, no input-semantic issues
PASS
4 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
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+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
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+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 سمانه — مت…9.86:13.0:1
#000000
#B9B0AB
Pass
h2 دعائي 215.46:13.0:1
#000000
#DEDDDA
Pass
h2 تسوقي حسب ا…16.19:13.0:1
#000000
#E2E2E0
Pass
h2 مختاراتنا …18.93:13.0:1
#000000
#F3F3F3
Pass
h2 فروعنا18.93:13.0:1
#000000
#F3F3F3
Pass
h2 الأقسام18.93:13.0:1
#000000
#F3F3F3
Pass
h2 موقع المتج…18.93:13.0:1
#000000
#F3F3F3
Pass
h3 حجاب شيفون …18.93:13.0:1
#000000
#F3F3F3
Pass
h3 وحيدة18.93:13.0:1
#000000
#F3F3F3
Pass
h3 سمر18.93:13.0:1
#000000
#F3F3F3
Pass
h3 اثر18.93:13.0:1
#000000
#F3F3F3
Pass
h3 اثر18.93:13.0:1
#000000
#F3F3F3
Pass
h3 لارا18.93:13.0:1
#000000
#F3F3F3
Pass
h3 الانتقال إ…18.93:13.0:1
#000000
#F3F3F3
Pass
title سمانه | متج…17.94:14.5:1
#000000
#EDEDED
Pass
a الرئيسية16.98:14.5:1
#000000
#E7E7E7
Pass
a حقائب16.98:14.5:1
#000000
#E7E7E7
Pass
a شالات16.98:14.5:1
#000000
#E7E7E7
Pass
a عبايات16.98:14.5:1
#000000
#E7E7E7
Pass
a عطور13.67:14.5:1
#000000
#D2D0D0
Pass

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.

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

Send Feedback