Peppi - Frontpage

Peppi system supports study, teaching, and other education related digital services at the University of Oulu. Peppi system combines the roles of students, teachers, and study administration under the same system.

Peppi consortium is responsible for system development.

Personnel

User guides and instruction videos for personnel can be found from Peppi- Palvelut wiki pages.

Students

User guides and instruction videos for students can be found from Students Peppi.

If you are having problems using Peppi, please contact system support at:

peppi@oulu.fi

University of Oulu (OY) is committed to making is committed to making its Peppi – Student’s Desktop service accessible in accordance with the Act on the provision of digital services 306/2019.

This accessibility statement applies to Peppi – Student’s Desktop service.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non-accessible content

• Keyboard Navigation
  • All functionality of the content is not operable through a keyboard interface (WCAG 2.1.1)
• Adjustable Timing
  • The user gets logged out of the service without any warning beforehand or the possibility to continue using the service (WCAG 2.2.1).
• Contrasts
  • The contrast ratio of some texts does not meet the criteria (WCAG 1.4.3).
• Use of Color
  • In some elements (e.g. some link texts, and icons) colour is the only visual means of conveying information, and the colours don’t always meet the criteria (WCAG 1.4.1, 1.4.11).
• Content on Hover or Focus
  • Some elements of the service open automatically when they receive pointer hover and don’t necessarily get hidden without moving pointer hover (WCAG 1.4.13).
• Language
  • The language of the Log In page cannot be programmatically determined (WCAG 3.1.1).
• Page Titles
  • The page titles are not always clear or distinctive (WCAG 2.4.2).
• Headings
  • All the headings of the service haven’t been marked programmatically with proper headings and heading levels (<h1>, <h2> etc.), which makes it difficult to understand the structure of the page with a screen reader (WCAG 1.3.1).
• Text Alternatives
  • All the images and graphs of the service don’t have proper text alternatives (WCAG 1.1.1).
• Link Purpose
  • There are occasionally shortages in link markings thus making it hard for screen reader users to know the purpose or target of the link. Some elements can be falsely marked as links programmatically even though they don’t lead anywhere. (WCAG 1.3.1, 2.4.4)
• Buttons
  • All the buttons have not been named clearly enough for the screen reader user to know their purpose (WCAG 4.1.2).
• Aria-haspopup
  • Aria-haspopup attribute has been used even though it is not supported by many screen readers. Even though this is not a WCAG violation per se, this can occasionally cause these screen readers to read these elements inaccurately or confusingly. (WCAG 4.1.2, best practice)
• Drop-Down Menus
  • Drop-down menus haven’t always been implemented properly, which makes them hard to understand with a screen reader (WCAG 3.2.2, 4.1.2).
• Combo Boxes
  • Combo Boxes haven’t been implemented properly, e.g. their name, role and value are left unclear when using a screen reader. The relationship between the selected values in the search field is also easily left unclear. (WCAG 1.3.1, 2.1.1, 3.2.1, 3.2.2, 4.1.2)
• Automatically Changing Content
  • Changing the value of some components automatically causes a change of content on the page, which is not communicated to the user beforehand (WCAG 3.2.2).
• Form Elements
  • The labels of the fields have not always been implemented correctly for screen reader users to understand (WCAG 1.3.1).
  • Error messages are not always implemented correctly (WCAG 3.3.1, 3.3.2, 3.3.3, 4.1.3).
  • Status messages are not always implemented correctly (WCAG 4.1.3).
• Tables
  • All the tables in the service have not been implemented correctly (e.g. they are visually tables, but not programmatically, column headings are missing, or the structure of the table is hard to understand programmatically), which makes understanding them with a screen reader difficult. In mobile use there can also be issues due to scaling problems. (WCAG 1.3.1, 1.4.10, 4.1.2)
• Calendar Table
  • There are issues in the implementation of the calendar table, which make using it difficult forscreen reader users (WCAG 1.3.1, 2.1.1).
• Current Page
  • Current pages or tabs have not always been marked programmatically (WCAG 1.3.1).
• Rich Text Editor
  • Using the rich text editor is difficult especially with a screen reader because of issues in the programmatical implementation (WCAG 1.3.1, 3.1.2, 4.1.2).
• PDF Files
  • The PDF files that can be downloaded from the service have several accessibility issues (WCAG 1.3.1, 1.3.2).

Students can ask the content in an accessible form. Students have the right to get support and advice on how to use the Student’s Desktop from peppi@oulu.fi.

Preparation of this accessibility statement

This statement was prepared on 30/10/2023.

