Accessibility Report for Laurea's User Management End-User Portal

How accessible is the user management end-user portal?

The accessibility of Laurea's User Management End-User Portal was evaluated in September-October 2023. While the online service met all new A- and AA-level criteria added in WCAG 2.2, it was found to have numerous significant accessibility issues, resulting in an overall fairly low level of accessibility. The main problems identified were as follows:

• Despite multiple navigation methods, content is often accessible through only one specific path.
• Numerous incorrect language tags affect screen reader users in particular.
• There are significant navigation issues: the navigation does not adapt well to mobile screens and magnifications. Visible name tags for navigation icons are not displayed for sighted keyboard users, and some submenus contain menu items that are inaccessible via keyboard alone. Additionally, some menu item and link names are vague or overly generic. Navigation functionality is also inconsistent for screen reader users.
• Many elements lack a visible keyboard focus indicator, and in some cases, keyboard focus is too faint to distinguish properly.
• There are recurring issues with color contrasts throughout the site.
• Some user interface components lack accessible names, roles, and/or values, or assistive devices incorrectly interpret their roles. The absence of proper element labeling also creates usability barriers for sighted keyboard users.
• The site contains many functional tables that are extremely unclear for screen reader users. Additionally, the tables present usability barriers for sighted keyboard users.
• In some situations, users are moved to a new, unexpected context without warning, and the focus order is occasionally illogical.
  The accessibility shortcomings are described in greater detail further below.

Did you notice any accessibility issues?

We are continuously working to improve the accessibility of our online service. If you come across any problems not mentioned on this page, please let us know, and we will do our best to address them. We will respond within 14 days.
You can contact us via the online form:

Accessibility - Laurea-ammattikorkeakoulu 

By Email:
verkkopalvelut@laurea.fi

Contents or functionalities that are not yet accessible:

