Website accessibility

This accessibility statement pertains to the website of the University of Eastern Finland available at https://www.uef.fi. It was updated on 14 April 2026. 

The accessibility of the website has been assessed by a third party. In addition, we at the University of Eastern Finland have also reviewed the website. Regional State Administrative Agency of Southern Finland has also reviewed the website's accessibility during the summer of 2023.

The uef.fi website was published in 2009. The previous major redesign of the website took place in 2015, and in 2021 it was moved onto a new publishing platform and the contents were reorganised. The accessibility requirements have guided the layout design of and the content production for our new website.

All UEF websites, mobile applications and related content must be accessible. Accessibility in a digital environment means that as many people as possible are able to use the digital services provided despite user, situation or technology specific differences. The accessibility requirements are based on the Act on the Provision of Digital Services and on the EU’s Web Accessibility Directive. 

Accessibility status of digital services

Partially compliant with the Web Content Accessibility Guidelines (WCAG) version 2.1 AA standard. 

Non-accessible content

Due to the large number of content creators, and the time required to instruct and train them, some content on our website may contain accessibility issues. However, we are constantly working to ensure that all content is accessible.

Some of the files linked to our website (e.g., doc, pdf) do not yet comply with accessibility requirements. These will be fixed and made accessible as the website and the documents are updated.

Furthermore, the campus maps linked to our website are not fully accessible, and their accessibility is currently being improved.

Colour contrast of some buttons found on the site does not meet the minimum contrast requirement. (WCAG 1.4.3. Contrast (minimum)) 

Not covered by legislation

• Office suite files (e.g., doc, pdf, odt) published before 23 September 2018.
• Website content on the old uef.fi server archived before 23 September 2019. This includes, e.g., research project websites that must be maintained due to the terms of the funder.
• Video and audio recordings published before 23 September 2020.
• Live video streams and audio broadcasts not recorded for storing or republishing.

We are committed to enhancing the accessibility of our digital services and are continuously working to improve it. Among our recent improvements are, e.g., transcripts of podcasts embedded on our website.

For users to whom our digital services remain inaccessible, we offer special support. In such cases, please contact us at [email protected].

This accessibility statement applies to the University of Eastern Finland’s digital service for students, UEF KAMU (kamu.uef.fi), and was last updated on 22 June 2026.

We have assessed the accessibility of the digital service in various ways, for example using the Siteimprove and Wave tools. The digital service was renewed and published on 21 May 2026, with accessibility taken into account in its technical solutions and content. 

All UEF websites, mobile applications and related content must be accessible. Accessibility in a digital environment means that as many people as possible are able to use the digital services provided regardless of differences relating to the user, situation or technology. The accessibility requirements are based on the Act on the Provision of Digital Services and on the EU’s Web Accessibility Directive. 

Accessibility status of the digital service

This digital service is partially compliant with the requirements of the level A and AA accessibility criteria (WCAG 2.1). The digital service contains some accessibility issues, which are described in more detail below.

Non-accessible content

Most of the identified accessibility issues pertain to content created by users. The digital service has a large number of content creators and editors, which is why some content may have accessibility issues. These accessibility issues are addressed on an on-going basis as content is updated.

Empty headings

The service contains individual empty heading elements that have been created in connection with content added by content creators or editors. Empty headings may cause confusion for people using screen readers and make it more difficult to understand the structure of the page. (WCAG 2.1, 2.4.6 Headings and Labels, AA)

This issue does not prevent use of the service or navigation on the website. Empty heading elements will be removed or corrected as content is updated in autumn 2026.

Missing text alternative for an inline frame

The feedback service embedded in the service (iframe) is missing an accessible name or text alternative. As a result, people using assistive technologies may not receive sufficient information about the purpose of the embedded content. (WCAG 2.1, 2.4.4 Link Purpose (In Context), A)

This issue has been noted and is awaiting correction by the technical service provider.

Empty user interface components

The service contains individual empty user interface components that have been created in connection with content added by content creators or editors. Empty user interface components may add unnecessary content for assistive technologies and make it more difficult to understand the structure of the page. (WCAG 2.1, 4.1.2 Name, Role, Value, A)

This issue does not prevent the use of the service or understanding of its content. Empty components will be removed as content is updated in autumn 2026.

Size or spacing of interactive elements

For some interactive elements in the service, the target size for pointer inputs does not fully meet the recommended minimum size, or the spacing between elements is too small. This may make the service more difficult to use, particularly on touchscreen devices. (WCAG 2.1, 2.5.5 Target Size, AAA)

