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 4 REVIEW 3 FIX

Web Manifest

Action

Valid manifest

FIX

Valid manifest

Name present: GetResponse

192x192 icon present

PWA Install Criteria Not Installable

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

Name GetResponse Icons 6 icon(s)

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.

Link & Button Quality

Action

5 issue(s) across 109 links and 9 buttons

REVIEW

5 issue(s) across 109 links and 9 buttons

3 link(s) with generic text

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

Got: /features/email-marketing ("Learn more"); /features/marketing-automation ("Learn more"); /features/landing-page-creator ("Learn more")

1 link(s) open in new tab without warning

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

Got: /legal/web-accessibility-statement

2 button(s) with no accessible text

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

Got: button.Tabs_arrow__OEf42 (#615 on page); button.Tabs_arrow__OEf42 (#616 on page)

105 link(s) with descriptive text

109 links

0 empty

3 generic text

1 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
/features/email-marketing	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Email Marketing
/features/marketing-automation	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Marketing Automation
/features/landing-page-creator	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Landing Page Creator
/legal/web-accessibility-statement	Accessibility statement	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

112 links and buttons have descriptive text

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

/features/email-marketing ("Learn more"); /features/marketing-automation ("Learn more"); /features/landing-page-creator ("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.

/legal/web-accessibility-statement

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.Tabs_arrow__OEf42 (#615 on page); button.Tabs_arrow__OEf42 (#616 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

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 Error 404 - page not found! ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

22 icon(s) detected

REVIEW

22 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

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #ffffff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Landmark Structure

4 landmarks

PASS

4 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

A+

Heading Hierarchy

28 headings

PASS

28 headings

Single H1 present

H1 Convert more customers. Keep them coming back.
H2 EMAIL MARKETING & AUTOMATION PLATFORM
H3 Trusted by 350K+ entrepreneurs, ecommerce stores, and Global Brands
H2 Limitless access to the tools that move your business forward — and sell more
H2 Unlimited emails
H2 Unlimited automations
H2 Unlimited landing pages
H2 Why GetResponse?
H3 We generated $43,000 in sales with just 10 emails using GetResponse.
H3 We generated €16.5K in sales from one email in just two days — and €25.4K from another single campaign.
H3 We increased our turnover by 72% by using GetResponse’s targeted marketing and automation.
H3 Advanced automations within GetResponse generated us $13k sales from a single campaign.
H2 Sync your data and growth with 150+ integrations
H2 Take further control of your marketing using our additional suite of AI tools and features.
H3 AI product recommendations
H3 SMS
H3 Web-push notifications
H3 Forms and Popups
H3 Funnels
H3 Webinars
H2 Join 350,000+ businesses growing sales with GetResponse email and automation
H3 Product
H3 Help and resources
H3 Company
H3 Top blog content
H3 Get the GetResponse App
H3 Follow us
H3 Change the language

A+

Alt Text Quality

All 29 images OK

PASS

All 29 images OK

7 decorative image(s) correctly marked

22 image(s) with good alt text

29 images 22 good alt text 7 decorative

All images have appropriate alt text.

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
#hero-email	email	Email address	aria-label
#email	email	Email address	aria-label

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 Convert more custome…	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h1 them coming back.	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h2 EMAIL MARKETING & AU…	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h2 access to the tools …	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h2 your business forwar…	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h2 emails	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h2 automations	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h2 landing pages	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h2 Why GetResponse?	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h2 Sync your data and g…	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h2 with 150+ integratio…	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h2 Take further control…	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h2 our additional suite…	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h2 Join 350,000+ busine…	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h3 Trusted by 350K+ ent…	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h3 We generated $43,000…	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h3 We generated €16.5…	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h3 We increased our tur…	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h3 Advanced automations…	4.96:1	3.0:1	#000000	#7A7B7D	Pass
h3 Product	4.96:1	3.0:1	#000000	#7A7B7D	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 94/100 — 2 failing, 30 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
See our pricing `div.Hero_article__oSqHR > div.StartFreeTrialForm_formwrapper__R89Ch > small > a`
TRUSTED BY 350K+ ENTREPRENEURS, ECOMMERCE STORES, AND GLOBAL BRANDS `section.Hero_hero__QlTB_ > section.BoxBrandsLogo_boxBrandsLogo__dFi_D > div.Container_container__Bfh8E > h3`
GetResponse: `div#__next > main._locale__main__qxd5i > div.awardsContainer_awards__eMqxx > div.awardsContainer_introduction__FsZX6`
The only email marketing and automation tool that stays affordable as you get m… `div#__next > main._locale__main__qxd5i > div.awardsContainer_awards__eMqxx > div.awardsContainer_text__8dqsP`
successful. `main._locale__main__qxd5i > div.awardsContainer_awards__eMqxx > div.awardsContainer_text__8dqsP > strong`
Limitless `div.Container_container__Bfh8E > div.UnlimitedTools_sectionTitle__1qSB8 > h2 > span`
Unlimited `div.Card_wrapContent__pnDb7 > div.Card_innerContent__MFD6e > h2.Card_title__TDB_w > span`
Unlimited `div.Card_wrapContent__pnDb7 > div.Card_innerContent__MFD6e > h2.Card_title__TDB_w > span`
Unlimited `div.Card_wrapContent__pnDb7 > div.Card_innerContent__MFD6e > h2.Card_title__TDB_w > span`
CEO at Med&Beauty `div#tabpanel-0 > div.CaseStudy_caseStudy__pchW9 > div.CaseStudy_content___o1in > p.CaseStudy_workstation__mRfD9`
Co-owner and Ecommerce Director at DAAG `div#tabpanel-1 > div.CaseStudy_caseStudy__pchW9 > div.CaseStudy_content___o1in > p.CaseStudy_workstation__mRfD9`
Marketing & Digital Manager at Würth Group `div#tabpanel-2 > div.CaseStudy_caseStudy__pchW9 > div.CaseStudy_content___o1in > p.CaseStudy_workstation__mRfD9`
Ecommerce Marketing Manager at Eveline Cosmetics `div#tabpanel-3 > div.CaseStudy_caseStudy__pchW9 > div.CaseStudy_content___o1in > p.CaseStudy_workstation__mRfD9`
See all features `section.ToolsAndFeatures_toolsAndFeatures__cLhSc > div.Container_container__Bfh8E > a.More_more__5cpar > span`
Visit our blog to learn more `div.FooterContainer_container__UAHAO > div.FooterColumns_columns__pM15e > div.FooterRecentPosts_recentPosts__FtAkH > a.FooterRecentPosts_view-all__AAWQq`
Cookie Notice `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a`
Google Data Processing Information `div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a`
Manage preferences `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-pc-btn-handler`
Reject All `div#onetrust-button-group-parent > div#onetrust-button-group > div.banner-actions-container > button#onetrust-reject-all-handler`
Accept `div#onetrust-button-group-parent > div#onetrust-button-group > div.banner-actions-container > button#onetrust-accept-btn-handler`

These are opportunities to improve the legibility of your content.

Best practices

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
Anti-Spam Policy `div.FooterLegal_mfooter-legal__PyJ0l > ul > li > a`
Manage cookies `div.FooterLegal_mfooter-legal__PyJ0l > ul > li > button.FooterManageCookie_action__shn6Q`

These items highlight common accessibility best practices.

○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

●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 are distinguishable without relying on color.

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

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