Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 3 REVIEW 5 FIX

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

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

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

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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 Reconnect

1.73:1

#000000

#48311D

needs 3.0:1 (large text)

32px · mid-page

h2 One Person Can Save a Marriage

2.28:1

#000000

#574434

needs 3.0:1 (large text)

24px · mid-page

h2 Happiness Begins When You Connect.

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Wondering why your relationship isn't wo…

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Six shifts this work makes possible

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Does This Story Sound Familiar?

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Love isn't lost.

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How Our Relationship Guidance System Wor…

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Happiness… Will You Be Next?

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

24px · bottom of viewport

h2 FAQ

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Book your complimentary session today.

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Experience Emotional Connection

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Communicate With Clarity

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Build a Partnership

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Keep Love Alive

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Become the Partner Your Relationship Req…

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Reignite Desire

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Book your complimentary session today.

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Transform your relationship.

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Silent Days

1.25:1

#000000

#231C11

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Reconnect	1.73:1	3.0:1	#000000	#48311D	Fail
h2 One Person Can Save …	2.28:1	3.0:1	#000000	#574434	Fail
h2 Happiness Begins Whe…	1.25:1	3.0:1	#000000	#231C11	Fail
h2 Wondering why your r…	1.25:1	3.0:1	#000000	#231C11	Fail
h2 Six shifts this work…	1.25:1	3.0:1	#000000	#231C11	Fail
h2 Does This Story Soun…	1.25:1	3.0:1	#000000	#231C11	Fail
h2 Love isn't lost.	1.25:1	3.0:1	#000000	#231C11	Fail
h2 How Our Relationship…	1.25:1	3.0:1	#000000	#231C11	Fail
h2 Happiness… Will Yo…	1.25:1	3.0:1	#000000	#231C11	Fail
h2 FAQ	1.25:1	3.0:1	#000000	#231C11	Fail
h2 Book your compliment…	1.25:1	3.0:1	#000000	#231C11	Fail
h3 Experience Emotional…	1.25:1	3.0:1	#000000	#231C11	Fail
h3 Communicate With Cla…	1.25:1	3.0:1	#000000	#231C11	Fail
h3 Build a Partnership	1.25:1	3.0:1	#000000	#231C11	Fail
h3 Keep Love Alive	1.25:1	3.0:1	#000000	#231C11	Fail
h3 Become the Partner Y…	1.25:1	3.0:1	#000000	#231C11	Fail
h3 Reignite Desire	1.25:1	3.0:1	#000000	#231C11	Fail
h3 Book your compliment…	1.25:1	3.0:1	#000000	#231C11	Fail
h3 Transform your relat…	1.25:1	3.0:1	#000000	#231C11	Fail
h3 Silent Days	1.25:1	3.0:1	#000000	#231C11	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+

Heading Hierarchy

25 headings

PASS

25 headings

Single H1 present

H1 ReconnectFind Happiness
H2 One Person Can Save a Marriage
H2 Happiness Begins When You Connect.
H2 Wondering why your relationship isn't working? The answer is always the same: patterns.
H2 Six shifts this work makes possible
H3 Experience Emotional Connection
H3 Communicate With Clarity
H3 Build a Partnership
H3 Keep Love Alive
H3 Become the Partner Your Relationship Requires
H3 Reignite Desire
H2 Does This Story Sound Familiar?
H2 Love isn't lost.
H2 How Our Relationship Guidance System Works
H3 Book your complimentary session today.
H3 Transform your relationship.
H2 Happiness… Will You Be Next?
H3 Silent Days
H3 No Intimacy – Strangers
H3 After the Affair
H3 Finally Found
H3 Starting Over, Together
H3 Closer Than the Distance
H2 FAQ
H2 Book your complimentary session today.

A+

Heading Text Quality

All 25 heading(s) have substantive, well-formed text

PASS

All 25 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Link & Button Quality

1 issue(s) across 25 links and 1 buttons

PASS

1 issue(s) across 25 links and 1 buttons

1 link(s) with generic text

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

Got: https://calendly.com/your-link ("Continue")

24 link(s) with descriptive text

25 links

0 empty

1 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://calendly.com/your-link	Continue	generic text	Replace with descriptive text
Before: Continue Suggested: Your Link

25 links and buttons have descriptive text

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

https://calendly.com/your-link ("Continue")

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

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 119 visible text node(s) render at >= 12 CSS pixels

PASS

All 119 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.

A+

Lighthouse Accessibility Audits

Score 95/100 — 1 failing, 20 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.

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
Get a Complimentary Session `body > section.hero > div.hero-content > a.btn`
“We don't talk anymore.” `body > div.dialogue-banner-wrap > div#dialogueBanner > span#dialogueLeft`
“I don't know how to start.” `body > div.dialogue-banner-wrap > div#dialogueBanner > span#dialogueRight`
Book Your Complimentary Session Today `body > section#how-it-works > div.section-inner > a.btn`
Continue `body > section#contact > div.section-inner > a.btn`
© 2026 Lasting Love Coaching. All rights reserved. `body > footer.site-footer > div.footer-inner > p.footer-copy`
2026 `footer.site-footer > div.footer-inner > p.footer-copy > span#year`

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

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

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

○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

○`[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

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

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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