Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 7 REVIEW 5 FIX

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.

Got: <input type="email" id="form-field-input-fa3b0aad-f2fe-47df-ee69-6441506710df-comp-mek85gex-">

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.

Got: <input type="email" id="form-field-input-fa3b0aad-f2fe-47df-ee69-6441506710df-comp-mek85gex-">

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

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

Heading Hierarchy

10 headings, 2 skip(s)

REVIEW

10 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

Heading level skipped: H2 → H4 (missing H3)

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

H1 WE RUN THE ADS. WE BUILD THE MACHINE BEHIND THEM.
H2 YOU'RE NOT LOSING TO BETTER BUSINESSES. YOU'RE LOSING TO BETTER ADS.
H4 Special Projects skipped
H2 Here's The Receipts: Real Campaigns, Real Growth, Real Revenue.
H2 E-Commerce
H2 Healthcare
H2 Service Based
H4 Special Projects skipped
H2 Why us?
H2 Every Day You Wait, a Competitor Gets the Customer That Should Have Been Yours.

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

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Alt Text Quality

5 of 24 images have issues

REVIEW

5 of 24 images have issues

5 image(s) with filename as alt text

2 decorative image(s) correctly marked

17 image(s) with good alt text

24 images 17 good alt text 2 decorative 5 generic

Issue	Count
filename	5 image(s)

Link & Button Quality

1 issue(s) across 66 links and 7 buttons

REVIEW

1 issue(s) across 66 links and 7 buttons

10 link(s) open in new tab without warning

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

Got: https://www.openheartmediaco.com/_files/ugd/a890dd_174a08c408cc435584597a6424…; https://www.openheartmediaco.com/_files/ugd/a890dd_174a08c408cc435584597a6424…; https://www.openheartmediaco.com/_files/ugd/a890dd_25dc6976fc414509b84f6fcaf2…; https://www.openheartmediaco.com/_files/ugd/a890dd_25dc6976fc414509b84f6fcaf2…; https://www.openheartmediaco.com/_files/ugd/a890dd_5caa80c7ac0f47a4855341e5fc…; https://www.openheartmediaco.com/_files/ugd/a890dd_5caa80c7ac0f47a4855341e5fc…; https://www.instagram.com/openheartmedia/?hl=en; https://www.linkedin.com/company/open-heart-media; https://www.facebook.com/openheartmedia2/; https://www.youtube.com/@openheartmedia9123

1 button(s) with no accessible text

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

Got: button#comp-kd5px9q0_r_comp-kkmqi5tc

56 link(s) with descriptive text

66 links

0 empty

0 generic text

10 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.openheartmediaco.com/_files/…	See Real Results →	new tab	Add '(opens in new tab)' to text
https://www.openheartmediaco.com/_files/…	See Real Results →	new tab	Add '(opens in new tab)' to text
https://www.openheartmediaco.com/_files/…	See Real Results →	new tab	Add '(opens in new tab)' to text
https://www.openheartmediaco.com/_files/…	See Real Results →	new tab	Add '(opens in new tab)' to text
https://www.openheartmediaco.com/_files/…	See Real Results →	new tab	Add '(opens in new tab)' to text
https://www.openheartmediaco.com/_files/…	See Real Results →	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/openheartmedia…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/open-he…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/openheartmedia2…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@openheartmedia9…	Youtube	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

62 links and buttons have descriptive text

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

https://www.openheartmediaco.com/_files/ugd/a890dd_174a08c408cc435584597a6424…; https://www.openheartmediaco.com/_files/ugd/a890dd_174a08c408cc435584597a6424…; https://www.openheartmediaco.com/_files/ugd/a890dd_25dc6976fc414509b84f6fcaf2…; https://www.openheartmediaco.com/_files/ugd/a890dd_25dc6976fc414509b84f6fcaf2…; https://www.openheartmediaco.com/_files/ugd/a890dd_5caa80c7ac0f47a4855341e5fc…; https://www.openheartmediaco.com/_files/ugd/a890dd_5caa80c7ac0f47a4855341e5fc…; https://www.instagram.com/openheartmedia/?hl=en; https://www.linkedin.com/company/open-heart-media; https://www.facebook.com/openheartmedia2/; https://www.youtube.com/@openheartmedia9123

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#comp-kd5px9q0_r_comp-kkmqi5tc

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

Mobile-Readable Font Sizes

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

REVIEW

