Charity WordPress Developer: 9 Questions Ontario Nonprofits Should Ask Before Signing (2026)

Illustrated laptop showing a nonprofit website wireframe with a Donate button and checklist for charity WordPress developer handoff

Searching charity WordPress developer usually returns portfolios full of pretty mockups. Pretty is easy. What Ontario nonprofits need is a builder who leaves the charity in control of the site after launch: staff who can change hours, a board that knows who owns the domain, and donors who can finish a gift on their phone without bouncing through five tabs.

This guide is for executive directors, communications leads, and board members who are about to hire or rehire WordPress help. It is WordPress-specific on purpose. It pairs with our broader notes on what boards should expect from a charity website developer in Canada, website updates staff can handle without a developer, and charity web design choices that help donors give.

Why WordPress shows up in most Canadian charity RFPs

WordPress remains a strong fit for Canadian nonprofits when the build is deliberate. Editors can update programs and stories without touching code. Roles separate day-to-day content from security work. Plugins support forms, events, and donation embeds when you keep the stack lean.

The risk is not WordPress itself. The risk is a freelancer who builds a locked showcase, keeps Administrator access, or stacks twenty plugins no one can maintain. Your RFP should force clarity on ownership, training, and the donate path before design colours enter the conversation.

Question 1: Who owns domain, hosting, and the main admin account?

Write the answer into the contract. The charity should own:

  • The domain registrar login
  • The hosting invoice and control panel
  • The primary WordPress Administrator account (or a documented path to create one)
  • SSL and email DNS records tied to the charity, not a personal Gmail

If the developer only offers a “managed package” where they hold every password, treat that as a red flag unless a written exit plan, export process, and transfer fee are already spelled out. Staff turnover is normal in the sector. Locked accounts are not.

Question 2: Which WordPress roles will staff actually use?

A competent charity WordPress developer sets roles on purpose:

  • Two people as Editor for hours, programs, stories, and appeals
  • Administrator reserved for the person or agency that handles plugins, users, and core updates
  • No shared “everyone is admin” account

Ask them to demo how an Editor adds a program date or weather closure without touching theme files. If the answer is “call us and we will change it,” you are buying a dependency, not a site.

Question 3: How short is the donate path on mobile?

CanadaHelps recommends anchoring Donate in primary navigation (often top-right) and keeping the gift path short. Their guidance also favours embedding giving on your own domain so donors do not bounce away mid-flow.

Ask the developer to:

  • Place Donate in the main menu on desktop and mobile
  • Complete a full test gift on a real phone after install
  • Prefer an embedded form (for example CanadaHelps) over a bare outbound link when your processor supports it
  • Document campaign-specific forms if you run multiple drives each year

If donate is buried under “Support Us > Ways to Give > Online,” rewrite the information architecture before launch.

Question 4: What is the plugin policy?

Lean stacks survive. Bloated stacks break after the first security update. Ask for:

  • A written list of every plugin and why it exists
  • A plan for updates (who applies them, how often, on staging first)
  • A hard no on abandoned plugins and “page builder soup” unless your team is trained on that builder

A charity site needs forms, backups, security basics, and a donation integration. It does not need five SEO plugins and three sliders fighting each other.

Question 5: Is there a staging site and a backup routine?

Production-only edits are how urgent appeals go dark on a Friday night. Require:

  • A staging environment that mirrors production
  • Automated backups with a restore test at least once before handoff
  • A short runbook: what to do if a plugin update breaks the donate form

This is not optional infrastructure. It is board-level risk management.

Question 6: How will accessibility be handled?

Ontario’s guidance on making websites accessible explains that as of January 1, 2021, designated public sector organizations and businesses or non-profits with 50 or more employees must make public websites meet WCAG 2.0 Level AA (with limited media exceptions). The organization that controls the site remains responsible, even when a contractor builds it.

Smaller charities still serve donors and clients who use screen readers, keyboards, and high-contrast modes. Ask your charity WordPress developer for:

  • Keyboard-friendly navigation and visible focus states
  • Alt text patterns staff can follow
  • Colour contrast that holds on buttons and body text
  • Form labels that work without placeholder-only cues
  • A short accessibility checklist in the handoff, not a vague “we care about inclusion” slide

Link this work to your existing AODA planning. Do not treat it as a last-week polish pass.

Question 7: What can staff update without a ticket?

Demand a one-page Editor cheat sheet covering:

  • Homepage notice or next-program block
  • New program or campaign page from a reusable pattern
  • Board list and contact hours
  • Blog or news post
  • How to swap a featured image without breaking layout

If every content change needs a developer hour, the build failed the operational test even if it looks polished in a browser on a big monitor.

Question 8: How is training and handoff scheduled?

Build training into the timeline, not as a free leftover. A solid handoff includes:

  • A live walkthrough with the two Editors
  • Recorded loom or PDF notes your next hire can follow
  • Login matrix (who has which role)
  • Proof the charity can export content and media

Ask when training happens relative to launch. Training on launch day, while the ED is already late for a board call, is how passwords get lost in a Slack thread.

Question 9: What does support look like in the first 90 days?

Clarify:

  • Response times for donate-form outages versus cosmetic tweaks
  • Whether core and plugin updates are included
  • Hourly rates after the warranty window
  • Who monitors uptime and SSL expiry

Put the answers in writing. Verbal “we’re always here” promises do not help a new board chair six months later.

A short RFP addendum you can copy

Paste this into your next brief:

  1. Charity owns domain, hosting, and Administrator access at launch.
  2. Two staff trained as Editors; reusable program page pattern included.
  3. Donate in main nav; full mobile gift test documented.
  4. Plugin list, staging site, and backup restore proof included.
  5. Accessibility checklist aligned to WCAG 2.0 AA habits; Ontario obligations noted where they apply.
  6. One-page Editor cheat sheet and 90-day support terms attached.

If a proposal cannot answer those six lines, keep shopping.

How NativaWeb approaches charity WordPress work

NativaWeb is a St. Catharines digital agency that builds WordPress sites for Ontario nonprofits with that handoff in mind: staff-editable content, clear ownership, short donate and volunteer paths, and accessibility habits that fit lean teams. We work on a typical 6-8 week timeline for scoped nonprofit builds, with transparent scope and no pressure sales.

If you want a second set of eyes on an existing WordPress site or a build plan for a redesign, book a free consultation at nativaweb.com. Bring your current login situation, your donation processor, and the two people who will edit the site. We will map the nine questions above to your real stack and leave you with a clear next step.