https://lostspringsoutdoors.com
Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.SCORE
76
GRADE
C
FIX
6
REVIEW
6
PASS
12
INFO
0
Checks
2412 PASS 6 REVIEW 6 FIX
DLandmark StructureAction15 landmarksFIX
Landmark Structure
Action15 landmarks
15 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
10 <nav> landmark(s) found
Warning::
5 of 10 <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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Why this matters
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Learn more ▾ ▴
The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.
Source: WAI-ARIA / WCAG 2.4.1
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
DTabindex Anti-PatternsAction0 positive, 55 -1-on-focusableFIX
Tabindex Anti-Patterns
Action0 positive, 55 -1-on-focusable
0 positive, 55 -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 id="sm-17923527437335496-1">
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 id="sm-17923527437335496-3">
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 id="sm-17923527437335496-5">
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 id="sm-17923527437383838-1">
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 id="sm-17923527437383838-3">
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 id="sm-17923527437383838-5">
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.)
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 ✗
CLink & Button QualityAction10 issue(s) across 135 links and 1 buttonsREVIEW
Link & Button Quality
Action10 issue(s) across 135 links and 1 buttons
10 issue(s) across 135 links and 1 buttons
Critical::
10 link(s) with no accessible text
Links without text are announced as raw URLs by screen readers.
Got: https://lostspringsoutdoors.com; https://lostspringsoutdoors.com/about-us/; https://lostspringsoutdoors.com/c/all-products/; https://lostspringsoutdoors.com/c/all-products/; https://lostspringsoutdoors.com/about-us/; https://lostspringsoutdoors.com/c/all-products/; https://lostspringsoutdoors.com/c/all-products/; https://lostspringsoutdoors.com/about-us/; https://lostspringsoutdoors.com/c/all-products/; https://lostspringsoutdoors.com/c/all-products/
Warning::
4 link(s) open in new tab without warning
Add '(opens in new tab)' to link text or aria-label.
Got: https://FaceBook.com; https://Pinterest.com; ; http://x.com
Info::
121 link(s) with descriptive text
135 links
10 empty
0 generic text
4 new tab
0 empty buttons
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://lostspringsoutdoors.com | (empty) | empty | Add link text or aria-label |
| https://lostspringsoutdoors.com/about-us… | (empty) | empty | Add link text or aria-label |
| https://lostspringsoutdoors.com/c/all-pr… | (empty) | empty | Add link text or aria-label |
| https://lostspringsoutdoors.com/c/all-pr… | (empty) | empty | Add link text or aria-label |
| https://lostspringsoutdoors.com/about-us… | (empty) | empty | Add link text or aria-label |
| https://lostspringsoutdoors.com/c/all-pr… | (empty) | empty | Add link text or aria-label |
| https://lostspringsoutdoors.com/c/all-pr… | (empty) | empty | Add link text or aria-label |
| https://lostspringsoutdoors.com/about-us… | (empty) | empty | Add link text or aria-label |
| https://lostspringsoutdoors.com/c/all-pr… | (empty) | empty | Add link text or aria-label |
| https://lostspringsoutdoors.com/c/all-pr… | (empty) | empty | Add link text or aria-label |
| https://lostspringsoutdoors.com/p/redcam… | REDCAMP 360 Degree Swivel Hunt… | img no alt | Add alt attribute to the image |
| https://lostspringsoutdoors.com/p/deepow… | DEEPOWER Archery Broadheads 10… | img no alt | Add alt attribute to the image |
| https://lostspringsoutdoors.com/p/tidewe… | TIDEWE Hunting Range finder 87… | img no alt | Add alt attribute to the image |
| https://lostspringsoutdoors.com/p/compou… | Compound Bow Kit, Hunting and … | img no alt | Add alt attribute to the image |
| https://FaceBook.com | Facebook-f | new tab | Add '(opens in new tab)' to text |
| https://Pinterest.com | new tab | Add '(opens in new tab)' to text | |
| new tab | Add '(opens in new tab)' to text | ||
| http://x.com | X-twitter | new tab | Add '(opens in new tab)' to text |
122 links and buttons have descriptive text
Links without text are announced as raw URLs by screen readers.
https://lostspringsoutdoors.com; https://lostspringsoutdoors.com/about-us/; https://lostspringsoutdoors.com/c/all-products/; https://lostspringsoutdoors.com/c/all-products/; https://lostspringsoutdoors.com/about-us/; https://lostspringsoutdoors.com/c/all-products/; https://lostspringsoutdoors.com/c/all-products/; https://lostspringsoutdoors.com/about-us/; https://lostspringsoutdoors.com/c/all-products/; https://lostspringsoutdoors.com/c/all-products/
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://FaceBook.com; https://Pinterest.com; ; http://x.com
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
BTap Target Adequacy3 tap target(s) too small or too close togetherREVIEW
Tap Target Adequacy
3 tap target(s) too small or too close together
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.
C404 Error PageActionHTTP 404, custom pageREVIEW
404 Error Page
ActionHTTP 404, custom page
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found – Lost Springs Outdoors ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
CFavicon & BrandingAction3 icon(s) detectedREVIEW
Favicon & Branding
Action3 icon(s) detected
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
CColor Contrast (Screenshot)Action20 text elements analyzed, 8 fail WCAG AAREVIEW
Color Contrast (Screenshot)
Action20 text elements analyzed, 8 fail WCAG AA
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
12 pass 8 fail WCAG AA 1 pass AA only
h2 Featured Products
1.03:1#000000
on#040503
needs 3.0:1 (large text)24px · bottom of viewport
h2 REDCAMP 360 Degree Swivel Hunting Chair …
1.03:1#000000
on#040503
needs 3.0:1 (large text)24px · bottom of viewport
h2 DEEPOWER Archery Broadheads 100 125 Grai…
1.03:1#000000
on#040503
needs 3.0:1 (large text)24px · bottom of viewport
h2 TIDEWE Hunting Range finder 875Y with Re…
1.03:1#000000
on#040503
needs 3.0:1 (large text)24px · bottom of viewport
h2 Compound Bow Kit, Hunting and Target, Li…
1.03:1#000000
on#040503
needs 3.0:1 (large text)24px · bottom of viewport
title | Hunting Supplies and Accessories / Los…
1.02:1#000000
on#000305
needs 4.5:1 (normal text)16px · top of page (header area)
a My Account
1.02:1#000000
on#000305
needs 4.5:1 (normal text)16px · top of page (header area)
a Checkout
1.02:1#000000
on#000305
needs 4.5:1 (normal text)16px · top of page (header area)
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h2 Featured Products | 1.03:1 | 3.0:1 | #000000 | #040503 | Fail |
| h2 REDCAMP 360 Degree S… | 1.03:1 | 3.0:1 | #000000 | #040503 | Fail |
| h2 DEEPOWER Archery Bro… | 1.03:1 | 3.0:1 | #000000 | #040503 | Fail |
| h2 TIDEWE Hunting Range… | 1.03:1 | 3.0:1 | #000000 | #040503 | Fail |
| h2 Compound Bow Kit, Hu… | 1.03:1 | 3.0:1 | #000000 | #040503 | Fail |
| title | Hunting Supplies a… | 1.02:1 | 4.5:1 | #000000 | #000305 | Fail |
| a My Account | 1.02:1 | 4.5:1 | #000000 | #000305 | Fail |
| a Checkout | 1.02:1 | 4.5:1 | #000000 | #000305 | Fail |
| a Shopping Cart | 6.52:1 | 4.5:1 | #000000 | #928F8A | Pass |
| a Order Tracking | 18.07:1 | 4.5:1 | #000000 | #F4EDE3 | Pass |
| a My Account | 18.07:1 | 4.5:1 | #000000 | #F4EDE3 | Pass |
| a Checkout | 18.07:1 | 4.5:1 | #000000 | #F4EDE3 | Pass |
| a Shopping Cart | 18.07:1 | 4.5:1 | #000000 | #F4EDE3 | Pass |
| a Order Tracking | 18.07:1 | 4.5:1 | #000000 | #F4EDE3 | Pass |
| label Search | 18.07:1 | 4.5:1 | #000000 | #F4EDE3 | Pass |
| div No products in the c… | 18.07:1 | 4.5:1 | #000000 | #F4EDE3 | Pass |
| bdi 0.00 | 18.07:1 | 4.5:1 | #000000 | #F4EDE3 | Pass |
| span Cart | 19.17:1 | 4.5:1 | #000000 | #F8F4EE | Pass |
| a All Products | 7.67:1 | 4.5:1 | #000000 | #E48518 | Pass |
| a Bows and Accessories | 16.76:1 | 4.5:1 | #000000 | #FAE4AC | 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.
BLighthouse Accessibility AuditsScore 88/100 — 6 failing, 23 passedREVIEW
Lighthouse Accessibility Audits
Score 88/100 — 6 failing, 23 passed
88
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Contrast
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
search > form.elementor-search-form > div.elementor-search-form__container > input#elementor-search-form-3aafcdbf search > form.elementor-search-form > div.elementor-search-form__container > input#elementor-search-form-3aafcdbf |
Proud Life Member of the Rocky Mountain Elk Foundation div.elementor-element > div.elementor-widget-container > p > strong |
https://www.rmef.org/ div.elementor-element > div.elementor-widget-container > p > a |
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 |
|---|
Pages div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h4.elementor-heading-title |
These are opportunities to improve keyboard navigation in your application.
Names and labels
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.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a |
div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-fade2ff > a.swiper-slide-inner div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-fade2ff > a.swiper-slide-inner |
div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-5255d76 > a.swiper-slide-inner div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-5255d76 > a.swiper-slide-inner |
div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-da9fd44 > a.swiper-slide-inner div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-da9fd44 > a.swiper-slide-inner |
div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-fade2ff > a.swiper-slide-inner div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-fade2ff > a.swiper-slide-inner |
div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-5255d76 > a.swiper-slide-inner div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-5255d76 > a.swiper-slide-inner |
div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-da9fd44 > a.swiper-slide-inner div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-da9fd44 > a.swiper-slide-inner |
div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-fade2ff > a.swiper-slide-inner div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-fade2ff > a.swiper-slide-inner |
div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-5255d76 > a.swiper-slide-inner div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-5255d76 > a.swiper-slide-inner |
div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-da9fd44 > a.swiper-slide-inner div.elementor-slides-wrapper > div#swiper-wrapper-ecb12ef39594bebe > div.elementor-repeater-item-da9fd44 > a.swiper-slide-inner |
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.
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.elementor-swiper > div.elementor-slides-wrapper > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 2 div.elementor-swiper > div.elementor-slides-wrapper > div.swiper-pagination > span.swiper-pagination-bullet |
Go to slide 3 div.elementor-swiper > div.elementor-slides-wrapper > div.swiper-pagination > span.swiper-pagination-bullet |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
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 |
|---|
Add to cart div.woocommerce > ul.products > li.product > a.button |
Add to cart div.woocommerce > ul.products > li.product > a.button |
Add to cart div.woocommerce > ul.products > li.product > a.button |
Add to cart div.woocommerce > ul.products > li.product > a.button |
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Deprecated ARIA roles were not used
○`[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
○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.
○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.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
AHeading Hierarchy10 headings, 1 skip(s)PASS
Heading Hierarchy
10 headings, 1 skip(s)
10 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
- H1 Hunting Supplies and Accessories
- H2 Featured Products
- H2 REDCAMP 360 Degree Swivel Hunting Chair for Blinds, Folding Hunting Seats with Armrest for Camping Backpacking Fishing
- H2 DEEPOWER Archery Broadheads 100 125 Grain 3 Blades Hunting Arrow Heads Arrow Tips Compatible with Crossbow and Compound Bow 1+1/2 inch Cut
- H2 TIDEWE Hunting Range finder 875Y with Rechargeable Battery & Case, 6.5X Magnification Portable Mini Size Laser Rangefinder, Distance/Angle/Speed/Scan Multi Functional Waterproof(Leaf Camo)
- H2 Compound Bow Kit, Hunting and Target, Limb Made in USA,Draw Weight 30-70 lbs Adjustable, Draw Length 19-31″,up to IBO 320FPS Speed, Package with Archery Hunting Accessories
- H4 Pages skipped
- H4 Your Account
- H4 Categories
- H4 Follow Us
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
AHeading 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
Warning::
3 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected:
- H2: 138 chars
- H2: 188 chars
- H2: 172 chars
Got: 3 >120-char heading(s)
A+Alt Text QualityAll 7 images OKPASS
Alt Text Quality
All 7 images OK
All 7 images OK
Info::
7 decorative image(s) correctly marked
7 images 7 decorative
All images have appropriate alt text.
A+Form AccessibilityAll 1 controls labeledPASS
Form Accessibility
All 1 controls labeled
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
| Control | Type | Label | Method |
|---|---|---|---|
| #elementor-search-form-3aafcdbf | search | Search | for/id |
A+Form Input Types1 form control(s) checked, no type mismatchesPASS
Form Input Types
1 form control(s) checked, no type mismatches
1 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+Form Input Quality1 form control(s) checked, no input-semantic issuesPASS
Form Input Quality
1 form control(s) checked, no input-semantic issues
1 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+Mobile Keyboard & AutofillNo autofill-eligible form controlsPASS
Mobile Keyboard & Autofill
No autofill-eligible form controls
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+Document LanguageLang attribute set to "en-US"PASS
Document Language
Lang attribute set to "en-US"
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+Iframe AccessibilityNo iframes on this pagePASS
Iframe Accessibility
No iframes on this page
No iframes on this page
Info::
No iframes on this page
A+Mobile-Readable Font SizesAll 36 visible text node(s) render at >= 12 CSS pixelsPASS
Mobile-Readable Font Sizes
All 36 visible text node(s) render at >= 12 CSS pixels
All 36 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.