Vallu entrance examination service

Accessibility statement

This accessibility statement concerns the Vallu entrance examination service. The accessibility of the service has been assessed by a third party and internally in 2023. The accessibility statement has been updated on 4.5.2026.

Status of service accessibility

The Vallu entrance examination service fulfils the accessibility requirements partly. Adjustments to accessibility will be made during 2026.

Where possible, content that is not fully accessible will be replaced, case by case, with an alternative accessible version as an individual accommodation.

Reporting of accessibility shortcomings

Any issues regarding accessibility can be emailed to saavutettavuus@metropolia.fi. Please include "Vallu entrance examination service" in the message.

Supervisory authority

If you detect any accessibility problems on the website, please first contact us, the website administrator. It may take us up to 14 days to respond. If you are not happy with our answer or do not hear from us in two weeks, you may contact the supervising authority.

Supervisory authority's contact details 

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

Inaccessible content

The following content and/or functions do not meet the requirements:

1. Alternative texts

Some images in the entrance exams may lack proper alt texts.

If necessary, accessible versions of the entrance examination tasks are produced, for example as image-free versions or with the exam attachments provided in an accessible Word or PDF format. This is done if an applicant has been granted, as an individual arrangement, permission to use a screen reader.

Accessibility requirements that are not met

• 1.1 Non-text content

2. Use of Colour and Contrast

In some exam tasks, colour may be used as the only means of conveying information. Contrast may be insufficient.

In questions involving pull-down menus, the background colour of the answer, depending on the browser, may not have enough contrast compared to the other alternatives. Furthermore, an open menu may not always stand out clearly from the text of the question.

If necessary, accessible versions are made of exam questions containing no images, for instance. This is done if an applicant has been granted, as an individual arrangement, permission to use a screen reader.

Accessibility requirements that are not met

• 1.4.1 Use of colour
• 1.4.3 Contrast (minimum)
• 1.4.5 Images of text

3. Keyboard Accessibility

Calculations can be entered partially using the keyboard.

The formula editor cannot be accessed using the keyboard. Certain formulas can be entered using keyboard shortcuts. The formula editor can be opened with the CTRL+E shortcut, enabling the user to add certain formulas. The system does not include instructions for using the formula editor with the keyboard.

Accessibility requirements that are not met

• 2.1.1 Keyboard

4. Navigation

There may be shortcomings in the heading structures within the tasks.

The task views do not have their own page titles; the page title remains the same for every view. The consistency of headings on other pages may be lacking, or some headings might not be programmatically marked.

Link texts and form field labels may be unclear.

Accessibility requirements that are not met

• 2.4.2 Page titled
• 2.4.4 Link purpose (in context)
• 2.4.6 Headings and labels

5. Accessibility of Mathematical Formulas

Mathematical formulas are by default presented in a visual form. The visual representation is generated with a library that also provides a MathML structure. MathML allows screen readers to interpret formulas to some extent, but their accessibility cannot be guaranteed.

Therefore, on a case-by-case basis as an individual arrangement, mathematical formulas can, in addition to the above-mentioned representation, also be provided in a textual format in Luetus format.

Not all calculator button names and functionalities are conveyed to screen readers. Buttons (e.g., result field) may lack aria-label attributes. The effect of input or result may not be automatically communicated to a screen reader.

Users of screen readers may not get information about all calculator buttons and their meaning. Some buttons (e.g. answer field) are missing aria-label attributes. In addition, the effect or result of input is not automatically transferred to the screen reader.

Accessibility requirements that are not met

• 4.1.2 Name, role, value

6. Status Messages

If the maximum number of characters has been used, the user may not be informed about it automatically when using Chrome browser. Firefox works better in this case. Users with no visual disability can detect this by checking the character counter. This may be difficult to detect by a person using a screen reader. The character count can be read after the answer field before 'Save answer' button.

Accessibility requirements that are not met

• 3.3.1 Error Identification
• 4.1.3 Status messages