Accessibility

D

Tabindex Anti-Patterns

Action

0 positive, 31 -1-on-focusable

FIX

0 positive, 31 -1-on-focusable

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

tabindex="-1" on naturally-focusable <button>

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

F

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://www.clay.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://www.clay.com/manifest.json

Manifest contains invalid JSON.

D

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 ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

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)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

No banner (header) landmark

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

C

Alt Text Quality

Action

69 of 336 images have issues

REVIEW

69 of 336 images have issues

69 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

97 decorative image(s) correctly marked

170 image(s) with good alt text

336 images 170 good alt text 97 decorative 69 missing

Issue	Count
missing	69 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

C

Mobile-Readable Font Sizes

Action

86% of visible text renders at >= 12 CSS px (61 below threshold)

REVIEW

86% of visible text renders at >= 12 CSS px (61 below threshold)

61 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <p> 10.0px ("Data infrastructure"); <p> 10.0px ("Agents"); <p> 10.0px ("Orchestration"); <p> 10.0px ("Execution"); <p> 10.0px ("Data foundations").

C

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

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗

C

Favicon & Branding

Action

6 icon(s) detected

REVIEW

6 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

B

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B

Lighthouse Accessibility Audits

Score 89/100 — 3 failing, 27 passed

REVIEW

89

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

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

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

Source: MDN Permissions-Policy

Failing Elements
“Clay has one of the most practical and exciting applications of AI, in a decad… `div.home-logo_content > div.home-logo_wrap > div > div.home-logo_base`
“Clay has one of the most practical and exciting applications of AI, in a decad… `div.home-logo_content > div.home-logo_wrap > div > div.home-logo_base`

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
Find people data `div.home-action_button-list > div.home-action_button-group > button.tab-btn > div.text-size-small`
Find company data `div.home-action_button-list > div.home-action_button-group > button.tab-btn > div.text-size-small`
Find jobs data `div.home-action_button-list > div.home-action_button-group > button.tab-btn > div.text-size-small`
ORCHESTRATION `div.u-stack-sm > div.home-feature_tag > div.home-feature_pill > div.eyebrow-text`
Start free trial `div.home-feature_btm > div.button-group > a.btn > div`
GTM INFRASTRUCTURE `div.container-regular > div.home-reps_content > div.home-reps_top > div#w-node-a7954d33-4c31-62e9-b2a5-a761c059e9b4-08f6d1bf`
CONFERENCE `a#w-node-ebc8eafc-8c30-e8de-a6b4-f225c27b9a65-08f6d1bf > div.update_intro > div.div-block-13 > div.eyebrow`
COMMUNITY STORY `a#w-node-_7234a7ff-6621-57ca-4845-c3c776e5d8c0-08f6d1bf > div.update_intro > div.div-block-13 > div.eyebrow`

These are opportunities to improve the legibility of your content.