• The navigation tools and buttons of the online service are inconsistent, making it difficult for users to navigate the site. Additionally, placing support mechanisms in different locations on various pages complicates their discovery. (WCAG 1.3.1, WCAG 2.4.5)
• Navigation methods do not consistently lead to the same content, and the site search functionality is not comprehensive. Furthermore, links on the homepage are not available in the main navigation, meaning content can only be found via a single route. (WCAG 1.3.1, WCAG 2.4.5)
• The site includes a "Skip to main content" link with a shortcut key (Alt+1). However, on the terms of use acceptance page, the link skips over one heading. (WCAG 1.3.1, WCAG 2.4.5)
• Landmarks have been used inconsistently, hindering usability for screen reader users. While the search and main content are marked with landmarks, other parts are not. Additionally, in order tables, rows indicating results are marked as navigation. (WCAG 1.3.1, WCAG 2.4.5)
• Many pages lack descriptive titles. (WCAG 2.4.2)
• The language setting is not specified on the login page. (WCAG 3.1.1, WCAG 3.1.2)
• On a 320px wide screen, navigation becomes difficult to detect because the icon overlaps with the Laurea logo. (WCAG 1.4.10)
• The login option buttons on the login page do not have focus indicators, leaving keyboard users unaware of which button they are interacting with. (WCAG 2.4.7, WCAG 1.4.11)
• The site generally has issues with color contrast choices. (WCAG 1.4.3, WCAG 1.4.11)
• The link to Laurea's homepage has a confusing name. (WCAG 1.3.1, WCAG 2.1.1, WCAG 2.4.6, WCAG 2.5.3, WCAG 4.1.2)
• Some labels are generic and may not fully describe the content accurately. (WCAG 2.5.3)
• In certain navigation rows, it is not possible to select submenu elements using the keyboard. (WCAG 2.1.1)
• Icon labels are not accessible via keyboard. (WCAG 2.5.3)
• The link to the homepage lacks an accessible name for screen readers. (WCAG 1.3.1, WCAG 2.1.1, WCAG 2.4.6, WCAG 2.5.3, WCAG 4.1.2)
• The upper and lower sections of navigation function differently: the lower section uses arrow keys to select submenu buttons, whereas the upper section uses tabbing. (WCAG 1.3.1, WCAG 2.1.1, WCAG 2.4.6, WCAG 2.5.3, WCAG 4.1.2)
• Some menus have confusingly similar names despite performing different functions. (WCAG 2.5.3, WCAG 4.1.2)
• On the login page, headings such as “Welcome” and “Login using the service provider” are visually presented as headings but are not marked with an HTML heading tag. (WCAG 1.3.1, WCAG 2.4.6)
• The headings on the terms of use acceptance page are illogical. (WCAG 1.3.1, WCAG 2.4.6)
• On the terms of use acceptance page, a table contains inner subheadings that can make it difficult for screen reader users to navigate the table. (WCAG 2.4.6)
• The "Set a new password" page includes a list of special characters that can be frustrating to read with a screen reader. Users must listen to the entire list of special characters before learning that their inclusion is optional. (WCAG 1.3.1)
• On the order page, the text "Product or tag name" in the search field is marked as a placeholder, which disappears when a search term is entered. Essential information (e.g., what can be searched for) should not only be provided as a placeholder. (WCAG 1.3.1, WCAG 3.3.2, WCAG 4.1.3)
• On several pages, a title and description text have been added within links. When browsing in screen reader mode, both are read as links. (WCAG 1.3.1)
• On the homepage, there is a button next to the bookmarks section labeled "Explore," but the name does not clearly describe the button's purpose. (WCAG 1.3.1, WCAG 2.4.6, WCAG 4.1.2)
• The expandable panel providing product details on the order, cart, and cancellation pages cannot be opened using only a keyboard. (WCAG 2.1.1)
• The headings on the order, cart, and cancellation pages are partially illogical. (WCAG 1.3.1, WCAG 2.4.6)
• In table views, the "View settings" submenu is closed by default. When accessed with a screen reader, the submenu's description text is read in English. The same description text appears when the mouse is hovered over the submenu but is not available via keyboard. (WCAG 2.1.1, WCAG 3.1.2)
• Text fields on the site do not have associated labels, so screen reader users might not know what to enter in the fields. This issue occurs on all forms across the site. (WCAG 1.3.1, WCAG 1.3.5, WCAG 3.3.2, WCAG 4.1.2, WCAG 4.1.3)
• The closing of error and success messages is not announced to screen readers. (WCAG 1.3.1)
• On the password setup page, error messages are difficult to understand. (WCAG 1.3.1)
• The strength of the password or changes to its strength are not communicated to screen readers. (WCAG 1.3.1)
• The page name label is not associated with the text field, meaning it is not read out when the field is focused. (WCAG 1.3.1)
• In the staff ordering process, some buttons and labels are in English. (WCAG 1.3.1)
• When a user selects another person through the "Change" button behind the "Supervisor" text field on the "New External User" page, no information is provided to the screen reader about the successful assignment of the new person to the field or the closure of the modal. (WCAG 1.3.1)
• On the "New External User" page, the view opened by the "Cost Center" and "Location Information" buttons is marked as a tree view, although it is visually a list. (WCAG 1.3.1)
• The selections in the modals on the "New External User" page cannot be removed. The "Remove Selection" button is only visible when nothing is selected in the field. (WCAG 3.3.2)
• On the "New External User" page, the "Start Date" field is formatted as "d.M.yyyy," even though the site is in Finnish. Additionally, the field's help text is a mix of English and Finnish. (WCAG 1.3.1)
• The "New External User" page does not indicate which fields are mandatory and which are not. (WCAG 1.3.1)
• On the "New External User" page, the error message for the "Department" field is not correctly associated with the field. While the error message is displayed, it is not read by the screen reader because the field itself is not a focusable element. (WCAG 1.3.1)
• On the "New Mailbox" page, when focusing on the "Email address" field, the screen reader does not convey that the domain "@laurea.fi" is automatically appended to the email address. Additionally, the field is in English. (WCAG 1.3.1)
• On the "New Mailbox" page, error messages are not presented next to the form fields. The error messages are in English, and the field names referenced in the error messages do not match the field names in the form. (WCAG 1.3.1)
• Modal dialogs on the site are not fully closed, allowing users to navigate to the underlying page. While the modals are closed when navigating with the keyboard using the tab key, screen readers navigating with arrow keys can escape to the underlying page. (WCAG 1.3.2, WCAG 2.4.3)
• The screen reader focus does not stay within the additional information modal for student orders when using arrow keys. (WCAG 1.3.2, WCAG 2.4.3)
• Functional tables used in the ordering process have numerous accessibility issues, such as columns and buttons with identical names, missing descriptive names and roles in some tables, no notification to screen readers about successfully selecting rows, and unexplained clickable empty spaces between table columns. (WCAG 1.3.1, WCAG 2.1.1, WCAG 2.4.3, WCAG 2.1.2, WCAG 4.1.3)
• Table rows cannot be selected using the keyboard if the row does not contain an interactive element (e.g., in the cart and order history). Consequently, users can only modify or view the details of the first product in the list. (WCAG 2.1.1)
• The tabbing order on the order page is not logical when navigating with a keyboard. (WCAG 2.4.3)
• The process for making an access order involves view changes, but the main page heading and page title remain the same. This makes it difficult for screen reader users to identify which stage of the process they are in. (WCAG 2.4.3, WCAG 3.2.1, WCAG 4.1.3)
• Screen readers are not notified of success when a user bookmarks a page, nor is the new text of the link, "Remove bookmark," read aloud. (WCAG 4.1.3)
• Sending an incorrect order from order history redirects the user directly to the "My Cart" page without any notification. (WCAG 4.1.3)
• On the order view, when switching pages using buttons, screen readers are not notified that the page has changed. (WCAG 4.1.3)

How Have We Tested Accessibility? 

The observations in this accessibility statement are based on an evaluation conducted by a third party to determine whether the user management end-user portal complies with the requirements defined by law. Evaluation Date: 24 October 2023

Accessibility Oversight 

The Finnish Transport and Communications Agency (Traficom) oversees compliance with accessibility requirements. If you are not satisfied with the response you receive or if you do not receive a response within two weeks, you can provide feedback to Traficom. The Traficom website provides detailed instructions on how to file a complaint and how the matter will be handled.

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

The portal was published on 30 March 2022.
This statement was prepared on 30 October 2023.
The statement was last updated on 30 October 2023.