Skip to content
https://aweber.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #246be8
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
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
Info::
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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Warning::
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
BANNER header NAV MAIN (missing!) CONTENTINFO footer

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

B
Favicon & Branding
11 icon(s) detected
REVIEW
11 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Heading Hierarchy
36 headings, 1 skip(s)
PASS
36 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Connect, automate, and sell your vision to the world
  • H3 AWeber Service Agreement skipped
  • H4 Use of AWeber Services
  • H4 Prohibited Activities
  • H4 Account Billing
  • H4 Termination
  • H4 Intellectual Property
  • H4 Ecommerce
  • H5 Ecommerce Payment Processing
  • H5 Ecommerce Customer Obligations
  • H5 Ecommerce Service Providers
  • H4 Migration Services
  • H4 Free Trial Period
  • H5 Eligibility
  • H5 Usage Limits During Free Trial
  • H4 Liability
  • H3 Want it Done For You?
  • H2 Easy-to-use marketing solutions for quicker success and at a fraction of the cost of other solutions
  • H3 What you can do using AWeber
  • H4 Effortlessly attract more customers
  • H4 More ways to increase revenue
  • H4 Keep your customers engaged and retained
  • H4 Let automations do the heavy lifting
  • H4 Get more eyes on your content
  • H5 There's a plan to support you every step of the way
  • H5 Customer love stories: How AWeber changed their lives!
  • H5 Streamline your workflow - connecting your favorite tools
  • H5 Make the move to AWeber without the stress
  • H6 Free migrations
  • H6 24/7 support for you
  • H3 Get started for free
  • H3 Support center
  • H3 About
  • H3 Developers
  • H3 Press & media
  • H3 Comparisons

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

A+
Alt Text Quality
All 32 images OK
PASS
All 32 images OK
Info::
1 decorative image(s) correctly marked
Info::
31 image(s) with good alt text
32 images 31 good alt text 1 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 5 controls have issues
PASS
1 of 5 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response">
Info::
4 control(s) properly labeled
5 controls
4 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#fnametextFirst Namefor/id
#lnametextLast Namefor/id
#emailtextEmail Addressfor/id
#querytextSearch AWeberaria-label
#g-recaptcha-responsetextarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response">

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

A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
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)
ElementRatioRequiredFGBGResult
h1 your vision to the w…18.26:13.0:1
#000000
#D3F5FE
Pass
h2 Easy-to-use marketin…18.26:13.0:1
#000000
#D3F5FE
Pass
h3 AWeber Service Agree…18.26:13.0:1
#000000
#D3F5FE
Pass
h3 Want it Done For You…18.26:13.0:1
#000000
#D3F5FE
Pass
h3 What you can do usin…18.26:13.0:1
#000000
#D3F5FE
Pass
h3 Get started for free18.26:13.0:1
#000000
#D3F5FE
Pass
title AWeber | Email Marke…9.14:14.5:1
#000000
#ED86E5
Pass
span 87% off ends soon!9.14:14.5:1
#000000
#ED86E5
Pass
s $59913.51:14.5:1
#000000
#DCC7F3
Pass
strong $7918.26:13.0:1
#000000
#D3F5FE
Pass
span to launch your email…18.26:14.5:1
#000000
#D3F5FE
Pass
strong Start for just $7918.26:13.0:1
#000000
#D3F5FE
Pass
a →18.26:14.5:1
#000000
#D3F5FE
Pass
a ✦ Newsletter Assis…18.26:14.5:1
#000000
#D3F5FE
Pass
a Features18.26:14.5:1
#000000
#D3F5FE
Pass
a Pricing18.26:14.5:1
#000000
#D3F5FE
Pass
a Blog18.26:14.5:1
#000000
#D3F5FE
Pass
a Sign in18.26:14.5:1
#000000
#D3F5FE
Pass
a My account18.26:14.5:1
#000000
#D3F5FE
Pass
a Get AWeber Free18.26:14.5:1
#000000
#D3F5FE
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
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 28 passed
PASS
92

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 AWeber Free div.aw-container > div.aw-row > div.nav > a#gtm-order-nav-00
Start for free → div.aw-row > div.aw-col-xs-12 > div.p--xs-small-t > a.btn
LIMITED TIME OFFER div.aw-row > div.aw-col-xs-12 > div.dfy-card > span.dfy-badge
$79 div.aw-col-xs-12 > div.dfy-card > div.dfy-pricing > span.dfy-price
for a limited time (Reg. $599) div.aw-col-xs-12 > div.dfy-card > div.dfy-pricing > span.dfy-price-note
Start for $79 today → div.aw-row > div.aw-col-xs-12 > div.dfy-card > a.btn
$599 div.card > div.card__header > p.h5 > strike.text--negative
Advanced landing page features div.card > div.card__footer > p > strike
Sales tracking and low transaction fees div.card > div.card__footer > p > strike
Remove AWeber branding div.card > div.card__footer > p.m--xs-xsmall-b > strike
Start your free trial → div.aw-row > div.aw-col-xs-12 > div.final-cta-box > a.btn

These are opportunities to improve the legibility of your content.

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
body.body--hero-dark > a.dfy-link body.body--hero-dark > a.dfy-link
body.body--hero-dark > div.aw-sticky-ribbon > a.dfy-link body.body--hero-dark > div.aw-sticky-ribbon > a.dfy-link

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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
●`[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 use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●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.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○`<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.
○`<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
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback