Nonprofit websites: make evidence and next steps easy to find

A nonprofit website should let visitors understand what a program does, inspect the evidence behind its claims, and choose a relevant next step. Donations are one path. People seeking services, volunteers, and institutional partners need different information and should not have to navigate through a fundraising pitch to find it.

Put evidence beside the claim it supports

Build program pages around a specific activity, audience, location, and reporting period. Link a result to its source document or explain how the organization recorded it. Distinguish work completed from work planned, and outputs from broader outcomes.

An activity count can show what happened without proving what caused a lasting change. If the organization lacks outcome evidence, say what it can substantiate instead of turning an aspiration into a result. Give a report an owner and review date so last year’s information does not silently describe the present.

Make the essential explanation available as readable page text. A downloadable report can provide detail, but it should not be the only way to understand the program. W3C’s headings guidance explains how headings organize content; descriptive sections also make a long evidence page easier to scan.

Separate the visitor’s next steps

Identify the action a program page supports and the information needed before that action. A potential participant may need eligibility and contact details. A volunteer needs responsibilities and availability. A donor needs to understand the supported work and what happens after submitting a contribution.

Use descriptive links rather than several identical “learn more” buttons. Keep the main program facts consistent across English and Spanish. Translation should include form errors and confirmation messages, not just the fundraising headline.

For teams in Costa Rica serving international supporters, explain the available donation methods and currencies exactly as the configured provider supports them. Do not imply that every foreign payment method works, or offer tax claims without appropriate professional review.

A hypothetical program page with honest limits

Imagine an organization reporting community workshops. This is a hypothetical example, not a 5e Labs client result. Its attendance records show twelve sessions and 180 recorded attendances, including repeat participants. The page should not translate that into “180 people achieved lasting change.”

A usable evidence block would identify the period, define attendances, link the activity report, and explain what was not measured. Its next steps can be distinct: request a workshop, volunteer for an upcoming session, or support the program through the donation page.

When the next report arrives, the content owner can update the period and figures in that block. The definition of attendance stays visible, so a reader can compare the reports without guessing whether the counting method changed.

Test the donation path through failure and confirmation

Review the handoff to the payment provider, including mobile use, keyboard access, errors, cancellations, and success messages. W3C’s form notification tutorial describes accessible feedback for both errors and successful completion.

Before publishing, check:

• The selected amount and any recurrence are explicit.
• Visitors can distinguish pending, failed, and completed submissions.
• A confirmation does not appear before the application has verified the relevant result.
• Test transactions use the provider’s test environment.
• Contact information is available when something goes wrong.

Audit one program page from claim to source to next step. If the evidence is ready but the navigation obscures it, a UX/UI design review with 5e Labs can focus on that specific journey rather than a cosmetic redesign.