A charity website donation journey: find the friction before redesigning

A charity website donation journey should help someone understand the cause, decide whether they want to support it and complete a donation with confidence. Before commissioning a redesign, examine the whole task from the first page a visitor sees to the confirmation and any later preference choices.

An attractive homepage cannot compensate for a confusing payment step or an unclear explanation of how a gift will be used. Equally, a donation form with fewer fields is not automatically better if it removes information a supporter needs to make an informed choice.

This guide offers a practical walkthrough for charity fundraising and digital teams. It focuses on useful evidence, accessible forms and respectful testing. The examples are illustrative; there are no promised donation increases, invented supporter results or assumptions that every charity needs a new website.

Start with the supporter's task

List the situations that bring people to the site. Someone may follow an appeal email, look up a charity after an event or want to make a regular gift to an organisation they already know. Those visitors arrive with different knowledge and may need different information before choosing to donate.

Follow the actual links used in each situation. An appeal may lead to a general homepage when a focused campaign page would answer the visitor's question more directly. A social link may open inside a mobile app, changing how the payment provider or cookie controls behave.

Write a simple task for each walkthrough: “Understand this appeal and make a one-off donation” is more useful than “test the website”. Give the participant a realistic starting point and let them explain what they expect at each step. Avoid telling them where the donation button is before they have looked.

Keep other visitor needs visible. People may arrive for help, volunteering, a complaint or information about the charity's work. A donation campaign should not make essential service information harder to find. The navigation needs to support the organisation's responsibilities as well as its fundraising ambitions.

Make the appeal understandable before the form

Explain what the charity does, whom the appeal supports and what a donation can contribute to. Use approved facts and language that respects the people represented. If an example amount describes a possible use of funds, make clear whether it is illustrative or a specific restricted purpose.

Avoid invented precision. A statement that a particular sum will achieve an exact outcome needs evidence and appropriate qualifications. Where gifts support a wider programme, explain that plainly. A simpler honest description can build more confidence than a dramatic claim that the charity cannot substantiate.

Use photography carefully. Images should have an appropriate licence or consent basis, accurate context and respectful captions. Stock photography should not be presented as evidence of the charity's actual beneficiaries or results. The same care applies to AI-assisted campaign text and any visual material created for an appeal.

Give visitors a route to supporting information without making them leave the task entirely. A concise explanation of the charity, relevant reporting and how to ask a question can help someone who is interested but cautious. Those links should remain available without overwhelming the appeal with administrative detail.

Review every field in the donation form

For each field, ask what it is needed for and at what stage. Distinguish information required to process the donation from optional preferences or later relationship-building. Avoid collecting a full supporter profile merely because the form platform makes the fields easy to add.

Labels should explain the input without relying on placeholder text that disappears when the person starts typing. Mark optional fields clearly and explain unusual requests. If an address is needed for a particular declaration or payment method, make the reason understandable in the relevant part of the journey.

Check the experience after an error. Does the form identify the field, explain how to correct it and preserve other entered values where safe? A generic message at the top of a long form can leave a phone user unable to find the problem, particularly when the page scroll position changes.

The W3C forms tutorial provides guidance on labels, grouping and feedback. Use it as a practical design reference, then test with keyboard users and relevant assistive technology. An automated accessibility scan can identify some issues but cannot establish that the complete donation task is usable.

Check amounts and recurring-gift choices

Present one-off and regular giving clearly. The selected frequency, amount and any additional contribution should be visible before confirmation. Visitors should not have to notice a small label change to understand that they are starting a recurring payment rather than making a single donation.

If you suggest amounts, allow a reasonable custom option where the service supports it. Explain what the amounts mean without implying unsupported outcomes. Review the layout on a narrow screen: amounts that look evenly spaced on desktop can become ambiguous when a frequency selector wraps onto another line.

Be transparent about optional additions, platform contributions or fees presented to the donor. The charity should understand how the provider displays them and what is selected by default. Ask test participants to explain the final amount in their own words before they proceed.

Provide accessible information about changing or cancelling a regular gift. The route may depend on the payment method and provider, so check the current arrangement rather than writing a generic promise. Make it easy for supporters to contact the right team if their circumstances change or a payment question arises.

Treat payment and confirmation as part of the website

Follow the journey into any external payment service. Check branding, page titles, currency and the explanation of who receives the money. A sudden visual change can be legitimate, but visitors need enough context to recognise that they are still completing the intended donation.

Test the available payment methods on relevant devices through an authorised test environment or a carefully controlled designated donation. Do not repeatedly create live donations simply to inspect screens. Check failed, cancelled and delayed outcomes as well as successful immediate confirmation.

The confirmation should distinguish what is known. If payment is still pending, avoid saying the funds have been received. If a receipt email is expected, explain the likely next step and a contact route if it does not arrive. The supporter should not be left wondering whether to try again.

Review the email as part of the same task. It should be recognisably from the charity, use the right reply address and contain an accurate record of the transaction. Promotional choices should remain separate from essential confirmation. A donation does not by itself resolve every question about future marketing permissions.

Work through an illustrative mobile appeal

Imagine a community charity sharing a link to an appeal for its services. A supporter opens it on a phone while travelling. The first screen shows a large decorative image, but the appeal explanation and donation link appear well below it. The visitor may never reach the form.

The team first tests a more useful opening: a clear appeal title, a short factual explanation and a visible donation route, with supporting imagery sized appropriately. This is a hypothesis to test, not evidence that reducing image height will increase donations for every charity.

Further down the journey, the participant selects a one-off amount but cannot tell whether a payment failed after returning from the provider. The team adds clearer outcome handling and a safe checking route. This change addresses uncertainty and duplicate-donation risk, rather than merely making the page look more polished.

Finally, the receipt invites newsletter subscription through a separate clear choice. The donor can understand what they are agreeing to and can complete the donation without subscribing. The improved journey supports an informed gift and a relationship the charity can manage responsibly afterward.

Measure stages without collecting unnecessary personal data

Define a small set of useful events: appeal viewed, donation route opened, form started and confirmed donation where the platform supports reliable measurement. Record which events represent an attempted action and which are confirmed by the payment system. They are not interchangeable counts.

Keep personal details out of analytics event names, page URLs and free-text parameters. A donation reference may also be sensitive or linkable, so decide what reporting genuinely needs. Access to supporter records belongs in the appropriate controlled systems, not in a general marketing dashboard.

Review consent and provider behaviour with the person responsible for privacy. An external payment platform may have its own cookies, redirects and reporting limitations. Document those boundaries before interpreting a gap between form starts and completed payments as proof that the website is losing supporters.

Compare like-for-like periods and sources where possible. An emergency appeal and an ordinary newsletter reach different audiences. Small numbers can fluctuate considerably, so avoid declaring a design winner from a handful of donations. Combine quantitative signals with observation and the questions received by the fundraising team.

Test accessibility and performance together

Check that the donation route is available with a keyboard, visible focus and readable text at zoom. Test errors, amount choices and payment redirects, not just the homepage. Ask whether essential instructions remain understandable when decorative imagery or animation is unavailable.

Use appropriately sized images and avoid loading heavy video before the visitor requests it. A cinematic campaign can still provide a quick first view with stable text and a clear action. The important performance question is whether supporters can read and act on the appeal under ordinary mobile conditions.

The W3C guidance on images helps distinguish informative from decorative content. Describe information an image contributes; do not stuff alternative text with fundraising keywords. Where an image contains important wording, ensure the equivalent is available as readable text.

Check motion preferences and intrusive overlays. A visitor should be able to read the appeal without repeatedly dismissing subscription requests. A prompt can be useful at a suitable point, but it should not obscure the donation form, trap keyboard focus incorrectly or make refusal difficult on a smaller screen.

Review trust and fundraising responsibilities

Ask a colleague unfamiliar with the redesign to find the charity's identity, contact details and relevant policies. They should be able to understand who operates the appeal and how to ask a question. A professional visual style supports trust, but it cannot substitute for accurate organisational information.

Review appeal wording and donor communications against the fundraising requirements that apply to the charity. The Fundraising Regulator's resources are a relevant starting point for UK trustees. International fundraising may require additional review; a globally accessible page does not establish permission to use every campaign approach everywhere.

Have the responsible people approve any claims about restricted funds, tax treatment or the use of donations. Keep the approved wording and review date with the campaign materials. This makes later updates easier when a programme changes or an appeal reaches a different stage.

Include an approach for complaints and corrections. If the charity discovers that a page contains an inaccurate claim, it needs an owner who can review and update it promptly. The content-management process matters as much as the initial design when maintaining public confidence over time.

Decide whether refinement or rebuilding is justified

Group findings by consequence and effort. A broken payment return, inaccessible error message or misleading frequency label should take priority over decorative details. Some problems can be repaired within the existing platform. Others may reveal a genuine limitation in the form, payment or content architecture.

Ask any proposed supplier to explain the problem each change addresses and how it will be tested. A redesign proposal should cover content, forms, integrations, analytics and ongoing ownership. Attractive mock-ups alone do not establish that supporter information and payment outcomes will move reliably through the organisation.

A digital engineering review can help distinguish a focused repair from a wider build. For charities with disconnected supporter and reporting systems, an operational transformation assessment can examine the work behind the public page as well.

Keep the first release manageable. Agree a set of verified fixes, document the test results and review real supporter questions afterward. The website should help people make a confident decision and allow the charity to handle the resulting relationship properly. That is a useful standard for both a modest refinement and a complete rebuild.

Check the human route for an unfinished donation

Some supporters will choose to ask a question before completing the form. Give that route a responsible owner and a realistic response expectation. Record common questions in a way that can improve the page, while keeping personal correspondence in the appropriate controlled system. A useful donation journey supports a considered decision even when the person does not donate during the first visit.

Prepare a practical walkthrough pack

Before the next review, gather the actual appeal links, a list of supported payment methods, the current receipt and a simple diagram of the data handoff. Identify who can answer content, fundraising, finance and technical questions. This prevents the exercise becoming a discussion about visual preferences alone.

Use a short observation sheet with the task, device, point of difficulty and expected next step. Record what the participant did rather than assuming why they did it. If they hesitate, ask what they expected to see. Their explanation may reveal an information gap that an analytics funnel cannot show.

Finish with named owners and a decision date for each material issue. Keep untested ideas in a separate backlog. The result should be a small set of changes the charity can verify, maintain and explain to its supporters, with a clear basis for any larger investment.

Checked sources

• W3C WAI: accessible forms tutorial
• W3C WAI: accessible images tutorial
• Fundraising Regulator: resources for trustees