Skip to content
https://www.acethehimalaya.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
72
GRADE
C
FIX
7
REVIEW
6
PASS
11
INFO
0
Checks
24
11 PASS 6 REVIEW 7 FIX
F
Heading Hierarchy
Action
156 headings, 1 skip(s)
FIX
156 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
12 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Experience the Difference!
  • H4 All Trips skipped
  • H2 Best Sellers for 2026
  • H2 Luxury & VIP Adventures
  • H2 Peak Climbing
  • H2 Short Treks
  • H2 Bhutan Tours
  • H3 Everest Base Camp Trek
  • H3 Everest Base Camp Trek with Helicopter Return
  • H3 Annapurna Base Camp Trek
  • H3 Annapurna Circuit Trek
  • H3 Manaslu Circuit Trek
  • H3 Everest Base Camp Luxury Trek
  • H3 Ghorepani Poon Hill Trek
  • H3 Gokyo to Everest Base Camp Trek
  • H3 Everest Base Camp Luxury Trek
  • H3 Luxury Everest Base Camp Trek with Helicopter Return
  • H3 VIP Everest Base Camp Trek
  • H3 Annapurna in Luxury
  • H3 Luxury Everest View Heli Trek
  • H3 Island Peak Climbing
  • H3 Mera Peak Climbing
  • H3 Everest Base Camp and Lobuche East
  • H3 Yala Peak Climbing
  • H3 Pisang Peak and Thorung La Pass
  • H3 Ama Dablam Expedition
  • H3 Ghorepani Poon Hill Trek
  • H3 Langtang Valley Trek
  • H3 Mardi Himal Trek
  • H3 Everest Panorama Trek
  • H3 Everest View Heli Trek
  • H3 Bhutan Vistas Tour
  • H3 Paro Tshechu Festival
  • H3 Bhutan Cultural Tour
  • H3 Druk Path Trek
  • H3 Bhutan Motorcycle Tour
  • H2 Your Trusted Partner for Himalayan Treks & Tours
  • H2 They Aced It!
  • H2 Traveler Reviews
  • H3 Google Reviews
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H3 (empty)
  • H2 Why Ace?
  • H3 Local Himalayan Experts
  • H3 High Standard of Safety prioritized
  • H3 Unbeatable Value
  • H3 Top-Notch Service
  • H3 Socially Responsible
  • H3 Guaranteed Departures
  • H2 Journey to the Himalayan Lands
  • H3 Nepal
  • H3 Bhutan
  • H3 Tibet
  • H2 Activities we offer
  • H3 Trekking in Nepal
  • H3 Climbing and Expedition in Nepal
  • H3 Cultural Tour & Sightseeing in Nepal
  • H3 Mountain Biking in Nepal
  • H3 Luxury Treks in Nepal
  • H3 Luxury Tours in Nepal
  • H3 Day Trips in Nepal
  • H3 Voluntourism Trips in Nepal
  • H3 Trekking in Bhutan
  • H3 Cultural Tour and Sightseeing in Bhutan
  • H3 Festival Tours in Bhutan
  • H3 Cycling and Mountain Biking in Bhutan
  • H3 Trekking in Tibet
  • H3 Cultural Tour and Sightseeing in Tibet
  • H3 Cycling and Mountain Biking in Tibet
  • H2 Everest Base Camp Popular Options
  • H3 Everest Base Camp Trek
  • H3 Everest Base Camp Trek with Helicopter Return
  • H3 Everest Base Camp Luxury Trek
  • H2 Best of Bhutan
  • H3 Bhutan Vistas Tour - 5 Days
  • H3 Druk Path Trek - 8 Days
  • H3 Paro Tshechu Festival - 8 Days
  • H3 Bhutan Cultural Tour - 10 Days
  • H3 Bhutan Multi Sports Tour - 11 Days
  • H3 Bhutan Biking - 8 Days
  • H2 Best of Tibet
  • H3 Kailash Mansarovar Yatra - 16 Days
  • H3 Lhasa Tour from Kathmandu - 10 Days
  • H3 Kathmandu to Lhasa Overland Tour with EBC - 15 Days
  • H3 Tibet Everest Base Camp Tour - 14 Days
  • H3 Lhasa Overland Tour from Kathmandu - 13 Days
  • H2 Frequently Asked Questions by Travelers
  • H3 Why trek with Ace the Himalaya?
  • H3 Can a first-timer trek in Nepal?
  • H3 Can you recommend the best trek in Nepal based on my fitness and interests?
  • H3 What is your booking process?
  • H3 How does Ace the Himalaya ensure safe travel?
  • H3 Who are your guides, and how experienced are they?
  • H3 Can I customize a private trek or tour itinerary with Ace?
  • H3 How does Ace the Himalaya support sustainable trekking?
  • H3 Is filtered drinking water available on the trek?
  • H3 Do you offer luxury trekking and tour packages?
  • H3 Do I need travel insurance to trek in Nepal?
  • H3 Where can I exchange money upon arrival in Nepal?
  • H3 What is your booking and cancellation policy?
  • H3 What kind of physical training is necessary for trek preparation?
  • H3 Why do travelers rate Ace the Himalaya so highly on TripAdvisor?
  • H2 Speak to an Expert
  • H2 Blog from the Himalayas
  • H3 Manaslu Circuit Trek in Autumn: Weather, Trails, and What to Expect
  • H3 Best Trekking Seasons in Nepal
  • H3 Safety Tips for the Manaslu Circuit Trek
  • H3 Can a First-Timer Trek the Manaslu Circuit?
  • H2 We're associated with
  • H3 Destinations
  • H3 Main Activites
  • H3 Company
  • H3 Useful Links
  • H3 A- One Business Complex, Thamel, Kathmandu, Nepal
  • H2 Speak with our worldwide representative
  • H3 Sujan
  • H3 Prem
  • H3 Kathy
  • H3 Melanie
  • H3 Abex
  • H3 Sihyoung
  • H4 Trekking in Nepal
  • H4 Climbing and Expedition
  • H4 Luxury Treks
  • H4 Cultural Tour and Sightseeing
  • H4 Cycling and Mountain Biking
  • H4 Luxury Tours
  • H4 Day Trips
  • H4 Multi Country Tours
  • H4 Voluntourism Trips
  • H4 Extend Your Trip
  • H4 Cultural Tour and Sightseeing
  • H4 Trekking in Bhutan
  • H4 Festival Tours
  • H4 Cycling and Mountain Biking
  • H4 Motorcycling
  • H4 Cultural Tour and Sightseeing
  • H4 Trekking in Tibet
  • H4 Cycling and Mountain Biking
  • H4 Company
  • H4 Everest Region
  • H4 Annapurna Region
  • H4 Langtang Region
  • H4 Manaslu Region
  • H4 Heli Treks
  • H4 Off the Beaten Path Treks

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

