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

Landmark Structure

Action

4 landmarks

FIX

4 landmarks

No <main> landmark found

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

No <nav> landmark found

No contentinfo (footer) 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

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

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

Form Accessibility

Action

6 of 10 controls have issues

FIX

6 of 10 controls have issues

5 control(s) without accessible label

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

Got: <input type="submit">; <input type="submit">; <input type="submit">; <input type="submit">; <input type="submit">

1 control(s) rely on placeholder only

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

Got: <input type="email" name="email" id="email-input">

4 control(s) properly labeled

10 controls

4 labeled

1 placeholder only

5 unlabeled

Control	Type	Label	Method
#email-b031e00a-4c03-408b-9114-914251a0ee77	email	Email*	for/id
#email-b031e00a-4c03-408b-9114-914251a0ee77	email	Email*	for/id
#email-b031e00a-4c03-408b-9114-914251a0ee77	email	Email*	for/id
#email-b031e00a-4c03-408b-9114-914251a0ee77	email	Email*	for/id
#email-input	email	(Enter your email)	placeholder only
input	submit	(none)	none
input	submit	(none)	none
input	submit	(none)	none
input	submit	(none)	none
input	submit	(none)	none

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

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

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

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

Action

4 issue(s) across 129 links and 9 buttons

REVIEW

4 issue(s) across 129 links and 9 buttons

18 link(s) open in new tab without warning

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

Got: https://help.givebutter.com/en/; https://community.givebutter.com/changelog; https://community.givebutter.com/; https://givebutter.com/login; https://givebutter.com/signup; https://givebutter.com/login; https://givebutter.com/signup?email=; https://www.linkedin.com/company/givebutter/; https://www.tiktok.com/@givebutter; https://x.com/givebutter (+8 more)

4 button(s) with no accessible text

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

Got: button.w-backgroundvideo-backgroundvideoplaypausebutton (#449 on page); button.w-backgroundvideo-backgroundvideoplaypausebutton (#461 on page); button.w-backgroundvideo-backgroundvideoplaypausebutton (#473 on page); button.w-backgroundvideo-backgroundvideoplaypausebutton (#485 on page)

111 link(s) with descriptive text

129 links

0 empty

0 generic text

18 new tab

4 empty buttons

Element	Text	Issue	Suggested Fix
/donor-management-crm	Donor management & CRM	img no alt	Add alt attribute to the image
/nonprofit-marketing	Marketing & engagement	img no alt	Add alt attribute to the image
/fundraising-pages	Fundraising pages	img no alt	Add alt attribute to the image
/donation-forms	Donation forms	img no alt	Add alt attribute to the image
/fundraising-events	Fundraising events	img no alt	Add alt attribute to the image
/auctions	Auctions	img no alt	Add alt attribute to the image
/widgets	Widgets	img no alt	Add alt attribute to the image
/nonprofit-payment-processing	Payment processing	img no alt	Add alt attribute to the image
/mobile-app	Mobile app	img no alt	Add alt attribute to the image
/integrations	Integrations	img no alt	Add alt attribute to the image
/plus	Unlock your full fundraising p…	img no alt	Add alt attribute to the image
/compare	Compare Givebutter	img no alt	Add alt attribute to the image
/reviews	Reviews	img no alt	Add alt attribute to the image
/switch	Switch to Givebutter	img no alt	Add alt attribute to the image
/success-stories	Success stories	img no alt	Add alt attribute to the image
/features/paypal-donations	PayPal	img no alt	Add alt attribute to the image
/integrations/meta	Meta integration	img no alt	Add alt attribute to the image
/features/venmo-donations	Venmo	img no alt	Add alt attribute to the image
/features/daf-donations	DAF donations	img no alt	Add alt attribute to the image
/features/text-to-donate	Text-to-donate	img no alt	Add alt attribute to the image
/plus/quickbooks	QuickBooks Online	img no alt	Add alt attribute to the image
/features/donate-buttons	Donate buttons	img no alt	Add alt attribute to the image
/features/pledges	Pledge donations	img no alt	Add alt attribute to the image
/features/peer-to-peer-fundraising	Peer-to-peer fundraising	img no alt	Add alt attribute to the image
/features/tap-to-pay	Tap to Pay	img no alt	Add alt attribute to the image
/blog	Butter Blog	img no alt	Add alt attribute to the image
/education-hub	Product education	img no alt	Add alt attribute to the image
/freebies	Freebies	img no alt	Add alt attribute to the image
/demo	Watch a demo	img no alt	Add alt attribute to the image
/fundraising-ideas	Fundraising ideas	img no alt	Add alt attribute to the image
https://help.givebutter.com/en/	Help center	new tab	Add '(opens in new tab)' to text
/events	Webinars (CFRE)	img no alt	Add alt attribute to the image
/contact	Contact us	img no alt	Add alt attribute to the image
/experts	Givebutter Experts	img no alt	Add alt attribute to the image
/about	About Givebutter	img no alt	Add alt attribute to the image
https://community.givebutter.com/changel…	Changelog	new tab	Add '(opens in new tab)' to text
https://community.givebutter.com/	Product roadmap	new tab	Add '(opens in new tab)' to text
https://givebutter.com/login	Log in	new tab	Add '(opens in new tab)' to text
https://givebutter.com/signup	Sign up	new tab	Add '(opens in new tab)' to text
https://givebutter.com/login	Log in	new tab	Add '(opens in new tab)' to text
https://givebutter.com/signup?email=	Sign up for free	new tab	Add '(opens in new tab)' to text
#w-tabs-0-data-w-pane-0	Collect more donations	img no alt	Add alt attribute to the image
#w-tabs-0-data-w-pane-1	Grow your  community	img no alt	Add alt attribute to the image
#w-tabs-0-data-w-pane-2	Host your best  event ever	img no alt	Add alt attribute to the image
#w-tabs-0-data-w-pane-3	Get the insights you need	img no alt	Add alt attribute to the image
https://givebutter.com/signup?email=	Sign up for free	img no alt	Add alt attribute to the image
/	Raise more. Pay less. Give bet…	img no alt	Add alt attribute to the image
https://www.linkedin.com/company/givebut…	linkedin icon	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@givebutter	tiktok icon	new tab	Add '(opens in new tab)' to text
https://x.com/givebutter	twitter icon	new tab	Add '(opens in new tab)' to text
https://apps.apple.com/us/app/givebutter…	download app store icon	new tab	Add '(opens in new tab)' to text
https://play.google.com/store/apps/detai…	get it on googleplay icon	new tab	Add '(opens in new tab)' to text
https://www.g2.com/products/givebutter/r…	givebuteter radted first fundr…	new tab	Add '(opens in new tab)' to text
https://www.getapp.com/nonprofit-softwar…	GetApp User reviews badge	new tab	Add '(opens in new tab)' to text
https://www.capterra.com/p/172048/Givebu…	4.9 rating Capterra badge	new tab	Add '(opens in new tab)' to text
https://stripe.partners/directory/givebu…	Stripe verified partner badge�…	new tab	Add '(opens in new tab)' to text
https://www.greatplacetowork.com/certifi…	Great Place To Work badge	new tab	Add '(opens in new tab)' to text
https://share.hsforms.com/1WurR1kdORMuoB…	Do Not Track Request	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

116 links and buttons have descriptive text

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

https://help.givebutter.com/en/; https://community.givebutter.com/changelog; https://community.givebutter.com/; https://givebutter.com/login; https://givebutter.com/signup; https://givebutter.com/login; https://givebutter.com/signup?email=; https://www.linkedin.com/company/givebutter/; https://www.tiktok.com/@givebutter; https://x.com/givebutter (+8 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

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

button.w-backgroundvideo-backgroundvideoplaypausebutton (#449 on page); button.w-backgroundvideo-backgroundvideoplaypausebutton (#461 on page); button.w-backgroundvideo-backgroundvideoplaypausebutton (#473 on page); button.w-backgroundvideo-backgroundvideoplaypausebutton (#485 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

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 Butter 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Heading Hierarchy

9 headings, 1 skip(s)

PASS

9 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H4 P
H4 G
H1 Where changemakers go to grow
H2 Trusted by millions of changemakers at nonprofits like yours
H2 Unlock even more possibilities with
H2 Givebutter leads the pack in user satisfaction
H2 The help you need,here for you 24/7
H2 Raise funds better, faster, and for free with Givebutter
H4 G skipped

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

A+

Alt Text Quality

All 137 images OK

PASS

All 137 images OK

102 decorative image(s) correctly marked

35 image(s) with good alt text

137 images 35 good alt text 102 decorative

All images have appropriate alt text.

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 Where changemakers g…	18.82:1	3.0:1	#000000	#FFF2CC	Pass
h2 Trusted by	18.82:1	3.0:1	#000000	#FFF2CC	Pass
h2 at nonprofits like y…	18.82:1	3.0:1	#000000	#FFF2CC	Pass
h2 Unlock even more pos…	18.82:1	3.0:1	#000000	#FFF2CC	Pass
h2 Givebutter leads the…	18.82:1	3.0:1	#000000	#FFF2CC	Pass
h2 The help you need,	18.82:1	3.0:1	#000000	#FFF2CC	Pass
h2 Raise funds better, …	18.82:1	3.0:1	#000000	#FFF2CC	Pass
title Fundraising Software…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Turn one-time donors…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Platform	18.66:1	4.5:1	#000000	#FEF1CB	Pass
div NEW	18.82:1	4.5:1	#000000	#FFF2CC	Pass
div Givebutter Wallet �…	18.82:1	4.5:1	#000000	#FFF2CC	Pass
p Multiply your impact…	18.82:1	4.5:1	#000000	#FFF2CC	Pass
div Learn more	18.82:1	4.5:1	#000000	#FFF2CC	Pass
div Navbar \| Feature - P…	18.82:1	4.5:1	#000000	#FFF2CC	Pass
div Your home for changi…	18.82:1	4.5:1	#000000	#FFF2CC	Pass
div Watch a demo	18.82:1	4.5:1	#000000	#FFF2CC	Pass
div Donor management & C…	18.82:1	4.5:1	#000000	#FFF2CC	Pass
div Marketing & engageme…	18.82:1	4.5:1	#000000	#FFF2CC	Pass
div Fundraising pages	18.82:1	4.5:1	#000000	#FFF2CC	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.

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 23 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.

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
div.footer-v2_list_wrapper > div#w-node-f114cd59-75c5-6f4c-d738-4477d8998cec-c8904a1f > div.footer-v2_list_social-list > a.footer-v2_list_social-link `div.footer-v2_list_wrapper > div#w-node-f114cd59-75c5-6f4c-d738-4477d8998cec-c8904a1f > div.footer-v2_list_social-list > a.footer-v2_list_social-link`
div.footer-v2_list_wrapper > div#w-node-f114cd59-75c5-6f4c-d738-4477d8998cec-c8904a1f > div.footer-v2_list_social-list > a.footer-v2_list_social-link `div.footer-v2_list_wrapper > div#w-node-f114cd59-75c5-6f4c-d738-4477d8998cec-c8904a1f > div.footer-v2_list_social-list > a.footer-v2_list_social-link`
div.footer-v2_list_wrapper > div#w-node-f114cd59-75c5-6f4c-d738-4477d8998cec-c8904a1f > div.footer-v2_list_social-list > a.footer-v2_list_social-link `div.footer-v2_list_wrapper > div#w-node-f114cd59-75c5-6f4c-d738-4477d8998cec-c8904a1f > div.footer-v2_list_social-list > a.footer-v2_list_social-link`
div.footer-v2_list_wrapper > div#w-node-f114cd59-75c5-6f4c-d738-4477d8998cec-c8904a1f > div.footer-v2_list_social-list > a.footer-v2_list_social-link `div.footer-v2_list_wrapper > div#w-node-f114cd59-75c5-6f4c-d738-4477d8998cec-c8904a1f > div.footer-v2_list_social-list > a.footer-v2_list_social-link`
div.footer-v2_list_wrapper > div#w-node-f114cd59-75c5-6f4c-d738-4477d8998cec-c8904a1f > div.footer-v2_list_social-list > a.footer-v2_list_social-link `div.footer-v2_list_wrapper > div#w-node-f114cd59-75c5-6f4c-d738-4477d8998cec-c8904a1f > div.footer-v2_list_social-list > a.footer-v2_list_social-link`
div.footer-v2_list_wrapper > div#w-node-f114cd59-75c5-6f4c-d738-4477d8998cec-c8904a1f > div.footer-v2_list_social-list > a.footer-v2_list_social-link `div.footer-v2_list_wrapper > div#w-node-f114cd59-75c5-6f4c-d738-4477d8998cec-c8904a1f > div.footer-v2_list_social-list > a.footer-v2_list_social-link`

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.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.w-mod-js `html.w-mod-js`

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

●Image elements have `[alt]` attributes

●Input buttons have discernible text.

●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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

○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

○Buttons have an accessible name

○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

○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 type="image">` elements have `[alt]` text

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○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

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

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