Skip to content
https://www.jasper.ai

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
favicon.ico Missing
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name 192×192 icon 512×512 icon Start URL Display Mode
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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 (missing!) MAIN CONTENTINFO (missing!)

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
Form Accessibility
2 of 8 controls have issues
REVIEW
2 of 8 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" id="neverbounce-email">
Info::
6 control(s) properly labeled
8 controls
6 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#email-e3dc6094-7a71-45e7-8a09-30e0dad23881emailBusiness Email*for/id
#firstname-e3dc6094-7a71-45e7-8a09-30e0dad23881textFirst Name*for/id
#lastname-e3dc6094-7a71-45e7-8a09-30e0dad23881textLast Name*for/id
#company-e3dc6094-7a71-45e7-8a09-30e0dad23881textCompany Name*for/id
#marketing_team_size-e3dc6094-7a71-45e7-8a09-30e0dad23881selectMarketing Team Size*for/id
#how_can_our_team_help-e3dc6094-7a71-45e7-8a09-30e0dad23881textareaHow can our team help?*for/id
#neverbounce-emailtext(Neverbounce email)placeholder only
inputsubmit(none)none

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

<input type="submit">

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.

<input type="text" id="neverbounce-email">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title 404 – Page Not Found | Jasper Custom Styling Navigation Homepage Link Search Form
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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 Not set CSS indicators Detected

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 24 passed
REVIEW
82

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.

ARIA

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
The State of AI in Marketing 2026 div.g_card_content > div.g_card_text_wrap > div.g_card_heading > div.g_heading
Put AI agents to work for marketing div.hero_main_layout > div.u-display-contents > div.g_content > div.g_heading
World-class marketing teams trust Jasper section.marquee_wrap > div.marquee_contain > div.marquee_headline > div.g_heading
The execution platform for intelligent marketing div.platform_content > div.u-display-contents > div.g_content > div.g_heading
Agents div.platform_list > div.platform_card_wrap > div.g_card_link_heading > div.g_heading
Content Pipelines div.platform_list > div.platform_card_wrap > div.g_card_link_heading > div.g_heading
Jasper IQ div.platform_list > div.platform_card_wrap > div.g_card_link_heading > div.g_heading
Why modern marketing teams choose Jasper div.tabs_contain > div.tabs_layout > div.tabs_header > div.g_heading
Automate every step of the content lifecycle div.tabs_item > div.tabs_item_inner > div.tabs_item_title > div.g_heading
Scale campaigns and performance div.tabs_item > div.tabs_item_inner > div.tabs_item_title > div.g_heading
Keep your brand voice consistent, everywhere div.tabs_item > div.tabs_item_inner > div.tabs_item_title > div.g_heading
Empower every marketer with automation div.tabs_item > div.tabs_item_inner > div.tabs_item_title > div.g_heading
Built for scale, backed by experts div.tabs_item > div.tabs_item_inner > div.tabs_item_title > div.g_heading
Marketing runs on content. Jasper automates how it’s made. section.solutions_wrap > div.solutions_contain > div.solutions_layout > div.g_heading
Proven strategies, real results div.stories_main_layout > div.u-display-contents > div.g_content > div.g_heading
Enterprise-grade security, quality outputs div.trust_layout > div.u-display-contents > div.g_content > div.g_heading
Your AI success starts here div.g_content > div.u-display-contents > div.g_content > div.g_heading
The Jasper Blog div.g_card_content > div.g_card_text_wrap > div.g_card_heading > div.g_heading
Watch Jasper Foundations div.g_card_content > div.g_card_text_wrap > div.g_card_heading > div.g_heading
Customer Stories div.g_card_content > div.g_card_text_wrap > div.g_card_heading > div.g_heading
Get Support div.g_card_content > div.g_card_text_wrap > div.g_card_heading > div.g_heading
Connect with community div.g_card_content > div.g_card_text_wrap > div.g_card_heading > div.g_heading
Search Knowledge Center div.g_card_content > div.g_card_text_wrap > div.g_card_heading > div.g_heading
Put AI agents
to work, on your terms div#w-node-a99eec1c-72a3-43d2-437f-e89b805eddf1-805eddee > div.u-display-contents > div.g_content > div.g_heading

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI assistant body > q-focus-sentinel > div
After AI assistant body > q-focus-sentinel > div
AI assistant, start div#qualified-multimodal-host > div
AI assistant, end div#qualified-multimodal-host > div

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.g_card_visual_img > div.u-flex-horizontal-nowrap > div.w-embed > iframe div.g_card_visual_img > div.u-flex-horizontal-nowrap > div.w-embed > iframe
div.g_card_visual_img > div.u-flex-horizontal-nowrap > div.w-embed > iframe div.g_card_visual_img > div.u-flex-horizontal-nowrap > div.w-embed > iframe
div.g_card_visual_img > div.u-flex-horizontal-nowrap > div.w-embed > iframe div.g_card_visual_img > div.u-flex-horizontal-nowrap > div.w-embed > iframe

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.platform_list > div.platform_card_wrap > div.g_clickable_wrap > a.g_clickable_link div.platform_list > div.platform_card_wrap > div.g_clickable_wrap > a.g_clickable_link
div.platform_list > div.platform_card_wrap > div.g_clickable_wrap > a.g_clickable_link div.platform_list > div.platform_card_wrap > div.g_clickable_wrap > a.g_clickable_link
div.platform_list > div.platform_card_wrap > div.g_clickable_wrap > a.g_clickable_link div.platform_list > div.platform_card_wrap > div.g_clickable_wrap > a.g_clickable_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

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
Logo options div.nav_wrap > div.nav_contain > div.utility-1_component > button.utility-1_trigger
Get A Demo Get A Demo div.g_content > div.u-display-contents > div.u-btn-group > div#ZJwxgq_y62ck8D3Hmpelk

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>`
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
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
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
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
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
`[accesskey]` values are unique
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
`<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.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
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
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.
A+
Heading Hierarchy
24 headings
PASS
24 headings
Info::
Single H1 present
  • H1 Put AI agents to work for marketing
  • H2 World-class marketing teams trust Jasper
  • H2 The execution platform for intelligent marketing
  • H3 Agents
  • H3 Content Pipelines
  • H3 Jasper IQ
  • H2 Why modern marketing teams choose Jasper
  • H3 Automate every step of the content lifecycle
  • H3 Scale campaigns and performance
  • H3 Keep your brand voice consistent, everywhere
  • H3 Empower every marketer with automation
  • H3 Built for scale, backed by experts
  • H2 Solutions for every marketer
  • H3 Marketing runs on content.Jasper automates how it’s made.
  • H2 Proven strategies, real results
  • H2 Enterprise-grade security, quality outputs
  • H2 Your AI success starts here
  • H3 The Jasper Blog
  • H3 Watch Jasper Foundations
  • H3 Customer Stories
  • H3 Get Support
  • H3 Connect with community
  • H3 Search Knowledge Center
  • H2 Put AI agents
to work, on your terms
A
Alt Text Quality
All 94 images OK
PASS
All 94 images OK
Info::
14 image(s) with alt text over 125 characters
Info::
64 decorative image(s) correctly marked
Info::
16 image(s) with good alt text
94 images 16 good alt text 64 decorative
IssueCount
too long14 image(s)
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 Put AI agents to wor…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 World-class marketin…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The execution platfo…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why modern marketing…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Solutions for every …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Proven strategies, r…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Enterprise-grade sec…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your AI success star…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Put AI agents
to w…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Agents21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Content Pipelines21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Jasper IQ21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Automate every step …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Scale campaigns and …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Keep your brand voic…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Empower every market…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Built for scale, bac…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Marketing runs on co…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Jasper automates how…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The Jasper Blog21.00:13.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.

Send Feedback