Skip to content
https://donorbox.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: App
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name App ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗
Name App Icons 6 icon(s)
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark 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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
7 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 7 <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
10 landmarks
REVIEW
10 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
1 of 7 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN CONTENTINFO footer

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

Why this matters

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

Learn more ▾

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

Source: WAI-ARIA Authoring Practices

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

B
Alt Text Quality
2 of 93 images have issues
REVIEW
2 of 93 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
91 image(s) with good alt text
93 images 91 good alt text 2 missing
IssueCount
missing2 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
Form Accessibility
Action
3 of 18 controls have issues
REVIEW
3 of 18 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="radio" name="cookie-category-tabs" id="cookie-decleration-checkbox">; <input type="radio" name="cookie-category-tabs" id="about-cookies-checkbox">; <input type="radio" name="cookie-category-tabs" id="cookie-selection-checkbox">
Info::
15 control(s) properly labeled
18 controls
15 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
#menu_togglecheckboxToggle menuaria-label
#information_togglecheckboxInformationfor/id
#use_cases_togglecheckboxUse Casesfor/id
#integrations_togglecheckboxIntegrationsfor/id
#languageselectSelect languagearia-label
#show-cookie-declerationcheckboxLess optionsfor/id
#show-more-checkboxcheckboxShow lessfor/id
necessarycheckboxnone
preferencescheckboxnone
statisticscheckboxnone
marketingcheckboxnone
#cookie-category-necessaryradioNecessaryfor/id
#cookie-category-preferencesradioPreferencesfor/id
#cookie-category-statisticsradioStatisticsfor/id
#cookie-category-marketingradioMarketingfor/id
#about-cookies-checkboxradio(none)none
#cookie-selection-checkboxradio(none)none
#cookie-decleration-checkboxradio(none)none

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

