Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 2 REVIEW 9 FIX

Landmark Structure

Action

7 landmarks

FIX

7 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

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

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Heading Hierarchy

Action

20 headings, 3 skip(s)

FIX

20 headings, 3 skip(s)

Multiple H1 headings (5 found)

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

Heading level skipped: H1 → H4 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Candid. .
H2 See the world. Make it better.
H1 What do you need to move forward? duplicate H1
H2 Our websites
H2 Our products and services
H1 Candid gets you the information you need to do good. duplicate H1
H1 Providing you with the nonprofit information you need duplicate H1
H4 Use Candid to look up a nonprofit and access the most complete data available. skipped
H2 Premier destination for nonprofits and nonprofit research
H4 Attract donors with your nonprofit profile skipped
H4 Research valuable nonprofit partners
H4 Access nonprofit API solutions
H4 Find up-to-date information on thousands of nonprofits including:
H2 Stay up to date on the latest facts and insights on nonprofits
H4 Quantity skipped
H4 Quality
H4 Productivity (instead of speed)
H4 Access nonprofit analysis solutions you need. Get started
H2 We power philanthropy
H1 Candid. . duplicate H1

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

Action

5 issue(s) across 56 links and 3 buttons

FIX

5 issue(s) across 56 links and 3 buttons

4 link(s) with no accessible text

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

Got: https://www.facebook.com/CandidDotOrg; https://www.youtube.com/c/CandidDotOrg; https://www.linkedin.com/company/candiddotorg/; https://www.instagram.com/CandidDotOrg/

1 link(s) with generic text

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

Got: https://candid.org/candid-search/look-up-nonprofits ("Learn more")

37 link(s) open in new tab without warning

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

Got: https://candid.org/; https://candid.org/contact-us; https://candid.org; https://learning.candid.org; https://issuelab.org; https://philanthropynewsdigest.org; https://candid.org/candid-search; https://maps.foundationcenter.org; https://candid.org/data/explore-apis; https://candid.org/resources/candid-near-you/community-resources/ (+27 more)

14 link(s) with descriptive text

56 links

4 empty

1 generic text

37 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://candid.org/	Candid. .	new tab	Add '(opens in new tab)' to text
https://candid.org/contact-us	Contact us	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/CandidDotOrg	(empty)	empty	Add link text or aria-label
https://www.youtube.com/c/CandidDotOrg	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/candidd…	(empty)	empty	Add link text or aria-label
https://www.instagram.com/CandidDotOrg/	(empty)	empty	Add link text or aria-label
https://candid.org	Candid	new tab	Add '(opens in new tab)' to text
https://learning.candid.org	Candid Learning	new tab	Add '(opens in new tab)' to text
https://issuelab.org	Issue Lab	new tab	Add '(opens in new tab)' to text
https://philanthropynewsdigest.org	Philanthropy News Digest	new tab	Add '(opens in new tab)' to text
https://candid.org/candid-search	Candid search	new tab	Add '(opens in new tab)' to text
https://maps.foundationcenter.org	Foundation Maps	new tab	Add '(opens in new tab)' to text
https://candid.org/data/explore-apis	APIs	new tab	Add '(opens in new tab)' to text
https://candid.org/resources/candid-near…	Candid community	new tab	Add '(opens in new tab)' to text
https://candid.org/nonprofit-compensatio…	Nonprofit Compensation Report	new tab	Add '(opens in new tab)' to text
https://candid.org/claim-nonprofit-profi…	Nonprofit profiles	new tab	Add '(opens in new tab)' to text
https://learning.candid.org/page/course-…	Nonprofit training	new tab	Add '(opens in new tab)' to text
https://candid.org/resources/candid-near…	Find us in your community	new tab	Add '(opens in new tab)' to text
https://candid.org/claim-nonprofit-profi…	Update now	new tab	Add '(opens in new tab)' to text
https://candid.org/candid-search/look-up…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Look Up Nonprofits
https://candid.org/data/explore-apis	Schedule consultation	new tab	Add '(opens in new tab)' to text
https://candid.org/claim-nonprofit-profi…	Update Profile	new tab	Add '(opens in new tab)' to text
https://candid.org/blogs	Candid insights	new tab	Add '(opens in new tab)' to text
https://candid.org/contact	Contact us	new tab	Add '(opens in new tab)' to text
https://candid.org/privacy-policy	Privacy policy	new tab	Add '(opens in new tab)' to text
https://candid.org/copyright	Legal notice	new tab	Add '(opens in new tab)' to text
https://candid.org/terms	Terms of use	new tab	Add '(opens in new tab)' to text
http://status.guidestar.org/	Site status	new tab	Add '(opens in new tab)' to text
https://candid.org/candid-search	Research nonprofits	new tab	Add '(opens in new tab)' to text
https://candid.org/data	Connect to Candid data	new tab	Add '(opens in new tab)' to text
https://learning.candid.org/page/live-tr…	Webinars	new tab	Add '(opens in new tab)' to text
https://candid.org/about	About Candid	new tab	Add '(opens in new tab)' to text
https://candid.org/press	Press room	new tab	Add '(opens in new tab)' to text
https://candid.org/about/financials	Support Candid	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/CandidDotOrg/	Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@CandidDotOrg	YouTube	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/candidd…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/CandidDotOrg	Instagram	new tab	Add '(opens in new tab)' to text
https://candid.org/	Candid. …	new tab	Add '(opens in new tab)' to text
https://www.guidestar.org/profile/13-183…	EIN 13-1837418	new tab	Add '(opens in new tab)' to text
https://candid.org/terms-of-service	Terms of service	new tab	Add '(opens in new tab)' to text
https://candid.org/privacy-policy	Read more, opens a new window	new tab	Add '(opens in new tab)' to text

