Accessibility Statement

Last Updated: April 27, 2026

Torbalevu is committed to ensuring that its online educational platform and all associated digital content are accessible to the widest possible audience, including individuals with disabilities. We continuously work to improve the accessibility of our services and to provide an equitable learning experience for all users, regardless of ability or the technology they use to access our content.

Our Commitment

We believe that access to quality education is a fundamental right. Our platform is designed and maintained with accessibility as a core consideration, not an afterthought. We strive to conform to recognized international accessibility standards and to remove barriers that may prevent any learner from fully participating in our courses and educational resources.

Our accessibility efforts are ongoing. We regularly audit our platform, incorporate feedback from users, and update our content and technical infrastructure to improve accessibility over time.

Standards and Guidelines

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, as published by the World Wide Web Consortium (W3C). These guidelines define how to make web content more accessible to people with a wide range of disabilities, including:

Visual disabilities — including blindness, low vision, and colour blindness.

Hearing disabilities — including deafness and hard of hearing.

Motor and physical disabilities — including limited fine motor control and use of assistive input devices.

Cognitive and neurological disabilities — including learning disabilities, attention disorders, and memory impairments.

WCAG 2.1 is organized around four core principles. Accessible content must be:

Principle	Description
Perceivable	Information and user interface components must be presentable in ways all users can perceive.
Operable	Interface components and navigation must be operable using various input methods, including keyboard-only.
Understandable	Information and the operation of the user interface must be understandable to all users.
Robust	Content must be robust enough to be interpreted reliably by a wide variety of user agents and assistive technologies.

Accessibility Features

Navigation and Structure

Our platform is built with a clear, consistent page structure using semantic HTML. All pages include logical heading hierarchies that allow screen reader users to efficiently navigate content. Keyboard navigation is supported throughout, and focus indicators are visible at all times to assist users who do not use a pointing device.

Skip navigation links are provided to allow users to bypass repetitive content and move directly to the main learning material on each page.

Text and Readability

All text content is presented at a minimum contrast ratio that meets WCAG AA requirements. Users may adjust text size using standard browser controls without loss of content or functionality. We avoid the use of text embedded within images where possible. Where such images exist, equivalent text alternatives are provided.

Images and Visual Content

All meaningful images include descriptive alternative text. Decorative images that do not convey information are marked in a way that causes assistive technologies to ignore them. Diagrams, charts, and infographics used in course content are accompanied by descriptive captions or text equivalents.

Video and Audio Content

Where video content is provided, we endeavour to include captions and, where appropriate, audio descriptions. Transcripts are made available for audio-only content. We do not use audio or video that plays automatically without user initiation.

Forms and Interactive Elements

All form fields are clearly labelled. Error messages are descriptive and identify the specific field requiring correction. Required fields are clearly indicated. Interactive elements such as quizzes and assessments are designed to be operable with a keyboard and compatible with common assistive technologies.

Links

All hyperlinks include descriptive, meaningful text that makes their purpose clear out of context. We avoid using vague link text such as "click here" or "read more" without additional context.

Colour and Visual Design

Colour is never used as the sole means of conveying information, indicating an action, or distinguishing visual elements. Our design system maintains sufficient contrast between text and background across all components.

Assistive Technology Compatibility

Our platform is tested for compatibility with widely used screen readers and other assistive technologies. We use ARIA (Accessible Rich Internet Applications) attributes where standard HTML does not provide sufficient semantic information, taking care to apply ARIA only where it adds meaningful accessibility value.

Known Limitations

While we strive for full conformance with WCAG 2.1 Level AA, some areas of our platform may not yet fully meet these standards. This may include certain third-party content or embedded tools that are provided by external vendors over whom we have limited control. We actively work with our third-party providers to encourage accessible design and to seek alternatives where accessibility cannot be adequately achieved.

We are transparent about these limitations and are committed to resolving them as resources and technical possibilities allow. We document known issues and prioritize remediation based on impact to users.

Assistive Technologies Supported

Our platform is designed and tested with the following types of assistive technologies in mind:

Screen readers — software that reads on-screen content aloud, including but not limited to NVDA, JAWS, and VoiceOver.

Screen magnification software — tools that enlarge on-screen content for users with low vision.

Voice recognition software — tools that allow users to control their device and navigate content by voice.

Switch access devices — hardware allowing users with limited motor control to navigate using one or more switches.

Keyboard-only navigation — full site operability without the use of a mouse or touch input.

Third-Party Content

Our platform may contain links to or embed content from third-party services. While we make reasonable efforts to use accessible third-party components, we cannot guarantee the accessibility of external sites or independently operated services. We encourage users who encounter accessibility barriers in third-party content to contact those providers directly.

Feedback and Contact

We welcome feedback on the accessibility of our platform. If you encounter any accessibility barriers, require content in an alternative format, or need assistance accessing any part of our service, please contact us. We are committed to responding promptly and to providing reasonable accommodation wherever possible.

When contacting us regarding an accessibility concern, please describe the barrier you encountered, the page or feature affected, and the assistive technology or browser you were using, if applicable. This information helps us investigate and address the issue more effectively.

We aim to acknowledge accessibility-related enquiries within 2 business days and to provide a substantive response or resolution within 10 business days.

Formal Complaints

If you are not satisfied with our response to an accessibility concern, you may submit a formal complaint by contacting us in writing at the address provided above. We will review all formal complaints and respond in a timely manner, documenting both the concern raised and the steps taken to address it.

Ongoing Improvement

Accessibility is an ongoing process. We conduct periodic reviews of our platform, including both automated testing and manual evaluation by team members with awareness of accessibility requirements. We incorporate user feedback as a critical component of our accessibility programme.

We are committed to training our content creators, developers, and support staff on accessibility best practices so that accessibility considerations are embedded in all phases of our product development and content creation workflows.

This statement is reviewed and updated regularly to reflect the current state of our platform and our progress toward full accessibility conformance.

Technical Specifications

Our platform relies on the following technologies for conformance with WCAG 2.1:

HTML5 — for semantic page structure.

CSS3 — for visual presentation that does not rely on colour alone for meaning.

WAI-ARIA — for enhanced semantics on dynamic and interactive components.

JavaScript — used in a way that does not prevent access for users who rely on assistive technologies or who have scripting limitations.

Our platform has been tested using current versions of major browsers including Chrome, Firefox, Safari, and Edge, in combination with leading assistive technologies on both desktop and mobile operating systems.