98% 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: <h4> 11.8px ("Special Projects").

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 404 Error: Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA

h1 WE RUN THE ADS.

1.51:1

#000000

#222B49

needs 3.0:1 (large text)

32px · bottom of viewport

h1 WE BUILD THE

1.51:1

#000000

#222B49

needs 3.0:1 (large text)

32px · bottom of viewport

h1 MACHINE BEHIND THEM.

1.51:1

#000000

#222B49

needs 3.0:1 (large text)

32px · bottom of viewport

h2 YOU'RE NOT LOSING TO BETTER BUSINESSES. …

1.51:1

#000000

#222B49

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Here's The Receipts:

1.51:1

#000000

#222B49

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Real Campaigns, Real Growth, Real Revenu…

1.51:1

#000000

#222B49

needs 3.0:1 (large text)

24px · bottom of viewport

h2 E-Commerce

1.51:1

#000000

#222B49

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Healthcare

1.51:1

#000000

#222B49

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Service Based

1.51:1

#000000

#222B49

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why us?

1.51:1

#000000

#222B49

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Every Day You Wait, a Competitor Gets th…

1.51:1

#000000

#222B49

needs 3.0:1 (large text)

24px · bottom of viewport

span Close

1.64:1

#000000

#5F191C

needs 4.5:1 (normal text)

16px · top of page (header area)

a HOME

1.60:1

#000000

#5C1819

needs 4.5:1 (normal text)

16px · above the fold

div SERVICES

1.61:1

#000000

#5D181A

needs 4.5:1 (normal text)

16px · above the fold

a Website Support

1.60:1

#000000

#5C181A

needs 4.5:1 (normal text)

16px · above the fold

a Social Media Management

1.59:1

#000000

#5B181B

needs 4.5:1 (normal text)

16px · above the fold

a SEO

1.59:1

#000000

#5B181C

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 WE RUN THE ADS.	1.51:1	3.0:1	#000000	#222B49	Fail
h1 WE BUILD THE	1.51:1	3.0:1	#000000	#222B49	Fail
h1 MACHINE BEHIND THEM.	1.51:1	3.0:1	#000000	#222B49	Fail
h2 YOU'RE NOT LOSING TO…	1.51:1	3.0:1	#000000	#222B49	Fail
h2 Here's The Receipts:	1.51:1	3.0:1	#000000	#222B49	Fail
h2 Real Campaigns, Real…	1.51:1	3.0:1	#000000	#222B49	Fail
h2 E-Commerce	1.51:1	3.0:1	#000000	#222B49	Fail
h2 Healthcare	1.51:1	3.0:1	#000000	#222B49	Fail
h2 Service Based	1.51:1	3.0:1	#000000	#222B49	Fail
h2 Why us?	1.51:1	3.0:1	#000000	#222B49	Fail
h2 Every Day You Wait, …	1.51:1	3.0:1	#000000	#222B49	Fail
title Open Heart Media \| D…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span top of page	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Menu	8.00:1	4.5:1	#000000	#A29F9F	Pass
span Close	1.64:1	4.5:1	#000000	#5F191C	Fail
a HOME	1.60:1	4.5:1	#000000	#5C1819	Fail
div SERVICES	1.61:1	4.5:1	#000000	#5D181A	Fail
a Website Support	1.60:1	4.5:1	#000000	#5C181A	Fail
a Social Media Managem…	1.59:1	4.5:1	#000000	#5B181B	Fail
a SEO	1.59:1	4.5:1	#000000	#5B181C	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.

Landmark Structure

11 landmarks

PASS

11 landmarks

<main> landmark present

4 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 2 all-caps heading(s)

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#form-field-input-fa3b0aad-f2fe-47df-ee69-6441506710df-comp-mek85gex-	email	Enter your email	aria-label
#checkbox-5	checkbox		none

A+

Form Input Types

2 form control(s) checked, no type mismatches

PASS

2 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

2 form control(s) checked, no input-semantic issues

PASS

2 form control(s) checked, no input-semantic issues

All form input semantics look correct

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

43 explicit tabindex attribute(s) checked, no anti-patterns

PASS

43 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

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

2 mobile-depth signal(s) detected

PASS

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

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

A+

Lighthouse Accessibility Audits

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

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
Special Projects `section#comp-mfcsfyee > div.comp-mfcsfyee-container > div#comp-mfcsjw2a > h4.font_4`

These are opportunities to improve keyboard navigation in your application.

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

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

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

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

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