This statement was last reviewed on 30/01/2024.

Feedback about Accessibility Issues

Academic Affairs at the University of Oulu is responsible for the accessibility of Student’s Desktop.

Regulatory authority's contact information

University of Oulu is committed to making PEPPI – Teacher’s Desktop accessible, in accordance with Act on the provision of digital services 306/2019.

This accessibility statement applies to PEPPI – Teacher’s Desktop.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non-accessible content

The content listed below is non-accessible according to the Act on the provision of digital services 306/2019.

The following non-compliances apply (the WCAG criteria, not being followed marked in the brackets):

• There are poor contrast ratios between texts and the background colours, e.g. light grey on white, green on white, red on white. (1.4.3).
• There are icons with poor contrast ratios, e.g. markings that combine white and green, blue on white, white on orange and the graphics on add note button. (1.4.11).
• Some information is conveyed through colour only (1.4.1), e.g. distinguishing required, optional, or alternative study modules on the ISP page and the graph that shows the study progress of the students.
• There is no way to dismiss the additional content (e.g. menu, tool tips or calendar input field elements) without moving pointer hover. (1.4.13).
• There is a time limit that can’t be adjusted, turned off or extended. (2.2.1).
• There are animations (e.g. on the PSP page) that can’t be stopped or hidden. (2.2.2).
• The keyboard focus indicator is not visible on several elements (2.4.7), e.g. the language selector in the main navigation, the user menu, and the drop-down menus on the PSP page.
• Some functions cannot be operated through a keyboard interface (2.1.1), e.g.:
  • dropdown menus in the main navigation (also on 320 px screen size)
  • different links and buttons, e.g.
    • Messages, Notifications, and Calendar elements on the front page
    • download links under the repots button
    • several buttons on the Scheduling tab under the PSP page
    • wrench icon links
    • the linking button and recipient adding on the Create task modal
    • the calendar buttons in My Calendar
    • the hamburger menu in the mobile size
  • most of the elements in the Add Studies to PSP modal
  • accordions
  • tooltips
  • the buttons that only appear on mouse hover, e.g. Favourites and Links on the frontpage
  • status or error messages and closing them
  • drag & drop elements.
• Some information is not accessible through a keyboard interface (2.1.1), e.g.:
  • descriptions of the top bar functions as well as other tool tips
  • the shortened texts on many tables.
• Keyboard focus is not visible on all elements, e.g. the language selection element, user information and the drop-down menus on the PSP page. (2.4.7)
• Several text fields lack the visual or programmatic label, the label hasn’t been linked to the fields properly, or the label is not descriptive enough. (3.3.2, 4.1.2)
• Some form elements have been marked in such a way that the user can’t get enough information about their functionalities or the functions are difficult to understand (1.1.1, 1.3.1, 4.1.2), e.g.:
  • text fields with auto-search
  • drop-down menus
  • the buttons that show or hide content (e.g. on the PSP table)
  • buttons with icons
  • the content of the Room reservation calendar and its functions
  • accordions
  • tabs
  • Progress Indicator.
• The text field instructions have not always been linked with the corresponding field but can only be found under separate buttons. (1.3.1, 3.3.2)
• Some buttons have not been marked as buttons. (1.3.1, 4.1.2)
• The state of a button is not always marked programmatically. (1.3.1)
• Using some components alters the content of the page, which can’t be determined from how the component functions, how it’s marked, or the textual context (1.3.1), e.g.:
  • radio buttons used to select studies
  • drop-down menus.
• Checkboxes and radio buttons that belong to the same category have not been grouped properly, which makes it difficult to understand them. (1.3.1, 3.3.2).
• Some tables have not been marked as tables programmatically. (1.3.1, 4.1.2)
• There are other deficiencies in tables (1.3.1), e.g.:
  • some have empty columns
  • there are no programmatical headers, or the heading rows are missing completely.
• The overall information, structure, and relationships of the site conveyed through presentation cannot be programmatically determined, which can make it difficult to understand (1.3.1, 2.4.1), e.g.:
  • Many pages have two nested main elements.
  • The side navigation hasn’t been marked as such.
  • Lists have been used to layout the form fields.
  • Tabs have not been marked as tabs.
  • The current page or tab has not been marked.
  • New (unread) messages have not been marked programmatically.
• Error and feedback messages have not been marked in such a way that they would be read aloud automatically with a screen reader. (4.1.3)
• Required and incorrect fields have not been marked properly. (3.3.1, 3.3.2)
• The reading sequence has faults that affect its meaning (1.3.2, 2.4.3), e.g.:
  • some buttons are read in an order different from how they are visually presented, e.g. before the headings they refer to
  • the reading order of the graph
  • in modals, the reading order is often confusing and closing the modal moves the focus to the beginning of the page.
• There are picture links and icons that have no text alternatives. (1.1.1)
• There are graphs that include text and are only presented as pictures but don’t have any text alternatives. (1.1.1, 1.4.5)
• Headings have not been marked as headings in all occasions, or headings that should be hierarchically different are marked the same. (1.3.1)
• The service is not completely usable when the text is resized up to 200 % (1.4.4) and when scaled up. (1.4.10)
• The language is not always properly determined. (3.1.2)
• Sometimes the focus jumps unpredictably when some buttons are pressed or radio buttons selected e.g. on the Curricula search page. (3.2.1)
• Changing the value of some elements causes instant and unpredictable changes on the page, which hasn’t been communicated to the user beforehand. (3.2.2)
• The user can generate non-accessible PDFs

Some of the deficiencies mentioned above are aimed to be fixed during the acadeic year 2022-2023 via Peppi's version updates. This accessibility statement will be updated as the deficiencies are being fixed.

Employees at the University of Oulu can request the content in an accessible form. Employees have the right to get support and advice on how to use the Teacher’s Desktop from peppi@oulu.fi.

Preparation of this accessibility statement

This statement was prepared on 23 October 2020.

The statement is based on accessibility evaluation, if the service fills the requirements in accordance to the Act on the provision of digital services 306/2019, conducted by Eficode Oy.

This statement was last reviewed on 30.11.2022.

Feedback about Accessibility Issues

Academic Affairs at the University of Oulu is responsible for the accessibility of Teacher’s Desktop.

Regulatory authority's contact information

Study Guide accessibility Statement

In general, the study guide is accessible. However, we are constantly analyzing the accessibility, and make changes whenever needed to improve accessibility.

Technical information about Study Guide accessibility

University of Oulu is committed to making its websites accessible, in accordance with the Accessibility Directive of the European Parliament. In Finland, the Accessibility Directive is implemented by the Act on the Provision of Digital Services.

This accessibility statement applies to University of Oulu Study Guide in https://opas.peppi.oulu.fi

Compliance status

The Study Guide is partially compliant with the Web Content Accessibility Guidelines (WCAG) 2.1 standard, Level AA, due to non-compliance listed below.

Non-accessible content

The content listed below is non-compliant for the following reasons:

Non-compliance with accessibility requirements

The Study Guide does not provide a mechanism to bypass blocks of content that are repeated on multiple web pages. Due to this, WCAG 2.1 criterion 2.4.1 is not met.

Preparation of this accessibility statement

This statement was prepared on October 1, 2020. The accessibility of Study Guide has been assessed by University of Oulu.

This statement was last reviewed on December 7th, 2022.

Feedback about Accessibility Issues

Academic Affairs at the University of Oulu is responsible for the accessibility of Study Guide.

Regulatory authority's contact information

Data privacy notice of the University of Oulu

Information on applying disclosure of information from student register Peppi

Typical uses for data released from the Student Registry include, e.g., scientific research or reaching a limited group of students. When applying for information, you need to specify what kind of information you ask for and for what purpose you need the information. Requests for information are processed at the University of Oulu in accordance with the Data Privacy notice, GDPR and other relevant legislation. Depending on the content of your request, the University of Oulu will either release the information, request more information or may have to refuse your request.

We aim to handle the applications as quickly as possible. When applying for information, prepare for four-week processing time. During holidays, the processing time is longer. If there is information missing from your application, we will contact you.

If you wish to contact students through students e-mail lists, you can apply for permit to do only that. In this case, no contact information will be transferred to you, only the permit to contact students via email list.

• Contact information that is over six moths old, will not be given.

If you need statistical information with no personal data, your request is not handled through this form. You can check if the information you need is available in the university’s reporting portal. If you are not University of Oulu personnel, you can contact peppi@oulu.fi for statistics.

The personnel and students at the University of Oulu

The application is done in electronic eForms system.

• The application: https://eforms.oulu.fi/en
• Log in with your University's M365 account
• Note! You cannot login to eForms using a fixed-term UFO user account (excluding few exceptions), but you can use Suomi.fi login method instead.
• Choose: Application for Disclosure of Information from student register Peppi

Persons and organisations outside the University of Oulu

If you are from another organization (outside the University of Oulu), you need to fill in an electronic eForms -application Application for Disclosure of Information from student register Peppi. Instead of M365 log in, you may choose the "Log in with Suomi.fi authentication".