EdTechLab

For university digital teams

Research-ready infrastructure without enterprise-vendor sprawl.

Digital and IT teams often inherit the risk when a research or teaching platform is inaccessible, weak on governance, or difficult to support. EdTechLab approaches that problem as infrastructure design rather than launch-only product polish.

What matters first

Hosting boundaries, accessibility, operational support, and whether the data model stands up to institutional review.

Useful standards frame

WCAG 2.2, UK GDPR, FAIR, xAPI, and 1EdTech standards where they are relevant to the workflow.

Common review questions

  • Can the platform explain what data is captured, why, and how it remains interpretable over time?
  • Are accessibility requirements visible in the delivery workflow or treated as a later remediation task?
  • Does the export, API, or integration path respect existing institutional systems?
  • Can the implementation survive version changes without destroying comparability or supportability?

Where EdTechLab fits

EdTechLab is useful when a team needs research-aware delivery quality without pretending that a generic SaaS category solves every institutional constraint. The work usually sits between procurement review, architecture judgment, workflow redesign, and product proof.

Evaluation checklist

Inspect the system underneath the demo.

Evidence model

Event definitions, metadata, provenance, and versioning should be explicit.

Accessibility baseline

Keyboard use, focus states, media alternatives, and semantic structure should already be visible in the live workflow.

Operational fit

Export routes, access control, support expectations, and implementation ownership should be clear before adoption.

Governance posture

Data minimisation, retention, provider boundaries, and incident routes should be documented.