Accessibility Statement

Prepared: August 2026 · Reviewed every 6 months

1. Our commitment

This accessibility statement applies to the Vecorra platform, operated by Trillectra AI Ltd — including the public website, the talent and student portals, and our timed exams, assessments and practical labs.

We want as many people as possible to be able to use Vecorra. That means you should be able to navigate the whole platform with a keyboard alone, use it with a screen reader or other assistive technology, zoom to 200% without losing content, and switch off animation via your operating system's reduce-motion setting. Because our platform decides who gets seen by employers, we treat accessibility of our exams and assessments as a fairness requirement, not a nice-to-have.

2. Conformance status

The Vecorra platform is partially conformant with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. "Partially conformant" means most of the platform meets the standard, but some parts do not yet. We audited the platform against WCAG 2.2 AA in August 2026 and fixed 26 issues; the known remaining limitations are listed below.

Known limitations

  • Pop-up error notifications are announced by screen readers politely (after the current announcement finishes) rather than immediately. The message is not lost, but you may hear it with a short delay.
  • In exam and quiz answer lists, the arrow keys move focus between options but do not change your selection — press Enter or Space to select an answer. This is deliberate, so a stray key press can never silently change a saved exam answer, but it differs from the standard keyboard pattern some screen-reader users expect.
  • Lesson content is written by course authors, so heading levels within a lesson may occasionally be skipped. Every lesson page still has a single main heading and a consistent structure.
  • Some compact controls (such as chat suggestion chips and session "Book" buttons) meet the WCAG minimum target size of 24 pixels but are smaller than the 44-pixel size recommended as best practice, so they can be fiddly on touch screens.
  • A small amount of amber-coloured large text and decorative accents meets the 3:1 contrast minimum for large text but sits below the 4.5:1 ratio we apply to standard text.
  • The JupyterLab environment used for hands-on practice and practical exams is third-party software; its accessibility is improving but imperfect (see section 5).

3. What we have done

Following a code-level audit against WCAG 2.2 AA (August 2026), we made the following improvements across the platform:

  • Keyboard operability: every interactive element — including expandable job and application cards, course module accordions, filters and the chat assistant — can be reached and operated with the keyboard, with a clearly visible focus indicator throughout.
  • Screen-reader-operable timed exams: the exam timer is announced at sensible intervals (not every second), answer options expose their selected state, the question navigator reports answered and flagged questions, and the submission confirmation behaves as a proper dialog.
  • Reduced motion: all animation respects your operating system's "reduce motion" setting.
  • Colour and contrast: text colours, status colours and focus indicators were adjusted to meet contrast minimums, and no information is conveyed by colour alone — status and results are always available as text.
  • Structure and labels: pages have consistent landmarks and heading structure, form fields are properly labelled, and decorative graphics are hidden from assistive technology.

4. Reasonable adjustments

If a disability or health condition means standard exam conditions would disadvantage you, you can request extra time as a reasonable adjustment under the Equality Act 2010:

  • What is available: 25% extra time (1.25×) or 50% extra time (1.5×) on all timed exams, assessments and interviews — including certification theory exams and practical labs.
  • How to request it: in your account, go to Profile → Access & adjustments and submit a request. You can add a short note describing what would help — please do not include medical details or diagnoses; we only need to know what would help, not why.
  • What happens next: an administrator reviews your request and you will see the decision on the same card. Once approved, the extra time applies automatically to every timed activity — you do not need to do anything before each exam.
  • Confidentiality: adjustments are never visible to employers. Your results are presented identically whether or not an adjustment was in place.

If extra time is not the adjustment you need, contact us using the details in section 6 and we will discuss alternatives.

5. Using JupyterLab with assistive technology

Hands-on practice and the practical exam run in JupyterLab, a third-party coding environment. It is largely keyboard operable:

  • Tab / Shift+Tab move between the main areas of the interface (file browser, notebook, menus).
  • Enter starts editing the selected notebook cell; Esc returns to command mode, where single-key shortcuts operate on whole cells.
  • Ctrl+Shift+C opens the command palette, from which every command can be run by typing its name — often the fastest route when a control is hard to reach.

JupyterLab 4's accessibility is actively improving, but it is not yet fully conformant — in particular, some screen-reader interactions with notebook cells and complex output remain imperfect. If you use assistive technology and hit a barrier in JupyterLab, please request an adjustment (section 4) or contact us (section 6) — barriers in the environment are exactly what the adjustments process is for.

6. Reporting accessibility problems

If you find a problem not listed on this page, or you think we are not meeting accessibility requirements, email m.fayemiwo@trillectraai.co.uk. Please tell us the page or activity where you hit the problem and the assistive technology you were using, if any. We aim to respond within 5 working days, and sooner where an exam or assessment deadline is involved.

7. Preparation of this statement

This statement was prepared in August 2026, based on a code-level audit of the platform against WCAG 2.2 Level AA carried out in August 2026. We review this statement, and re-test the platform's key user journeys, every 6 months.

Return to the Vecorra homepage