Accessibility statement

How accessible TruIntel is today, what we know is not yet right, and how to reach us.

Accessibility statement for TruIntel

This statement applies to truintel.co.za and the TruIntel live classroom, booking, messaging and dashboard features. TruIntel is operated by TW Technology Solutions (Pty) Ltd, 74 Rockdale Avenue, Westville, Durban, 4018.

We want as many people as possible to be able to use this platform. That means you should be able to:

  • change colours, contrast levels and fonts using your browser or device settings, or the options under Settings, Accessibility;
  • zoom in up to 400 percent without the text spilling off the screen;
  • navigate the whole platform using a keyboard or speech recognition software;
  • use it with a screen reader such as NVDA, JAWS, VoiceOver or TalkBack.

We have written the platform in plain language. The live classroom is designed to show automatic captions once the video service is switched on for your institution.

How accessible this platform is

Compliance status. This platform is partially compliant with the Web Content Accessibility Guidelines (WCAG) version 2.2 at Level AA, because of the non-compliances listed below. We have not yet had an independent audit, and the signed-in dashboard and classroom pages have not yet been through our full screen-reader test matrix, so this statement describes our target and our own checks, not a verified claim of conformance.

Non-accessible content

  1. Freehand ink on the whiteboard has no text alternative. This fails WCAG 2.2 success criterion 1.1.1 (Non-text content). Mentors are asked to describe what they draw. We do not plan to add ink recognition; we are looking at a keyboard-navigable list of typed board items instead.
  2. Live captions are automatic and can contain errors. This partially meets success criterion 1.2.4 (Captions, live). Captions depend on the speech recognition of the video service and the browser; there is not yet a way for a human captioner to feed corrected text into a session.
  3. Session recordings do not yet carry edited captions or a transcript. Where a session is recorded with both parties' consent, the recording has no edited captions, which fails success criterion 1.2.2 (Captions, prerecorded).
  4. Signed-in pages are still being checked. Our automated checks found issues on the dashboard, classroom, messaging and payment pages, mostly missing form labels and skip links, that are being fixed in the current release. Until they land, some controls on those pages will read poorly with a screen reader.

Content not within scope

  • The PayPal checkout, which opens in PayPal's own pages.
  • Mentor introduction videos hosted on Loom or YouTube, and other material mentors upload, which we do not control.
  • The Microsoft and Google sign-in pages used to connect a calendar.

Disproportionate burden

None claimed.

What has been done

  • Every public page has a skip link, a single main landmark, one main heading and ordered headings, and declares its language as South African English.
  • Every form field has a label; required fields are marked in text; errors are announced, linked to the field and focus moves to the first problem.
  • A visible focus ring of at least 3 pixels on every control in both themes, and controls of at least 24 by 24 pixels.
  • Colour tokens checked at 4.5:1 for text in the light and dark themes, plus a high-contrast option in Settings.
  • Reduced motion is honoured from your operating system and from Settings; text size can be raised to 150 percent; an easier-reading option widens letter and word spacing and removes italics.
  • Two permanent live regions carry status messages and alerts to screen readers, including every toast and the page title on arrival.
  • The Tru-We chat opens as a dialog that keeps focus, closes on Escape and returns focus to where you were; replies land in a live log.
  • Optional voice guidance and sound cues, off by default, for sighted and low-vision users who want spoken confirmation of what changes on the page.
  • Windows contrast themes are respected: focus rings and control borders stay visible.

Feedback and contact

If you need information in a different format, or you find something you cannot use, email quickfix@tw-tech.co.za or call 031 279 5700. Tell us the page, what you were trying to do, and the browser and assistive technology you use. We aim to reply within 5 working days.

Enforcement

If you are not satisfied with our response, you may lodge a complaint with the South African Human Rights Commission or approach an Equality Court under the Promotion of Equality and Prevention of Unfair Discrimination Act, 2000.

Technical information

TW Technology Solutions is committed to making TruIntel accessible in line with the Constitution of South Africa (section 9), the Promotion of Equality and Prevention of Unfair Discrimination Act, 2000, and the DHET Strategic Policy Framework on Disability for the Post-School Education and Training System (2018). Our technical target is WCAG 2.2 Level AA.

What we are doing to improve accessibility

  1. Finish the signed-in page fixes found by our checks, then run the manual test matrix: keyboard only; NVDA with Chrome and Firefox on Windows; VoiceOver on iOS Safari; TalkBack on Android Chrome; 200 and 400 percent zoom; Windows contrast themes.
  2. Add a path for a human captioner to feed corrected captions into a live session.
  3. Add a keyboard-navigable list of typed whiteboard items with text alternatives.
  4. Publish an Accessibility Conformance Report on the VPAT 2.5 template, WCAG edition.

We will add a date to each item here as it is scheduled, and review this statement at least once a year and on every major release.

Preparation of this statement

Prepared on
28 September 2026
Last reviewed on
28 September 2026
Last tested on
28 September 2026, by TW Technology Solutions
Prepared with
The TruIntel accessibility lint (an automated check of images, names, labels, landmarks, headings and focus order on every page), a contrast check of every colour token pair in both themes, and manual keyboard checks in a Chromium browser on the public pages, sign-in, sign-up and settings. Screen-reader and mobile testing has not yet been completed.

This statement follows the W3C minimum for an accessibility statement (commitment, standard, contact and known limitations) and the itemised layout of the UK public-sector model statement.