Skip to content
https://pars-setia.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
5
REVIEW
4
PASS
15
INFO
0
Checks
24
15 PASS 4 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #0a0a0a
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Alt Text Quality
Action
12 of 57 images have issues
REVIEW
12 of 57 images have issues
Critical::
12 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
1 decorative image(s) correctly marked
Info::
44 image(s) with good alt text
57 images 44 good alt text 1 decorative 12 missing
IssueCount
missing12 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
Mobile Keyboard & Autofill
2/7 eligible field(s) missing autocomplete or inputmode
REVIEW
2/7 eligible field(s) missing autocomplete or inputmode
Info::
2 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: tel, email.
Got: <input type="tel" name="phone" id="cPhone">, <input type="email" name="email" id="cEmail">
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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 Pars Setia | Iranian Dates Supplier & Ex…
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
32px · bottom of viewport · over background image/gradient
h2 Looking for a Reliable Iranian Dates Sup…
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 About Pars Setia
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 5000-Ton Cold Storage
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Products — Mazafati & Kalute Irani…
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Iranian Mazafati Dates; An Authentic Fla…
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Iranian Kalute Dates; A Reliable Choice …
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mazafati vs Kalute Dates — Which Varie…
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Packaging Types — Customized for Your …
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How to Order Iranian Dates from Pars Set…
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Markets We Supply
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Brands
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Iranian Dates for the Russian Market
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Partner With Us
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Live Bulk Date Prices (Tehran Market & O…
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Bulk Order Price Estimator
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Live Currency Exchange & Tether (USDT) R…
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Frequently Asked Questions
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Contact Us
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Precise-Weight Pouch Packaging
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
19px · bottom of viewport

1 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)
ElementRatioRequiredFGBGResult
h1 Pars Setia | Iranian…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Looking for a Reliab…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 About Pars Setia1.06:13.0:1
#000000
#0A0A0A
Fail
h2 5000-Ton Cold Storag…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Our Products — Maz…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Iranian Mazafati Dat…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Iranian Kalute Dates…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Mazafati vs Kalute D…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Packaging Types — …1.06:13.0:1
#000000
#0A0A0A
Fail
h2 How to Order Iranian…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Markets We Supply1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Our Brands1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Iranian Dates for th…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Partner With Us1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Live Bulk Date Price…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Bulk Order Price Est…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Live Currency Exchan…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Frequently Asked Que…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Contact Us1.06:13.0:1
#000000
#0A0A0A
Fail
h3 Precise-Weight Pouch…1.06:13.0:1
#000000
#0A0A0A
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
5 landmarks
PASS
5 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Main navigation" MAIN CONTENTINFO footer
A+
Heading Hierarchy
38 headings
PASS
38 headings
Info::
Single H1 present
  • H1 Pars Setia | Iranian Dates Supplier & Exporter
  • H2 Looking for a Reliable Iranian Dates Supplier?
  • H2 About Pars Setia
  • H2 5000-Ton Cold Storage
  • H2 Our Products — Mazafati & Kalute Iranian Dates
  • H2 Iranian Mazafati Dates; An Authentic Flavor for Global Export
  • H2 Iranian Kalute Dates; A Reliable Choice for Your Export Market
  • H2 Mazafati vs Kalute Dates — Which Variety Fits Your Market?
  • H2 Packaging Types — Customized for Your Market & Country
  • H3 Precise-Weight Pouch Packaging
  • H3 Shrink-Wrapped Drawer Packaging
  • H3 5kg Telescopic Bulk Carton
  • H3 Traditional Packaging
  • H2 How to Order Iranian Dates from Pars Setia
  • H3 Send your inquiry
  • H3 Receive specifications & quotation
  • H3 Agree packaging & terms
  • H3 Sorting, packing & cold storage
  • H3 Shipment & documents
  • H2 Markets We Supply
  • H2 Our Brands
  • H3 PARS SETIA
  • H3 FINIKATRA
  • H2 Iranian Dates for the Russian Market
  • H2 Partner With Us
  • H2 Live Bulk Date Prices (Tehran Market & Origin Rates)
  • H3 Mazafati Dates (Bulk Wholesale)
  • H3 Kalute Dates (Bulk Wholesale)
  • H2 Bulk Order Price Estimator
  • H2 Live Currency Exchange & Tether (USDT) Rates
  • H2 Frequently Asked Questions
  • H2 Contact Us
  • H3 Contact Our Managers
  • H4 Saess Fouladvand
  • H4 Salar Fouladvand
  • H4 Explore
  • H4 Languages
  • H4 Contact
A+
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
2 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: 2 all-caps heading(s)
A+
Form Accessibility
All 21 controls labeled
PASS
All 21 controls labeled
Info::
21 control(s) properly labeled
21 controls
21 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
selectselectLanguagearia-label
#calcProductselectDate typefor/id
#calcTonsnumberQuantity (tons)for/id
#calcCurrencyselectShow price infor/id
#ratesBaseCurrencyselectBase Currencyfor/id
#cNametextName *none
#cPhonetelPhone / WhatsApp *none
#cEmailemailEmailnone
#cCompanytextCompanynone
#cProductselectDate typenone
#cTonnagenumberTonnage (tons)none
#cCountrytextDestination countrynone
#cPorttextDestination port / citynone
#cIncotermselectDelivery terms (Incoterms)none
#cShipselectShipping typenone
#cTimingtextTarget shipment date / frequencynone
#cPayselectPayment methodnone
#cPackselectPackaging typenone
#cPackNotetextareaPackaging detailsnone
#cMsgtextareaAnything else we should know?none
#chatInputtextType your messagearia-label
A+
Form Input Types
21 form control(s) checked, no type mismatches
PASS
21 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
21 form control(s) checked, no input-semantic issues
PASS
21 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
PASS
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input id="cWebsite">
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.)
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+
Mobile-Readable Font Sizes
All 311 visible text node(s) render at >= 12 CSS pixels
PASS
All 311 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 32 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
Chat on WhatsApp div.managers-grid > div.manager-card > a.manager-info-link > span.wa-label

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
tbody#currencyTableBody > tr > td.currency-code > img tbody#currencyTableBody > tr > td.currency-code > img
tbody#currencyTableBody > tr > td.currency-code > img tbody#currencyTableBody > tr > td.currency-code > img
tbody#currencyTableBody > tr > td.currency-code > img tbody#currencyTableBody > tr > td.currency-code > img
tbody#currencyTableBody > tr > td.currency-code > img tbody#currencyTableBody > tr > td.currency-code > img
tbody#currencyTableBody > tr > td.currency-code > img tbody#currencyTableBody > tr > td.currency-code > img
tbody#currencyTableBody > tr > td.currency-code > img tbody#currencyTableBody > tr > td.currency-code > img
tbody#currencyTableBody > tr > td.currency-code > img tbody#currencyTableBody > tr > td.currency-code > img
tbody#currencyTableBody > tr > td.currency-code > img tbody#currencyTableBody > tr > td.currency-code > img
tbody#currencyTableBody > tr > td.currency-code > img tbody#currencyTableBody > tr > td.currency-code > img
tbody#currencyTableBody > tr > td.currency-code > img tbody#currencyTableBody > tr > td.currency-code > img
tbody#currencyTableBody > tr > td.currency-code > img tbody#currencyTableBody > tr > td.currency-code > img
tbody#currencyTableBody > tr > td.currency-code > img tbody#currencyTableBody > tr > td.currency-code > img

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
●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.
●Select elements have associated label elements.
●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
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●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
●Links are distinguishable without relying on color.
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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.
○`[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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○No element has a `[tabindex]` value greater than 0
○`<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
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback