E-thesis accessibility statement

The service doesn't meet all of the A and AA level accessibility requirements of the Web Content Accessibility Guidelines (WCAG) 2.1. The accessibility deficiencies identified are described in detail below.

For the time being, the website does not meet all relevant requirements. The E-thesis repository contains thousands of PDF files stored before 23 September 2020. There are no resources available for converting them to comply with the relevant accessibility requirements. In the future special attention will be given to the accessibility of any theses stored in E-thesis. Students writing their theses are instructed in creating accessible files. Currently, accessible PDF files cannot be obtained from theses files made with the LaTeX typesetting system, because they do not have code markings. The problem has been recognized worldwide, but so far there is no fully functional solution available. Thesis files stored in the E-thesis repository can be browsed at Helsinki University Library premises using the library terminals. Their accessibility is currently being investigated. The accessibility of the thesis files to be stored in the publication repository is described in the accessibility statement of Helda, the open access repository of the University of Helsinki (in Finnish only).

If you notice accessibility issues on the website, please give us feedback:

By email: e-thesis@helsinki.fi

If you notice any accessibility problems on the site, please first give feedback to us, the site administrator. It may take up to 14 days to receive an answer. If you are not satisfied with the answer or do not receive an answer within two weeks, you may file a complaint with the Finnish Transport and Communications Agency Traficom Digital Accessibility Supervision Unit. Traficom’s accessibility requirements website (saavutettavuusvaatimukset.fi) has detailed instructions on how to file a complaint and how the issue will be handled. 

Contact information of the supervisory authority 

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

Student views

Operability issues:

• Focus order
  The "Add information in another language" button doesn't move focus to the appearing language selection element. Also, the "Remove language" button doesn't move focus to the original "Add information in another language" button.
  In these cases, there is also no screen reader feedback. (WCAG 2.4.3 Focus order, 4.1.3 Status messages)

Understandability issues:

• Multiple languages in error messages and feedback
  When using a screen reader, the service displays some feedback and error messages in the browser language that could differ from the page language. Correction suggestions in multiple languages are unclear to the user. Also, some error messages don't have the correct language set in the code. (WCAG 3.1.2 Language of Parts, 3.3.3 Error Suggestion).

Examiner views

Perceivability issues:

• Linking error messages to fields programmatically
  Error messages are not always programmatically linked to fields. Because of this, it is possible for screen reader users entirely miss, for example, instructions for correcting information entered into a field (WCAG 1.3.1 Info and Relationships).
• Reading order
  The content of the page is not always in an understandable reading order (WCAG 1.3.2 Meaningful Sequence).

Understandability issues:

• Multiple languages
  The service may display content in several languages on one page, and the appropriate language code is not always used for content deviating from the user interface language. A screen reader therefore reads such text with the wrong pronunciation rules, making it sound unclear (WCAG 3.1.2 Language of Parts).
• Multiple languages in error messages and feedback
  When using a screen reader, the service displays some feedback and error messages in a language that differs from the page language or in multiple languages. Either messages do not have their own language codes, or correction suggestions in multiple languages are unclear to the user (WCAG 3.1.2 Language of Parts, 3.3.3 Error Suggestion).
• Unexpected change of context
  In the service, changing the value of a check box opens a modal popup to which focus is then shifted. This constitutes an unexpected change of context that should not take place (WCAG 3.2.2 On Input).

Robustness issues:

• Screen reader not reading visual status messages
  Screen reader output is unavailable for some E-thesis functions even if status messages are visually displayed in the user interface (WCAG 4.1.3 Status Messages).

Administrative staff views

Perceivability issues:

• Linking error messages to fields programmatically
  Error messages are not always programmatically linked to fields. Because of this, it is possible for screen reader users to entirely miss, for example, instructions for correcting information entered into a field (WCAG 1.3.1 Info and Relationships).
• Inactive buttons
  The status of inactive buttons is supposed to change when filling in certain form fields, but this does not always function as intended when using a keyboard and a screen reader. In such cases, the buttons are easily overlooked especially with a screen reader (WCAG 1.3.1 Info and Relationships, 2.4.3 Focus Order, 4.1.2 Name, Role, Value).
• Reflow
  Not all service viewports match the width of 320 CSS pixels or a corresponding magnified viewport without the need for scrolling in two dimensions or loss of information (WCAG 1.4.10 Reflow).

Operability issues:

• Focus order
  Keyboard focus doesn't always return from a modal window to the button that originated the action (WCAG 2.4.3 Focus order).

Robustness issues:

• Screen reader not reading visual status messages
  Screen reader output is unavailable for some E-thesis functions even if status messages are visually displayed in the user interface (WCAG 4.1.3 Status Messages).
• Disappearance of target element when activated
  In some E-thesis functions, focus shifts are not controlled. In cases where the element in focus disappears, focus is then sent to a random place on the page. In such cases, screen reader users will not receive feedback on the action taken (WCAG 4.1.3 Status Messages).

We are committed to improving the accessibility of digital services. Critical and easily implementable accessibility improvements will be made during 2026.

This statement was updated on 18th February 2026. 

We offer support to users for whom the digital service is not accessible

Users for whom the system or the files it contains is not accessible can request support from the service address e-thesis@helsinki.fi.

• Accessibility guidelines for members of the University of Helsinki community (Helsinki.fi)
• Accessibility of the University’s digital services (on Flamma, requires login)
• Website on accessibility requirements (in Finnish and Swedish)
• Act on the Provision of Digital Services (in Finnish and Swedish; English translation coming to https://www.finlex.fi/en/laki/kaannokset/2019/en20190306)
• Web Content Accessibility Guidelines (WCAG) 2.1