Websites for charities, foundations and NGOs
A charity website has to take a donation without making anyone create an account, keep annual reports easy to find, and be simple enough for a volunteer to update on a Sunday evening. I build those sites on WordPress. I’m Mariusz Szatkowski, a senior developer since 2006, based in Gdynia, Poland, and I work alone: I write the code you get, and your logins go to nobody else.
You bring the graphic design and wireframes, as a Figma file or as a filled-in template where you mark which element goes where on each page. I turn that into a responsive theme with blocks your staff can use without calling a developer.
A donation form that keeps the donor
Every extra screen loses donors. The form asks for an amount with a few suggestions, a choice between one-off and monthly, and contact details for the receipt. Only then does it hand over to your payment provider. Card, Apple Pay and Google Pay can run through Stripe, PayPal through its own checkout, Direct Debit through GoCardless; in Ireland, SEPA Direct Debit through Stripe works the same way. Card data is handled by the provider and never stored on your server.
Monthly giving depends on the provider supporting subscriptions or mandates, so I check its documentation before quoting. After payment the donor gets a thank-you email, and the progress bar on a campaign page shows only money that has actually arrived.
Gift Aid and donor records
For UK charities the form can carry a Gift Aid checkbox with the declaration wording you supply, plus separate fields for full name and home address. The declaration is stored with the donation record, so your finance team can export the records it needs for a claim. Whether a donation qualifies, and how you claim, stays with you and your accountant.
Irish charities often ask donors for different details for tax relief. Tell me which fields your finance team needs and I build the form and the export around them.
Accessibility rules in the UK and Ireland
In the UK, the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 cover public sector bodies. Regulation 4(1)(b) excludes NGO websites unless the NGO provides services that are essential to the public or that specifically address the needs of disabled people. Ireland’s S.I. No. 358/2020 contains the same exclusion in Regulation 3(2)(b). Both implement EU Directive 2016/2102. If your charity runs disability services or something the public depends on, ask your adviser whether the regulations reach you.
I build to WCAG 2.2 AA either way, because a donation form you can’t complete with a keyboard loses money:
- A visible label on every field and error messages a screen reader announces.
- Full keyboard operation with a visible focus state and no traps in modal windows.
- Text contrast of at least 4.5:1 and a logical heading structure.
- axe-core checks before every deployment, NVDA and VoiceOver testing before launch.
Donor and volunteer data
Charities hold data about donors, volunteers and often the people they help, sometimes including health information. Consent boxes are separate and unticked by default. Volunteer applications go into an area only named people can open, not into a shared inbox. Third-party scripts load only after consent, and I document in writing which ones the site uses.
Your privacy notice and records of processing come from you or your adviser; I implement them technically. Before I get access to a site holding personal data, I sign a processing agreement under Article 28 GDPR (UK GDPR has the same article). I use no sub-processors.
Volunteers, events and appeals
- Volunteer sign-up: a form with the fields you actually need, exportable to a spreadsheet.
- Events: registration with a place limit and a reminder email.
- Appeals: a separate page template your staff assemble from existing blocks for an emergency appeal or a seasonal campaign.
- Newsletter: sign-up with double opt-in, connected to the tool you already use.
I don’t sell hosting. You choose the provider, and I set up WordPress there or take over your existing installation.
How a project runs
- Brief: you describe what the site must do through the contact form. I ask questions in writing.
- Quote: scope, assumptions and timeline are in the quote before any code is written. Pricing is individual.
- Build: the code lives in a private Git repository; every change goes to staging first.
- Sign-off: you review on staging and get a written description of each change, plus a short guide for the people who will edit the site.
- Maintenance: if you want, I look after the site afterwards: uptime monitoring every 1 to 5 minutes, backups kept for at least 30 days in EU countries, updates tested on staging. No 24/7 on-call cover.
The contract is under Polish law and invoices carry my EU VAT ID PL7393037445. I communicate by email, documents and the repository.
Contact
Send me your current site address, what should change and which payment provider you use through the contact form. You will get questions back or a quote with the assumptions behind it. More about my work: WordPress developer.
I describe similar accessibility and data protection needs for government offices, hospitals and cultural institutions.