Names and labels

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.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`
div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img `div.home-logo_base > div.logo-card > div.home-logo_height > img.home-logo_img`

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

●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

●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

●Links are distinguishable without relying on color.

●Links have a discernible name

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Image elements do not have `[alt]` attributes that are redundant text.

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

○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

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○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

26 headings

PASS

26 headings

Single H1 present

H1 Build systems to grow revenue
H2 GTM engineers build on Clay
H3 What do you want to build?
H3 Build, test, and scale any GTM play you can imagine.
H3 Get data from the most complete data marketplace
H3 Put agents that know your business to work
H3 Orchestrate workflows across tools in real time
H3 Launch new plays as fast as you have ideas
H3 Build systems that make reps more productive
H3 Hear from the teams that grow with Clay
H3 Learn more about GTM engineering
H3 Sculpt: The go-to-market conference returns in 2026
H3 Get started with Clay
H3 How Clay Uses Clay: ABM campaigns to break into Tier 1 accounts
H3 Sandra has built the Clay community in Lagos
H3 Where girls often choose between career or marriage, she carved her own path
H2 Turn your growth ideas into reality today
H3 Use cases
H3 Customers
H3 Product
H3 Blog
H3 Resources
H3 Company
H3 Legal
H3 Customers
H3 Legal

A+

Heading Text Quality

All 26 heading(s) have substantive, well-formed text

PASS

All 26 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <textarea name="prompt" id="sculptor-prompt">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#sculptor-prompt	textarea	(Find companies )	placeholder only

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

A

Link & Button Quality

267 links, 75 buttons — all OK

PASS

267 links, 75 buttons — all OK

27 link(s) open in new tab without warning

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

Got: https://www.sculpt.clay.com; https://university.clay.com/; https://university.clay.com/cohorts; https://community.clay.com/; https://luma.com/claylive?k=c; https://www.linkedin.com/company/grow-with-clay/; https://www.youtube.com/@GrowWithClay; https://www.nytimes.com/2026/01/28/business/dealbook/clay-start-up-tender-off…; https://university.clay.com/; https://university.clay.com/cohorts (+17 more)

240 link(s) with descriptive text

267 links

0 empty

0 generic text

27 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.sculpt.clay.com	The most creative minds in GTM…	new tab	Add '(opens in new tab)' to text
/mcp	Clay MCPGive reps the best pro…	img no alt	Add alt attribute to the image
/customers/intercom	Intercom Grew their outbound-s…	img no alt	Add alt attribute to the image
https://university.clay.com/	UniversityLink long form descr…	new tab	Add '(opens in new tab)' to text
https://university.clay.com/cohorts	Cohort live classesLink long f…	new tab	Add '(opens in new tab)' to text
https://community.clay.com/	Clay communityLink long form d…	new tab	Add '(opens in new tab)' to text
https://luma.com/claylive?k=c	Live eventsLink long form desc…	new tab	Add '(opens in new tab)' to text
https://www.clay.com/blog/sandra-uche	Clay CommunityIn Nigeria, she …	img no alt	Add alt attribute to the image
https://www.linkedin.com/company/grow-wi…	LinkedInLink long form descrip…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@GrowWithClay	YouTubeLink long form descript…	new tab	Add '(opens in new tab)' to text
https://www.nytimes.com/2026/01/28/busin…	Article – NY TimesClay allow…	new tab	Add '(opens in new tab)' to text
/mcp	Clay MCPGive reps the best pro…	img no alt	Add alt attribute to the image
https://www.clay.com/use-cases/crm-enric…	CRM enrichmentKeep your CRM cl…	img no alt	Add alt attribute to the image
/customers/intercom	Intercom Grew their outbound-s…	img no alt	Add alt attribute to the image
https://university.clay.com/	UniversityLink long form descr…	new tab	Add '(opens in new tab)' to text
https://university.clay.com/cohorts	Cohort live classesLink long f…	new tab	Add '(opens in new tab)' to text
https://community.clay.com/	Clay communityLink long form d…	new tab	Add '(opens in new tab)' to text
https://luma.com/claylive?k=c	Live eventsLink long form desc…	new tab	Add '(opens in new tab)' to text
https://www.clay.com/blog/sandra-uche	Clay CommunityIn Nigeria, she …	img no alt	Add alt attribute to the image
https://www.linkedin.com/company/grow-wi…	LinkedInLink long form descrip…	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@GrowWithClay	YouTubeLink long form descript…	new tab	Add '(opens in new tab)' to text
https://www.nytimes.com/2026/01/28/busin…	Article – NY TimesClay allow…	new tab	Add '(opens in new tab)' to text
https://www.glassdoor.com/Overview/Worki…	love	new tab	Add '(opens in new tab)' to text
https://university.clay.com/	Learn more about building play…	new tab	Add '(opens in new tab)' to text
https://sculpt.clay.com/	ConferenceSculpt: The go-to-ma…	new tab	Add '(opens in new tab)' to text
https://university.clay.com/	Get started with ClayFind the …	new tab	Add '(opens in new tab)' to text
/livestreams/how-clay-uses-clay-abm-dire…	LivestreamHow Clay Uses Clay: …	img no alt	Add alt attribute to the image
https://app.clay.com/signup?source=websi…	Start free trial	new tab	Add '(opens in new tab)' to text
https://community.clay.com/	Community	new tab	Add '(opens in new tab)' to text
https://status.clay.com/	Status	new tab	Add '(opens in new tab)' to text
https://docs.google.com/forms/d/e/1FAIpQ…	Do not sell my data	new tab	Add '(opens in new tab)' to text
https://www.hudsonchristie.com/	Hudson	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/grow-wi…	Visit Clay on LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@GrowWithClay	Visit Clay on YouTube	new tab	Add '(opens in new tab)' to text
https://www.clay.com/slack-community	Visit Clay on Slack	new tab	Add '(opens in new tab)' to text

315 links and buttons have descriptive text

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

https://www.sculpt.clay.com; https://university.clay.com/; https://university.clay.com/cohorts; https://community.clay.com/; https://luma.com/claylive?k=c; https://www.linkedin.com/company/grow-with-clay/; https://www.youtube.com/@GrowWithClay; https://www.nytimes.com/2026/01/28/business/dealbook/clay-start-up-tender-off…; https://university.clay.com/; https://university.clay.com/cohorts (+17 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

A+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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 Build systems to gro…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 GTM engineers build …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Turn your growth ide…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 What do you want to …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Build, test, and sca…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Get data from the mo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Put agents that	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Orchestrate workflow…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Launch new plays as …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Build systems that m…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Hear from the teams …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Learn more about GTM…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sculpt: The go-to-ma…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Get started with Cla…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 How Clay Uses Clay: …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Sandra has built the…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Where girls often ch…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Use cases	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Customers	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Product	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.