Skip to content
https://copy.ai

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 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
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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.

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::
9 navigation landmark(s) detected
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 9 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
15 landmarks
REVIEW
15 landmarks
Info::
<main> landmark present
Info::
9 <nav> landmark(s) found
Warning::
1 of 9 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) 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!) NAV MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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 2 controls have issues
REVIEW
2 of 2 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" id="submit">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="email" name="Email" id="Email">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#Emailemail(What's your email?)placeholder only
#submitsubmit(none)none

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

<input type="submit" id="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="email" name="Email" id="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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Not Found | Copy.ai Custom Styling Navigation Homepage Link Search Form
B
Lighthouse Accessibility Audits
Score 87/100 — 3 failing, 21 passed
REVIEW
87

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 parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
“Thanks to Copy.ai, we’re generating 5x more meetings with our personalized, AI… div.cs_container > div.slider-main_component > div.swiper > div#swiper-wrapper-cd1efeb44cb70397
AI Copilots & The Illusion of Progress Are you wondering why you're seeing such… div.slider-main_component > div.slider-main_inner-wrapper > div.swiper > div#swiper-wrapper-fec14eca45d9319a

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.

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
OVERVIEW div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
WORKFLOWS div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
INTELLIGENCE LAYER div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
SALES div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
MARKETING div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
OPERATIONS div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
BY TEAM div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
LEARN MORE div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
GET HELP div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
OVERVIEW div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
WORKFLOWS div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
INTELLIGENCE LAYER div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
SALES div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
MARKETING div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
OPERATIONS div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
BY TEAM div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
LEARN MORE div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer
GET HELP div.footer--layout > div.footer_column > div.footer_links-group > div.upheading--footer

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
nav.mega--nav > div.mega--nav_padding > div.mega--nav-container > a.navbar_brand nav.mega--nav > div.mega--nav_padding > div.mega--nav-container > a.navbar_brand
div.mega--nav_padding > div.mega--nav-container > div.mega--nav_burger_button > a.mega--nav_burger_trigger div.mega--nav_padding > div.mega--nav-container > div.mega--nav_burger_button > a.mega--nav_burger_trigger

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.

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
Image elements have `[alt]` attributes
Input buttons have discernible text.
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
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
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.
`[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
`[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
Buttons have an accessible name
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 type="image">` elements have `[alt]` text
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
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.
Elements with visible text labels have matching accessible names.
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
28 headings
PASS
28 headings
Info::
Single H1 present
  • H1 GTM Platform
  • H2 Design Your GTM AI Playbook
  • H3 Prospecting Cockpit
  • H3 Content Creation
  • H3 Inbound Lead Processing
  • H3 Account Based Marketing
  • H3 Translation + Localization
  • H3 Deal Coaching + Forecasting
  • H2 “Thanks to Copy.ai, we’re generating 5x more meetings with our personalized, AI-powered GTM strategy.”
  • H2 "Copy.ai has been phenomenal in transforming the way we develop marketing content. By automating workflows that would typically take weeks and cost thousands of dollars through agencies, they've saved
  • H2 “I didn't even know AI workflows were something that I was lacking until someone said, “Did you know you could do all of this with Copy.ai?”
  • H2 The anti-point solution platform
  • H3 GTM AI Platform
  • H3 Workflows
  • H4 Actions
  • H4 Agents
  • H4 Tables
  • H4 Chat
  • H4 Infobase
  • H4 Brand Voice
  • H3 2,000+ Integrations
  • H3 LLM Model Agnostic
  • H2 Drive your GTM AI strategy
  • H3 AI Copilots & The Illusion of Progress
  • H3 Invest in Purpose-Built Solution, or DIY?
  • H3 GTM AI: A New Approach for Getting Rid of GTM Bloat
  • H3 How to Go from GTM Bloat to Velocity
  • H2 See the Copy.ai platform in action
A+
Alt Text Quality
All 61 images OK
PASS
All 61 images OK
Info::
19 decorative image(s) correctly marked
Info::
42 image(s) with good alt text
61 images 42 good alt text 19 decorative
All images have appropriate alt text.
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 GTM21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Platform21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Design Your GTM AI…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 “Thanks to Copy.ai…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 "Copy.ai has been ph…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 “I didn't even kno…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 The anti-point solut…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Drive your GTM AI s…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 See the Copy.ai plat…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Prospecting Cockpit21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Content Creation21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Inbound Lead Process…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Account Based Market…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Translation + Locali…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Deal Coaching + Fore…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 GTM AI Platform21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Workflows21.00:13.0:1
#000000
#FFFFFF
Pass
h3 2,000+ Integrations21.00:13.0:1
#000000
#FFFFFF
Pass
h3 LLM Model Agnostic21.00:13.0:1
#000000
#FFFFFF
Pass
h3 AI Copilots & The Il…21.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