Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 4 REVIEW 4 FIX

Mobile-Readable Font Sizes

Action

62% of visible text renders at >= 12 CSS px (35 below threshold)

FIX

62% of visible text renders at >= 12 CSS px (35 below threshold)

35 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> 6.5px ("DAR AL SHARKA"); <span> 10.0px ("✨ الترندات"); <span> 10.0px ("تصنيفاتنا"); <div> 10.5px ("حرير"); <div> 10.5px ("Tast").

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: #c9a96e

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.

Link & Button Quality

1 issue(s) across 59 links and 13 buttons

REVIEW

1 issue(s) across 59 links and 13 buttons

5 link(s) open in new tab without warning

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

Got: https://wa.me/9647739742869; https://www.instagram.com/dar.alsharjah; ; ; https://wa.me/9647739742869

1 button(s) with no accessible text

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

Got: button.music-btn (#276 on page)

54 link(s) with descriptive text

59 links

0 empty

0 generic text

5 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://wa.me/9647739742869	📱 9647739742869	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/dar.alsharjah	Instagram	new tab	Add '(opens in new tab)' to text
	Facebook	new tab	Add '(opens in new tab)' to text
	TikTok	new tab	Add '(opens in new tab)' to text
https://wa.me/9647739742869	WhatsApp	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

66 links and buttons have descriptive text

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

https://wa.me/9647739742869; https://www.instagram.com/dar.alsharjah; ; ; https://wa.me/9647739742869

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.music-btn (#276 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

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 Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 10 fail WCAG AA

REVIEW

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

10 pass 10 fail WCAG AA

h1 الشارقة... عنوان الأنا�…

1.03:1

#000000

#040507

needs 3.0:1 (large text)

32px · mid-page

h3 بحث

1.05:1

#000000

#08090C

needs 3.0:1 (large text)

19px · mid-page

span DAR AL SHARKA

1.29:1

#000000

#1C202B

needs 4.5:1 (normal text)

16px · top of page (header area)

a 🇮🇶 العربية

1.26:1

#000000

#1A1E28

needs 4.5:1 (normal text)

16px · above the fold

a 🇬🇧 English

1.24:1

#000000

#191C26

needs 4.5:1 (normal text)

16px · above the fold

a ☀️ کوردی

1.22:1

#000000

#181B24

needs 4.5:1 (normal text)

16px · above the fold

a الرئيسية

1.18:1

#000000

#151821

needs 4.5:1 (normal text)

16px · above the fold

a كل العبايات

1.16:1

#000000

#13161E

needs 4.5:1 (normal text)

16px · above the fold

a وصل حديثاً

1.14:1

#000000

#11141B

needs 4.5:1 (normal text)

16px · above the fold

a الأكثر مبيعاً

1.12:1

#000000

#101218

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 الشارقة... ع…	1.03:1	3.0:1	#000000	#040507	Fail
h2 تصفحي حسب ا…	19.27:1	3.0:1	#000000	#F7F5F0	Pass
h2 وصل حديثاً	19.27:1	3.0:1	#000000	#F7F5F0	Pass
h2 لمناسباتك �…	19.27:1	3.0:1	#000000	#F7F5F0	Pass
h2 الأكثر مبي�…	19.27:1	3.0:1	#000000	#F7F5F0	Pass
h2 تجربة تسوق …	19.27:1	3.0:1	#000000	#F7F5F0	Pass
h2 كلمات من ال…	19.27:1	3.0:1	#000000	#F7F5F0	Pass
h3 بحث	1.05:1	3.0:1	#000000	#08090C	Fail
h3 دار الشارق�…	19.27:1	3.0:1	#000000	#F7F5F0	Pass
title دار الشارق�…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a تخطَّ إلى ا…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span دار الشارق�…	8.64:1	4.5:1	#000000	#A5A6AB	Pass
span DAR AL SHARKA	1.29:1	4.5:1	#000000	#1C202B	Fail
a 🇮🇶 العرب�…	1.26:1	4.5:1	#000000	#1A1E28	Fail
a 🇬🇧 English	1.24:1	4.5:1	#000000	#191C26	Fail
a ☀️ کوردی	1.22:1	4.5:1	#000000	#181B24	Fail
a الرئيسية	1.18:1	4.5:1	#000000	#151821	Fail
a كل العبايا�…	1.16:1	4.5:1	#000000	#13161E	Fail
a وصل حديثاً	1.14:1	4.5:1	#000000	#11141B	Fail
a الأكثر مبي�…	1.12:1	4.5:1	#000000	#101218	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.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

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

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

11 headings

PASS

11 headings

Single H1 present

H3 بحث
H1 الشارقة... عنوان الأناقة
H2 تصفحي حسب الفئة
H2 وصل حديثاً
H2 لمناسباتك السعيدة
H2 الأكثر مبيعاً
H2 تجربة تسوق استثنائية
H2 كلمات من القلب
H3 دار الشارقة للعبايات
H4 روابط سريعة
H4 خدمة العملاء

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 12 images OK

PASS

All 12 images OK

12 image(s) with good alt text

12 images 12 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	input	البحث	aria-label

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

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

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+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: دار الشارقة للعبايات

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name دار الشارقة للعبايات ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name دار الشارقة للعبايات Display Mode standalone Theme Color #C9A96E Background Color #F7F5F0 Icons 2 icon(s)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Service worker registration detected

The page calls `navigator.serviceWorker.register(...)` -- the prerequisite for any real PWA capability (offline support, push notifications, background sync, Cache API). This is a positive signal; whether the registered worker actually does what you want is a separate question (check DevTools > Application > Service Workers).

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.

Lighthouse Accessibility Audits

Score 90/100 — 3 failing, 22 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.

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
body > main#main-content > div#musicPlayer > button.music-btn `body > main#main-content > div#musicPlayer > button.music-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
DAR AL SHARKA `div.header-center > a.logo > span.logo-text > span.logo-text-en`
عرض الكل `section.section > div.container > div.sec-head-row > a.sec-link`
-34% `article.pcard > a.pcard-img > div.pcard-badges > span.pcard-badge`
38,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-old`
-38% `article.pcard > a.pcard-img > div.pcard-badges > span.pcard-badge`
40,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-old`
الأكثر طلباً `div.container > div.sec-head-row > div > span.section-eyebrow`
عرض الكل `section.section > div.container > div.sec-head-row > a.sec-link`
-4% `article.pcard > a.pcard-img > div.pcard-badges > span.pcard-badge`
50,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-old`
-34% `article.pcard > a.pcard-img > div.pcard-badges > span.pcard-badge`
38,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-old`
-38% `article.pcard > a.pcard-img > div.pcard-badges > span.pcard-badge`
40,000 د.ع `article.pcard > div.pcard-info > div.pcard-price > span.pcard-old`
لماذا نحن؟ `section.why-section > div.container > div.section-head > span.section-eyebrow`
آراء عميلاتنا `section.testimonials-section > div.container > div.section-head > span.section-eyebrow`
تصميم وتطوير Mohammed Khaleel 🇮🇶 `footer.site-footer > div.container > div.footer-bottom > p.footer-credit`

These are opportunities to improve the legibility of your content.

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
دار الشارقة للعبايات DAR AL SHARKA `header.site-header > div.container > div.header-center > a.logo`

○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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●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

○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

○Form elements have associated labels

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

○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

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