Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 1 REVIEW 6 FIX

Link & Button Quality

Action

6 issue(s) across 95 links and 29 buttons

FIX

6 issue(s) across 95 links and 29 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#main-content

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://fareharbor.com/sell/private-events/ ("Learn More")

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://www.phuketelephantsanctuary.org/"]

13 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://cta-na2.hubspot.com/web-interactives/public/v1/track/redirect?encrypt…; https://spark.fareharbor.com/; https://www.facebook.com/groups/644603410546239/; https://help.fareharbor.com/hc/en-us/sections/46224192090651-Webinars; https://cta-na2.hubspot.com/web-interactives/public/v1/track/redirect?encrypt…; https://nahoku2.com/; https://www.seapines.com/experiences/harbour-town; https://www.facebook.com/groups/644603410546239/; https://compass.fareharbor.com/; https://compass.fareharbor.com/guides/webinars/ (+3 more)

4 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button (#653 on page); button (#665 on page); button (#677 on page); button (#693 on page)

79 link(s) with descriptive text

95 links

1 empty

1 generic text

13 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
https://cta-na2.hubspot.com/web-interact…	Get a demo	new tab	Add '(opens in new tab)' to text
https://spark.fareharbor.com/	Spark	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/groups/64460341…	Community	new tab	Add '(opens in new tab)' to text
https://help.fareharbor.com/hc/en-us/sec…	Webinars	new tab	Add '(opens in new tab)' to text
https://cta-na2.hubspot.com/web-interact…	Get a demo	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
https://fareharbor.com/sell/private-even…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Private Events
https://nahoku2.com/	logo, company name	new tab	Add '(opens in new tab)' to text
https://www.seapines.com/experiences/har…	shape	new tab	Add '(opens in new tab)' to text
https://www.phuketelephantsanctuary.org/	Phuket Elephant Sanctuary	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/groups/64460341…	Community	new tab	Add '(opens in new tab)' to text
https://compass.fareharbor.com/	Compass	new tab	Add '(opens in new tab)' to text
https://compass.fareharbor.com/guides/we…	Webinars	new tab	Add '(opens in new tab)' to text
https://spark.fareharbor.com/	Spark	new tab	Add '(opens in new tab)' to text
https://status.fareharbor.com/	Status	new tab	Add '(opens in new tab)' to text
https://marketing.fareharbor.com/	English	img no alt	Add alt attribute to the image
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

104 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#main-content

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

Generic link text like 'click here' doesn't describe the destination.

https://fareharbor.com/sell/private-events/ ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://www.phuketelephantsanctuary.org/"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://cta-na2.hubspot.com/web-interactives/public/v1/track/redirect?encrypt…; https://spark.fareharbor.com/; https://www.facebook.com/groups/644603410546239/; https://help.fareharbor.com/hc/en-us/sections/46224192090651-Webinars; https://cta-na2.hubspot.com/web-interactives/public/v1/track/redirect?encrypt…; https://nahoku2.com/; https://www.seapines.com/experiences/harbour-town; https://www.facebook.com/groups/644603410546239/; https://compass.fareharbor.com/; https://compass.fareharbor.com/guides/webinars/ (+3 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Icon-only buttons need an aria-label so screen readers can announce them.

button (#653 on page); button (#665 on page); button (#677 on page); button (#693 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-ov74cm

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://fareharbor.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://fareharbor.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

A+

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

23 headings

PASS

23 headings

Single H1 present

H1 Powerful booking software. Unmatched support.
H2 Core Values
H2 Are competitors booking your customers?
H2 Manage bookings with confidence
H2 Sell anywhere, securely
H2 Scale and grow
H2 Private Events
H2 Cards
H2 A game-changer for private charters: How FareHarbor helped Cruise San Diego scale
H2 Loved by more than 20,000 companies
H2 Start streamlining your bookings today
H2 Footer navigation
H3 Solutions
H3 Resources
H3 Company
H2 We value your privacy
H2 Privacy Preference Center
H3 Manage Consent Preferences
H4 Strictly Necessary Cookies
H4 Functional Cookies
H4 Targeting Cookies
H4 Performance Cookies
H3 Vendors List

A+

Alt Text Quality

All 18 images OK

PASS

All 18 images OK

6 decorative image(s) correctly marked

12 image(s) with good alt text

18 images 12 good alt text 6 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 7 controls labeled

PASS

All 7 controls labeled

7 control(s) properly labeled

7 controls

7 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#vendor-search-handler	text	Vendor list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Powerful	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Unmatched support.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Core Values	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Are competitors book…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Manage bookings with…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Sell anywhere, secur…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Scale and grow	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Private Events	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Cards	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 A game-changer for p…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Loved by more than 2…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Start streamlining y…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Footer navigation	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 We value your privac…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Privacy Preference C…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Solutions	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Company	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Manage Consent Prefe…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Vendors List	21.00:1	3.0:1	#000000	#FFFFFF	Pass

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

Lighthouse Accessibility Audits

Score 92/100 — 2 failing, 28 passed

PASS

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.

ARIA

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
English `ul > li.wpml-ls-slot-footer > a.wpml-ls-link > span.wpml-ls-native`

These are opportunities to improve the usage of ARIA in your application which 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
Check my booking health > `div.feature > div.stack-l > div.links > a.operator-iq-cta`

These are opportunities to improve the legibility of your content.

○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]` 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.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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 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

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

○Form elements have associated labels

○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.

○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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.