Indigo Trust

https://indigotrust.org.uk · 35/92 checks passed · not_for_profit

Compliance report (framework 0.8)

Gate passed (every Core check must pass) · not counted towards the gate: paused 35, draft 48, ready for review 54.

Site level: 0 (no scored checks yet).

By level

LevelResult
Level 1 — Basic 23/37 (10 failed)
Level 2 — Enhanced 2/27 (4 failed)
Level 3 — Advanced 0/10 (6 failed)

By category

CategoryResult
Accessibility 10/13
Accountability 0/5
AI & Automation 2/8
Interoperability 0/3
Privacy 8/16
Provenance 0/2
Security 5/11
Transparency 0/13
Responsibility to the Future 0/3

Level 1 — Basic

Accessibility

AI & Automation

  • human_or_disclosed: The page returns a 403 Forbidden error with no accessible content, so authorship or AI disclosure cannot be verified.
    Fix: Restore access to the page and include a clear statement about whether content is human-authored or AI-assisted.

Privacy

Security

  • strict-transport-security: header not set on the response.

Transparency

Level 2 — Enhanced

Accessibility

Accountability

AI & Automation

Interoperability

Privacy

  • banner_present: The page only displays a '403 - Forbidden' error with no cookie or consent banner visible.
    Fix: Restore access to the page and ensure a cookie/consent banner is served on all pages including error pages if cookies are set.
  • partner_sharing_mentioned: No banner or consent copy is present, so no disclosure of third-party partner data sharing is made.
    Fix: Add a consent banner that explicitly discloses any data sharing with third-party partners before non-essential cookies are set.
  • partner_count_specific: No partner sharing is disclosed and no numeric count of partners is stated on the page.
    Fix: If partner sharing occurs, state the specific number of partners (e.g., 'We share data with X partners') in the consent banner.

Provenance

Security

Transparency

Level 3 — Advanced

Accessibility

  • known_issues: The statement only vaguely says the site 'is a work in progress' and 'there is always more that can be done' without naming any specific accessibility issues or limitations.
    Fix: List the specific known accessibility problems (e.g., failing WCAG 2.1 AA criteria, non-conformant pages or components) so users know what barriers to expect.
  • remediation_timeline: The statement offers no timeline or dated commitment for resolving accessibility issues, referencing only an aspirational 2025/26 WCAG 2.1 AA compliance goal without a concrete remediation schedule.
    Fix: Add specific target dates by which identified issues will be fixed and commit to a review/update schedule for the statement.
  • feedback_channel: A feedback email (indigo@sfct.org.uk) is provided, but there is no stated commitment on how quickly the site owner will respond.
    Fix: State a clear response commitment, such as acknowledging feedback within a defined number of working days.

Accountability

Interoperability

Security

  • plan_exists: The page covers governance, investment, safeguarding, DEI, and accessibility policies but contains no published incident response plan or security incident policy.
    Fix: Publish a documented incident response plan describing how the Trust identifies, manages, and remediates data or security incidents.
  • notification_commitment: There is no commitment anywhere on the page to publicly notify affected users of significant security or data incidents.
    Fix: Add an explicit statement committing to notify affected individuals and the public when significant incidents occur.
  • timeframe: The page states no timeframe for disclosing incidents to affected users since no incident response content exists.
    Fix: Specify a concrete disclosure timeframe (e.g., notifying affected users within 72 hours of discovering an incident).

Transparency

Responsibility to the Future

  • specific_metrics: The page contains no specific environmental figures such as carbon emissions, energy use, or measurable sustainability targets.
    Fix: Publish quantified environmental metrics (e.g., annual carbon footprint, energy consumption, or emissions reduction targets) alongside the sustainability commitments.
  • hosting_disclosure: The accessibility and about sections mention the website but disclose nothing about the carbon or energy profile of its hosting infrastructure.
    Fix: Add a statement disclosing the website's hosting provider and its carbon or energy profile, ideally noting use of green/renewable-powered hosting.
  • plan_exists: The governance page describes trustees, investment, DEI and safeguarding but contains no published plan for what happens if the organisation fails, winds down, or exits.
    Fix: Publish a wind-down/exit plan describing how the Trust would cease operations, including timelines and responsible parties, on the governance page.
  • data_and_content_fate: The page does not address what would happen to user data or published website content in the event of the organisation closing.
    Fix: Add a statement specifying how user data would be handled and whether website content would be preserved, transferred, or deleted upon closure.
  • custodians_or_mirrors: No custodians, mirrors, or archive partners are identified anywhere on the page for preserving content after an exit.
    Fix: Name a specific custodian or archive partner (e.g., a web archive or SFCT successor entity) responsible for maintaining or mirroring the site's content if the Trust ceases operating.
  • policy_exists: The page references an SFCT DEI Policy and employment practices but contains no published policy specifically addressing worker wellbeing or working conditions.
    Fix: Publish a dedicated worker wellbeing or working conditions policy (or link to one) covering staff welfare on the About page.
  • accountability: The page names accountability for investment (Investment Committee) and safeguarding contacts but does not identify who is responsible for overseeing worker conditions or wellbeing.
    Fix: Name a specific role, committee, or contact responsible for overseeing worker conditions and wellbeing and how staff can raise concerns.