EdTechLab

Accessibility statement

Accessibility is treated as part of delivery quality, not a later compliance pass.

This statement covers the public EdTechLab website at edtechlab.co.uk. It explains the standards target, how the site is tested, what accessibility features are currently supported, and how to report an issue.

Target

WCAG 2.2 AA

Public pages are designed against current W3C accessibility guidance.

Last reviewed

11 March 2026

Reviewed during the Phase C content and trust implementation pass.

Feedback

If you have trouble using the website, need information in another format, or want to report an accessibility issue, email hello@edtechlab.co.uk. We aim to respond within 5 working days.

Current support

  • Semantic headings and page landmarks across all public routes.
  • Keyboard-visible focus states and a skip link to the main content area.
  • Descriptive alternative text for product screenshots and key interface images.
  • Responsive layouts tested across mobile, tablet, and desktop viewports.
  • Captions track and transcript summary for the EngagedLab walkthrough video.
  • Reduced-motion support for animated decorative elements.

How the site is tested

Accessibility checks combine automated and manual review. The current public pages are checked with automated accessibility assertions in Chromium, responsive browser checks across Chromium, Firefox, WebKit, and Edge where available, and manual keyboard navigation review on the core site routes.

The review also includes page-title, heading, canonical, structured-data, and broken-link validation so that new content does not erode the underlying accessibility and content quality baseline.

Scope and limitations

The public site is designed to stay simple enough to inspect and improve.

As of 11 March 2026, EdTechLab is not aware of any critical accessibility failures on the public website routes listed in the current site map. That is not a claim of perfection. New content, browsers, and assistive-technology combinations can surface issues over time, so this statement is reviewed whenever major content or design changes are published.

Where a limitation is identified, the aim is to reproduce it, assess user impact, and fix it in the main site code rather than treat the issue as a documentation problem.

Content owners

New pages are reviewed before publish rather than patched retroactively.

Video content

Walkthrough media includes captions support and a text transcript summary on-page.

Support route

Accessibility issues can be reported directly through the main lab inbox.

Related trust pages

Accessibility sits alongside privacy, security, and honest product proof.

The public site keeps trust information visible: data handling in the privacy policy, platform and sub-processor details on the Security & Trust page, and product evidence through walkthroughs, case studies, and Lab Notes.