ThingLink accessibility statement

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 have no trouble seeing 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.

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. 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 the Chrome and Edge browsers.
• 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 producers are responsible for ThingLink content. You must be aware of your responsibility and make conscious choices for accessibility. The teaching media team supports the creation of accessible ThingLink content.

NB! Content production in ThingLink is practically impossible without a mouse or touchpad (WCAG 2.1.1). In practice, you need a pointer device to be able to place tags (in individual content) and blocks (in scenarios) as well as to establish connections.

1. Offer access to the accessibility view and instruct users

ThingLink automatically creates a separate accessibility view, for which a button will be displayed in the top right-hand corner of the content. In addition, follow these steps:

1. Add a link to the accessibility view to a prominent location (such as the content publication page or the relevant learning environment). Also remember to provide links to any other language versions.
2. Inform users of the following before they open the content or, at the latest, at the beginning of the content:
   • Purpose and context of the content
   • Content navigation: linear navigation, optional paths or unrestricted navigation
   • Access to the accessibility view and its direct link
   • Language versions

Tip: ThingLink’s info panel should not be used for instructions, as it comes last in the reading sequence. Instead, create a separate presentation view or info tag that comes first in the sequence.

2. Determine and check the reading and navigation sequence

Logical order is central especially to keyboard and screen reader users.

• Always define the tag sequence, even if content navigation is unrestricted. By default, ThingLink uses the tag creation order (WCAG 2.4.3).
• The accessibility view will be generated automatically in accordance with the settings for ThingLink content. The accessibility view displays the content reading sequence. Check that it makes sense and, if necessary, reorganise the tags (WCAG 1.3.2).
• Name and label tags consistently (WCAG 3.2.4).
• When creating scenarios, ensure blocks are appropriately sequenced and see to any branching paths in the block view.
• In more extensive wholes, plan internal and consistent navigation and tag use in advance (WCAG 3.2.3).

3. Use appropriate contrast and visual choices

• Ensure sufficient contrast between text and background (WCAG 1.4.3, 1.4.11).
• Do not use colours as the only means of conveying information (WCAG 1.4.1).
• Refrain from using transparent or low-contrast tags. Please note that ThingLink’s ready-made tag icons include colour combinations that do not meet the contrast requirements. You can create icons with sufficient contrast.

Such choices support visually impaired users, users who zoom into (magnify) the content, as well as use in challenging lighting conditions.

4. Use appropriate text alternatives and structure

All non-text content must be provided with appropriate text alternatives (WCAG 1.1.1, 1.2.1, 1.3.1, 1.4.5):

• Add text alternatives to images and graphic elements.
• Make sure that the key content of videos and audio files is also available in text format.
• Refrain from using images that contain only text if the same content can be presented as actual text.
• Use headings, lists and links so that they can be understood without visual perception.

5. Provide captions and text alternatives for audio and video content

• Videos with speech or other audio content: Provide accessible captions or a separate text alternative in the language of the video’s audio track (WCAG 1.2.2).
• Audio files: Provide a text alternative in the language of the audio file (WCAG 1.2.1).
• Caption content: In addition to speech, indicate other sounds relevant to understanding, such as [a signal] or [laughter]. If changes in speakers are evident only by listening, indicate it in the captions.
• Media alternatives: Also consider alternative forms, such as screenplays or visual instructions. For hearing-impaired users, these can be easier and faster to use than captions or audio description.

6. Refrain from using flashes that cause seizures

ThingLink does not check for flashes or flashing lights exceeding the photosensitivity threshold in videos. The threshold for harmful flashing is more than three flashes per second (WCAG 2.3.1). Exceeding the threshold can trigger migraines or epileptic seizures.

• If flashing must feature in the content, add a clear photosensitivity warning to both the video link and the beginning of the video.
• Offer alternative content in accessible form, for example, by describing the phenomenon in text form.
• Separate the flashing content into a separate video instead of including it in the longer one.

7. Consider third-party content

If you embed content produced by third parties in ThingLink content, it may not meet accessibility requirements. Choose the necessary content carefully so that everyone can use it.

8. Test and document

• Test the content in both the default view and the accessibility view.
• Test the content with Immersive Reader.
• Describe to users how you have tested the content, including the tools. Example: “Use has been tested in both the default view and the accessibility use on the macOS 26.3.1 operating system, the VoiceOver screen reader and the Firefox 140.8.0esr web browser.”

Accessibility assessment

This accessibility statement applies to the ThingLink service at thinglink.com. The service is managed by the University of Helsinki teaching media team. This statement describes how accessible the service is and how you can provide us with feedback on its accessibility. The statement was drawn up 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 issues in accessibility?

We strive to continuously improve the accessibility of this website. Please contact us if you come across any accessibility issues not described on this page, or if the material you need is inaccessible. You can reach us either by using the Feedback button on the lower right hand corner of this page or by sending e-mail to uni-help@helsinki.fi.

Supervisory authority

The Finnish Transport and Communications Agency Traficom monitors the accessibility of websites and mobile applications of actors within the scope of the Act on the Provision of Digital Services. If you are not satisfied with the response or you do not receive a response within two weeks, you can submit a notification to the Finnish Transport and Communications Agency Traficom’s supervision of digital accessibility. 

Finnish Transport and Communications Agency Traficom
Digital accessibility supervision
www.saavutettavuusvaatimukset.fi
saavutettavuus@traficom.fi
telephone switchboard 029 534 5000

Information on the accessibility statement

The service was deployed on 1 February 2020.
The statement was drawn up on 20 April 2026.
The statement was last updated on 3 June 2026.
Act on the Provision of Digital Services (306/2019) (In Finnish)