This accessibility statement applies to the Secure email service. Specialists from the National Land Survey of Finland (NLS) have assessed the website’s compliance with accessibility requirements. The statement was revised on 10 July 2025.
The website is not fully compliant with accessibility requirements
The accessibility of the website was assessed on 26 June 2025. The assessment found that the service does not meet all the accessibility requirements.
The accessibility issues discovered during the review are listed below. The findings are based on Web Content Accessibility Guidelines (WCAG) 2.2. The number and link provided after each finding indicates which WCAG section is not yet fulfilled at the website.
Significant issues in perceivability
- When the text size is increased or the mobile view is used, problems arise. Visual cues indicating the menu-like quality will disappear from view. Icon buttons used to add and remove recipients when writing a new message also jump to illogical places. WCAG 1.4.4, WCAG 1.4.10
- Input fields and some menus have a light grey border that does not stand out clearly from the page background. WCAG 1.4.11
Moderate issues in perceivability
- The page layout has been made using tables. This may cause issues, especially to screen reader users. WCAG 1.3.1
- Vision-based expressions are used in the instructions. WCAG 1.3.3
- A large proportion of the buttons are turquoise and have white text. The buttons are on a white background. The contrast between turquoise and white is weak. WCAG 1.4.3, WCAG 1.4.11
- Footer elements overlap in mobile view. WCAG 1.4.10
Significant operability issues
- For composing a new message, there is a field labelled ‘GSM’, and no further instructions are provided. The field does not clearly indicate that a phone number for receiving a message is entered in it. WCAG 2.4.6, WCAG 2.5.3, WCAG 3.3.2
- The icon buttons used to add and remove recipients when writing a new message are small and close to each other. WCAG 2.5.8
Moderate issues in operability
- The service contains numerous labels and element names that do not correspond to one another. The names of the elements often contain a large amount of explanation, and the labels are short. The label text is not always found in the name. WCAG 2.5.3
- A button with the text ‘Select files’ is provided for adding attachments. To the screen reader, the element being activated is ‘Attachments: No file selected ‘. The element to be activated covers more than just the button, and the name comes from the section label rather than the button label. WCAG 2.5.3, WCAG 1.3.1
Significant issues in understandability
- The user must enter their own email address, but the input field reserved for it is not marked as mandatory. If the user presses the ‘Continue’ button while the input field is empty, nothing happens. WCAG 3.3.1, WCAG 3.3.2
- If the user enters an invalid email address in the address book, the service will not add it, but will not notify the user of the error. WCAG 3.3.1, WCAG 3.3.3, WCAG 4.1.3
- Labels are missing from the language and recording format menus. WCAG 3.3.2, WCAG 2.4.6
- The system automatically removes an invalid input or part of it before it can be corrected. In some cases, the user is not even notified of the deletion; instead, the input is forwarded in a modified form. WCAG 3.3.1, WCAG 3.3.2, WCAG 3.3.3, WCAG 3.3.7
Moderate issues in understandability
- Most of the buttons relatively large and without an outline. However, individual pages also feature outlined, flatter buttons in shades that differ from those used elsewhere. On these buttons, only the shape of the button corners separates the keyboard focus from the default state. WCAG 3.2.4, WCAG 2.4.7
- Mandatory items are not clearly stated. An asterisk has been used when composing a new message, but its meaning has not been explained in text. On some pages, a mandatory field is not marked as mandatory at all, and the field being mandatory only becomes apparent when the user tries to proceed. Even the error message does not always explain clearly what it is about. WCAG 3.3.2, WCAG 3.3.3
- There are three mandatory fields when composing a new message. If they are left blank, error messages are displayed that are not very clear. WCAG 3.3.3
Moderate robustness issues
- When opening a message, the user is sometimes asked to enter the message ID. The field where the ID is entered is unnamed. WCAG 4.1.2
- It can be difficult for blind users to perceive changes in status and the success of functions, as they are not always communicated to the user. WCAG 4.1.3
Minor issues
- The abbreviation MML is used in page headings and as the logo’s text alternative. It is used in all languages. Page titles do not always identify the content of the page and do not mention the name of the service. WCAG 2.4.2, WCAG 1.1.1, WCAG 3.1
- The sender's email address input field contains only ‘Sender’ as the label. It does not clearly indicate to sighted users that they should enter an email address, rather than, for example, the sender’s name. WCAG 2.4.6, WCAG 3.3.2
- Skip links and help icons are mainly in English, even when a different language has been selected. WCAG 3.1
Website correction plan
The issues discovered in the website will be corrected as soon as possible, by 30 June 2026 at the latest. Issues have also been reported to the service provider to advance the fixes.