Sense About Science

https://senseaboutscience.org · 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 19/37 (17 failed)
Level 2 — Enhanced 10/27 (16 failed)
Level 3 — Advanced 0/10 (9 failed)

By category

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

Level 1 — Basic

Accessibility

FAIL WCAG 2.1 Level A automated testing
  • 8 WCAG 2.1 Level A violations reported by axe-core: aria-allowed-attr, aria-hidden-focus, aria-input-field-name, aria-required-children, aria-valid-attr-value, image-alt, link-name, nested-interactive.
FAIL Valid semantic HTML structure
  • 8 WCAG 2.1 Level A violations reported by axe-core: aria-allowed-attr, aria-hidden-focus, aria-input-field-name, aria-required-children, aria-valid-attr-value, image-alt, link-name, nested-interactive.
FAIL Text alternatives for images
FAIL Decorative images properly marked

AI & Automation

FAIL AI use policy in place
  • policy_exists: The page describes an AI Week talk and a Responsible Handover Framework but does not present an AI use policy or statement for the organization's own AI use.
    Fix: Publish a clear AI use policy or statement on the site explaining how Sense about Science itself uses AI.
  • scope_clear: The content discusses AI governance generally and a framework for developers, but does not explain what AI is used for by the organization.
    Fix: Add a section specifying the concrete purposes and contexts in which the organization uses AI tools.

Privacy

FAIL No fingerprinting script patterns
  • 1 inline script matched a tracker/ad pattern; first match: ' (function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){ …'.

Security

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

Transparency

Level 2 — Enhanced

Accessibility

Accountability

FAIL Published response timeframes
  • response_timeframe: The page provides contact details but does not publish any response timeframe for inquiries.
    Fix: Add a clear statement on the contact section indicating how quickly users can expect a response (e.g., within 5 business days).
  • specific: Since no timeframe is published at all, there is no specific duration such as days or hours given.
    Fix: Specify a concrete response window in days (e.g., 'We aim to respond within 7 working days') rather than vague language.
FAIL Documented complaints process
  • process_exists: The page only lists an email, phone, and address with a note on abusive messages, but no documented complaints or feedback process is provided.
    Fix: Publish a dedicated complaints/feedback policy page outlining how users can submit concerns and how they will be handled.
  • steps_clear: No steps for making a complaint are described on the page.
    Fix: Provide a clear, numbered set of steps (e.g., who to contact, what information to include, escalation path) for submitting complaints.

AI & Automation

FAIL Published AI use policy (detailed)
  • detailed_scope: No AI policy is present, so the scope of AI use is not detailed on the page.
    Fix: Create an AI policy page that enumerates specific AI systems, use cases, and operational scope.
  • limitations: While the talk references AI harms and missed opportunities generally, the page does not acknowledge limitations of AI systems used by the organization.
    Fix: Include explicit statements about known limitations, risks, and failure modes of any AI systems the organization deploys.
  • safeguards: The page mentions a Responsible Handover Framework conceptually but does not describe safeguards or quality controls governing the organization's AI use.
    Fix: Document specific safeguards such as human review, quality assurance checks, and escalation procedures for AI outputs.
FAIL AI-assisted content clearly marked
  • marking_policy: The page discusses a Responsible Handover Framework for AI tools but does not state any policy for marking AI-assisted content on the site.
    Fix: Publish a clear policy stating how any AI-assisted content on the site will be labelled or disclosed to readers.
  • consistent: No AI content markings are visible on the page, and without a policy there is no evidence of consistent application.
    Fix: Apply a consistent visible label or disclosure to every piece of AI-assisted content across the site and document the convention.
FAIL Human oversight of AI documented
  • oversight_exists: While the page discusses AI governance externally, it does not document human oversight of AI outputs used on this website.
    Fix: Add a statement describing how humans review AI outputs before they are published on the site.
  • review_process: No review or approval workflow for AI-generated content is described on the page.
    Fix: Document the specific review and approval steps (e.g., editor sign-off) that AI-generated content must pass through before publication.
  • accountability: The page names Dr Sameh ElBadry as a speaker but does not identify anyone accountable for AI-generated content on the website.
    Fix: Name a specific role or person (e.g., editorial lead) responsible for AI-generated content and include their contact details.

Interoperability

Privacy

FAIL Data collection limited to necessity
  • necessity: The policy does not explicitly state that data collection is limited to what is necessary; it only lists categories and purposes without a data minimisation statement.
    Fix: Add an explicit statement that Sense about Science only collects the minimum personal data necessary to deliver each stated service.
FAIL Published data retention periods
  • retention_stated: The policy contains no section describing how long personal data is retained before deletion.
    Fix: Add a 'Data retention' section specifying how long each category of personal data (e.g., donor records, newsletter subscriptions) is kept.
  • specific: Because no retention periods are stated at all, there are no specific time periods provided.
    Fix: Specify concrete retention durations such as 'donor records kept for 7 years for tax purposes' and 'newsletter data kept until unsubscribe.'
FAIL No dark patterns in consent flows
  • equal_choices: The page provides no visible accept/reject controls for cookies, instead directing users to adjust browser settings, which makes rejection less accessible than implicit acceptance.
    Fix: Implement a cookie consent banner that presents 'Accept' and 'Reject' buttons with equal visual prominence before any non-essential cookies are set.
  • no_forced_consent: The page indicates analytics and third-party cookies are set without offering a granular opt-in, effectively bundling non-essential cookies with site use.
    Fix: Offer granular, unbundled consent options allowing users to opt in separately to analytics, third-party, and embedded-content cookies, with no non-essential cookies set prior to consent.
FAIL Cookie banner partner disclosure
  • banner_present: No cookie or consent banner is visible; the page only contains a passive footer note stating 'By using this website you imply consent to its use of HTML cookies.'
    Fix: Implement a visible cookie consent banner that allows users to actively accept, reject, or configure cookies before non-essential cookies are set.
  • partner_sharing_mentioned: The on-page consent copy only mentions HTML cookies generally and does not disclose any data sharing with third-party partners.
    Fix: Add clear disclosure in the banner and privacy notice identifying any third-party partners with whom data is shared and the purposes of that sharing.
  • partner_count_specific: No partner sharing is disclosed and no numeric count of partners is stated anywhere on the page.
    Fix: If third-party partners receive user data, state the exact number of partners (e.g., 'shared with X partners') and link to a full list in the consent interface.

Provenance

Security

Transparency

FAIL Named responsible person in contact
  • role_clear: While Mike Hudson's background is described, no specific role or authority is stated for handling enquiries at Sense about Science, and the generic 'hello@' inbox has no named owner or defined remit.
    Fix: Add a named staff member or role (e.g., 'Enquiries Manager' or 'Communications Lead') alongside the contact email to clarify who handles enquiries and their authority.
FAIL Substantive statement of purpose
  • mission_clear: The page describes the Knowbot tool but does not articulate Sense about Science's overall organisational mission or editorial approach.
    Fix: Add a concise statement of Sense about Science's mission and editorial approach on this page, or link prominently to a dedicated 'Who we are' mission page.
FAIL Governance structure disclosed
  • governance_exists: The page describes Knowbot and its partner foundation but does not outline any governance or editorial structure for Sense about Science or oversight of the AI tool.
    Fix: Add a section describing the governance or editorial oversight structure, including how content and the Knowbot AI are reviewed and managed.
  • roles_clear: Aside from a brief bio of Mike Hudson, the page does not identify key organisational roles or responsibilities such as trustees, editors, or AI oversight leads.
    Fix: Include a clear list of key roles and responsibilities (e.g., editorial lead, trustees, AI governance contact) or link directly to the Team and Trustees pages from this page.
FAIL Algorithm explanation if applicable
  • impact_clear: The page describes what Knowbot does but does not clearly describe the impact of its algorithmic decisions on users, such as risks of inaccurate or misleading answers beyond a brief 'AI isn't perfect' remark.
    Fix: Add a section explicitly describing how Knowbot's outputs may affect users (e.g., potential for errors, hallucinations, or bias) and what users should do to mitigate those impacts.
FAIL Annual data practices statement
  • annual_statement: The page provides no evidence of a regular or periodic review of data practices, only a brief cookie consent notice.
    Fix: Publish a privacy statement that explicitly notes an annual or periodic review cycle and link to it from this page.
  • dated: No date, version, or 'last updated' indicator is provided for any data practices or privacy statement on this page.
    Fix: Add a clearly visible 'Last updated' date or version number to the privacy/data practices statement linked from the footer.

Level 3 — Advanced

Accessibility

FAIL Published accessibility statement
  • statement_exists: The page is about the Knowbot AI tool and contains no dedicated accessibility statement, though the footer references an 'Accessing this website' link that is not present on this page.
    Fix: Publish a dedicated accessibility statement page describing the site's conformance to standards such as WCAG 2.1 AA and link it prominently.
  • known_issues: There is no acknowledgement of any known accessibility issues or limitations anywhere on this page.
    Fix: Add a section to the accessibility statement listing known accessibility barriers users may encounter and the parts of the site affected.
  • remediation_timeline: The page provides no timeline or commitment for remediating accessibility issues.
    Fix: Include target dates or a stated commitment for fixing identified accessibility issues within the accessibility statement.
  • feedback_channel: While a general contact email (hello@senseaboutscience.org) is provided, there is no accessibility-specific feedback mechanism with a stated response commitment, and the page notes abusive messages will not receive a response rather than committing to reply.
    Fix: Provide a dedicated accessibility feedback contact with a clear commitment to respond within a specified timeframe.