<input type="radio" name="cookie-category-tabs" id="cookie-decleration-checkbox">; <input type="radio" name="cookie-category-tabs" id="about-cookies-checkbox">; <input type="radio" name="cookie-category-tabs" id="cookie-selection-checkbox">

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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Free Donate Button - Donorbox Nonprofit Fundraising Software ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
20 icon(s) detected
REVIEW
20 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
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 Raise more donations. Retain more donors…
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Powerful features made
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 easy to use
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 100,000+ nonprofits worldwide have raise…
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Security that never sleeps, so you can r…
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Rated
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 and
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 on G2
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 99.99% Uptime. 110% Here For You.
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trusted by world-changers big and small
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Boost Donations Everywhere: Combine Onli…
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Here's what it’s like to use Donorbox
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Click on your industry
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The fundraising engine of choice for suc…
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Like most websites, we use cookies!
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Donation Form
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 CRM
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Donorbox Live™ Kiosk
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Events
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Jay·AI
1.85:1
#000000
on
#1B357C
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Raise more donations…1.85:13.0:1
#000000
#1B357C
Fail
h2 Powerful features ma…1.85:13.0:1
#000000
#1B357C
Fail
h2 easy to use1.85:13.0:1
#000000
#1B357C
Fail
h2 100,000+ nonprofits …1.85:13.0:1
#000000
#1B357C
Fail
h2 Security that never …1.85:13.0:1
#000000
#1B357C
Fail
h2 Rated1.85:13.0:1
#000000
#1B357C
Fail
h2 and1.85:13.0:1
#000000
#1B357C
Fail
h2 on G21.85:13.0:1
#000000
#1B357C
Fail
h2 99.99% Uptime. 110% …1.85:13.0:1
#000000
#1B357C
Fail
h2 Trusted by world-cha…1.85:13.0:1
#000000
#1B357C
Fail
h2 Boost Donations Ever…1.85:13.0:1
#000000
#1B357C
Fail
h2 Here's what it’s l…1.85:13.0:1
#000000
#1B357C
Fail
h2 Click on your indust…1.85:13.0:1
#000000
#1B357C
Fail
h2 The fundraising engi…1.85:13.0:1
#000000
#1B357C
Fail
h2 Like most websites, …1.85:13.0:1
#000000
#1B357C
Fail
h3 Donation Form1.85:13.0:1
#000000
#1B357C
Fail
h3 CRM1.85:13.0:1
#000000
#1B357C
Fail
h3 Donorbox Live™ Kio…1.85:13.0:1
#000000
#1B357C
Fail
h3 Events1.85:13.0:1
#000000
#1B357C
Fail
h3 Jay·AI1.85:13.0:1
#000000
#1B357C
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+
Heading Hierarchy
46 headings
PASS
46 headings
Info::
Single H1 present
  • H1 Raise more donations. Retain more donors. All in one place.
  • H2 Powerful features made refreshingly easy to use
  • H3 Donation Form
  • H3 CRM
  • H3 Donorbox Live™ Kiosk
  • H3 Events
  • H3 Jay·AI
  • H3 Donation Pages
  • H3 Donor Portal with QuickDonate™
  • H3 Membership
  • H3 Crowdfunding
  • H3 Peer-to-Peer (P2P)
  • H3 Donate Button
  • H3 Text-to-Give
  • H2 100,000+ nonprofits worldwide have raised $3B with Donorbox
  • H2 Security that never sleeps, so you can rest easy.
  • H3 You shouldn’t have to worry about scammers stealing your donors' personally identifiable information and credit card data.
  • H2 Rated #1 Fundraising and Donor Management on G2
  • H2 99.99% Uptime. 110% Here For You.
  • H2 Trusted by world-changers big and small
  • H2 Boost Donations Everywhere: Combine Online and On-Site Fundraising with Donorbox Live Kiosk
  • H2 Here's what it’s like to use Donorbox
  • H3 Starting out
  • H3 Create your campaign
  • H3 Launch your campaign
  • H3 Receive your donations
  • H3 Stepping it up
  • H3 Integrate your apps
  • H3 Connect with your donors
  • H3 Expand your toolkit
  • H3 Supercharging your fundraising
  • H3 Premium Software
  • H3 Account Ambassador
  • H3 Fundraising Coach
  • H3 Priority Tech Support
  • H2 Click on your industry
  • H3 Churches
  • H3 Universities
  • H3 Animals
  • H3 Nonprofits
  • H3 Journalism
  • H3 Arts
  • H3 Political
  • H3 Medical
  • H2 The fundraising engine of choice for successful nonprofits.
  • H2 Like most websites, we use cookies!
A+
Lighthouse Accessibility Audits
Score 97/100 — 1 failing, 30 passed
PASS
97

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
refreshingly main > section#powerful_features > h2.en > span
Amplify Your Impact body#application_homepage > main > section#powerful_features > a.button
View case study ➔ section#trusted_by_world > article#mayas_hope_case_study > div > a.button
View case study ➔ section#trusted_by_world > article#upward_scholars_case_study > div > a.button
Stage 1 main > section#like_to_use_donorbox > div#starting_out > span.stage_text
(takes 12 minutes) div#starting_out > section > div.en > i
(takes 3 minutes) div#starting_out > section > div.en > i
(takes 10 minutes) div#starting_out > section > div.en > i
Get Started ➔ main > section#like_to_use_donorbox > div#starting_out > a.button
Stage 2 main > section#stepping_it_up_to_next_level > div > span.stage_text
Step it up ➔ main > section#stepping_it_up_to_next_level > div > a.button
Stage 3 main > section#charge_your_fundraising > div > span.stage_text
Unlock Premium Features main > section#charge_your_fundraising > div > a.button
Use only necessary cookies div#top-right > div.actions-and-tabs > div.actions > button#allow-necessary

These are opportunities to improve the legibility of your content.

○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]` 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
●`[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
●Elements use only permitted ARIA attributes
●`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
●Definition list items are wrapped in `<dl>` elements
●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
●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
●ARIA IDs are unique
●`<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-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback