Submit service request
Help link to main page

Peppi accessibility statement

Jamk University of Applied Sciences is committed to making its Peppi – Students’ Desktop service accessible in accordance with Act on the provision of digital services 306/2019.

This accessibility statement applies to Peppi – Students’ Desktop service (opiskelija.peppi.jamk.fi).

Compliance status

This web service 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 for the following reason(s):

Non-compliance with the Act on the provision of digital services 306/2019

  • Keyboard Navigation
    • All functionality of the content is not operable through a keyboard interface (WCAG 2.1.1)
  • Visible Focus
    • The keyboard focus is not visible on all the elements (e.g. some drop-down menus) (WCAG 2.4.7).
  • 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).
    • The contrast ratio of some icons and icon buttons do not meet the criteria (WCAG 1.4.11).
  • Use of Colour
    • In some elements (e.g. the graph on the front page, 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).
  • Resizing Text
    • All the texts and icons of the service can’t be resized without assistive technology up to 200 percent without loss of content or functionality (WCAG 1.4.4).
  • Language
    • The language of the Log In page cannot be programmatically determined (WCAG 3.1.1).
    • There can be passages or phrases in another language, but the language of those cannot be programmatically determined (WCAG 3.1.2).
  • Page Titles
    • The page titles are not always clear or distinctive (WCAG 2.4.2).
  • Multiple Ways
    • There is only one way available to locate e.g. the different pages under the Agreements page because they are not included in the main navigation (WCAG 2.4.5).
  • 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).
    • Pressing some buttons brings more content to the page, which is not communicated clearly to the screen reader user (WCAG 1.3.1, 2.4.3).
  • 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 1.3.1, 2.1.1, 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 (e.g. some radio buttons, drop-down elements, and search fields) automatically causes a change of content on the page, which is not communicated to the user beforehand (WCAG 3.2.2).
  • Form Elements
    • Radio buttons and checkboxes belonging to the same group have not been grouped together programmatically (WCAG 1.3.1).
    • 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 for screen 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).
  • Focus Order
    • E.g. the content of the main navigation is read with a screen reader even when the navigation is closed (WCAG 2.4.3).
    • Clicking the Enrol and Cancel buttons in the tables on the Enrolments page moves the focus of the screen readers in an unpredictable manner (WCAG 2.4.3).
  • 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 Peppi – Students’ Desktop through a feedback form.

Preparation of this accessibility statement

This statement was prepared on 24/05/2022.

This statement is based on an assessment done by a third party (Eficode Oy). The assessment evaluated whether the service is accessible in accordance with the Act on the provision of digital services 306/2019.

This statement was last reviewed on 29/09/2022.

Feedback and contact information

Did you notice a deficiency in accessibility? You can inform us, as well as give feedback about the accessibility of our service through a feedback form.

If you notice any accessibility deficiencies on the website, please contact the administration of the service first. As per the law, Jyväskylä University of Applied Sciences aims to reply to all the feedback. If you are not satisfied with the received reply, please inform the Regional State Administrative Agency for Southern Finland.

Enforcement procedure

If you notice any accessibility deficiencies on the site, please first send feedback to us, i.e. the site administrator. It may take us up to 14 days to reply. If you are not satisfied with the reply or do not receive a reply at all within two weeks, you can notify the Regional State Administrative Agency for Southern Finland.

Contact information of the regulatory authority

Regional State Administrative Agency for Southern Finland (Etelä-Suomen aluehallintovirasto)
Accessibility control unit (Saavutettavuuden valvonnan yksikkö)
Accessibility requirements web service (available in Finnish and Swedish) www.saavutettavuusvaatimukset.fi
saavutettavuus(a)avi.fi
Telephone switchboard 0295 016 000

Back to top Back to top