17 links and buttons have descriptive text

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

https://www.facebook.com/CandidDotOrg; https://www.youtube.com/c/CandidDotOrg; https://www.linkedin.com/company/candiddotorg/; https://www.instagram.com/CandidDotOrg/

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://candid.org/candid-search/look-up-nonprofits ("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://candid.org/; https://candid.org/contact-us; https://candid.org; https://learning.candid.org; https://issuelab.org; https://philanthropynewsdigest.org; https://candid.org/candid-search; https://maps.foundationcenter.org; https://candid.org/data/explore-apis; https://candid.org/resources/candid-near-you/community-resources/ (+27 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

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

3 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 3 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

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

Alt Text Quality

Action

19 of 23 images have issues

REVIEW

19 of 23 images have issues

18 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image(s) with generic alt text

4 image(s) with good alt text

23 images 4 good alt text 1 generic 18 missing

Issue	Count
missing	18 image(s)
generic	1 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

Lighthouse Accessibility Audits

Score 84/100 — 4 failing, 25 passed

REVIEW

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

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more about valid ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Update now `div.extended-banner > div.row > div.col-md-4 > a#aHomeUpdateNow`
Learn more `div.extended-banner > div.row > div.col-md-4 > a#aHomeLearn`
Schedule consultation `div.extended-banner > div.row > div.col-md-4 > a#aHomeContact`

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-md-6 > div.input-group > div.input-group-append > button#SearchSubmit `div.col-md-6 > div.input-group > div.input-group-append > button#SearchSubmit`

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#mainPageContent > div.row > div.col-sm-5 > img.img-fluid `div#mainPageContent > div.row > div.col-sm-5 > img.img-fluid`
div.input-group-append > button#SearchSubmit > span.search-icon > img `div.input-group-append > button#SearchSubmit > span.search-icon > img`
div.row > div.col-md-4 > div.img-container > img.img-half `div.row > div.col-md-4 > div.img-container > img.img-half`
div.row > div.col-md-4 > div.img-container > img.img-half `div.row > div.col-md-4 > div.img-container > img.img-half`
div.row > div.col-md-4 > div.img-container > img.img-half `div.row > div.col-md-4 > div.img-container > img.img-half`
div.extended-banner > div.row > div#imgRow > img `div.extended-banner > div.row > div#imgRow > img`
div.extended-banner > div.row > div#imgRow > img `div.extended-banner > div.row > div#imgRow > img`
div.extended-banner > div.row > div#imgRow > img `div.extended-banner > div.row > div#imgRow > img`
div.extended-banner > div.row > div#imgRow > img `div.extended-banner > div.row > div#imgRow > img`
div.extended-banner > div.row > div#imgRow > img `div.extended-banner > div.row > div#imgRow > img`
div#mainPageContent > div.row > div.col-md-5 > img.img-fluid `div#mainPageContent > div.row > div.col-md-5 > img.img-fluid`
div.row > div.col-md-4 > div.img-container-small > img.img-half `div.row > div.col-md-4 > div.img-container-small > img.img-half`
div.row > div.col-md-4 > div.img-container-small > img.img-half `div.row > div.col-md-4 > div.img-container-small > img.img-half`
div.row > div.col-md-4 > div.img-container-small > img.img-half `div.row > div.col-md-4 > div.img-container-small > img.img-half`
div.row > div.col-md-3 > div.img-container-small > img.img-half `div.row > div.col-md-3 > div.img-container-small > img.img-half`
div.row > div.col-md-3 > div.img-container-small > img.img-half `div.row > div.col-md-3 > div.img-container-small > img.img-half`
div.row > div.col-md-3 > div.img-container-small > img.img-half `div.row > div.col-md-3 > div.img-container-small > img.img-half`
div.row > div.col-md-3 > div.img-container-small > img.img-half `div.row > div.col-md-3 > div.img-container-small > img.img-half`

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Use Candid to look up a nonprofit and access the most complete data available. `div#mainPageContent > div.row > div.col-sm-7 > h4`
Attract donors with your nonprofit profile `div.extended-banner > div.row > div.col-md-4 > h4`
Quantity `div#mainPageContent > div.row > div.col-md-7 > h4`

These are opportunities to improve keyboard navigation in your application.

○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

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

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

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

●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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

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

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

○Identical links have the same purpose.

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

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: <input type="text" name="txtSearch" id="txtSearch">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#txtSearch	text	(By name, EIN, or keyword)	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 What do you need to …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Candid gets you the …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Providing you with t…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 See the world. Make …	12.59:1	3.0:1	#000000	#FEBE10	Pass
h2 Premier destination …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Stay up to date on t…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 We power philanthrop…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Nonprofit data for d…	12.59:1	4.5:1	#000000	#FEBE10	Pass
a Candid at a glance	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Candid.	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Contact us	16.96:1	4.5:1	#000000	#FFE59F	Pass
a Our websites	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Candid	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Candid Learning	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Issue Lab	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Philanthropy News Di…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Our products and ser…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Candid search	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Foundation Maps	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a APIs	21.00:1	4.5: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.