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

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

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 ✗

Link & Button Quality

2 issue(s) across 398 links and 35 buttons

REVIEW

2 issue(s) across 398 links and 35 buttons

2 link(s) with generic text

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

Got: /templates/details/unified-lead-capture ("Learn more"); /templates/details/unified-lead-capture ("Learn more")

8 link(s) open in new tab without warning

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

Got: http://www.facebook.com/ZapierApp?utm_source=zapier.com&utm_medium=referral&utm_campaign=zapier; https://www.linkedin.com/company/zapier/?utm_source=zapier.com&utm_medium=referral&utm_campaign=zapier; https://x.com/zapier?utm_source=zapier.com&utm_medium=referral&utm_campaign=zapier#!; https://www.youtube.com/user/ZapierApp/videos?utm_source=zapier.com&utm_medium=referral&utm_campaign=zapier; /blog/feeds/latest/; https://zapier.com/app/get-help; https://zapier.com/apps; https://zapier.com/l/partners

388 link(s) with descriptive text

398 links

0 empty

2 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/templates/details/unified-lead-capture	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Unified Lead Capture
/templates/details/unified-lead-capture	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Unified Lead Capture
http://www.facebook.com/ZapierApp?utm_so…	Follow us on Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/zapier/…	Follow us on LinkedIn	new tab	Add '(opens in new tab)' to text
https://x.com/zapier?utm_source=zapier.c…	Follow @zapier on X	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/ZapierApp/v…	See helpful Zapier videos on Y…	new tab	Add '(opens in new tab)' to text
/blog/feeds/latest/	Subscribe to our blog	new tab	Add '(opens in new tab)' to text
https://zapier.com/app/get-help	Help	new tab	Add '(opens in new tab)' to text
https://zapier.com/apps	App Integrations	new tab	Add '(opens in new tab)' to text
https://zapier.com/l/partners	Partners Program	new tab	Add '(opens in new tab)' to text

423 links and buttons have descriptive text

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

/templates/details/unified-lead-capture ("Learn more"); /templates/details/unified-lead-capture ("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.

http://www.facebook.com/ZapierApp?utm_source=zapier.com&utm_medium=referral&utm_campaign=zapier; https://www.linkedin.com/company/zapier/?utm_source=zapier.com&utm_medium=referral&utm_campaign=zapier; https://x.com/zapier?utm_source=zapier.com&utm_medium=referral&utm_campaign=zapier#!; https://www.youtube.com/user/ZapierApp/videos?utm_source=zapier.com&utm_medium=referral&utm_campaign=zapier; /blog/feeds/latest/; https://zapier.com/app/get-help; https://zapier.com/apps; https://zapier.com/l/partners

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

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 (Not Found) | Zapier ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

5 icon(s) detected

REVIEW

5 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

Landmark Structure

13 landmarks

PASS

13 landmarks

<main> landmark present

7 <nav> landmark(s) found

1 of 7 <nav> elements are unlabeled

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

Skip navigation link present

Page Structure — as a screen reader sees it

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

Heading Hierarchy

22 headings

PASS

22 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H5 NEW: 95% of AI initiatives stall. Be the 5% who break through. Get an AI consultation →
H1 The automation layer for agentic AI
H2 Your complete toolkit for AI automation
H3 AI Workflows
H2 For the Fortune 500 and first-time founders
H2 No AI hype here. Just results.
H2 EXPLORE ZAPIER’S AI TOOLS
H2 Real teams, real AI workflows, real results
H3 Capture every lead, everywhere
H2 Start quickly with these AI templates
H1 Go from concept to enterprise-ready automation in seconds duplicate H1
H2 AI + automation, all in one place
H2 Move fast.Stay in control.
H2 Want AI automation IT and innovators agree on?
H2 Zapier is secure automation that sticks
H2 Ready to transform how your enterprise uses AI?
H2 Apps by title
H2 Top searches
H2 Popular apps
H2 Trending apps
H2 Top apps by category
H2 Our best content

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

1 of 144 images have issues

PASS

1 of 144 images have issues

1 image(s) with generic alt text

52 decorative image(s) correctly marked

91 image(s) with good alt text

144 images 91 good alt text 52 decorative 1 generic

Issue	Count
generic	1 image(s)

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>

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
textarea	textarea	(Desc)	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+

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 The automation layer…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Go from concept to e…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Your complete toolki…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 For the Fortune 500 …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 No AI hype here. Jus…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 EXPLORE ZAPIER’S A…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Real teams, real AI …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Start quickly with t…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 AI + automation, all…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Want AI automation I…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Zapier is secure aut…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Ready to transform h…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Apps by title	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Top searches	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Popular apps	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Trending apps	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Top apps by category	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our best content	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 AI Workflows	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Capture every lead, …	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.

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 28 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
Sign up `header.Header-module_root_Pe4MYpPz > div.atoms-module_flex_3DCW-0eq > div.atoms-module_flex_3DCW-0eq > a.Button-module_root_RSLKls-N`
Start free with email `div.css-2aluhk > div > div.css-nthnsr > a.css-10oo67n`
Explore AI Workflows `div.css-1gsru6p > div.css-88rmq > div.css-10hfgem > a.css-10oo67n`
See more customer stories `div.css-11f4i8f > div.css-adhjkt > div.css-uwxktl > a.css-10oo67n`
Explore Zapier AI `div > div.css-n8bumm > div.css-1dpz2n0 > a.css-10oo67n`
Read customer story `div > div.css-1urq2yf > div.css-1f0wmsz > a.css-5g5gm0`
Start building `div.zapier-marketing-ui-root-w1jAupkp > form.zapier-marketing-ui-form-1rDQ0Ifa > div.zapier-marketing-ui-submit-ALsFrsal > button.zapier-marketing-ui-button-18BedXz4`
Start automating today `div.css-o5z76k > div.css-1ynwstu > div.css-x5v32v > a.css-26lard`
Get started with secure AI automation `div.css-1nsdth1 > div.css-h1280k > div.css-xi606m > a.css-10oo67n`
Start free with email `div.css-146ru92 > div.css-cvw8pd > div.css-10hue4b > a.css-tbxawv`
Contact Sales `div.css-146ru92 > div.css-cvw8pd > div.css-10hue4b > a.css-tbxawv`

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
H `nav > ul.AlphabetNav-module_list_3RrTHOgs > li > a.AlphabetNav-module_link_oqEGGfHB`
I `nav > ul.AlphabetNav-module_list_3RrTHOgs > li > a.AlphabetNav-module_link_oqEGGfHB`
J `nav > ul.AlphabetNav-module_list_3RrTHOgs > li > a.AlphabetNav-module_link_oqEGGfHB`

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

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

●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"]`

●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

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○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

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.