Accessibility

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

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 Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

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.

D

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.

D

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 ✗

F

Navigation UX

Action

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Skip navigation link detected

3 navigation landmark(s) detected

Breadcrumbs

Search

Skip Link Skip link detected

Labeled Navigation 3 <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

Heading Hierarchy

16 headings, 1 skip(s)

REVIEW

16 headings, 1 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H4 (missing H2)

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

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H3 For Couples in Greenwich, Connecticut and Florida.
H1 Couples Therapy
H2 Are you caught in the same arguments without resolution?
H3 It’s never too late to seek help, rebuild your connection, and rediscover the intimacy and closeness you once shared.
H4 Couples Therapy can help to:
H4 Issues that I can help with:
H1 How It Works duplicate H1
H4 In our sessions, we work together to explore challenges, build healthier patterns, and strengthen the foundation for a more balanced, fulfilling relationship. skipped
H4 Sex Therapy
H4 Couples Therapy
H4 About Me
H4 Individual Therapy
H2 Change is Possible
H3 Now is the time to reclaim the confidence, connection, intimacy, and love you deserve.
H4 (empty)
H4 Sex Therapy < BACK NEXT > About Me

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

B

Link & Button Quality

1 issue(s) across 43 links and 6 buttons

REVIEW

1 issue(s) across 43 links and 6 buttons

1 link(s) with no accessible text

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

Got: /about-linda-1

3 link(s) open in new tab without warning

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

Got: /contact; /contact; /contact

39 link(s) with descriptive text

43 links

1 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/contact	Contact Me	new tab	Add '(opens in new tab)' to text
/contact	Contact Me	new tab	Add '(opens in new tab)' to text
/contact	Contact Me	new tab	Add '(opens in new tab)' to text
/about-linda-1	(empty)	empty	Add link text or aria-label

45 links and buttons have descriptive text

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

/about-linda-1

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.

/contact; /contact; /contact

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

B

Tabindex Anti-Patterns

0 positive, 4 -1-on-focusable

REVIEW

0 positive, 4 -1-on-focusable

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

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

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

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

B

Mobile-Readable Font Sizes

97% of visible text renders at >= 12 CSS px (1 below threshold)

REVIEW

97% of visible text renders at >= 12 CSS px (1 below threshold)

1 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <strong> 11.6px ("SCHEDULE A 15 MINUTE CONSULTATION").

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Marriage & Family Therapist ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

B

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 5 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 How It Works	6.02:1	3.0:1	#000000	#98876C	Pass
h2 Change is Possible	6.02:1	3.0:1	#000000	#98876C	Pass
h3 Now is the time to r…	6.02:1	3.0:1	#000000	#98876C	Pass
title Marriage & Family Th…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to Content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Marriage + Family Th…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a About	5.55:1	4.5:1	#000000	#7E848A	Pass
span Specialties	7.01:1	4.5:1	#000000	#97958E	Pass
a Couples Therapy	5.55:1	4.5:1	#000000	#74868F	Pass
a Sex Therapy	5.86:1	4.5:1	#000000	#798A91	Pass
a Individual Therapy	6.41:1	4.5:1	#000000	#869091	Pass
a Details	6.80:1	4.5:1	#000000	#8D9494	Pass
a Contact Me	7.35:1	4.5:1	#000000	#969A94	Pass
span Open Menu	8.00:1	4.5:1	#000000	#A1A098	Pass
span Close Menu	8.46:1	4.5:1	#000000	#A9A499	Pass
a Contact Me	8.69:1	4.5:1	#000000	#ADA699	Pass
a Marriage + Family Th…	8.47:1	4.5:1	#000000	#ACA490	Pass
a About	8.78:1	4.5:1	#000000	#ADA79C	Pass
span Specialties	8.52:1	4.5:1	#000000	#ACA58D	Pass
a Couples Therapy	8.52:1	4.5:1	#000000	#ABA590	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.

A

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

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

A

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 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: - H4: 158 chars

Got: 1 >120-char heading(s)

A

Alt Text Quality

All 11 images OK

PASS

All 11 images OK

3 image(s) with alt text over 125 characters

3 decorative image(s) correctly marked

5 image(s) with good alt text

11 images 5 good alt text 3 decorative

Issue	Count
too long	3 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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-US"

PASS

Lang attribute set to "en-US"

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

Got: en-US

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+

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 91/100 — 3 failing, 23 passed

PASS

91

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
Are you caught in the same arguments without resolution? `div.sqs-text-block-container > div.sqs-html-content > h2 > span.sqsrte-text-color--black`
Do you find yourselves avoiding each other? `div.sqs-text-block-container > div.sqs-html-content > p > span.sqsrte-text-color--black`
Has your communication turned mostly negative or critical? `div.sqs-text-block-container > div.sqs-html-content > p > span.sqsrte-text-color--black`
Every relationship faces challenges, but couples therapy can help you navigate … `div.sqs-text-block-container > div.sqs-html-content > p > span.sqsrte-text-color--black`
Couples Therapy can help to: `li.accordion-item > h4.accordion-item__title-wrapper > button#button-yui_3_17_2_1_1745712717462_4953-1 > span.accordion-item__title`
Issues that I can help with: `li.accordion-item > h4.accordion-item__title-wrapper > button#button-yui_3_17_2_1_1745712717462_4953-2 > span.accordion-item__title`
Couples therapy is a supportive, collaborative process. Most sessions will be t… `div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > p`
In our first session, we’ll talk about what brings you here and what you’re hop… `div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > p`
Every couple is unique, and I tailor my approach to fit your needs, drawing fro… `div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > p`
Sessions are 60 minutes and typically held once a week — either in person or ov… `div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > p`
Understanding each other’s vulnerabilities `div.sqs-html-content > ul > li > p`
Communicating openly and without defensiveness `div.sqs-html-content > ul > li > p`
Reconnecting with each other’s values and dreams `div.sqs-html-content > ul > li > p`
Moving past difficult impasses `div.sqs-html-content > ul > li > p`
Managing emotions with greater awareness `div.sqs-html-content > ul > li > p`
Creating lasting change through shared goals `div.sqs-html-content > ul > li > p`
In our sessions, we work together to explore challenges, build healthier patter… `div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > h4`
SCHEDULE A 15 MINUTE CONSULTATION `div#block-680f7fed05d981ff71969907 > div#yui_3_17_2_1_1790974449724_69 > div#yui_3_17_2_1_1790974449724_68 > a.sqs-block-button-element--large`

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
In our sessions, we work together to explore challenges, build healthier patter… `div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > h4`

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.sqs-text-block-container > div.sqs-html-content > h4 > a`

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

○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

●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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●All heading elements contain content.

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

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

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

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

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