D
Tabindex Anti-Patterns
Action
3 positive, 23 -1-on-focusable
FIX
3 positive, 23 -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>
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.)
Warning::
Positive tabindex on <input id="input_9_5">: tabindex=49
Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
Warning::
Positive tabindex on <input id="input_9_2">: tabindex=50
Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
Warning::
Positive tabindex on <button id="gform_submit_button_9">: tabindex=51
Positive tabindex values force an element into a specific position in the tab order, breaking the natural document flow. Almost always a bug. Use tabindex="0" to make non-focusable elements focusable, or remove the attribute entirely to keep natural order.
Info::
tabindex="-1" on naturally-focusable <button id="slick-slide-control21">
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 <button id="slick-slide-control22">
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 <button id="slick-slide-control23">
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.)
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: #000
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::
2 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 2 <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
Landmark Structure
5 landmarks
REVIEW
5 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
BANNER header NAV MAIN CONTENTINFO footer

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
Alt Text Quality
1 of 237 images have issues
REVIEW
1 of 237 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
8 image(s) with alt text over 125 characters
Info::
228 image(s) with good alt text
237 images 228 good alt text 1 missing
IssueCount
missing1 image(s)
too long8 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

C
404 Error Page
Action
Could not test
REVIEW
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.

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, 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 Experience the Difference!
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Your Trusted Partner for Himalayan Treks…
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 They Aced It!
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Traveler Reviews
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why Ace?
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Journey to the Himalayan Lands
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Activities we offer
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Everest Base Camp Popular Options
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Best of Bhutan
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Best of Tibet
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Frequently Asked Questions by Travelers
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Speak to an Expert
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Blog from the Himalayas
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 We're associated with
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Speak with our worldwide representative
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Everest Base Camp Trek
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Everest Base Camp Trek with Helicopter R…
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Annapurna Base Camp Trek
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Annapurna Circuit Trek
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Manaslu Circuit Trek
1.05:1
#000000
on
#080808
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Experience the Diffe…1.05:13.0:1
#000000
#080808
Fail
h2 Your Trusted Partner…1.05:13.0:1
#000000
#080808
Fail
h2 They Aced It!1.05:13.0:1
#000000
#080808
Fail
h2 Traveler Reviews1.05:13.0:1
#000000
#080808
Fail
h2 Why Ace?1.05:13.0:1
#000000
#080808
Fail
h2 Journey to the Himal…1.05:13.0:1
#000000
#080808
Fail
h2 Activities we offer1.05:13.0:1
#000000
#080808
Fail
h2 Everest Base Camp Po…1.05:13.0:1
#000000
#080808
Fail
h2 Best of Bhutan1.05:13.0:1
#000000
#080808
Fail
h2 Best of Tibet1.05:13.0:1
#000000
#080808
Fail
h2 Frequently Asked Que…1.05:13.0:1
#000000
#080808
Fail
h2 Speak to an Expert1.05:13.0:1
#000000
#080808
Fail
h2 Blog from the Himala…1.05:13.0:1
#000000
#080808
Fail
h2 We're associated wit…1.05:13.0:1
#000000
#080808
Fail
h2 Speak with our world…1.05:13.0:1
#000000
#080808
Fail
h3 Everest Base Camp Tr…1.05:13.0:1
#000000
#080808
Fail
h3 Everest Base Camp Tr…1.05:13.0:1
#000000
#080808
Fail
h3 Annapurna Base Camp …1.05:13.0:1
#000000
#080808
Fail
h3 Annapurna Circuit Tr…1.05:13.0:1
#000000
#080808
Fail
h3 Manaslu Circuit Trek1.05:13.0:1
#000000
#080808
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.

