Accessibility statement

This accessibility statement concerns the example tasks related to the Vallu entrance examination service at testpage.uasexam.fi. The example tasks allow users to familiarize themselves with different types of tasks in the applicant’s exam view. In addition, they can be used to practise answering the tasks and using the calculator. We have carried out the accessibility assessment of the service ourselves. This accessibility statement was updated on 21 May 2026.

Status of service accessibility

The testpage.uasexam.fi 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 "testpage.uasexam.fi" 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

Inaccessible content and its shortcomings

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

2. Use of colour and contrast

Inaccessible content and its shortcomings

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

3. Navigation

Inaccessible content and its shortcomings

The structure of the front page (uasinfo.fi/international-uas-exam-example-questions) differs from the structure of the task pages, so navigation between the pages is not necessarily consistent. (It is not possible to return to the front page from the task pages.)

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

4. Mathematical formulas and calculator

Inaccessible content and its shortcomings

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.

Calculations can be entered partially using the keyboard. 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