Skip to content
https://fzcars.ir

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
86
GRADE
B
FIX
3
REVIEW
3
PASS
18
INFO
0
Checks
24
18 PASS 3 REVIEW 3 FIX
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: #9a0002
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::
1 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 1 <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
Favicon & Branding
8 icon(s) detected
REVIEW
8 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: FZ Cars
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name FZ Cars ✓192×192 icon ✗512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name FZ Cars Display Mode standalone Theme Color #9a0002 Background Color #f8f9fb Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA 1 pass AA only
h2 قوانین و مقررات
1.04:1
#000000
on
#04060B
needs 3.0:1 (large text)
24px · mid-page
h2 قوانین پلتفرم FZCARS
1.05:1
#000000
on
#05080E
needs 3.0:1 (large text)
24px · mid-page
h2 مقدمه
1.17:1
#000000
on
#141720
needs 3.0:1 (large text)
24px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 خودروی اید…17.93:13.0:1
#000000
#ECEDEF
Pass
h2 ورود3.80:13.0:1
#000000
#626975
Pass
h2 قوانین و مق…1.04:13.0:1
#000000
#04060B
Fail
h2 قوانین پلت…1.05:13.0:1
#000000
#05080E
Fail
h2 مقدمه1.17:13.0:1
#000000
#141720
Fail
h2 داده‌هایی …17.93:13.0:1
#000000
#ECEDEF
Pass
h2 دسترسی‌ها…17.93:13.0:1
#000000
#ECEDEF
Pass
h2 کوکی‌ها و …17.93:13.0:1
#000000
#ECEDEF
Pass
h2 داده‌های ش…17.93:13.0:1
#000000
#ECEDEF
Pass
h2 مبانی قانو…17.93:13.0:1
#000000
#ECEDEF
Pass
h2 امنیت، احر…17.93:13.0:1
#000000
#ECEDEF
Pass
h2 تحلیل، تحق…17.93:13.0:1
#000000
#ECEDEF
Pass
h2 انتشار عمو…17.93:13.0:1
#000000
#ECEDEF
Pass
h2 اقدامات ام…17.93:13.0:1
#000000
#ECEDEF
Pass
h2 مسئولیت‌ه…17.93:13.0:1
#000000
#ECEDEF
Pass
h2 حقوق شما نس…17.93:13.0:1
#000000
#ECEDEF
Pass
h2 نقش پلتفرم …17.93:13.0:1
#000000
#ECEDEF
Pass
h2 تعهدات کار…17.93:13.0:1
#000000
#ECEDEF
Pass
h2 حل اختلاف و…17.93:13.0:1
#000000
#ECEDEF
Pass
h2 جستجوی خود…17.93:13.0:1
#000000
#ECEDEF
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
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 CONTENTINFO footer

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A
Heading Hierarchy
58 headings
PASS
58 headings
Info::
Single H1 present
Warning::
2 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 ورود
  • H2 قوانین و مقررات
  • H2 قوانین پلتفرم FZCARS
  • H2 مقدمه
  • H2 داده‌هایی که از شما جمع‌آوری می‌شود
  • H3 اطلاعات حساب کاربری
  • H3 اطلاعات مرتبط با آگهی‌ها و تراکنش‌ها
  • H3 اطلاعات تعاملات در ارتباط با سایر کاربران
  • H3 نظرات، بازخوردها و تماس با پشتیبانی
  • H3 گزارش‌ها و شکایات
  • H3 اطلاعات خطا و عملکرد سیستم
  • H2 دسترسی‌های دستگاه
  • H3 دسترسی به موقعیت مکانی
  • H3 دسترسی به عکس، رسانه، فایل و فضای ذخیره‌سازی
  • H3 دسترسی به دوربین
  • H3 دسترسی به میکروفون
  • H3 اعلان‌ها (نوتیفیکیشن‌ها)
  • H3 دسترسی‌های فنی پایه
  • H2 کوکی‌ها و فناوری‌های مشابه
  • H2 داده‌های شخصی حساس
  • H2 مبانی قانونی پردازش داده
  • H2 امنیت، احراز هویت و مقابله با تخلف
  • H2 تحلیل، تحقیق و شخصی‌سازی
  • H2 انتشار عمومی اطلاعات و اشخاص ثالث
  • H2 اقدامات امنیتی
  • H2 مسئولیت‌های امنیتی کاربر
  • H2 حقوق شما نسبت به داده‌های شخصی
  • H2 نقش پلتفرم در معاملات
  • H2 تعهدات کاربران و سلب مسئولیت
  • H2 حل اختلاف و مقررات پایانی
  • H2 جستجوی خودرو
  • H3 پیشنهاد برند
  • H3 نوع خودرو
  • H3 میانبرها
  • H2 درخواست‌ها
  • H2 سفارش خودرو
  • H2 درخواست کارشناسی
  • H1 خودروی ایده‌آل خود را پیدا کنید
  • H2 جستجو
  • H2 برندها
  • H2 نوع بدنه
  • H2 برگزیده‌ها
  • H3 AMG SLC 43
  • H3 COROLA
  • H3 Hilux SRS
  • H3 M750 Li
  • H3 NX300 NX300
  • H3 FJ Cruiser GXR
  • H3 5 Series 520i
  • H3 Hilux SRS
  • H2 چرا از ما خرید کنید؟
  • H3 گسترده‌ترین انتخاب
  • H3 شفافیت کامل
  • H3 پلتفرم مورد اعتماد
  • H3 (empty)
  • H4 مرور
  • H4 تماس
  • H2 (empty)

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
51 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: 51 all-caps heading(s)
A+
Alt Text Quality
All 107 images OK
PASS
All 107 images OK
Info::
97 decorative image(s) correctly marked
Info::
10 image(s) with good alt text
107 images 10 good alt text 97 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 14 controls labeled
PASS
All 14 controls labeled
Info::
14 control(s) properly labeled
14 controls
14 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#modal-phonetelشماره موبایلfor/id
#modal-codetextکد تأیید پیامکیfor/id
#modal-terms-acceptcheckboxnone
#hsm-inputsearchnone
#sr-makeselectبرند *none
#sr-modelselectمدل *none
#sr-trimselectتیپnone
#sr-yeartextسال تولیدnone
#sr-colorselectرنگ بدنهnone
#sr-order-notestextareaتوضیحاتnone
#sr-inspection-notestextareaتوضیحات *none
ktextکلمه کلیدیnone
maselectهمه برندهاnone
ulselectهمه شهرهاnone
A+
Form Input Types
14 form control(s) checked, no type mismatches
PASS
14 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
14 form control(s) checked, no input-semantic issues
PASS
14 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"
PASS
Lang attribute set to "fa"
Info::
<html lang="fa"> is set and valid
Got: fa
A+
Tabindex Anti-Patterns
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 7 visible text node(s) render at >= 12 CSS pixels
PASS
All 7 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title صفحه یافت نشد ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 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.
Info::
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 100/100 — 0 failing, 27 passed
PASS
100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

○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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●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
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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
○`<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.
○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