Skip to content
https://gharbdental.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
7
REVIEW
6
PASS
11
INFO
0
Checks
24
11 PASS 6 REVIEW 7 FIX
D
Form Accessibility
Action
8 of 8 controls have issues
FIX
8 of 8 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="form_fields[field_190ade3]" id="form-field-field_190ade3">; <input type="text" name="form_fields[field_190ade3]" id="form-field-field_190ade3">
Warning::
6 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="form_fields[name]" id="form-field-name">; <input type="tel" name="form_fields[email]" id="form-field-email">; <textarea name="form_fields[message]" id="form-field-message">; <input type="text" name="form_fields[name]" id="form-field-name">; <input type="email" name="form_fields[email]" id="form-field-email">; <textarea name="form_fields[message]" id="form-field-message">
8 controls
0 labeled
6 placeholder only
2 unlabeled
ControlTypeLabelMethod
#form-field-nametext(نام)placeholder only
#form-field-emailtel(شماره تماس)placeholder only
#form-field-messagetextarea(پیام)placeholder only
#form-field-nametext(نام)placeholder only
#form-field-emailemail(آدرس ایمیل)placeholder only
#form-field-messagetextarea(پیام)placeholder only
#form-field-field_190ade3text(none)none
#form-field-field_190ade3text(none)none

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

<input type="text" name="form_fields[field_190ade3]" id="form-field-field_190ade3">; <input type="text" name="form_fields[field_190ade3]" id="form-field-field_190ade3">

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="form_fields[name]" id="form-field-name">; <input type="tel" name="form_fields[email]" id="form-field-email">; <textarea name="form_fields[message]" id="form-field-message">; <input type="text" name="form_fields[name]" id="form-field-name">; <input type="email" name="form_fields[email]" id="form-field-email">; <textarea name="form_fields[message]" id="form-field-message">

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

D
Tabindex Anti-Patterns
Action
0 positive, 46 -1-on-focusable
FIX
0 positive, 46 -1-on-focusable
Info::
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.)
Info::
tabindex="-1" on naturally-focusable <a id="sm-1785478781564984-1">
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 <a id="sm-1785478781564984-3">
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 <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.)
Info::
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.)
Info::
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.)
Info::
tabindex="-1" on naturally-focusable <a id="sm-1785478781564984-5">
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 <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.)
Info::
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.)
Info::
tabindex="-1" on naturally-focusable <a id="sm-1785478781564984-7">
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 <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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
tabindex="-1" on naturally-focusable <a id="sm-1785478781564984-9">
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 <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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
Info::
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.)
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-73bt87
404 Page Quality Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://gharbdental.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://gharbdental.com/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 ModeNo Dark Mode Detected
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::
4 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 4 <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.
C
Landmark Structure
Action
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
2 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) NAV "فهرست" MAIN CONTENTINFO (missing!)

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

