ThingLink is a service which allows you to add interactive content to images and videos, including 360-degree material. The content is added using tags.
ThingLink offers two parallel user interfaces:
- Graphical user interface (default view) – Visual, interactive view
- Accessibility view – Text-based option specifically designed for users of assistive technologies
The accessibility view is identified by the word ‘accessibility’ included in the web address:
- https://app.widgets.thinglink.com/accessibility/*
- https://www.thinglink.com/view/scenario/*/accessibility
- The asterisk ( * ) stands for a content-specific numeral identifier, for example: https://app.widgets.thinglink.com/accessibility/1205257932048957445
ThingLink complies partly with the accessibility requirements. Using ThingLink content should be possible in most cases. However, creating ThingLink content is not possible with keyboard only.
This statement covers content viewing and creation in ThingLink’s browser version, not the mobile application.
Students and other users: How to use ThingLink content
- General
- Understandable
- Use with limited vision or if you are a screen reader user
- Keyboard navigation
- Use without hearing or with hearing loss
- Flashing content
This section describes what you should know about using ThingLink content and any accessibility deficiencies.
General
The accessibility issues you encounter usually relate to the graphical user interface for ThingLink content. Teachers and other content producers are responsible for the consistency and logic of their content. Also note that the button for accessing the accessibility view may not be displayed by default. Establish a link in accordance with the instructions above or ask the content producer for the link.
Understandable
- Tags and viewports are not always in logical order, which may make it difficult to access content specifically when using a keyboard or a screen reader (WCAG 1.3.2).
- The structure of larger wholes where several ThingLink content elements have been connected by links may feel inconsistent (WCAG 3.2.3).
- In the graphical user interface, the navigation buttons Back and Home are always located in the top left-hand corner.
Tip: Start by reading any introductory text or instructions included in content. They will help you navigate the content.
Use with limited vision or a screen reader
If you can see the screen content, you can usually use ThingLink content effortlessly in both the default view and the accessibility view. You can also use Microsoft’s integrated Immersive Reader to listen to the text content of individual tags.
If you are visually impaired, consider the following potential problems:
- Contrast may be insufficient between the text and background or in user interface elements (WCAG 1.4.3, 1.4.11).
- Colour may be the only means of conveying information (WCAG 1.4.1).
- Tags may be transparent or have a weak contrast ratio, making them difficult to detect.
These issues usually depend on the content producer’s choices.
For screen reader users: Tests have shown that screen readers can usually access content in both the default and accessibility views. However, please note the following:
- The reading sequence does not necessarily match the visual sequence (WCAG 1.3.2).
- Text alternatives (alt-text) for images may be missing or inappropriate (WCAG 1.1.1).
- Videos without accessible audio tracks may lack text alternatives (WCAG 1.2.1).
Tip: Advance information of the content’s logic and purpose as well as the tools (including screen reader software) used to test it will make its use easier.
Keyboard navigation
ThingLink has its own instructions for keyboard use (thinglink.com). Consider the following potential issues:
- The reading sequence does not necessarily match the visual sequence (WCAG 1.3.2).
- When exiting Immersive Reader in certain browsers, the open component cannot be closed using the keyboard, trapping the user (WCAG 2.1.2). In testing, this issue did not occur in Chromium browsers (Chrome and Edge).
- In certain content, video player controls cannot be used with a keyboard. At times, the info panel and its content cannot be accessed using a keyboard either (WCAG 2.1.1).
Use without hearing or with hearing loss
If the content producer has created their ThingLink content in accordance with the accessibility principles, you should not encounter any accessibility issues. Potential issues:
- Videos may be missing captions, or the captions may be deficient or incorrect (WCAG 1.2.2).
- Videos or audio files may be missing text alternatives (WCAG 1.2.1).
Flashing content
Content may contain flashes that can trigger migraines or epileptic seizures (WCAG 2.3.1).
ThingLink does not automatically check whether videos contain flashing that exceeds the threshold of more than three times per second. If content producers have followed the instructions, a clear warning will be given about flashing content.
Content creation in ThingLink cannot be done using only a keyboard
Creating content in ThingLink requires a mouse or touchpad (WCAG 2.1.1). In practice, you need a pointing device to position tags (in individual pieces of content) and blocks (in scenarios), and to create the necessary connections.
Teachers and other content creators: please consult separate instructions on how to create accessible ThingLink content. These guidelines help you to produce ThingLink materials that are as accessible as possible.
Information about this statement
This statement was published in September 2025.
This statement was updated 3.6.2026.
The latest version of this accessibility statement was authored collaboratively by the University of Helsinki, the University of Eastern Finland, the Metropolia University of Applied Sciences and the University of Oulu. Their accessibility specialists and ThingLink experts from the University of Helsinki and the University of Eastern Finland surveyed ThingLink’s compliance with the Act on the Provision of Digital Services (306/2019) using primarily the Edge (version 147.0.3912.72) Firefox browsers (version 140.5.0esr) as well as the VoiceOver screen reader on macOS. The mobile version has not yet been tested.
The statement also draws from ThingLink’s accessibility statement for the accessibility view.
Did you notice an accessibility issue in ThingLink?
Regulatory authority
A response to an email sent to thinglink@oulu.fi may take up to 14 days. If you are not satisfied with the response or do not receive a response within two weeks, you can file a complaint with Traficom. Traficom’s website provides detailed information about your rights as a user of our service.
Regulatory authority’s contact information
Finnish Transport and Communications Agency Traficom
Digital Accessibility Supervision Unit
https://www.webaccessibility.fi
saavutettavuus@traficom.fi
telephone switchboard 029 534 5000