B
Lighthouse Accessibility Audits
Score 83/100 — 6 failing, 27 passed
REVIEW
83

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.custsupport__col--profiles > div.owl-carousel > div.owl-dots > button.owl-dot div.custsupport__col--profiles > div.owl-carousel > div.owl-dots > button.owl-dot
div.custsupport__col--profiles > div.owl-carousel > div.owl-dots > button.owl-dot div.custsupport__col--profiles > div.owl-carousel > div.owl-dots > button.owl-dot
div.custsupport__col--profiles > div.owl-carousel > div.owl-dots > button.owl-dot div.custsupport__col--profiles > div.owl-carousel > div.owl-dots > button.owl-dot
div.custsupport__col--profiles > div.owl-carousel > div.owl-dots > button.owl-dot div.custsupport__col--profiles > div.owl-carousel > div.owl-dots > button.owl-dot
div.custsupport__col--profiles > div.owl-carousel > div.owl-dots > button.owl-dot div.custsupport__col--profiles > div.owl-carousel > div.owl-dots > button.owl-dot
div.custsupport__col--profiles > div.owl-carousel > div.owl-dots > button.owl-dot div.custsupport__col--profiles > div.owl-carousel > div.owl-dots > button.owl-dot

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.footer__thirdparty-row > div.footer__social > div.footer__social-media > a.social-btn div.footer__thirdparty-row > div.footer__social > div.footer__social-media > a.social-btn
div.footer__thirdparty-row > div.footer__social > div.footer__social-media > a.social-btn div.footer__thirdparty-row > div.footer__social > div.footer__social-media > a.social-btn
div.footer__thirdparty-row > div.footer__social > div.footer__social-media > a.social-btn div.footer__thirdparty-row > div.footer__social > div.footer__social-media > a.social-btn
div.footer__thirdparty-row > div.footer__social > div.footer__social-media > a.social-btn div.footer__thirdparty-row > div.footer__social > div.footer__social-media > a.social-btn
div.footer__thirdparty-row > div.footer__social > div.footer__social-media > a.social-btn div.footer__thirdparty-row > div.footer__social > div.footer__social-media > a.social-btn
div.footer__member-text > div.footer__member-contact > div.footer__member-contact-item > a div.footer__member-text > div.footer__member-contact > div.footer__member-contact-item > 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
Learn more div.three__col--card > div.three__col--content > p > a
752 reviews div.container > div.review-trustpilot > div.review-google__score > span.googlereviewscroerw
from USD 1,500 a.new__trip__card > div.new__trip__content > div.d-flex > span.new__option__price
USD 1,500 div.new__trip__content > div.d-flex > span.new__option__price > span
from USD 2,300 a.new__trip__card > div.new__trip__content > div.d-flex > span.new__option__price
USD 2,300 div.new__trip__content > div.d-flex > span.new__option__price > span
from USD 3,150 a.new__trip__card > div.new__trip__content > div.d-flex > span.new__option__price
USD 3,150 div.new__trip__content > div.d-flex > span.new__option__price > span
SUBSCRIBE div#gform_wrapper_9 > form#gform_9 > div.gform-footer > button#gform_submit_button_9
Follow div.inavii-view__header > div.inavii-view__header-row > div.inavii-view__header-actions > a.inavii-view__header-follow
Load More div.inavii-view > div.inavii-view__bottom > div.inavii-view__footer > div.inavii-view__footer-load-more
Follow div.inavii-view > div.inavii-view__bottom > div.inavii-view__footer > a.inavii-view__footer-follow
Nepal div.menu-destinations-container > ul#menu-destinations > li#menu-item-52391 > a
Bhutan div.menu-destinations-container > ul#menu-destinations > li#menu-item-79620 > a
Tibet div.menu-destinations-container > ul#menu-destinations > li#menu-item-52389 > a
Multi Country div.menu-destinations-container > ul#menu-destinations > li#menu-item-57206 > a
Trekking in Nepal div.menu-main-activites-container > ul#menu-main-activites > li#menu-item-55449 > a
Luxury Treks div.menu-main-activites-container > ul#menu-main-activites > li#menu-item-52395 > a
Climbing and Expedition div.menu-main-activites-container > ul#menu-main-activites > li#menu-item-52393 > a
Mountain Biking in Nepal div.menu-main-activites-container > ul#menu-main-activites > li#menu-item-57207 > a
About Us div.menu-company-container > ul#menu-company > li#menu-item-55445 > a
Meet Our Team div.menu-company-container > ul#menu-company > li#menu-item-55446 > a
17 Reasons to Choose Ace div.menu-company-container > ul#menu-company > li#menu-item-55447 > a
Awards and Achievements div.menu-company-container > ul#menu-company > li#menu-item-55448 > a
Contact Us div.menu-company-container > ul#menu-company > li#menu-item-57704 > a
Mission Statement div.menu-company-container > ul#menu-company > li#menu-item-73976 > a
Blog div.menu-useful-links-container > ul#menu-useful-links > li#menu-item-55431 > a
Terms and Conditions div.menu-useful-links-container > ul#menu-useful-links > li#menu-item-55441 > a
Sustainability Policy div.menu-useful-links-container > ul#menu-useful-links > li#menu-item-72386 > a
Privacy Policy div.menu-useful-links-container > ul#menu-useful-links > li#menu-item-59369 > a
Cookie Policy div.menu-useful-links-container > ul#menu-useful-links > li#menu-item-59496 > a
Site Map div.menu-useful-links-container > ul#menu-useful-links > li#menu-item-57971 > a
HEAD OFFICE div.footer__mid-col > div.footer__member > div.footer__member-text > span.btn

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
Nepal Bhutan Tibet Multi Country div.container > div.footer__top-row > div.footer__top-col > ul.footer__top-list
Trekking in Nepal Luxury Treks Climbing and Expedition Mountain Biking in Nepal div.container > div.footer__top-row > div.footer__top-col > ul.footer__top-list
About Us Meet Our Team 17 Reasons to Choose Ace Awards and Achievements Contact… div.container > div.footer__top-row > div.footer__top-col > ul.footer__top-list
Blog Terms and Conditions Sustainability Policy Privacy Policy Cookie Policy Si… div.container > div.footer__top-row > div.footer__top-col > ul.footer__top-list

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul#gform_fields_9 > li#field_9_5 > div.ginput_container > input#input_9_5 ul#gform_fields_9 > li#field_9_5 > div.ginput_container > input#input_9_5
ul#gform_fields_9 > li#field_9_2 > div.ginput_container > input#input_9_2 ul#gform_fields_9 > li#field_9_2 > div.ginput_container > input#input_9_2
SUBSCRIBE div#gform_wrapper_9 > form#gform_9 > div.gform-footer > button#gform_submit_button_9

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
14 Days Everest Base Camp Trek from USD 1,500 div.swiper-slide > div.item > div > a.new__trip__card
12 Days Everest Base Camp Trek with Helicopter Return from USD 2,300 div.swiper-slide > div.item > div > a.new__trip__card
37 Trips Trekking in Nepal div.item > div > div.best--seller > a.scale
7 Trips Climbing and Expedition in Nepal div.item > div > div.best--seller > a.scale
14 Days from USD 1,500 Everest Base Camp Trek Ideal for budget-conscious, phys… div.container > div.row > div.col-md-4 > a.new__trip__card
12 Days from USD 2,300 Everest Base Camp Trek with Helicopter Return Best suit… div.container > div.row > div.col-md-4 > a.new__trip__card
14 Days from USD 3,150 Everest Base Camp Luxury Trek Perfect for trekkers who … div.container > div.row > div.col-md-4 > a.new__trip__card
5 Days Bhutan Vistas Tour - 5 Days from USD 1,560 div.swiper-slide > div.item > div > a.new__trip__card
8 Days Druk Path Trek - 8 Days from USD 2,760 div.swiper-slide > div.item > div > a.new__trip__card
16 Days Kailash Mansarovar Yatra - 16 Days from USD 3,200 div.swiper-slide > div.item > div > a.new__trip__card
10 Days Lhasa Tour from Kathmandu - 10 Days from USD 1,275 div.swiper-slide > div.item > div > a.new__trip__card
Nepal nav > ul > li.has-submenu > a
Trekking in Nepal div.allMobileMenu > ul > li.has-submenu-second > a
Climbing and Expedition div.allMobileMenu > ul > li.has-submenu-second > a
Luxury Treks div.allMobileMenu > ul > li.has-submenu-second > a
Cultural Tour and Sightseeing div.allMobileMenu > ul > li.has-submenu-second > a
Cycling and Mountain Biking div.allMobileMenu > ul > li.has-submenu-second > a
Luxury Tours div.allMobileMenu > ul > li.has-submenu-second > a
Day Trips div.allMobileMenu > ul > li.has-submenu-second > a
Multi Country Tours div.allMobileMenu > ul > li.has-submenu-second > a
Voluntourism Trips div.allMobileMenu > ul > li.has-submenu-second > a
Extend Your Trip div.allMobileMenu > ul > li.has-submenu-second > a
Bhutan nav > ul > li.has-submenu > a
Back li.has-submenu > div.allMobileMenu > div.backButton > a.backMenu
Cultural Tour and Sightseeing div.allMobileMenu > ul > li.has-submenu-second > a
Trekking in Bhutan div.allMobileMenu > ul > li.has-submenu-second > a
Festival Tours div.allMobileMenu > ul > li.has-submenu-second > a
Cycling and Mountain Biking div.allMobileMenu > ul > li.has-submenu-second > a
Motorcycling div.allMobileMenu > ul > li.has-submenu-second > a
Tibet nav > ul > li.has-submenu > a
Back li.has-submenu > div.allMobileMenu > div.backButton > a.backMenu
Cultural Tour and Sightseeing div.allMobileMenu > ul > li.has-submenu-second > a
Back li.has-submenu-second > div.allMobileMenuSecond > div.backButton > a.backMenu
Trekking in Tibet div.allMobileMenu > ul > li.has-submenu-second > a
Back li.has-submenu-second > div.allMobileMenuSecond > div.backButton > a.backMenu
Cycling and Mountain Biking div.allMobileMenu > ul > li.has-submenu-second > a
Back li.has-submenu-second > div.allMobileMenuSecond > div.backButton > a.backMenu
Company nav > ul > li.has-submenu > a
Back li.has-submenu > div.allMobileMenu > div.backButton > a.backMenu
Nepal Treks nav > ul > li.has-submenu > a
Everest Region div.allMobileMenu > ul > li.has-submenu-second > a
Annapurna Region div.allMobileMenu > ul > li.has-submenu-second > a
Langtang Region div.allMobileMenu > ul > li.has-submenu-second > a
Manaslu Region div.allMobileMenu > ul > li.has-submenu-second > a
Heli Treks div.allMobileMenu > ul > li.has-submenu-second > a
Off the Beaten Path Treks div.allMobileMenu > ul > li.has-submenu-second > a
○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
●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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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
●All heading elements contain content.
●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 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
○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
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○Image elements do not have `[alt]` attributes that are redundant text.
○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 Text Quality
All 156 heading(s) have substantive, well-formed text
PASS
All 156 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s_word">
Info::
3 control(s) properly labeled
4 controls
3 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#input_9_6textNamefor/id
#input_9_5textName*for/id
#input_9_2emailEmail*for/id
s_wordtext(Search Trips)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="s_word">

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

A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "s_word" should use type="search" (currently type="text")
Field name "s_word" suggests type="search". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="search">.
A+
Form Input Quality
4 form control(s) checked, no input-semantic issues
PASS
4 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 "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Iframe Accessibility
All 2 iframe(s) have descriptive titles
PASS
All 2 iframe(s) have descriptive titles
Info::
All 2 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 2 visible text node(s) render at >= 12 CSS pixels
PASS
All 2 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback