Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Link & Button Quality

Action

8 issue(s) across 121 links and 20 buttons

FIX

8 issue(s) across 121 links and 20 buttons

1 link(s) with no accessible text

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

Got: #

1 link(s) with generic text

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

Got: https://unbounce.com/concierge/ ("Learn more")

15 link(s) open in new tab without warning

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

Got: /concierge/; /conversion-benchmark-report/; https://developer.unbounce.com/; https://documentation.unbounce.com/; https://chat.openai.com/?q=Summarize%20the%20biggest%20reasons%20businesses%2…; https://www.perplexity.ai/search/new?q=Summarize%20the%20biggest%20reasons%20…; https://claude.ai/new?q=Summarize%20the%20biggest%20reasons%20businesses%20tr…; https://www.google.com/search?udm=50&aep=11&q=Explain%20what%20makes%20Unboun…; https://x.com/i/grok?text=Summarize%20the%20biggest%20reasons%20businesses%20…; https://www.instagram.com/unbounce/ (+5 more)

6 button(s) with no accessible text

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

Got: button.search-submit (#329 on page); button.search-toggle (#347 on page); button (#997 on page); button (#1011 on page); button (#1025 on page); button (#1035 on page)

104 link(s) with descriptive text

121 links

1 empty

1 generic text

15 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
https://unbounce.com/concierge/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Concierge
/concierge/	Highlight-Visual	new tab	Add '(opens in new tab)' to text
/conversion-benchmark-report/	Highlight-Visual	new tab	Add '(opens in new tab)' to text
https://developer.unbounce.com/	Integrate with us	new tab	Add '(opens in new tab)' to text
https://documentation.unbounce.com/	Help center	new tab	Add '(opens in new tab)' to text
https://chat.openai.com/?q=Summarize%20t…	ChatGPT-logo	new tab	Add '(opens in new tab)' to text
https://www.perplexity.ai/search/new?q=S…	perplexity-logo	new tab	Add '(opens in new tab)' to text
https://claude.ai/new?q=Summarize%20the%…	claude-logo	new tab	Add '(opens in new tab)' to text
https://www.google.com/search?udm=50&aep…	gemini-logo	new tab	Add '(opens in new tab)' to text
https://x.com/i/grok?text=Summarize%20th…	grok-logo	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/unbounce/	instagram-logo	new tab	Add '(opens in new tab)' to text
https://linkedin.com/company/unbounce	linkedIn-logo	new tab	Add '(opens in new tab)' to text
https://twitter.com/unbounce	x-twitter-logo	new tab	Add '(opens in new tab)' to text
https://www.g2.com/products/unbounce/rev…	g2-logo	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
https://cookiepedia.co.uk/giving-consent…	More information about your pr…	new tab	Add '(opens in new tab)' to text
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
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

118 links and buttons have descriptive text

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

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://unbounce.com/concierge/ ("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

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

/concierge/; /conversion-benchmark-report/; https://developer.unbounce.com/; https://documentation.unbounce.com/; https://chat.openai.com/?q=Summarize%20the%20biggest%20reasons%20businesses%2…; https://www.perplexity.ai/search/new?q=Summarize%20the%20biggest%20reasons%20…; https://claude.ai/new?q=Summarize%20the%20biggest%20reasons%20businesses%20tr…; https://www.google.com/search?udm=50&aep=11&q=Explain%20what%20makes%20Unboun…; https://x.com/i/grok?text=Summarize%20the%20biggest%20reasons%20businesses%20…; https://www.instagram.com/unbounce/ (+5 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.search-submit (#329 on page); button.search-toggle (#347 on page); button (#997 on page); button (#1011 on page); button (#1025 on page); button (#1035 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

Web Manifest

Action

Valid manifest

FIX

Valid manifest

Name present: App

192x192 icon present

PWA Install Criteria Not Installable

Name App ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗

Name App Icons 6 icon(s)

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.

Heading Hierarchy

62 headings, 1 skip(s)

REVIEW

62 headings, 1 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.

1 empty heading(s)

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

H5 Products and features
H4 Landing pages
H4 A/B testing
H4 Smart Traffic
H5 Products and features
H4 AI Copywriting
H4 Integrations
H4 Templates
H5 More solutions by Unbounce
H4 Insightly CRM
H5 Industries
H5 Use cases
H5 Flexible limits and extra support
H5 Flexible limits and extra support
H5 The essentials
H6 What is a landing page?
H6 Landing page examples
H6 Conversion benchmark report
H5 Marketing resources
H5 Marketing resources
H1 Launch faster. Convert more.
H2 Convert more customers with one platform
H4 Build and test stunning pages without a single line of code skipped
H4 A/B testing
H4 AI optimization
H4 +104%
H5 Forrest Schaffer - Senior Manager of Growth
H5 Forrest Schaffer Senior Manager of Growth
H2 Convert more customers with one platform
H3 Launch landing pages faster, accelerate results
H3 Own your experiments, maximize conversions
H3 Simplify CRO, get the most out of your marketing
H2 Launch tailored pages in a few clicks
H3 Create pages without building from scratch
H3 Give customers what they’re looking for
H3 Customize your pages to match your vision
H2 Everything you need to A/B test in one place
H3 No developer, no problem
H3 Experiment limitlessly
H3 Test with confidence
H2 Let AI and ML do the heavy lifting
H3 Convert more in a few clicks
H3 Push for peak performance
H3 Get audience insights
H2 Seamlessly integrate with your stack
H2 Why marketers love Unbounce
H3 SaaS businesses
H3 Ecommerce stores
H3 Marketing agencies
H2 Scale your marketing without limits
H2 Build, test, and optimize landing pages—all in one platform
H3 (empty)
H2 We’re with you all the way
H3 Start building pages for free
H3 Scale your marketing without limits
H2 Privacy Preference Center
H3 Manage Consent Preferences
H4 Performance Cookies
H4 Targeting Cookies
H4 Strictly Necessary Cookies
H4 Functional Cookies
H3 Cookie List

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

Form Accessibility

Action

3 of 11 controls have issues

REVIEW

3 of 11 controls have issues

2 control(s) without accessible label

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

Got: <input type="text" name="hidden">; <input type="text" id="essb_copy_link_field">

1 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="search" name="s">

8 control(s) properly labeled

11 controls

8 labeled

1 placeholder only

2 unlabeled

Control	Type	Label	Method
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#vendor-search-handler	text	Cookie 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
s	search	(Search...)	placeholder only
hidden	text	(none)	none
#essb_copy_link_field	text	(none)	none

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

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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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 - Unbounce ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

10 icon(s) detected

REVIEW

10 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 Present

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Action

Score 76/100 — 7 failing, 21 passed

REVIEW

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
search-icon `div.container-fluid > div.menu-container > div.nav-toggles > button.search-toggle`

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.graphic-content-block > div.graphic-content-block > div.mt-3 > img.mt-0 `div.graphic-content-block > div.graphic-content-block > div.mt-3 > img.mt-0`

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.

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
div#footer-links-ai > ul#menu-footer-ai-nav > li.heading-ai-nav > a.dropdown-toggle `div#footer-links-ai > ul#menu-footer-ai-nav > li.heading-ai-nav > a.dropdown-toggle`

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
Build and test stunning pages without a single line of code `div.prodfeat-top > div#bx1 > div.prodfeat-disc > h4.prodfeat-add`

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
search-icon `div.container-fluid > div.menu-container > div.nav-toggles > button.search-toggle`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
toggle menu `div.container-fluid > div.menu-container > div.nav-toggles > button.navbar-toggler`

○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

●Form elements have associated labels

●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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○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

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

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

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

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

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

Alt Text Quality

1 of 75 images have issues

PASS

1 of 75 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 decorative image(s) correctly marked

73 image(s) with good alt text

75 images 73 good alt text 1 decorative 1 missing

Issue	Count
missing	1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

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 Launch faster.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Convert more.	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Convert more custome…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Convert more custome…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Launch tailored page…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Everything you need …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Let AI and ML do the…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Seamlessly integrate…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Why marketers love U…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Scale your marketing…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Build, test, and opt…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 We’re with you all…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Privacy Preference C…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Launch landing pages…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Own your experiments…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Simplify CRO, get th…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Create pages without…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Give customers what …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Customize your pages…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 No developer, no pro…	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.

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