Accessibility

D

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 ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 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

Search

Skip Link

Labeled Navigation 3 <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

Tabindex Anti-Patterns

0 positive, 4 -1-on-focusable

REVIEW

0 positive, 4 -1-on-focusable

tabindex="-1" on naturally-focusable <a>

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

tabindex="-1" on naturally-focusable <a>

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

tabindex="-1" on naturally-focusable <a>

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

tabindex="-1" on naturally-focusable <a>

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

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

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

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title صفحه پیدا نشد | دونکوب ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

B

Favicon & Branding

10 icon(s) detected

REVIEW

10 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

B

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

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 #173f32 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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 دونکوب؛ فروشگاه تخصصی…

2.58:1

#000000

on

#712F9B

needs 3.0:1 (large text)

32px · above the fold

h2 محصولات

1.50:1

#000000

on

#4A0A5E

needs 3.0:1 (large text)

24px · above the fold

h2 دسته‌بندی‌ها

1.33:1

#000000

on

#361C0A

needs 3.0:1 (large text)

24px · above the fold · over background image/gradient

h2 پیشنهادهای دونکوب

1.08:1

#000000

on

#1A0803

needs 3.0:1 (large text)

24px · bottom of viewport

h2 راهنما و مقاله‌های تا…

1.08:1

#000000

on

#1A0803

needs 3.0:1 (large text)

24px · bottom of viewport

h2 دونکوب

1.08:1

#000000

on

#1A0803

needs 3.0:1 (large text)

24px · bottom of viewport

h3 چای سبز برگ‌درشت ۱۰۰ �…

1.08:1

#000000

on

#1A0803

needs 3.0:1 (large text)

19px · bottom of viewport

h3 گل محمدی خشک ۴۰ گرم

1.08:1

#000000

on

#1A0803

needs 3.0:1 (large text)

19px · bottom of viewport

h3 هل سبز ۵۰ گرم

1.08:1

#000000

on

#1A0803

needs 3.0:1 (large text)

19px · bottom of viewport

h3 زعفران سرگل ممتاز ۱ گر…

1.08:1

#000000

on

#1A0803

needs 3.0:1 (large text)

19px · bottom of viewport

h3 تفاوت چای سبز و چای سی�…

1.08:1

#000000

on

#1A0803

needs 3.0:1 (large text)

19px · bottom of viewport

h3 ۳ دمنوش گیاهی برای عصر…

1.08:1

#000000

on

#1A0803

needs 3.0:1 (large text)

19px · bottom of viewport

h3 راهنمای دم‌کردن زعفر�…

1.08:1

#000000

on

#1A0803

needs 3.0:1 (large text)

19px · bottom of viewport

h3 راهنما

1.08:1

#000000

on

#1A0803

needs 3.0:1 (large text)

19px · bottom of viewport

h3 حساب کاربری

1.08:1

#000000

on

#1A0803

needs 3.0:1 (large text)

19px · bottom of viewport

h3 نمادهای اعتماد

1.08:1

#000000

on

#1A0803

needs 3.0:1 (large text)

19px · bottom of viewport

title دونکوب | خرید ادویه و د…

2.13:1

#000000

on

#6C2375

needs 4.5:1 (normal text)

16px · top of page (header area)

a رفتن به محتوای اصلی

3.65:1

#000000

on

#98524E

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a فروشگاه

2.14:1

#000000

on

#6A304C

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

a ادویه‌ها

4.35:1

#000000

on

#915BB3

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

4 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 دونکوب؛ فر�…	2.58:1	3.0:1	#000000	#712F9B	Fail
h2 محصولات	1.50:1	3.0:1	#000000	#4A0A5E	Fail
h2 دسته‌بندی�…	1.33:1	3.0:1	#000000	#361C0A	Fail
h2 پیشنهادهای…	1.08:1	3.0:1	#000000	#1A0803	Fail
h2 راهنما و مق…	1.08:1	3.0:1	#000000	#1A0803	Fail
h2 دونکوب	1.08:1	3.0:1	#000000	#1A0803	Fail
h3 چای سبز برگ…	1.08:1	3.0:1	#000000	#1A0803	Fail
h3 گل محمدی خش…	1.08:1	3.0:1	#000000	#1A0803	Fail
h3 هل سبز ۵۰ گ�…	1.08:1	3.0:1	#000000	#1A0803	Fail
h3 زعفران سرگ�…	1.08:1	3.0:1	#000000	#1A0803	Fail
h3 تفاوت چای س…	1.08:1	3.0:1	#000000	#1A0803	Fail
h3 ۳ دمنوش گیا…	1.08:1	3.0:1	#000000	#1A0803	Fail
h3 راهنمای دم�…	1.08:1	3.0:1	#000000	#1A0803	Fail
h3 راهنما	1.08:1	3.0:1	#000000	#1A0803	Fail
h3 حساب کاربر�…	1.08:1	3.0:1	#000000	#1A0803	Fail
h3 نمادهای اع�…	1.08:1	3.0:1	#000000	#1A0803	Fail
title دونکوب \| خر�…	2.13:1	4.5:1	#000000	#6C2375	Fail
a رفتن به محت…	3.65:1	4.5:1	#000000	#98524E	Fail
a فروشگاه	2.14:1	4.5:1	#000000	#6A304C	Fail
a ادویه‌ها	4.35:1	4.5:1	#000000	#915BB3	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

7 landmarks

PASS

7 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

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

16 headings

PASS

16 headings

Single H1 present

H1 دونکوب؛ فروشگاه تخصصی ادویه، چای، دمنوش و گیاهان
H2 محصولات
H2 دسته‌بندی‌ها
H2 پیشنهادهای دونکوب
H3 چای سبز برگ‌درشت ۱۰۰ گرم
H3 گل محمدی خشک ۴۰ گرم
H3 هل سبز ۵۰ گرم
H3 زعفران سرگل ممتاز ۱ گرم
H2 راهنما و مقاله‌های تازه
H3 تفاوت چای سبز و چای سیاه چیست؟
H3 ۳ دمنوش گیاهی برای عصرهای آرام
H3 راهنمای دم‌کردن زعفران برای برنج
H2 دونکوب
H3 راهنما
H3 حساب کاربری
H3 نمادهای اعتماد

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

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

A+

Alt Text Quality

All 15 images OK

PASS

All 15 images OK

2 decorative image(s) correctly marked

13 image(s) with good alt text

15 images 13 good alt text 2 decorative

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
donkoob-product-search-desktop	search	جست‌وجو در دونکوب	aria-label

A+

Link & Button Quality

38 links, 9 buttons — all OK

PASS

38 links, 9 buttons — all OK

38 link(s) with descriptive text

38 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

47 links and buttons have descriptive text

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 "fa"

PASS

Lang attribute set to "fa"

<html lang="fa"> is set and valid

Got: fa

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Mobile-Readable Font Sizes

All 75 visible text node(s) render at >= 12 CSS pixels

PASS

All 75 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

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 #173f32 Background Color #faf8f3 Icons 3 icon(s)

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

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.

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 96/100 — 1 failing, 27 passed

PASS

96

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.

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
مشاهده همه `div.container > section.section > div.section-head > a`
سفارش‌ها `footer.footer > div.container > nav.footer-phone-links > a`

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

●`[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.

●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

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

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

○Select elements have associated label elements.

○Skip links are focusable.

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

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