Accessibility statement for the Elisa E-mail service
This accessibility statement applies to the Elisa Email Service. We will tell you how accessible the Elisa Email Service is, what kind of shortcomings there are in its accessibility and how you can give us feedback on the accessibility of the service.
The Act on the Provision of Digital Services will apply to the service as of 28 June 2025. The accessibility of the service has been assessed by an external expert. The statement was prepared on 5 June 2025 and it was last updated on 23 June 2026.
Accessibility status of the digital service
The service partially meets the A and AA level accessibility criteria (WCAG criteria 2.2). We are correcting the accessibility deficiencies observed in the service as part of continuous development.
Identified accessibility issues
Below we outline the identified shortcomings in meeting the accessibility requirements of Elisa’s Email Service web interface.
Images, icons and other non-text content
Some non-text content in the service, such as icons or other visual elements, does not have sufficient text alternatives, or their purpose is not conveyed clearly enough to assistive technologies (WCAG 1.1.1 Non-text Content).
Structure, relationships and presentation of content
The service has structural shortcomings, meaning that not all parts of the content, their relationships, or the meanings of different parts of the user interface are programmatically conveyed to assistive technologies (WCAG 1.3.1 Info and Relationships).
There are issues with the presentation order of content. When using a screen reader or keyboard, content does not always proceed in a logical order, or focus does not move to the contents of an opened menu as expected (WCAG 1.3.2 Meaningful Sequence and 2.4.3 Focus Order).
Instructions in the service sometimes refer to visual interface elements in a way that is not equally clear for all users (WCAG 1.3.3 Sensory Characteristics).
Language and abbreviations
The service includes content where the language, or the language of individual parts, is not correctly conveyed to assistive technologies (WCAG 3.1.2 Language of Parts).
Abbreviations are used in the service without always being clearly explained to users (WCAG 3.1.4 Abbreviations).
Contrast, use of color and content adaptability
Some text and icons in the service do not meet sufficient contrast requirements. There are deficiencies in both text contrast and in the contrast of user interface components and graphical elements (WCAG 1.4.3 Contrast (Minimum) and 1.4.11 Non-text Contrast).
There are views or parts of the user interface that do not adapt sufficiently on small screens or when zoomed, requiring horizontal scrolling or causing loss of content (WCAG 1.4.10 Reflow).
Not all content or functionality remains usable when text size is increased according to user needs (WCAG 1.4.4 Resize Text).
Keyboard access and focus
Not all functionality of the service can be used smoothly with a keyboard alone. In some situations, keyboard focus does not move as expected, or it may be difficult for users to perceive where focus is on the page (WCAG 2.1.1 Keyboard, 2.4.3 Focus Order and 2.4.7 Focus Visible).
There are situations where keyboard use may become blocked, or the user cannot proceed or exit a user interface component as expected (WCAG 2.1.2 No Keyboard Trap).
In some cases, focus may be obscured by other content or interface elements, making it difficult for the user to see where they are on the page (WCAG 2.4.11 Focus Not Obscured (Minimum)).
Target size, naming and touch interaction
Some buttons, links or other interactive elements may be too small or too close to each other, which can make them difficult to use, especially on touch screens or for users with motor impairments (WCAG 2.5.8 Target Size (Minimum)).
For some user interface components, the visible label and the programmatically determined name do not sufficiently match, which may make the service more difficult to use with speech input or assistive technologies (WCAG 2.5.3 Label in Name).
Forms, fields, errors and instructions
The service contains form fields or functions where labels, instructions or supporting texts are insufficient or not clearly conveyed to users (WCAG 3.3.2 Labels or Instructions).
In error situations, not all errors are identified or presented clearly enough to the user (WCAG 3.3.1 Error Identification).
Users are not always given sufficiently clear suggestions or instructions for correcting errors (WCAG 3.3.3 Error Suggestion).
In some situations, changing the value or selection of a form field may trigger a change without informing the user clearly in advance (WCAG 3.2.2 On Input).
Consistency and predictability
The same function or interface element used for the same purpose is not always identified consistently across different parts of the service (WCAG 3.2.4 Consistent Identification).
Use with screen readers and assistive technologies
The service includes user interface components whose role, name, state or value is missing or incorrect. This prevents or makes it difficult to use the service with screen readers and other assistive technologies (WCAG 4.1.2 Name, Role, Value).
The service includes status and notification messages that are not always conveyed automatically or clearly enough to users of screen readers or other assistive technologies (WCAG 4.1.3 Status Messages).
Alternative ways of using the service
In addition to the web interface, the Elisa Email Service can also be used with separate POP3 and IMAP email clients. Some of these external email applications have been designed with particular attention to accessibility and may significantly facilitate email use.