Skip to content
https://geocaching.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
3
REVIEW
4
PASS
6
INFO
0
Checks
13
6 PASS 4 REVIEW 3 FIX
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: #ffffff
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
color-scheme meta Not set Dark theme-color Not set CSS indicators Not detected

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found Inline @media print Not detected
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
2 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Geocaching Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
7 icon(s) detected
REVIEW
7 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: Geocaching
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Geocaching 192×192 icon 512×512 icon Start URL Display Mode standalone
Name Geocaching Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 13 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

7 pass 13 fail WCAG AA 1 pass AA only
span English
2.05:1
#000000
on
#41413E
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
option English
1.70:1
#000000
on
#3C341F
needs 4.5:1 (normal text)
16px · top of page (header area)
option Български
2.06:1
#000000
on
#503E26
needs 4.5:1 (normal text)
16px · above the fold
option Català
2.04:1
#000000
on
#513D22
needs 4.5:1 (normal text)
16px · above the fold
option Čeština
1.36:1
#000000
on
#332014
needs 4.5:1 (normal text)
16px · above the fold
option Dansk
1.60:1
#000000
on
#3F2D1D
needs 4.5:1 (normal text)
16px · above the fold
option Deutsch
2.29:1
#000000
on
#60412A
needs 4.5:1 (normal text)
16px · above the fold
option Ελληνικά
2.40:1
#000000
on
#5C4730
needs 4.5:1 (normal text)
16px · above the fold
option Eesti
1.89:1
#000000
on
#4B3827
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
option Español
2.62:1
#000000
on
#5B4E43
needs 4.5:1 (normal text)
16px · above the fold
option Français
2.47:1
#000000
on
#584A40
needs 4.5:1 (normal text)
16px · above the fold
option Italiano
1.93:1
#000000
on
#4C392D
needs 4.5:1 (normal text)
16px · mid-page
option 日本語
1.67:1
#000000
on
#432F25
needs 4.5:1 (normal text)
16px · mid-page

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Join the world's lar…19.26:13.0:1
#000000
#F5F5F5
Pass
h2 3 steps to begin you…19.26:13.0:1
#000000
#F5F5F5
Pass
h3 1. Create an account19.26:13.0:1
#000000
#F5F5F5
Pass
h3 2. Find a geocache19.26:13.0:1
#000000
#F5F5F5
Pass
h3 3. Share your experi…19.26:13.0:1
#000000
#F5F5F5
Pass
title Geocaching20.86:14.5:1
#000000
#FCFFFD
Pass
a Skip to content4.93:14.5:1
#000000
#797B7A
Pass
span English2.05:14.5:1
#000000
#41413E
Fail
option English1.70:14.5:1
#000000
#3C341F
Fail
option Български2.06:14.5:1
#000000
#503E26
Fail
option Català2.04:14.5:1
#000000
#513D22
Fail
option Čeština1.36:14.5:1
#000000
#332014
Fail
option Dansk1.60:14.5:1
#000000
#3F2D1D
Fail
option Deutsch2.29:14.5:1
#000000
#60412A
Fail
option Ελληνικά2.40:14.5:1
#000000
#5C4730
Fail
option Eesti1.89:14.5:1
#000000
#4B3827
Fail
option Español2.62:14.5:1
#000000
#5B4E43
Fail
option Français2.47:14.5:1
#000000
#584A40
Fail
option Italiano1.93:14.5:1
#000000
#4C392D
Fail
option 日本語1.67:14.5:1
#000000
#432F25
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

A+
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "main" MAIN CONTENTINFO footer
A+
Heading Hierarchy
6 headings
PASS
6 headings
Info::
Single H1 present
  • H1 Join the world's largest treasure hunt.
  • H2 There are 1,165 geocaches around Singapore.
  • H2 3 steps to begin your adventure
  • H3 1. Create an account
  • H3 2. Find a geocache
  • H3 3. Share your experience
A+
Alt Text Quality
All 7 images OK
PASS
All 7 images OK
Info::
5 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
7 images 2 good alt text 5 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
selectselect(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select>

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

A+
Lighthouse Accessibility Audits
Score 95/100 — 1 failing, 27 passed
PASS
95

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

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English Български Català Čeština Dansk Deutsch Ελληνικά Eesti Español Français … nav > div#header-language-select > div.language-dropdown > select

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Background and foreground colors have a sufficient contrast ratio
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
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
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
ARIA IDs are unique
No form fields have multiple labels
`<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
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
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.
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback