Skip to content
Talk to us

WordPress care plans for Irish charities: what governance-accountable maintenance looks like

Jack O'Connor· 19 min read· ·Updated

WordPress care plans for Irish charities: what governance-accountable maintenance looks like, HostLogic

When a Charities Regulator inquiry opens or a Data Protection Commission investigation begins, the first thing auditors want is documented evidence: written, timestamped records showing that your organisation governed its digital infrastructure responsibly. An assurance from the team about what they believe happened carries very little weight at that point. For most Irish charities, those records do not exist.

A standard WordPress care plan covers updates, backups and uptime monitoring, which tells you what changed on the site. Whether the organisation was compliant, accessible and data-protection-ready at the moment it mattered is a separate question that the same records cannot answer. For charities operating under trustee scrutiny, funder due diligence, and the obligations flowing from the Charities Regulator’s Charities Governance Code, that gap is no longer acceptable.

This analysis is written for trustees and operations directors who need to understand what governance-accountable website maintenance actually requires. You will learn why standard agency maintenance falls short of regulatory expectations, what accessibility conformance and cookie consent monitoring look like as governance obligations, and how a properly structured care plan produces the kind of audit-ready monthly evidence that survives serious scrutiny.

The regulatory landscape Irish charities now navigate

The regulatory obligations sitting behind a charity’s website have grown considerably. The Charities Regulator published the Charities Governance Code in November 2018, and since the 2021 reporting year every registered charity has had to report its compliance with the Code’s core standards to the Regulator. The Code works on a ‘comply or explain’ basis, so trustees must either show that they meet each standard or record why they do not and what they do instead. An organisation that cannot evidence either position at the point of inquiry is treated as non-compliant, whatever its website actually does.

The Code is built on six principles: advancing charitable purpose, behaving with integrity, leading people, exercising control, working effectively, and being accountable and transparent. A charity’s website touches at least two of them. Exercising control covers compliance with the law and the management of risk, which is where data protection and cyber security sit, and being accountable and transparent covers how the charity presents itself and its information to the public.

The Data Protection Commission enforces the GDPR and the Data Protection Act 2018 in Ireland. Cookie consent obligations in Ireland derive principally from SI 336/2011, the European Communities (Electronic Communications Networks and Services) (Privacy and Electronic Communications) Regulations 2011, which give effect to the ePrivacy Directive, and the DPC is the regulator for cookies as well as for the GDPR. Consent that was valid when a banner was configured can stop being valid after a routine update, and that is exactly the kind of drift a standard maintenance arrangement does not monitor.

For charities in receipt of public funding that meet the definition of a public sector body under SI 358/2020, the European Union (Accessibility of Websites and Mobile Applications of Public Sector Bodies) Regulations 2020 apply. Where a charity meets that threshold, its website must be perceivable, operable, understandable and robust, with conformance assessed against EN 301 549, the harmonised standard under which WCAG 2.1 AA is the applicable benchmark for web content. The National Disability Authority is the monitoring body under those Regulations.

SI 636/2023, the European Union (Accessibility Requirements of Products and Services) Regulations 2023, came into operation on 28 June 2025 and gives effect to the European Accessibility Act. Its in-scope services include e-commerce and certain electronic communications services, and its obligations sit alongside those under SI 358/2020 for organisations that meet either threshold. Organisations affected by SI 636/2023 should take their own legal advice on the services they provide. The Code and these instruments together mean that website governance is a board-level risk, and the question is whether the organisation can produce documented evidence that it complied, which is a different question from whether it intended to.

Ultimately the accountability lands on named people. Trustees carry collective responsibility for governance failures, and while incorporated structures such as a company limited by guarantee limit personal financial exposure in most circumstances, that protection is not absolute and it does nothing to limit regulatory or reputational consequence. In practice, operations directors and board secretaries own the obligation day to day.

Why standard WordPress maintenance services fall short

Given that regulatory framework, the question becomes practical: what does a standard WordPress maintenance services agreement actually provide, and where does it stop?

The honest answer is that it stops at operations. A typical agreement delivers core WordPress updates, plugin updates, uptime monitoring, and periodic backups. These are legitimate technical functions, but they generate no evidence of compliance state. A plugin update log records that an action was taken on a given date. It does not record whether WCAG 2.1 AA conformance was preserved afterwards, or whether the update altered how the site sets cookies. A changelog is an operational record, and a regulatory inquiry will not accept one in place of a governance record.

Accessibility is the clearest illustration of this gap. Most WordPress care plan agreements contain no commitment to WCAG 2.1 AA, no baseline audit, and no process for verifying that conformance has not degraded between update cycles. Conformance degrades silently: a plugin update, a new image uploaded without alt text, or a theme revision can introduce failures that no standard maintenance check will detect. The website continues to receive updates; nobody is accountable for what those updates do to its accessibility status.

Cookie consent follows the same pattern. Consent under SI 336/2011 and the GDPR has to be valid every time a cookie is set, not only on the day the banner was configured. A consent banner set up accurately in one quarter can drift into non-compliance after a theme or plugin update changes its behaviour. Standard website maintenance services treat consent configuration as a one-time setup task; the ongoing monitoring obligation under SI 336/2011 falls back to the charity, whether or not the charity is aware of it.

Backup arrangements present a parallel problem. A standard backup confirms that a copy of the site exists. It does not confirm what data that backup covers, whether it has been tested against a defined recovery scenario, or whether the recovery time objective is documented. That level of continuity evidence is precisely what a Charities Regulator inquiry into data stewardship would expect to see.

The underlying issue is accountability. Standard agencies provide a technical service; they do not co-own a compliance obligation. When a DPC investigation or a Charities Regulator inquiry arrives, the charity holds the obligation in full. Drawing that line, between what standard maintenance covers and what governance accountability requires, is the first thing any operations director should do before signing an agreement.

Defining governance-accountable website maintenance

The gap identified in the previous section is definitional. Standard maintenance was never designed to carry governance accountability, because governance accountability was never asked of it. Defining what that accountability requires is the necessary first step before any vendor claim can be assessed.

Governance-accountable maintenance is an engagement in which the vendor takes documented, evidenced responsibility for the compliance posture of the website as well as its technical operation, month to month. The distinction from standard maintenance is structural. A maintained website receives updates. A governed website has a named responsible party, a documented compliance position and a monthly evidence record that survives independent scrutiny. The difference between the two surfaces the moment a regulator or funder asks a question.

A changelog records actions. A governance evidence record confirms status, which is the harder and more useful thing. The structured monthly record that governance-accountable maintenance produces should confirm, as at a specific date, the accessibility conformance status, cookie consent behaviour, data protection posture, backup integrity and continuity readiness of the website. Each item carries a status, a timestamp and a named responsible party.

The ‘comply or explain’ principle in the Charities Governance Code, and the accountability principle in Article 5(2) of the GDPR, make documentation as important as the compliance fact itself. An organisation that cannot produce a coherent, dated, vendor-signed evidence trail is treated as non-compliant, regardless of whether its website actually met the standard at the relevant time. Reconstructing a compliance position retrospectively from email threads does not satisfy this standard.

The evidence bar varies by audience. A Charities Regulator statutory inquiry, a DPC investigation, and a funder due diligence review each carry different documentation expectations, different timescales, and different thresholds for what constitutes adequate demonstration of control. A governance-accountable engagement is designed to meet all three simultaneously.

Finally, the vendor must own the obligation between engagements rather than wait to be asked. Compliance drift, where a plugin update quietly degrades consent behaviour or introduces an accessibility regression, is the vendor’s responsibility to detect and flag. That proactive duty is what separates governance accountability from a support ticket queue.

Accessibility conformance is a governance requirement

Accessibility sits at the intersection of distinct obligations that governance-accountable maintenance must treat carefully. For publicly funded Irish charities that meet the public sector body threshold under SI 358/2020, the legal standard is perceivability, operability, understandability and robustness, assessed via the EN 301 549 harmonised standard, under which WCAG 2.1 AA is the applicable benchmark for web content. Organisations uncertain whether they meet the threshold should take their own legal advice. WCAG 2.2 AA is the current version of the standard and the sensible target for any new audit, since it is where guidance is heading and the additional criteria are modest. Because accessibility is a legal obligation for charities in scope, it falls under the Code’s exercising control principle, which means trustees cannot hand it down to the web team as a technical preference.

The baseline audit problem

A development sign-off records conformance at a single point in time, against a specific build, which is not what a governance document has to do. A governance-accountable WordPress support services engagement requires a documented WCAG 2.1 AA audit conducted against the live, production website, repeated on a defined cycle. Content changes and plugin updates happen continuously; the audit baseline must track them.

Silent degradation

Accessibility conformance erodes without announcement. A plugin update can alter keyboard navigation behaviour. A new staff member uploading a banner image without alt text introduces a failure instantly. A theme change can break colour contrast ratios across dozens of pages simultaneously. No standard maintenance check detects any of these, because standard maintenance is not looking for them. The failures accumulate silently until a complaint, an audit, or a regulatory inquiry surfaces them.

Monthly verification and the evidence record

Monthly accessibility verification should confirm that no new WCAG 2.1 AA failures have been introduced since the previous cycle. Any regression should be logged, remediated and recorded in the compliance evidence for that month. This is the cadence that produces a defensible audit trail. Reviewing the current conformance status of a site is the starting point; maintaining evidenced conformance month to month is the obligation.

Statement versus conformance

An accessibility statement is a published document. Accessibility conformance is a live, evidenced status. Charities in scope of SI 358/2020 need both, and standard WordPress care plans provide neither. The statement without evidenced conformance is a liability document; it asserts a standard the organisation cannot prove it meets.

Funders increasingly request conformance evidence as a condition of grant renewal. An audit trail of monthly conformance records is the only documentation that satisfies this requirement retrospectively, because it cannot be reconstructed after the fact.

Cookie consent monitoring and data protection posture

Accessibility conformance and cookie consent are distinct obligations, but they share the same failure mode: both can degrade silently after a routine update, and neither is monitored by a standard maintenance agreement.

Under the GDPR and SI 336/2011, a valid cookie consent mechanism must meet three conditions at all times: no non-essential cookies may be set before affirmative consent is given, consent records must be retained, and users must be able to withdraw consent as easily as they gave it. A banner configured correctly at launch can fail all three conditions after a WordPress core update or a consent-plugin version change alters its behaviour. The organisation remains liable from the moment of failure, regardless of when it is discovered.

A cookie consent failure is also visible to anyone who opens the site in a private window. A consent mechanism that fires tracking pixels before consent is recorded suggests to a regulator, a funder or a donor that the organisation lacks systematic oversight of how personal data flows through its digital infrastructure.

What governance-accountable consent monitoring covers

A governance-accountable maintenance service includes monthly verification of three specific conditions: that the consent mechanism blocks all non-essential cookies prior to consent, that consent logs are being retained correctly, and that the mechanism’s behaviour has not been altered by any update applied during that cycle. It is a recurring, evidenced obligation rather than a one-time configuration check.

Data protection posture documentation goes further than a published privacy policy. It should confirm, as a structured governance record: which data is collected through the website, through which mechanisms (forms, tracking pixels, embedded third-party scripts), under which legal basis, with which retention periods, and with which third-party processors. This document belongs in the organisation’s data protection register, not on the public-facing site.

Standard WordPress maintenance agreements contain none of this. Updates are applied, backups are confirmed, and the consent layer is left untouched between vendor visits. The DPC liability for any failure in that interval sits entirely with the charity.

A governance-accountable care plan closes that gap by producing a monthly written record of the website’s consent and data protection status, dated and retained by the organisation. The record needs to be suitable for the data protection register, and it needs to arrive every month without the organisation having to ask for it.

What audit-ready monthly evidence actually looks like

The consent and data protection record described in the previous section is one component of a broader governance document. Understanding what that full document looks like in practice is where the distinction between maintenance and governance becomes concrete.

An audit-ready monthly evidence record is a structured document with a date, a named responsible party, and a versioned compliance status for each governance obligation. An email summary, a screenshot folder or a changelog exported from a plugin will not do the job. Format matters because a regulator reviewing it needs to assess compliance posture at a specific point in time rather than reconstruct it from fragments.

The minimum obligations the record must cover are:

  • Core and plugin update status
  • WCAG 2.1 AA conformance status
  • Cookie consent behaviour verification
  • Backup integrity confirmation
  • Uptime and availability record
  • Data protection posture status

Each item carries three pieces of information: a status (compliant, non-compliant, or remediation in progress), a timestamp, and a note of any action taken. This three-field structure is what gives the record evidentiary weight. A status without a timestamp is unverifiable. An action note without a status classification does not confirm resolution.

Retention is as important as production. A Charities Regulator inquiry or DPC investigation may request evidence covering twelve months or more. A record produced once and not retained systematically is a one-off document with no evidentiary continuity. The documentation infrastructure has to be designed for retention from the outset, because it cannot be assembled backwards.

The vendor’s name and responsibility must appear explicitly in the record. A document that lists compliance facts without attributing who assessed and owns them does not shift liability in a regulatory proceeding. The charity remains the data controller and the duty-bearer; the record must show that a named vendor accepted documented responsibility for the compliance posture it is confirming. That attribution has to be explicit on the page, not implied by the letterhead.

Before signing any website maintenance services agreement, trustees and operations directors should establish what monthly evidence the arrangement will produce. The question should be specific: which governance obligations does the record cover, and which does it exclude. A vendor who cannot describe that in writing is unlikely to produce it in practice.

Questions trustees and operations directors should ask any WordPress support vendor

Whether your organisation is a charity, a publicly funded body, or both, the vendor evaluation questions are the same. Before signing any WordPress support agreement, put these six questions to every provider under consideration.

1. What monthly evidence record does your agreement produce?

The answer should name the governance obligations the record covers, the format it arrives in, and who signs it. A governance-accountable care plan should be demonstrable in writing rather than described in a brochure.

2. Which governance obligations does your agreement take documented responsibility for?

Updates and uptime are operational functions. The answer you need names accessibility conformance, cookie consent monitoring, data protection posture and continuity planning as explicit, documented commitments. Assurances about ‘best practice’ give you nothing you can file.

3. How do you confirm accessibility conformance is maintained after each update cycle?

A developer casting an eye over the site does not constitute a process. The answer should describe a defined testing methodology with a documented output, produced after every update cycle and retained as part of the monthly evidence record. If the vendor cannot describe the methodology, no documented output exists.

4. What happens to our evidence records if we change provider?

Documentation held only in a vendor’s systems is not audit-ready. Your organisation must own the compliance records independently of the vendor relationship. If a Charities Regulator inquiry or DPC investigation arrives after you have moved to a new supplier, you need twelve months of prior evidence to hand. Confirm this in writing before you sign.

5. How do you handle a compliance failure discovered mid-cycle?

A governance-accountable vendor has a defined remediation and notification process: a named contact, a written notification to the organisation, a remediation timeline, and a record of closure. A standard maintenance vendor has a support ticket queue. The distinction matters in a regulatory proceeding.

6. Can your monthly report be presented to trustees or the Charities Regulator without further interpretation?

If the honest answer involves caveats, the documentation is not audit-ready. Reports that require a technical translator before they can be presented to a board or regulator place the interpretive burden back on the organisation, which defeats the purpose of the engagement entirely.

How a governance-accountable WordPress care plan is structured in practice

Those questions define what a governance-accountable engagement must deliver. Here is what that structure looks like in practice.

The foundation is managed WordPress hosting and maintenance: uptime monitoring, core and plugin updates, backups and performance management. That operational layer is the floor. Governance obligations are layered on top as discrete, documented commitments, each with its own evidence output.

Cookie consent and data protection monitoring comes first. Each month, consent behaviour is verified: no cookies fire before consent is given, the mechanism still functions correctly after that cycle’s updates, and a written posture record is produced for the organisation’s data protection register. Where an update changes consent behaviour, the organisation hears about it at the time rather than discovering the drift during a DPC inquiry.

Accessibility audit and remediation against WCAG 2.1 AA is priced and delivered separately. It begins with a baseline audit of the live site, establishing a documented conformance position. Monthly verification then confirms whether updates, content changes or plugin modifications have introduced regressions. Regressions are remediated and logged. The monthly conformance record is structured for direct use in funder due diligence or a Charities Regulator inquiry, so that nothing has to be reformatted once the request arrives.

Monthly evidence records are retained by the organisation, not filed in a vendor inbox. Each record is a structured, dated document attributing responsibility clearly. The documentation infrastructure is designed from the outset to be portable and regulator-ready, not reconstructed under pressure.

The governance layer sits on a technically sound base. HostLogic is an Automattic for Agencies Pro Partner and runs client sites on Pressable, Automattic’s managed WordPress platform, on WP Cloud infrastructure. The compliance posture is evidenced because the operational foundation beneath it is stable enough to make that evidence credible.

The engagement is built for the compliance officer, operations director, or board secretary who needs to place a document in front of trustees or a regulator and stand behind it without qualification.

The shift from website maintenance to website governance

The engagement model described above addresses a gap that standard WordPress care plans were never built to close. That gap is documentary.

The Charities Governance Code has required every registered charity to report its compliance with the core standards since the 2021 reporting year, and legal compliance and risk management, including data protection, sit inside those standards. An organisation that cannot produce dated, structured evidence of its website’s compliance posture is treated as non-compliant, regardless of whether its site actually met the standard at the time. The distinction matters: technical adequacy without documented proof offers no protection in a Charities Regulator inquiry or a DPC investigation.

Standard WordPress maintenance agreements were not designed for this. They produce operational records: changelogs, backup confirmations, uptime logs. None of that constitutes governance evidence. The organisation retains full regulatory liability; the vendor retains none.

Three practical steps follow from this.

First, audit your current maintenance agreement against the governance obligations it is supposed to cover. Most agreements will not mention WCAG conformance, cookie consent monitoring, or data protection posture at all. Second, establish what monthly evidence your current or prospective vendor produces, and in what format. Third, confirm in writing that accessibility conformance and consent monitoring appear in the agreement as documented obligations rather than optional extras or reactive services.

The question for your next trustee meeting is whether your maintenance arrangement produces evidence that would survive regulatory scrutiny if an inquiry arrived tomorrow. The site is almost certainly maintained. If the honest answer to the second question is no, the arrangement falls short of the obligations your organisation carries.

Conclusion

Irish charities operate under regulatory obligations, including the Charities Governance Code, the GDPR, SI 336/2011 and, where applicable, SI 358/2020, that standard WordPress maintenance agreements were never designed to meet. Governance-accountable maintenance means documented WCAG 2.1 AA conformance, monitored cookie consent, data protection posture records and audit-ready monthly evidence. These are trustee responsibilities.

The gap between a maintained website and a governable one is significant. Operational records protect vendors. Governance evidence protects your organisation.

Your next step is straightforward: review your current agreement, establish what monthly evidence it produces, and confirm accessibility and consent monitoring appear as contractual obligations in writing.

Trustees and operations directors who close this gap now are building the documented foundation that demonstrates regulatory accountability when scrutiny arrives. It is worth building before it is needed, because there is no way to build it afterwards.

Share this article

See exactly how your WordPress site is performing

Get a free HostLogic site audit covering Core Web Vitals, security posture, infrastructure and a maintenance gap analysis. Written report within 3 working days. No obligation, no sales pitch.