Skip to content
https://shahoclimb.com

Accessibility

· 11 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
GRADE
D
FIX
5
REVIEW
3
PASS
3
INFO
0
Checks
11
3 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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::
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'>.
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Tap Target Adequacy
3 tap target(s) too small or too close together
REVIEW
3 tap target(s) too small or too close together
Info::
3 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.
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: ShahoClimb
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ShahoClimb ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name ShahoClimb Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Lighthouse Accessibility Audits
Action
Score 74/100 — 5 failing, 15 passed
REVIEW
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.bottom-header > div.container > nav.main-menu > button.btn-menu div.bottom-header > div.container > nav.main-menu > button.btn-menu
div.col-12 > div.product-carousel > div.owl-nav > button.owl-prev div.col-12 > div.product-carousel > div.owl-nav > button.owl-prev
div.col-12 > div.product-carousel > div.owl-nav > button.owl-next div.col-12 > div.product-carousel > div.owl-nav > button.owl-next
div.col-12 > div.product-carousel > div.owl-nav > button.owl-prev div.col-12 > div.product-carousel > div.owl-nav > button.owl-prev
div.col-12 > div.product-carousel > div.owl-nav > button.owl-next div.col-12 > div.product-carousel > div.owl-nav > button.owl-next
div.col-12 > div.product-carousel > div.owl-dots > button.owl-dot div.col-12 > div.product-carousel > div.owl-dots > button.owl-dot
div.col-12 > div.product-carousel > div.owl-dots > button.owl-dot div.col-12 > div.product-carousel > div.owl-dots > button.owl-dot
div.col-12 > div.product-carousel > div.owl-dots > button.owl-dot div.col-12 > div.product-carousel > div.owl-dots > button.owl-dot
div.col-12 > div.product-carousel > div.owl-dots > button.owl-dot div.col-12 > div.product-carousel > div.owl-dots > button.owl-dot
div.col-12 > div.product-carousel > div.owl-nav > button.owl-prev div.col-12 > div.product-carousel > div.owl-nav > button.owl-prev
div.col-12 > div.product-carousel > div.owl-nav > button.owl-next div.col-12 > div.product-carousel > div.owl-nav > button.owl-next

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.row > div.col-lg-2 > div.logo-area > a div.row > div.col-lg-2 > div.logo-area > a
nav.main-menu > div.side-menu > div.logo-nav-res > a nav.main-menu > div.side-menu > div.logo-nav-res > a
section#main-slider-res > div.carousel-inner > div.carousel-item > a.main-slider-slide section#main-slider-res > div.carousel-inner > div.carousel-item > a.main-slider-slide
div.row > div.col-xl-10 > section#main-slider-res > a.carousel-control-prev div.row > div.col-xl-10 > section#main-slider-res > a.carousel-control-prev
div.row > div.col-xl-10 > section#main-slider-res > a.carousel-control-next div.row > div.col-xl-10 > section#main-slider-res > a.carousel-control-next
div.owl-item > div.item > div.amazing-product > a div.owl-item > div.item > div.amazing-product > a
footer.modern-footer > div.container > div.footer-social > a footer.modern-footer > div.container > div.footer-social > a
footer.modern-footer > div.container > div.footer-social > a footer.modern-footer > div.container > div.footer-social > a
footer.modern-footer > div.container > div.footer-social > a footer.modern-footer > div.container > div.footer-social > a

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. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ورود | ثبت‌نام ul.nav > li.nav-item > a.nav-link > span.label-dropdown
div.side-menu > div.search-box-side-menu > form#mobileSearchForm > input#mobileSearchInput div.side-menu > div.search-box-side-menu > form#mobileSearchForm > input#mobileSearchInput
طناب div.item > div.product-card > div.product-card-body > a.product-meta

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
کوله پشتی Pekynew Tabriz 20L پکینیو div.item > div.product-card > div.product-card-body > h5.product-title
طناب div.item > div.product-card > div.product-card-body > h5.product-title

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-12 > div.product-carousel > div.owl-dots > button.owl-dot div.col-12 > div.product-carousel > div.owl-dots > button.owl-dot
div.col-12 > div.product-carousel > div.owl-dots > button.owl-dot div.col-12 > div.product-carousel > div.owl-dots > button.owl-dot
div.col-12 > div.product-carousel > div.owl-dots > button.owl-dot div.col-12 > div.product-carousel > div.owl-dots > button.owl-dot

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●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.
●Document has a `<title>` element
●`<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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted 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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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.
○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+
Mobile-Readable Font Sizes
Font-size measurement not available for this scan
PASS
Font-size measurement not available for this scan
Info::
Font-size measurement not available for this scan
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
No HTML captured -- mobile-depth check is N/A
PASS
No HTML captured -- mobile-depth check is N/A
Info::
No HTML captured -- mobile-depth check is N/A
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback