Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 3 REVIEW 3 FIX

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

3 issue(s) across 117 links and 18 buttons

REVIEW

3 issue(s) across 117 links and 18 buttons

2 link(s) with generic text

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

Got: /c/how-it-works ("Learn more"); /c/how-it-works ("Learn more")

1 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/c/opt-out-rights"]

8 link(s) open in new tab without warning

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

Got: /c/start; /c/crowdfunding; /c/start/funeral-fundraising; /c/start/medical-fundraising; /c/start/charity-fundraising; /c/questions; /c/how-it-works; https://www.gofundme.com/c/safety/gofundme-guarantee

1 button(s) with no accessible text

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

Got: button.hrt-disp-none (#983 on page)

106 link(s) with descriptive text

117 links

0 empty

2 generic text

8 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/c/start	starting your fundraiser	new tab	Add '(opens in new tab)' to text
/c/crowdfunding	crowdfunding	new tab	Add '(opens in new tab)' to text
/c/start/funeral-fundraising	memorial	new tab	Add '(opens in new tab)' to text
/c/start/medical-fundraising	medical	new tab	Add '(opens in new tab)' to text
/c/start/charity-fundraising	nonprofits	new tab	Add '(opens in new tab)' to text
/c/questions	questions	new tab	Add '(opens in new tab)' to text
/c/how-it-works	how GoFundMe works	new tab	Add '(opens in new tab)' to text
/c/how-it-works	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: How It Works
/c/how-it-works	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: How It Works
https://www.gofundme.com/c/safety/gofund…	GoFundMe Giving Guarantee	new tab	Add '(opens in new tab)' to text
/c/opt-out-rights	Your Privacy Choices	img no alt	Add alt attribute to the image
<button>	(empty)	empty	Add button text or aria-label

123 links and buttons have descriptive text

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

/c/how-it-works ("Learn more"); /c/how-it-works ("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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/c/opt-out-rights"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

/c/start; /c/crowdfunding; /c/start/funeral-fundraising; /c/start/medical-fundraising; /c/start/charity-fundraising; /c/questions; /c/how-it-works; https://www.gofundme.com/c/safety/gofundme-guarantee

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.hrt-disp-none (#983 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 Fundraiser not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

Name present: GoFundMe

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name GoFundMe ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗

Name GoFundMe Theme Color #ffffff Icons 2 icon(s)

A+

Landmark Structure

7 landmarks

PASS

7 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

20 headings

PASS

20 headings

Single H1 present

H1 #1 crowdfunding platform
H2 Successful fundraisers start here
H2 More than $50 million is raised every week on GoFundMe.*
H2 Fundraising on GoFundMe is easy, powerful, and trusted
H3 Use our tools to create your fundraiser
H3 Reach donors by sharing
H3 Securely receive funds
H2 Discover fundraisers inspired by what you care about
H2 Featured topics
H3 Fundraise with smart coaching
H3 GoFundMe Giving Funds
H3 How to Help: Hawaii Flood Relief
H3 Fund Fibroid Research with Lupita Nyong'o
H2 Fundraising on GoFundMe is easy, powerful, and trusted.
H2 How GoFundMe works
H2 Top crowdfunding tips
H2 Secondary menu
H3 Donate
H3 Fundraise
H3 About

A+

Alt Text Quality

All 35 images OK

PASS

All 35 images OK

11 decorative image(s) correctly marked

24 image(s) with good alt text

35 images 24 good alt text 11 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Favicon & Branding

6 icon(s) detected

PASS

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

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 #1 crowdfunding plat…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Successful fundraise…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 More than $50 millio…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Fundraising on GoFun…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Discover fundraisers…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Featured topics	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Fundraising on GoFun…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 How GoFundMe works	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Top crowdfunding tip…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h2 Secondary menu	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 Use our tools to cre…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 Reach donors by shar…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 Securely receive fun…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 Fundraise with smart…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 GoFundMe Giving Fund…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 How to Help: Hawaii …	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 Fund Fibroid Researc…	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 Donate	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 Fundraise	20.12:1	3.0:1	#000000	#FAFAFA	Pass
h3 About	20.12:1	3.0:1	#000000	#FAFAFA	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 100/100 — 0 failing, 26 passed

PASS

100

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.

○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

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

●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

●`<frame>` or `<iframe>` elements have a title

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

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

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

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

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