B
Heading Hierarchy
29 headings
REVIEW
29 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 کلینیک دندانپزشکی دنتال غرب
  • H2 درباره دنتال غرب
  • H2 Dental Gharb Clinic
  • H2 About Gharb Dental
  • H2 نمونه کار های کلینیک دنتال غرب
  • H2 کلینیک دندانپزشکی دنتال غرب
  • H2 دندانپزشکی
  • H2 کلینیک دندانپزشکی
  • H2 دندانپزشکی در تهران
  • H2 دندانپزشکی تخصصی غرب تهران
  • H2 دندانپزشکی زیبایی غرب تهران
  • H2 دندانپزشکی زیبایی در سعادت‌آباد
  • H2 دندانپزشکی در سعادت‌آباد
  • H2 کلینیک دندانپزشکی در سعادت‌آباد
  • H2 کامپوزیت دندان
  • H2 کامپوزیت دندان در سعادت‌آباد
  • H2 مرکز زیبایی دندان در سعادت‌آباد
  • H2 لمینت دندان
  • H2 لمینت دندان در تهران
  • H2 لمینت دندان در سعادت‌آباد
  • H2 ایمپلنت دندان
  • H2 ارتودنسی دندان
  • H2 ارتودنسی در تهران
  • H2 ایمپلنت دیجیتال در تهران
  • H2 ایمپلنت دندان در سعادت‌آباد
  • H2 مرکز ایمپلنت دندان در غرب تهران
  • H2 کاشت دندان در سعادت‌آباد
  • H2 بلیچینگ دندان
  • H2 بلیچینگ تخصصی

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Mobile-Readable Font Sizes
90% of visible text renders at >= 12 CSS px (5 below threshold)
REVIEW
90% of visible text renders at >= 12 CSS px (5 below threshold)
Info::
5 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: <strong> 11.0px ("دنتال غرب"); <p> 11.0px ("با تکیه بر جدیدترین فناوری\u200cهای دندانپزشک..."); <p> 11.0px ("هدف ما ساختن لبخندی سالم، زیبا و ماندگار..."); <span> 11.5px ("پایین بروید"); <p> 11.5px ("Scroll Down").
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA 1 pass AA only
title کلینیک دندانپزشکی در …
3.14:1
#000000
on
#11666B
needs 4.5:1 (normal text)
16px · top of page (header area)
a پرش به محتوا
4.42:1
#000000
on
#14807F
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 کلینیک دند…18.95:13.0:1
#000000
#F3F3F5
Pass
h2 درباره دنت…18.95:13.0:1
#000000
#F3F3F5
Pass
h2 Dental Gharb Clinic18.95:13.0:1
#000000
#F3F3F5
Pass
h2 About Gharb Dental18.95:13.0:1
#000000
#F3F3F5
Pass
h2 نمونه کار ه…18.95:13.0:1
#000000
#F3F3F5
Pass
title کلینیک دند…3.14:14.5:1
#000000
#11666B
Fail
a پرش به محتو…4.42:14.5:1
#000000
#14807F
Fail
a صفحه اصلی6.08:14.5:1
#000000
#169A94
Pass
a خدمات8.22:14.5:1
#000000
#19B5A8
Pass
a خدمات تخصص…9.90:14.5:1
#000000
#1BC7B7
Pass
a ایمپلنت دن…10.84:14.5:1
#000000
#1CD0C1
Pass
a جراحی دندا…18.95:14.5:1
#000000
#F3F3F5
Pass
a جراحی لثه18.95:14.5:1
#000000
#F3F3F5
Pass
a خدمات دندا…18.95:14.5:1
#000000
#F3F3F5
Pass
a لمینیت18.95:14.5:1
#000000
#F3F3F5
Pass
a کامپوزیت د…18.95:14.5:1
#000000
#F3F3F5
Pass
a بلیچینگ دن…18.95:14.5:1
#000000
#F3F3F5
Pass
a خدمات عموم…18.95:14.5:1
#000000
#F3F3F5
Pass
a پر کردن دند…18.95:14.5:1
#000000
#F3F3F5
Pass
a عصب کشی دند…18.95:14.5:1
#000000
#F3F3F5
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.

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
27 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: 27 all-caps heading(s)
A+
Alt Text Quality
All 37 images OK
PASS
All 37 images OK
Info::
17 decorative image(s) correctly marked
Info::
20 image(s) with good alt text
37 images 20 good alt text 17 decorative
All images have appropriate alt text.
A+
Form Input Types
8 form control(s) checked, no type mismatches
PASS
8 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
8 form control(s) checked, no input-semantic issues
PASS
8 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 "fa-IR"
PASS
Lang attribute set to "fa-IR"
Info::
<html lang="fa-IR"> is set and valid
Got: fa-IR
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
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+
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::
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.
A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 28 passed
PASS
93

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.

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
درباره دنتال غرب div.e-con-inner > div.elementor-element > div.elementor-widget-container > h2.elementor-heading-title
دنتال غرب با تکیه بر جدیدترین فناوری‌های دندانپزشکی و تیمی حرفه‌ای، تجربه‌ای متمای… div.e-con-inner > div.elementor-element > div.elementor-widget-container > p
About Gharb Dental div.e-con-inner > div.elementor-element > div.elementor-widget-container > h2.elementor-heading-title
Dental Gharb combines the latest dental technologies with a team of skilled pro… div.e-con-inner > div.elementor-element > div.elementor-widget-container > p
Dental Gharb div.elementor-element > div.elementor-widget-container > p > strong
Our goal is to create a healthy, beautiful, and lasting smile for you. div.e-con-inner > div.elementor-element > div.elementor-widget-container > p
Examination div.elementor-element > div.elementor-widget-container > span.elementor-heading-title > a
Fillings div.elementor-element > div.elementor-widget-container > span.elementor-heading-title > a
Extraction div.elementor-element > div.elementor-widget-container > span.elementor-heading-title > a
root canal div.elementor-element > div.elementor-widget-container > span.elementor-heading-title > a
Implant div.elementor-element > div.elementor-widget-container > span.elementor-heading-title > a
Cleaning div.elementor-element > div.elementor-widget-container > span.elementor-heading-title > a
Imaging div.elementor-element > div.elementor-widget-container > span.elementor-heading-title > a
Surgery div.elementor-element > div.elementor-widget-container > span.elementor-heading-title > a
Dentures div.elementor-element > div.elementor-widget-container > span.elementor-heading-title > a
contact us div.e-con-inner > div.elementor-element > div.elementor-widget-container > p.elementor-heading-title
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-name form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-name
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-tel > input#form-field-email form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-tel > input#form-field-email
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-textarea > textarea#form-field-message form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-textarea > textarea#form-field-message
Send Message div.e-con-inner > div.elementor-element > div.elementor-widget-container > p.elementor-heading-title
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-name form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-text > input#form-field-name
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-email > input#form-field-email form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-email > input#form-field-email
form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-textarea > textarea#form-field-message form.elementor-form > div.elementor-form-fields-wrapper > div.elementor-field-type-textarea > textarea#form-field-message
Other Contact Ways div.e-con-inner > div.elementor-element > div.elementor-widget-container > p.elementor-heading-title
درباره‌ی ما div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
جرم‌گیری و بلیچینگ div.elementor-testimonial > div.elementor-testimonial__footer > cite.elementor-testimonial__cite > span.elementor-testimonial__title
کلینیک دندانپزشکی دنتال غرب div.elementor-element > div.elementor-widget-container > h2.elementor-heading-title > a
ادامه مطلب div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text

