Menu

Close

Quick links

This accessibility statement explains how well the end-user portal of Laurea’s user management system complies with the Act on the Provision of Digital Services, what accessibility shortcomings exist in the online service, and how you can give us feedback on accessibility issues.

Laurea University of Applied Sciences is responsible for this online service. We want as many users as possible to be able to access our digital services. We take accessibility into account in the development of digital services.

How accessible is the online service?

This online service partially meets the Level A and AA accessibility criteria required by law (WCAG criteria 2.1 and 2.2). The online service has some accessibility shortcomings, which are described in more detail below.

Did you notice any gaps in accessibility?

We are constantly striving to improve the accessibility of the online service. If you observe any issues that are not described on this page, please let us know and we will do our best to fix any shortcomings. We will respond to requests and comments as soon as possible, but no later than within two weeks.

You can contact us by sending an email to xyz(at)xyz.fi / via an online form [URL].

Accessibility monitoring

The Finnish Transport and Communications Agency Traficom monitors the implementation of accessibility requirements. If you are not satisfied with the response you have received or you do not receive a response at all within two weeks, you can give feedback to the Finnish Transport and Communications Agency Traficom. The website of the Finnish Transport and Communications Agency Traficom provides detailed information on how to file a complaint and how the matter will be processed.

Finnish Transport and Communications Agency Traficom
Digital Accessibility Supervision Unit
www.webaccessibility.fi
saavutettavuus@traficom.fi
telephone switchboard 029 534 5000

More detailed information on technical accessibility

The service is not yet fully accessible. 

Content or functionalities that are not yet accessible: 

Perceivable

  • The online service offers several colour themes. However, the contrast between text and background colours is insufficient in places in all themes. (WCAG 1.4.3)
  • The website logo lacks alternative text. (WCAG 1.1.1)
  • In some elements, the keyboard focus is either not visible at all or is not clear enough. (WCAG 2.4.7 and 1.4.11)

Structure

  • No programmatic main language has been assigned to the service. In addition, the service contains content in different languages whose programmatic language has also not been marked. (WCAG 3.1.1 and 3.1.2)
  • The page title of the online service does not change when the views change. (WCAG 2.4.2)
  • There are not multiple ways for users to locate themselves within the online service. The site includes search functions, but they do not cover the entire site. (WCAG 2.4.5)

Navigation and content comprehensibility

  • The items in the profile menu are not accessible with the keyboard. In addition, extra stops occur with the tab key. In some views (e.g. New order), there are extra stops when moving with the keyboard. (WCAG 2.1.1)
  • Screen reader and keyboard focus sometimes behave illogically during transitions, for example when a new view loads. In addition, the screen reader cursor can move out of modal dialogs to the page underneath. (WCAG 2.4.3 and 1.3.2)
  • Some pop-up content (modal dialogs) used in the service has not been implemented correctly from a technical perspective, which may make it difficult to understand with a screen reader. The headings in the modal dialogs have also not been programmatically marked as headings. (WCAG 4.1.2 and 1.3.1)
  • The name of the site appears at the top of the page and serves as a link to the front page. The element is missing a link role, which may make it difficult for screen reader users to understand. (WCAG 4.1.2)
  • The shopping cart is referred to inconsistently in the service’s links and buttons as both “Orders” and “Shopping Cart”. This can be misleading. The screen reader also does not provide information about the number of products added to the shopping cart. (WCAG 3.2.4 and 1.3.1)
  • The service includes some icon buttons (arrow, info, filter, settings, tick, and magnifying glass) that do not have accessible names. As a result, they are unclear for screen reader users. (WCAG 4.1.2)
  • The service contains error messages that are not sufficiently descriptive and do not offer suggestions for corrections. (WCAG 3.3.1, 3.3.3)
  • The service’s login fields and some search fields do not have visible and programmatic names. In addition, some form fields provide the user with essential instructions or other information in an unclear way, or they disappear when the user starts typing in the field. (WCAG 3.3.2 and 4.1.2)
  • The service contains tables, some of which are missing column headings. (WCAG 1.3.1)
  • The labels on some checkboxes are not always very descriptive. Some checkboxes in tables do not have an accessible name at all. Screen readers also do not correctly recognize the form fields in the E-mail Notifications view as checkboxes. (WCAG 2.4.6 and 4.1.2)
  • The service has search functions in several views. When a word is searched for in the fields, the selected keyword filter is displayed below the field. The selected keyword can be removed by pressing the tick button with the mouse, but keyboard and screen reader users cannot remove it. (WCAG 2.1.1)
  • The screen reader does not interpret all functionalities correctly, such as the tree view on the New Order page or tables. The roles of some functionalities are either marked incorrectly or not marked at all. Not all functional elements have the correct functional role. In addition, the status of all functionalities, such as opened/closed or selected/not selected, is not marked correctly. (WCAG 4.1.2)
  • Changes to page content and issues that require the user’s attention are not always announced to the screen reader as status messages. Such situations include, for example, error messages in form fields and animations indicating that a page is loading. (WCAG 4.1.3)

Using the service on mobile devices

There are some usability and accessibility problems with mobile devices:

  • On mobile devices, the mobile menu overlaps with the Laurea logo. In this case, it is very difficult to distinguish the mobile menu behind the logo, especially with a light theme. (WCAG 1.4.10)
  • The mobile menu button has semantic flaws. From the perspective of screen reader users, it is only an anonymous button, and screen readers are also unable to indicate whether the menu is open or closed.
  • When the mobile menu is opened, screen reader and keyboard users cannot find the contents of the menu logically as the next content. The contents of the menu are opened behind the menu button in order of focus. In addition, all submenus in the mobile menu (Order requests, Review, Responsibilities) are always programmatically open, even if they are visually closed. (WCAG 2.4.3)
  • When the User Interface Settings modal is opened in the mobile view, its content is not fully visible in the vertical position of the mobile device, but some of the content is cut out of view. (WCAG 1.4.10)
  • With a high-contrast theme, mobile menu items are not visible at all. Texts are white on a white background. (WCAG 1.4.3)
  • The New request view cannot be used on mobile devices. In the mobile view, it is not possible to scroll to the table view on the right side, and therefore the product cannot be added to the shopping cart. For the time being, it is recommended to place new orders on a computer, as the function has usability and accessibility problems on mobile devices. (WCAG 1.4.10)
  • Not all content adapts properly to mobile device screens. Examples include the search fields at the top of the Pending Reviews view and the action buttons at the bottom; the Select button in the owner selection view of the New RDI Folder view, which is not fully visible; and the Responsibilities / My Responsibilities view, which narrows to a very small size when the user has clicked the view’s own menu button. (WCAG 1.4.10)
  • The New External User view has combo boxes. The VoiceOver screen reader on iPhone cannot easily reach menu items in an opened combo box. The screen reader cursor does not logically move to menu items after opening the menu. The VoiceOver screen reader user can only reach the items in the open menu at the end of the page. (WCAG 1.3.2)

An effort will be made to correct the shortcomings listed in this statement by 31.12.2026.

How have we tested accessibility?

The observations in this accessibility statement are based on a third-party assessment of whether the online service meets legal requirements.

The online service was published on 5.5.2026

This statement was prepared on 1.9.2026.

The statement was last updated on 1.9.2026.

Act on the Provision of Digital Services (306/2019) (in Finnish and Swedish)Accessibility Requirements website (in Finnish and Swedish)