Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 4 REVIEW 5 FIX

Link & Button Quality

Action

11 issue(s) across 195 links and 192 buttons

FIX

11 issue(s) across 195 links and 192 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://ecom.docusign.com/plans-and-pricing/esignature?promocode=SECURE30

2 link(s) with generic text

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

Got: https://www.docusign.com/why-docusign ("Learn More"); /blog/fast-company-worlds-most-innovative-companies-2026 ("Learn More")

3 link(s) open in new tab without warning

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

Got: https://play.google.com/store/apps/details?id=com.docusign.ink&referrer=utm_s…; https://apps.apple.com/us/app/docusign-upload-sign-docs/id474990205; https://www.onetrust.com/products/cookie-consent/

8 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.css-mandbn (#1926 on page); button.css-mandbn (#1929 on page); button.css-mandbn (#1932 on page); button.css-mandbn (#1935 on page); button (#5061 on page); button (#5071 on page); button (#5085 on page); button (#5099 on page)

189 link(s) with descriptive text

195 links

1 empty

2 generic text

3 new tab

8 empty buttons

Element	Text	Issue	Suggested Fix
https://www.docusign.com/why-docusign	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Why Docusign
https://ecom.docusign.com/plans-and-pric…	(empty)	empty	Add link text or aria-label
/blog/fast-company-worlds-most-innovativ…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Fast Company Worlds Most Innovative Companies 2026
https://play.google.com/store/apps/detai…	Download the Docusign Mobile A…	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/us/app/docusign-u…	Download the Docusign Mobile A…	new tab	Add '(opens in new tab)' to text
https://www.onetrust.com/products/cookie…	Powered by OneTrust Opens in a…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

373 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://ecom.docusign.com/plans-and-pricing/esignature?promocode=SECURE30

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://www.docusign.com/why-docusign ("Learn More"); /blog/fast-company-worlds-most-innovative-companies-2026 ("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.

https://play.google.com/store/apps/details?id=com.docusign.ink&referrer=utm_s…; https://apps.apple.com/us/app/docusign-upload-sign-docs/id474990205; https://www.onetrust.com/products/cookie-consent/

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.css-mandbn (#1926 on page); button.css-mandbn (#1929 on page); button.css-mandbn (#1932 on page); button.css-mandbn (#1935 on page); button (#5061 on page); button (#5071 on page); button (#5085 on page); button (#5099 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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

Theme color only

FIX

Theme color only

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: #ffffff

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

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 ✗

Form Accessibility

Action

81 of 92 controls have issues

REVIEW

81 of 92 controls have issues

81 control(s) without accessible label

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

Got: <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select> (+71 more)

11 control(s) properly labeled

92 controls

11 labeled

0 placeholder only

81 unlabeled

Control	Type	Label	Method
#marketingConsent	checkbox		none
#workEmail	text	name@company.com	for/id
#countryCode-options	select	Country/region: France	none
#ot-group-id-C0003	checkbox	Functional Cookies	for/id
#ot-group-id-C0002	checkbox	Performance Cookies	for/id
#ot-group-id-C0004	checkbox	Targeting Cookies	for/id
#vendor-search-handler	text	Cookie list search	aria-label
#chkbox-id	checkbox	checkbox label	for/id
#select-all-hosts-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-groups-handler	checkbox	checkbox label	for/id
#select-all-vendor-leg-handler	checkbox	checkbox label	for/id
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none
select	select	(none)	none

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

<select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select>; <select> (+71 more)

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

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title The requested page could not be found (404) | Docusign ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

18 icon(s) detected

REVIEW

18 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

0 pass 20 fail WCAG AA

h1 Everything you need to agree

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Most Innovative Companies of 2026

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 AI-powered agreement management

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Do (much) more with IAM

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Build custom agreement workflows

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Trusted the world over

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Companies do better with Docusign

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Recommended for you

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Bringing agreements to life, together

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The smartest way to navigate agreements

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How We Evaluate LLM Accuracy for Contrac…

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The Duck Talks Back: How I’m Using AI …

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Can You Notarize for Family? Measuring t…

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 How We Evaluate LLM Accuracy for Contrac…

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The Duck Talks Back: How I’m Using AI …

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Can You Notarize for Family? Measuring t…

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Docusign IAM is the agreement platform y…

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Join Michael Lewis at Momentum26

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Privacy Preference Center

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Search, manage, and analyze agreements w…

1.54:1

#000000

#31048E

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Everything you need …	1.54:1	3.0:1	#000000	#31048E	Fail
h2 Most Innovative Comp…	1.54:1	3.0:1	#000000	#31048E	Fail
h2 AI-powered agreement…	1.54:1	3.0:1	#000000	#31048E	Fail
h2 Do (much) more with …	1.54:1	3.0:1	#000000	#31048E	Fail
h2 Build custom agreeme…	1.54:1	3.0:1	#000000	#31048E	Fail
h2 Trusted the world ov…	1.54:1	3.0:1	#000000	#31048E	Fail
h2 Companies do better …	1.54:1	3.0:1	#000000	#31048E	Fail
h2 Recommended for you	1.54:1	3.0:1	#000000	#31048E	Fail
h2 Bringing agreements …	1.54:1	3.0:1	#000000	#31048E	Fail
h2 The smartest way to …	1.54:1	3.0:1	#000000	#31048E	Fail
h2 How We Evaluate LLM …	1.54:1	3.0:1	#000000	#31048E	Fail
h2 The Duck Talks Back:…	1.54:1	3.0:1	#000000	#31048E	Fail
h2 Can You Notarize for…	1.54:1	3.0:1	#000000	#31048E	Fail
h2 How We Evaluate LLM …	1.54:1	3.0:1	#000000	#31048E	Fail
h2 The Duck Talks Back:…	1.54:1	3.0:1	#000000	#31048E	Fail
h2 Can You Notarize for…	1.54:1	3.0:1	#000000	#31048E	Fail
h2 Docusign IAM is the …	1.54:1	3.0:1	#000000	#31048E	Fail
h2 Join Michael Lewis a…	1.54:1	3.0:1	#000000	#31048E	Fail
h2 Privacy Preference C…	1.54:1	3.0:1	#000000	#31048E	Fail
h3 Search, manage, and …	1.54:1	3.0:1	#000000	#31048E	Fail

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+

Landmark Structure

15 landmarks

PASS

15 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

No banner (header) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

31 headings

PASS

31 headings

Single H1 present

H1 Everything you need to agree
H2 Most Innovative Companies of 2026
H2 AI-powered agreement management
H3 Search, manage, and analyze agreements with AI
H3 Send, sign, and track documents
H3 Automate agreement processes
H3 Build and scale with developer tools and APIs
H3 Bring people, agreements, and information together
H3 Optimize your contract lifecycle
H2 Do (much) more with IAM
H2 Build custom agreement workflows
H2 Trusted the world over
H2 Companies do better with Docusign
H2 Recommended for you
H2 Bringing agreements to life, together
H2 The smartest way to navigate agreements
H2 How We Evaluate LLM Accuracy for Contract Review
H2 The Duck Talks Back: How I’m Using AI to Navigate AI Code Review
H2 Can You Notarize for Family? Measuring the Risks and Implications
H2 How We Evaluate LLM Accuracy for Contract Review
H2 The Duck Talks Back: How I’m Using AI to Navigate AI Code Review
H2 Can You Notarize for Family? Measuring the Risks and Implications
H2 Docusign IAM is the agreement platform your business needs
H2 Join Michael Lewis at Momentum26
H2 Privacy Preference Center
H3 Manage Consent Preferences
H4 Strictly Necessary Cookies
H4 Functional Cookies
H4 Performance Cookies
H4 Targeting Cookies
H3 Cookie List

A+

Alt Text Quality

All 71 images OK

PASS

All 71 images OK

1 image(s) with alt text over 125 characters

20 decorative image(s) correctly marked

50 image(s) with good alt text

71 images 50 good alt text 20 decorative

Issue	Count
too long	1 image(s)

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 30 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.

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
United States Canada - English Canada - français France Australia 日本 Brasil Ned… `div.css-1auxedf > div.css-gqnsnt > div.css-5x7bn > div#menu-:Rpla9n6:`

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

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
main#main-content > div.css-9ubqd > div.css-6hzlwo > a.css-ymzsdo `main#main-content > div.css-9ubqd > div.css-6hzlwo > a.css-ymzsdo`

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
02:19 `div.css-1lcy5eq > div.css-9wpbst > div.css-1bx5ylf > button.css-1gy05p1`
01:45 `div.css-1lcy5eq > div.css-9wpbst > div.css-1bx5ylf > button.css-1gy05p1`
United States `div.css-gqnsnt > div.css-5x7bn > div.css-5x7bn > button#toggle-:Rpla9n6:`

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

●Select elements have associated label elements.

●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

●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

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

●`[lang]` attributes have a valid value

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

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

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

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