This issue has been noted and is awaiting correction by the technical service provider.

Please note that this requirement is part of WCAG 2.1 level AAA and is not included in the statutory WCAG 2.1 level A and AA requirements.

Missing text alternatives for links

The service contains individual links that are missing an accessible name or whose purpose is not clear from the link text. This may make it more difficult for people using screen readers to understand where the links lead. (WCAG 2.1, 2.4.4 Link Purpose (In Context), A)

The editors responsible for the content in question have been contacted, and these accessibility issues will be fixed as content is updated in autumn 2026.

Missing text alternatives for buttons

The service contains individual empty button elements that have been created in connection with content added by content creators or editors. In such situations, the button is missing an accessible name, which means that people using assistive technologies may not be able to identify the purpose of the button. (WCAG 2.1, 4.1.2 Name, Role, Value, A)

These empty button elements will be removed or corrected as content is updated in autumn 2026.

Disproportionate burden

Old study guides in PDF format

The digital service contains study guides that have been published in PDF format. Some of the guides have been transferred to the current service from the previously used WebOodi system and are not fully compliant with the WCAG 2.1 requirements.

The number of study guides is extremely high, and making all the files immediately accessible would impose a disproportionate burden on the organisation. For this reason, the university invokes the disproportionate burden clause under the Act on the Provision of Digital Services in this respect.

The university is currently exploring solutions for improving the accessibility of the study guides, as well as a timetable for making the materials accessible. A more detailed plan and implementation timetable will be added to this accessibility statement in autumn 2026.

 

Not covered by legislation

Office suite files (e.g., doc, pdf, odt) published before 23 September 2018.

Video and audio recordings published before 23 September 2020.

Live video streams and audio broadcasts not recorded for storing or republishing.

We are committed to enhancing the accessibility of our digital services and are continuously working to improve it. For users to whom our digital services remain inaccessible, we offer special support. In such cases, please contact us at [email protected]. 

Did you discover an accessibility issue in our digital service?

Please let us know, and we’ll do our best to fix the issue!
You can give feedback relating to accessibility via this electronic form or by sending an email to [email protected]. 

Supervisory authority

If you discover an accessibility issue on our website, please give us, i.e. the website administrators, feedback first. Please note that it may take up to 14 days to reply to your feedback. If you are not satisfied with our response or if you receive no response at all within two weeks, you can lodge a complaint with the Finnish Transport and Communications Agency Traficom's Digital Accessibility Supervision Unit. Traficom’s accessibility requirements website (saavutettavuusvaatimukset.fi) explains, in detail, how you can lodge a complaint and how the matter will be processed.

Contact information for the supervisory authority

Finnish Transport and Communications Agency Traficom
Digital Accessibility Supervision
www.webaccessibility.fi
[email protected]
Telephone number (switchboard) 029 534 5000

This accessibility statement pertains to the University of Eastern Finland’s websites available on WordPress servers at https://sites.uef.fi, https://blogs.uef.fi and https://blogs2.uef.fi. It was updated on 4 November 2025.

We have self-assessed the accessibility of the websites in different ways. The WordPress service was introduced at the University of Eastern Finland in 2014. In 2019, the themes used on the websites were upgraded to an accessible one. In June 2023, themes and add-ons that even better meet the requirements of the Act on the Provision of Digital Services were introduced. 

All UEF websites, mobile applications and related content must be accessible. Accessibility in a digital environment means that as many people as possible are able to use the digital services provided despite user, situation or technology specific differences. The accessibility requirements are based on the Act on the Provision of Digital Services and on the EU’s Web Accessibility Directive. 

Accessibility status of digital services 

For the time being, WordPress themes for 2019 and 2023 are both in use. The theme for 2019 is partially compliant with the Web Content Accessibility Guidelines (WCAG) version 2.1 AA standard and the theme for 2023 is partially compliant with the A and AA standard accessibility requirements.

Non-accessible content 

The following deficiencies can be found on websites using the 2019 theme:  

• Some images are missing text alternatives (WCAG 1.1 Text Alternatives)  
• Some links are poorly distinguishable (WCAG 1.4.1 Use of Colour)  
• Some links displayed in the menu are hidden from the user at a specific display size (WCAG 1.4.10 Reflow)  
• Text cannot be resized up to 200% without loss of content or functionality (WCAG 1.4.4 Resize Text)  
• Some links are missing text alternatives (WCAG 2.4.4 Link Purpose (In Context) and WCAG 4.1.2 Name, Role, Value)  

These deficiencies will be fixed on each website as they adopt the 2023 theme.

On some websites using the 2023 theme there are deficiencies due to the fact that after the theme change, not all content has been reviewed and the site still uses content presentation methods that were enabled by the previous theme, or the styles of the theme (e.g. colors) have been modified. This causes deficiencies in color contrasts (WCAG 1.4.3 Contrast (minimum)), for example. We aim to correct these deficiencies by instructing site administrators and as we notice these deficiencies.

Some of the files linked to our website (e.g., doc, pdf) in the themes for 2019 and 2023 do not yet comply with the accessibility requirements. These will be fixed and made accessible as the files and website are updated.

On some websites, accessibility is compromised by the fact that the language used does not fully correspond to the site's language settings, and content written in a different language has not been marked accordingly (WCAG 3.1.1 Language of Page).

Not covered by legislation 

• Office suite files (e.g., doc, pdf, odt) published before 23 September 2018.    
• Video and audio recordings published before 23 September 2020.
• Live video streams and audio broadcasts not recorded for storing or republishing. 

We are committed to enhancing the accessibility of our digital services and are continuously working to improve it.  

For users to whom our digital services remain inaccessible, we offer special support. In such cases, please contact us at [email protected].

This accessibility statement applies to the site https://opas.peppi.uef.fi and was prepared on 7 February 2024. The site https://opas.peppi.uef.fi has been published on 29 November 2021.

The accessibility of the website has been evaluated by a third party.

The websites, mobile applications and related contents must be accessible. Accessibility in a digital environment means that online services can be used by as many individuals as possible despite different user-, situation- and technology-based circumstances. Accessibility requirements are based on the Act on the Provision of Digital Services and European Union’s Web Accessibility Directive.

Peppi Study Guide application and its technical accessibility are developed by University of Turku. Based on the feedback, University of Eastern Finland is developing the instructions, content, and structure of the study guide.

Accessibility status of the website

Overall, the current accessibility standard of the website is good.This web site partially complies with the accessibility requirements of Web Content Accessibility Guidelines (WCAG) 2.1-standard AA level. The accessibility deficiencies are listed below.

Non-accessible website content

The following is a description of the identified accessibility deficiencies. The study guide application does not provide a mechanism to skip blocks of content that are repeated across multiple web pages. This is why the website is not yet fully compliant with the accessibility standards WCAG 2.1, criteria 2.4.1.

This accessibility statement will be modified as soon as the detected errors have been corrected.

Actions to support accessibility

You can get support and advice on using the study guide at [email protected]. 
The user guide for the study guide is in the Peppi Handbook (login required): https://studentuef.sharepoint.com/:u:/r/sites/peppihandbook/SitePages/Students.aspx?csf=1&web=1&e=hX2K38

You can send support requests related to accessibility support and accessible content to [email protected].

Accessibility feedback

Did you notice a deficiency in accessibility in our digital service? Let us know and we will do our best to fix the deficiency. Give us feedback on accessibility by email: [email protected].

You will receive an answer to your feedback within two weeks.

Regulatory authority

If you notice any accessibility deficiencies on the website, please contact us, the site administrators, first. The reply to the feedback may take up to 14 days. If you are not satisfied with the received reply or do not receive a reply at all within two weeks, you can notify the Regional State Administrative Agency for Southern Finland. The website of the Regional State Administrative Agency for Southern Finland (in Finnish) includes detailed information on how to notify the agency about accessibility deficiencies and how the notification is processed.

Contact information of the regulatory authority

Regional State Administrative Agency for Southern Finland (Etelä-Suomen aluehallintovirasto)
Accessibility control unit (Saavutettavuuden valvonnan yksikkö)
www.saavutettavuusvaatimukset.fi
[email protected]
Telephone exchange: +358 295 016 000

This accessibility statement concerns the uef.varbi.com website of the University of Eastern Finland and has been prepared on 25 September 2023 and updated on 7 June 2024. The recruitment system and the uef.varbi.com website were introduced on 1 April 2023.

We have assessed the accessibility of the service by using the Wave and Siteimprove tools.

All of the University of Eastern Finland’s websites, mobile applications and content that is available on these must be accessible. Accessibility in a digital environment means that as many people as possible are able to use the digital services provided despite user, situation or technology specific differences. The accessibility requirements are based on the Act on the Provision of Digital Services and on the EU Web Accessibility Directive.

Accessibility status of the website 

UEF's Varbi recruitment system complies with the AA level accessibility requirements.

Accessibility feedback

Provide accessibility feedback by emailing to [email protected] or through web form https://link.webropolsurveys.com/S/92514831AA9FFE46.

This accessibility statement applies to the University of Eastern Finland website https://uef.cloud.panopto.eu/. The website was published on 01.04.2023. 
Small updates are made to the website every month, the last major update was on 28.06.2024.
The statement was last revised on 8.11.2024 

We have assessed the accessibility of the service ourselves. The service provider has also assessed the accessibility of the service.

• Learn About Accessibility Features
• Panopto Accessibility Conformance Report WCAG Edition (pdf)
   

All of the University of Eastern Finland’s websites and web services, mobile applications and content available on these must be accessible. The accessibility requirements are based on the Act on the Provision of Digital Services and on the EU’s Web Accessibility Directive. Accessibility in a digital environment means that as many people as possible are able to use the digital services provided despite user, situation or technology specific differences.

Accessibility status

Partially compliant with the AA level accessibility requirements. Pages have been reviewed with SiteImprove and Wave.

Non-accessible content

Non-accessible content has been detected in this service.

Perceivable

Non-accessible content and its shortcomings

• Non-text Content: The playlist is missing alternative text, the search field is missing a form label, and there is an empty heading on the page.
• 1.2.2, 1.2.4 Captions (Prerecorded): Not all media content includes captions, or there are deficiencies in the captions provided.
• 1.2.3, 1.2.5 Audio Description or Media Alternative (Prerecorded): There is no text alternative or audio description available for all media content.
• 1.3.1 Info and Relationships: The table headers lack defined data cells.
• 1.4.3 Contrast (Minimum): The contrast between most text elements and background on the site meets a minimum ratio of 4.5:1, but some links have a contrast of 3.27:1. 

Operable

Non-accessible content and its shortcomings

• 2.1.4 Character Key Shortcuts: This requirement is only partially met.
• 2.4.4 Link Purpose (In Context): The purpose of all links cannot be determined programmatically.
• 2.5.3 Label in Name: The visible label and the accessible name do not match. 

Understandable

Non-accessible content and its shortcomings

• 3.1.1 Language of Page: The primary language of the page is not declared in the <html> element.
• The language used in the video may differ from the user interface language. 

Robust

Non-accessible content and its shortcomings

• 4.1.2 Name, Role, Value: The names and roles of all user interface components cannot be determined programmatically.

Undue Burden

Providing captions or text alternatives for videos requires an undue amount of work due to the considerable volume of material. The service currently offers basic automated captions, but meeting quality standards would require extensive manual correction. As automatic speech recognition systems improve, we expect to be able to produce more captions in the future.

Not covered by legislation

Our site includes content offered for teaching purposes to a limited group for a set period. The accessibility of each learning material published on the site is the responsibility of the content creators, meaning there may be accessibility issues, such as missing text alternatives for videos. Our site also features live video or audio broadcasts that are not recorded for later access or redistribution. The University of Eastern Finland provides guidance and advice on addressing these accessibility issues; however, responsibility for the content remains with the original creators.

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. This statement covers content viewing and creation in ThingLink’s browser version, not the mobile application. Neither are the new task types (Activity) in the scenarios published in September 2026 included in this statement.

Students and users: How to use ThingLink 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 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.

Teachers and content producers: How to create accessible ThingLink content

Content producers are responsible for ThingLink content. You must be aware of your responsibility and make conscious choices for accessibility. The eLearning Support Services (oppitupa) support the creation of accessible ThingLink content: [email protected].

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 (login with UEF id). The service is managed by the eLearning Support Services at the University of Eastern Finland. 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 the Edge browser (version 147.0.3912.72) and 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: [email protected].

Accessibility monitoring

The Finnish Transport and Communications Agency (Traficom) monitors compliance with accessibility requirements. If you are not satisfied with our response or if you do not receive a response within two weeks, you can lodge a complaint with the Finnish Transport and Communications Agency Traficom's Digital Accessibility Supervision Unit. Traficom’s accessibility requirements website (saavutettavuusvaatimukset.fi) explains how you can lodge a complaint and how the matter will be processed.

Contact information for the supervisory authority 

Finnish Transport and Communications Agency Traficom
Digital Accessibility Supervision
www.webaccessibility.fi
[email protected]
Telephone number (switchboard) +358 29 534 5000

Accessibility Statement Information

The ThingLink website was published (introduced at UEF) in 2020.

This accessibility statement was last updated on April 20, 2026.