Accountability

FAIL Published moderation policies
  • policy_exists: No moderation policy is published; the page only notes that abusive messages will not receive a response.
    Fix: Publish a dedicated moderation policy page outlining rules for user/community interactions across platforms.
  • criteria_clear: Criteria are limited to a vague mention of 'abusive, rude or derogatory' messages without definitions or examples.
    Fix: Define specific moderation criteria with examples of prohibited content and clear thresholds for action.
  • enforcement: The page does not describe how moderation decisions are made, who enforces them, or any appeal process.
    Fix: Document the enforcement workflow, including who reviews content, what actions are taken, and how users can appeal.

Interoperability

Security

FAIL Incident response plan published
  • plan_exists: The page describes the Knowbot AI tool and its partner but contains no published incident response plan or security policy.
    Fix: Publish a dedicated incident response plan or security policy page outlining how the organisation detects, manages, and remediates security incidents.
  • notification_commitment: There is no statement committing to publicly notify users of significant security or data incidents.
    Fix: Add an explicit commitment to publicly notify affected users and stakeholders when a significant incident occurs.
  • timeframe: The page provides no timeframe for disclosing incidents to affected users.
    Fix: Specify a concrete disclosure timeframe (e.g., notifying affected users within 72 hours of discovering an incident).

Transparency

FAIL Algorithmic decision criteria published
  • criteria_published: The page does not publish the specific criteria Knowbot uses to generate or rank its answers, only stating it draws from the website's content.
    Fix: Publish a description of the criteria Knowbot uses to select, rank, and generate answers (e.g., retrieval method, source selection rules, model used).
  • weighting: There is no explanation of how Knowbot weights or prioritises sources or criteria when producing responses.
    Fix: Add details on how Knowbot prioritises content (e.g., recency, relevance scoring, source authority) when generating answers.
  • auditable: The page lacks technical detail—such as the underlying model, data pipeline, evaluation metrics, or governance—needed for external audit or review.
    Fix: Provide an auditable technical summary including the model provider, training/retrieval data scope, testing methodology, and a contact or process for independent review.
FAIL Open source code or tech docs
  • open_source: No link to source code for Knowbot or the website is provided on the page.
    Fix: Publish or link to a public repository (e.g., GitHub) for Knowbot or the site where feasible, or state the licensing/source-availability position.
  • tech_docs: The page describes Knowbot in general terms but provides no technical documentation about the AI model, data handling, or retrieval approach.
    Fix: Add or link to technical documentation detailing Knowbot's underlying model, data sources, retrieval methodology, and privacy/safety safeguards.

Responsibility to the Future

FAIL Environmental / sustainability disclosure
  • disclosure_exists: The page describes an Environment and Health Atlas project mapping diseases but contains no published environmental impact or sustainability disclosure for the organization or its website.
    Fix: Publish a dedicated environmental or sustainability statement describing the organization's and website's environmental impact and reduction commitments.
  • specific_metrics: The page provides no specific figures on carbon emissions, energy use, or other environmental metrics.
    Fix: Add quantified environmental metrics such as annual carbon emissions or energy consumption to the disclosure.
  • hosting_disclosure: There is no mention of the carbon or energy profile of the website's hosting infrastructure, only a website credit to 'Surface Impression'.
    Fix: Disclose the hosting provider's energy source or carbon profile, for example whether the site is hosted on renewable-powered or green-certified infrastructure.
FAIL Succession and continuity plan
  • plan_exists: The page describes the Knowbot AI partnership and organisation details but contains no published plan for what happens if the organisation fails or exits.
    Fix: Publish a succession or wind-down plan explaining what would happen to services and operations if Sense about Science ceases to operate.
  • data_and_content_fate: The page does not address what happens to user data or published content in the event of organisational failure or exit.
    Fix: Add a section specifying how user data and published website content would be preserved, transferred, or deleted if the organisation shuts down.
  • custodians_or_mirrors: No custodians, mirrors, or archive partners are identified anywhere on the page.
    Fix: Name specific custodians, mirror hosts, or archival partners (e.g., a web archive service) responsible for preserving content and data after an exit.
FAIL Worker wellbeing policy
  • policy_exists: The page is about the Knowbot AI tool and its partner foundation, containing no published policy on worker wellbeing or working conditions.
    Fix: Publish a dedicated worker wellbeing or working conditions policy and link to it from the site.
  • specific_commitments: The content mentions vacancies and internships only in navigation but includes no specific commitments on pay, hours, mental health, or benefits.
    Fix: Add explicit commitments covering pay, working hours, mental health support, and employee benefits within a wellbeing policy.
  • accountability: The page identifies no person, team, or oversight body responsible for worker conditions, referencing only general contact details and trustees in navigation.
    Fix: Name a specific role or committee accountable for overseeing worker wellbeing and describe how staff can raise concerns.