Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 2 REVIEW 5 FIX

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

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

Link & Button Quality

Action

1 issue(s) across 94 links and 12 buttons

REVIEW

1 issue(s) across 94 links and 12 buttons

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"]

7 link(s) open in new tab without warning

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

Got: /c/start; /c/start/funeral-fundraising; /c/start/medical-fundraising; /c/start/charity-fundraising; /c/how-it-works; /c/pricing#US; /c/safety

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 (#725 on page)

86 link(s) with descriptive text

94 links

0 empty

0 generic text

7 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/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/how-it-works	Learn more about how GoFundMe …	new tab	Add '(opens in new tab)' to text
/c/pricing#US	simple pricing	new tab	Add '(opens in new tab)' to text
/c/safety	Trust & Safety	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

97 links and buttons have descriptive text

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/start/funeral-fundraising; /c/start/medical-fundraising; /c/start/charity-fundraising; /c/how-it-works; /c/pricing#US; /c/safety

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 (#725 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

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

A+

Landmark Structure

6 landmarks

PASS

6 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

19 headings

PASS

19 headings

Single H1 present

H1 Where successful fundraisers start
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 Get what you need to help your fundraiser succeed on GoFundMe
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 How GoFundMe works
H2 GoFundMe is a trusted leader in online fundraising.
H2 Secondary menu
H3 Donate
H3 Fundraise
H3 About

A+

Alt Text Quality

All 18 images OK

PASS

All 18 images OK

1 decorative image(s) correctly marked

17 image(s) with good alt text

18 images 17 good alt text 1 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.

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 successful fun…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 More than $50 millio…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Fundraising on GoFun…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Discover fundraisers…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Get what you need to…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Featured topics	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 How GoFundMe works	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 GoFundMe is a truste…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Secondary menu	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Use our tools to cre…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Reach donors by shar…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Securely receive fun…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Fundraise with smart…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 GoFundMe Giving Fund…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 How to Help: Hawaii …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Fund Fibroid Researc…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Donate	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Fundraise	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 About	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title GoFundMe \| The #1 Cr…	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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 24 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

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●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

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

○Links are distinguishable without relying on color.

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