These are opportunities to improve the legibility of your content.

Names and labels

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
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon
div.elementor-element > div.elementor-element > div.elementor-widget-container > a div.elementor-element > div.elementor-element > div.elementor-widget-container > a
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon
div.e-con-inner > div.elementor-element > div.elementor-widget-container > a div.e-con-inner > div.elementor-element > div.elementor-widget-container > a
div.e-con-inner > div.elementor-element > div.elementor-widget-container > a div.e-con-inner > div.elementor-element > div.elementor-widget-container > a
div.e-con-inner > div.elementor-element > div.elementor-widget-container > a div.e-con-inner > div.elementor-element > div.elementor-widget-container > a
div.e-con-inner > div.elementor-element > div.elementor-widget-container > a div.e-con-inner > div.elementor-element > div.elementor-widget-container > a
div.e-con-inner > div.elementor-element > div.elementor-widget-container > a div.e-con-inner > div.elementor-element > div.elementor-widget-container > a
div.e-con-inner > div.elementor-element > div.elementor-widget-container > a div.e-con-inner > div.elementor-element > div.elementor-widget-container > a
div.e-con-inner > div.elementor-element > div.elementor-widget-container > a div.e-con-inner > div.elementor-element > div.elementor-widget-container > a
div.e-con-inner > div.elementor-element > div.elementor-widget-container > a div.e-con-inner > div.elementor-element > div.elementor-widget-container > a
div.e-con-inner > div.elementor-element > div.elementor-widget-container > a div.e-con-inner > div.elementor-element > div.elementor-widget-container > a
div.e-con-inner > div.elementor-element > div.elementor-widget-container > a div.e-con-inner > div.elementor-element > div.elementor-widget-container > a
div.elementor-element > div.elementor-element > div.elementor-widget-container > a div.elementor-element > div.elementor-element > div.elementor-widget-container > a
div.elementor-element > div.elementor-element > div.elementor-widget-container > a div.elementor-element > div.elementor-element > div.elementor-widget-container > a
div.elementor-element > div.elementor-element > div.elementor-widget-container > a div.elementor-element > div.elementor-element > div.elementor-widget-container > a
div.elementor-element > div.elementor-element > div.elementor-widget-container > a div.elementor-element > div.elementor-element > div.elementor-widget-container > a
div.elementor-widget-container > div.elementor-social-icons-wrapper > span.elementor-grid-item > a.elementor-icon div.elementor-widget-container > div.elementor-social-icons-wrapper > span.elementor-grid-item > a.elementor-icon
div.elementor-widget-container > div.elementor-social-icons-wrapper > span.elementor-grid-item > a.elementor-icon div.elementor-widget-container > div.elementor-social-icons-wrapper > span.elementor-grid-item > a.elementor-icon
div.elementor-widget-container > div.elementor-social-icons-wrapper > span.elementor-grid-item > a.elementor-icon div.elementor-widget-container > div.elementor-social-icons-wrapper > span.elementor-grid-item > a.elementor-icon
div.elementor-widget-container > div.elementor-social-icons-wrapper > span.elementor-grid-item > a.elementor-icon div.elementor-widget-container > div.elementor-social-icons-wrapper > span.elementor-grid-item > a.elementor-icon

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.

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.
`button`, `link`, and `menuitem` elements have accessible names
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
`<frame>` or `<iframe>` elements have a title
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
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
`<video>` elements contain a `<track>` element with `[kind="captions"]`
`[accesskey]` values are unique
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
`<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
Select elements have associated label elements.
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.
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.
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback