https://parspack.com
Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.SCORE
68
GRADE
D
FIX
8
REVIEW
7
PASS
9
INFO
0
Checks
249 PASS 7 REVIEW 8 FIX
DMobile Keyboard & AutofillAction2/2 eligible field(s) missing autocomplete or inputmodeFIX
Mobile Keyboard & Autofill
Action2/2 eligible field(s) missing autocomplete or inputmode
2/2 eligible field(s) missing autocomplete or inputmode
Warning::
2 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: name, email.
Got: <input type="text" name="name">, <input type="text" name="email">
DTap Target AdequacyAction22 tap target(s) too small or too close togetherFIX
Tap Target Adequacy
Action22 tap target(s) too small or too close together
22 tap target(s) too small or too close together
Warning::
22 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.
DMobile-Readable Font SizesAction61% of visible text renders at >= 12 CSS px (24 below threshold)FIX
Mobile-Readable Font Sizes
Action61% of visible text renders at >= 12 CSS px (24 below threshold)
61% of visible text renders at >= 12 CSS px (24 below threshold)
Warning::
24 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: <div> 11.0px ("مناسب برای سایت\u200cهای پربازدید وردپرسی"); <div> 11.0px ("Up to"); <div> 11.0px ("10000 MB HDD"); <div> 11.0px ("Up to"); <div> 11.0px ("4 vCPU").
FFavicon & BrandingAction1 icon(s) detectedFIX
Favicon & Branding
Action1 icon(s) detected
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
DWeb ManifestActionNot foundFIX
Web Manifest
ActionNot found
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.
DDark Mode SupportActionNo dark mode signalsFIX
Dark Mode Support
ActionNo dark mode signals
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.
DPrint StylesheetActionNo print stylesFIX
Print Stylesheet
ActionNo print styles
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 ✗
BLandmark Structure9 landmarksREVIEW
Landmark Structure
9 landmarks
9 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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
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
CAlt Text QualityAction19 of 54 images have issuesREVIEW
Alt Text Quality
Action19 of 54 images have issues
19 of 54 images have issues
Critical::
19 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
2 decorative image(s) correctly marked
Info::
33 image(s) with good alt text
54 images 33 good alt text 2 decorative 19 missing
| Issue | Count |
|---|---|
| missing | 19 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
CForm AccessibilityAction7 of 7 controls have issuesREVIEW
Form Accessibility
Action7 of 7 controls have issues
7 of 7 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Warning::
6 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="name">; <input type="text" name="company_name">; <input type="text" name="website">; <input type="text" name="phone">; <input type="text" name="email">; <textarea name="description">
7 controls
0 labeled
6 placeholder only
1 unlabeled
| Control | Type | Label | Method |
|---|---|---|---|
| name | text | (نام و نام خانوادگی) | placeholder only |
| company_name | text | (نام شرکت / سازمان) | placeholder only |
| website | text | (آدرس وبسایت) | placeholder only |
| phone | text | (شماره همراه) | placeholder only |
| text | (آدرس ایمیل) | placeholder only | |
| description | textarea | (موضوع یا چالش اصلی که در آن نیاز به مشاوره دارید را در حداکثر ۵ خط توضیح دهید) | placeholder only |
| #g-recaptcha-response-100000 | textarea | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
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="name">; <input type="text" name="company_name">; <input type="text" name="website">; <input type="text" name="phone">; <input type="text" name="email">; <textarea name="description">
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
CLink & Button QualityAction4 issue(s) across 188 links and 15 buttonsREVIEW
Link & Button Quality
Action4 issue(s) across 188 links and 15 buttons
4 issue(s) across 188 links and 15 buttons
Critical::
1 link(s) with no accessible text
Links without text are announced as raw URLs by screen readers.
Got: https://status.parspack.com/?utm_source=parspack&utm_medium=topbar
Warning::
52 link(s) open in new tab without warning
Add '(opens in new tab)' to link text or aria-label.
Got: https://my.parspack.com/; https://parspack.com/servers; https://parspack.com/host; https://parspack.com/cloud-storage; https://parspack.com/domain; https://parspack.com/dedicated-servers; https://parspack.com/vps; https://parspack.com/cloud-server; https://parspack.com/ssl; https://parspack.com/host/wordpress (+42 more)
Critical::
3 button(s) with no accessible text
Icon-only buttons need an aria-label so screen readers can announce them.
Got: button.button (#96 on page); button.button (#928 on page); button.button (#933 on page)
Info::
135 link(s) with descriptive text
188 links
1 empty
0 generic text
52 new tab
3 empty buttons
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://status.parspack.com/?utm_source=… | (empty) | empty | Add link text or aria-label |
| https://my.parspack.com/ | شروع کنید | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/servers | خرید سرور | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/host | خرید هاست | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/cloud-storage | خرید فضای ابری | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/domain | خرید دامنه | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/dedicated-servers | خرید سرور اختصاص… | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/vps | خرید سرور مجازی | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/cloud-server | خرید سرور ابری | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/ssl | خرید SSL | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/host/wordpress | خرید هاست وردپرس | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/host/dedicated | خرید هاست اختصاص… | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/domain/ir | خرید دامنه ir | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/domain/internationa… | خرید دامنه com | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/paas | خرید PaaS | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/cdn | خرید CDN | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/host/download-host | خرید هاست دانلود | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/servers/foreign | سرور خارجی | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/servers/iran | سرور ایران | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/servers/linux | سرور لینوکس | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/vps/foreign | سرور مجازی خارج | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/vps/iran | سرور مجازی ایران | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/vps/mikrotik | سرور مجازی میکرو… | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/host/cloud-host | هاست ابری | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/host/reseller | هاست نمایندگی | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/host/linux | هاست لینوکس | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/host/iran | هاست ایران | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/cdn | شروع کن | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/vps/iran | سرور مجازی ایران | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/vps/foreign/germany | سرور مجازی آلمان | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/vps/foreign/turkey | سرور مجازی ترکیه | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/vps/foreign/canada | سرور مجازی کاناد… | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/vps/foreign/sweden | سرور مجازی سوئد | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/vps/foreign/england | سرور مجازی انگلی… | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/vps/foreign/netherl… | سرور مجازی هلند | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/vps/foreign/france | سرور مجازی فرانس… | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/vps | مشاهده همه سروره… | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/paas | شروع کن | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/host/free-cloud-hos… | دریافت هاست رایگ… | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/contact-us | درخواست پشتیبان… | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/cloud-server/free-s… | دریافت سرور رایگ… | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/blog/hosting/docker… | آموزش جامع نصب د… | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/blog/online-busines… | نرمافزار تاندر… | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/blog/os/linux/fedor… | سیستمعامل فدور… | new tab | Add '(opens in new tab)' to text |
| https://parspack.com/blog/ | مشاهده بلاگ پارس… | new tab | Add '(opens in new tab)' to text |
| https://www.linkedin.com/company/parspac… | پارس پک در لینکد… | new tab | Add '(opens in new tab)' to text |
| https://twitter.com/Parspack | پارس پک در توییت… | new tab | Add '(opens in new tab)' to text |
| https://www.aparat.com/parspack.com | پارس پک در آپارا… | new tab | Add '(opens in new tab)' to text |
| https://www.instagram.com/parspackcom/ | پارس پک در اینست… | new tab | Add '(opens in new tab)' to text |
| https://www.linkedin.com/company/parspac… | پارس پک در لینکد… | new tab | Add '(opens in new tab)' to text |
| https://twitter.com/Parspack | پارس پک در توییت… | new tab | Add '(opens in new tab)' to text |
| https://www.aparat.com/parspack.com | aparat | new tab | Add '(opens in new tab)' to text |
| https://www.instagram.com/parspackcom/ | پارس پک در اینست… | new tab | Add '(opens in new tab)' to text |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
147 links and buttons have descriptive text
Links without text are announced as raw URLs by screen readers.
https://status.parspack.com/?utm_source=parspack&utm_medium=topbar
Why this matters
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
https://my.parspack.com/; https://parspack.com/servers; https://parspack.com/host; https://parspack.com/cloud-storage; https://parspack.com/domain; https://parspack.com/dedicated-servers; https://parspack.com/vps; https://parspack.com/cloud-server; https://parspack.com/ssl; https://parspack.com/host/wordpress (+42 more)
Why this matters
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
Icon-only buttons need an aria-label so screen readers can announce them.
button.button (#96 on page); button.button (#928 on page); button.button (#933 on page)
Why this matters
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
BIframe Accessibility2/3 iframe(s) missing title; 0 placeholder(s)REVIEW
Iframe Accessibility
2/3 iframe(s) missing title; 0 placeholder(s)
2/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
C404 Error PageActionCould not testREVIEW
404 Error Page
ActionCould not test
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.
404 page quality check not available.
CLighthouse Accessibility AuditsActionScore 74/100 — 7 failing, 24 passedREVIEW
Lighthouse Accessibility Audits
ActionScore 74/100 — 7 failing, 24 passed
74
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Names and labels
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.swiper-container > div.swiper-navigation-container > div.swiper-custom-button-prev > button.button div.swiper-container > div.swiper-navigation-container > div.swiper-custom-button-prev > button.button |
div.swiper-container > div.swiper-navigation-container > div.swiper-custom-button-next > button.button div.swiper-container > div.swiper-navigation-container > div.swiper-custom-button-next > button.button |
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 |
|---|
header.hero-section > div.hero-section__inner > div.hero-section__image-wrapper > img.lazyloaded header.hero-section > div.hero-section__inner > div.hero-section__image-wrapper > img.lazyloaded |
li.swiper-slide > blockquote.card > div.testimonial__author-wrapper > img.testimonial__avatar li.swiper-slide > blockquote.card > div.testimonial__author-wrapper > img.testimonial__avatar |
li.swiper-slide > blockquote.card > div.testimonial__author-wrapper > img.testimonial__avatar li.swiper-slide > blockquote.card > div.testimonial__author-wrapper > img.testimonial__avatar |
li.swiper-slide > blockquote.card > div.testimonial__author-wrapper > img.testimonial__avatar li.swiper-slide > blockquote.card > div.testimonial__author-wrapper > img.testimonial__avatar |
li.swiper-slide > blockquote.card > div.testimonial__author-wrapper > img.testimonial__avatar li.swiper-slide > blockquote.card > div.testimonial__author-wrapper > img.testimonial__avatar |
li.swiper-slide > blockquote.card > div.testimonial__author-wrapper > img.testimonial__avatar li.swiper-slide > blockquote.card > div.testimonial__author-wrapper > img.testimonial__avatar |
li.swiper-slide > blockquote.card > div.testimonial__author-wrapper > img.testimonial__avatar li.swiper-slide > blockquote.card > div.testimonial__author-wrapper > img.testimonial__avatar |
li.swiper-slide > blockquote.card > div.testimonial__author-wrapper > img.testimonial__avatar li.swiper-slide > blockquote.card > div.testimonial__author-wrapper > img.testimonial__avatar |
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 |
|---|
body.rtl > a#top-banner body.rtl > a#top-banner |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Contrast
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
پارس پک div.footer__copyright > div.wrapper > p.pe > a |
These are opportunities to improve the legibility of your content.
Tables and lists
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
تکیهگاه فنی مطمئن و خدمات باکیفیت
پارسپک برای زومیت همواره تکیهگاه فنی مطمئن ب… div.testimonial-section__swiper-container > div.swiper-container > div.swiper > ul#swiper-wrapper-cfc3e740dda17263 |
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
بلاگ پارسپک div.mega-menu__body > div#menu-blog-docs > div.column > li.menu-item |
مستندات پارسپک div.mega-menu__body > div#menu-blog-docs > div.column > li.menu-item |
آموزش جامع نصب داکر در دبیان
در این مقاله به صورت گامبهگام به آموزش جامع نصب د… div.swiper > div#swiper-wrapper-e6744c7c5df7f78e > div.swiper-slide > li.card |
نرمافزار تاندر برد چیست و چگونه کار میکند؟
در این مقاله با تاندربرد (Thunderbi… div.swiper > div#swiper-wrapper-e6744c7c5df7f78e > div.swiper-slide > li.card |
سیستمعامل فدورا لینوکس چیست؟
در این مقاله همه نکات درباره سیستمعامل فدورا لینو… div.swiper > div#swiper-wrapper-e6744c7c5df7f78e > div.swiper-slide > li.card |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
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 |
|---|
Go to slide 1 div.hero-section__swiper-container > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 2 div.hero-section__swiper-container > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 3 div.hero-section__swiper-container > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 4 div.hero-section__swiper-container > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 1 div.products-showcase__cards > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 2 div.products-showcase__cards > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 3 div.products-showcase__cards > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 4 div.products-showcase__cards > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 5 div.products-showcase__cards > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 6 div.products-showcase__cards > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 7 div.products-showcase__cards > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 8 div.products-showcase__cards > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 1 div.testimonial-section__swiper-container > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 2 div.testimonial-section__swiper-container > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 3 div.testimonial-section__swiper-container > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 4 div.testimonial-section__swiper-container > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 5 div.testimonial-section__swiper-container > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 6 div.testimonial-section__swiper-container > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 7 div.testimonial-section__swiper-container > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 1 div.latest-posts__cards > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 2 div.latest-posts__cards > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 3 div.latest-posts__cards > div.swiper-navigation-container > div.swiper-pagination > span.swiper-pagination-bullet |
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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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
●Background and foreground colors have a sufficient contrast ratio
●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
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[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
○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
○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.
○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.
A+Heading Hierarchy46 headingsPASS
Heading Hierarchy
46 headings
46 headings
Info::
Single H1 present
- H1 پارسپک، فناوری ابری به سادگی
- H2 انواع سرورهای ابری، مجازی و اختصاصی
- H2 انواع هاستینگ از اشتراکی تا اختصاصی
- H2 فضای ذخیره سازی ابری
- H2 متنوع ترین TLD ها برای انتخاب دامنه
- H2 جعبه ابزاری به وسعت کسب و کار شما
- H3 خرید سرور اختصاصی
- H3 خرید سرور مجازی
- H3 خرید سرور ابری
- H3 خرید SSL
- H3 خرید هاست وردپرس
- H3 خرید هاست اختصاصی
- H3 خرید دامنه ir
- H3 خرید دامنه com
- H3 خرید PaaS
- H3 خرید CDN
- H3 خرید هاست دانلود
- H3 CDN پارسپک
- H2 انواع سرور مجازی در لوکیشنهای متنوع
- H3 سرور مجازی ایران
- H3 سرور مجازی آلمان
- H3 سرور مجازی ترکیه
- H3 سرور مجازی کانادا
- H3 سرور مجازی سوئد
- H3 سرور مجازی انگلیس
- H3 سرور مجازی هلند
- H3 سرور مجازی فرانسه
- H3 PaaS پارسپک؛ از ایده تا اجرا در کوتاهترین زمان
- H2 چرا پارسپک؟
- H3 ۱۶ سال سابقه درخشان
- H3 جامعه ۲۰۰ هزار نفری
- H3 پیشگام در فضای ابری
- H3 سختافزارهای پیشرفته
- H3 هاست رایگان
- H2 پشتیبانی در هر لحظه
- H2 نظر تعدادی از مشتریان ما در ۱۶ سال گذشته
- H2 انواع پشتیبانی
- H3 پشتیبانی تلفنی
- H3 پشتیبانی تیکتی
- H3 پشتیبانی مسنجری پایه
- H3 پشتیبانی مسنجری پیشرفته
- H3 سرور رایگان؛ شروع قدرتمند، بدون هزینه
- H2 آخرین مقالات بلاگ
- H3 آموزش جامع نصب داکر در دبیان
- H3 نرمافزار تاندر برد چیست و چگونه کار میکند؟
- H3 سیستمعامل فدورا لینوکس چیست؟
A+Heading Text Quality1 heading-text-quality issue(s) detectedPASS
Heading Text Quality
1 heading-text-quality issue(s) detected
1 heading-text-quality issue(s) detected
Info::
42 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: 42 all-caps heading(s)
AForm Input Types3 input(s) using type=text where a specific type would helpPASS
Form Input Types
3 input(s) using type=text where a specific type would help
3 input(s) using type=text where a specific type would help
Info::
Input "website" should use type="url" (currently type="text")
Field name "website" suggests type="url". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="url">.
Info::
Input "phone" should use type="tel" (currently type="text")
Field name "phone" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.
Info::
Input "email" should use type="email" (currently type="text")
Field name "email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A+Form Input Quality7 form control(s) checked, no input-semantic issuesPASS
Form Input Quality
7 form control(s) checked, no input-semantic issues
7 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+Document LanguageLang attribute set to "fa-IR"PASS
Document Language
Lang attribute set to "fa-IR"
Lang attribute set to "fa-IR"
Info::
<html lang="fa-IR"> is set and valid
Got: fa-IR
A+Tabindex Anti-Patterns0 positive, 1 -1-on-focusablePASS
Tabindex Anti-Patterns
0 positive, 1 -1-on-focusable
0 positive, 1 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <input>
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+PWA DepthNo PWA depth issues detectedPASS
PWA Depth
No PWA depth issues detected
No PWA depth issues detected
Info::
No PWA depth issues detected
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
Mobile UX Depth
1 mobile-depth signal(s) detected
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+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
20 pass
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 پارسپک، | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 فناوری ابر… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 انواع سرور… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 انواع هاست… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 فضای ذخیره … | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 متنوع ترین … | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 جعبه ابزار… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 انواع سرور … | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 چرا پارسپ… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 پشتیبانی د… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 نظر تعدادی … | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 انواع پشتی… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 آخرین مقال… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 CDN پارسپک | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 PaaS پارسپک… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 ۱۶ سال سابق… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 جامعه ۲۰۰ ه… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 پیشگام در ف… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 سختافزار… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h3 هاست رایگا… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.