Accessibility Statement for Elisa Prepaid Services
This accessibility statement applies to the Elisa Prepaid services.
The service is subject to the Act on the Provisioning of Digital Services, which implements the European Accessibility Act and applies from 28 June 2025. The accessibility of this service has been assessed in cooperation with external accessibility experts. This accessibility statement was created on 17 June 2025 and last updated on 2 April 2026.
Accessibility Status of Prepaid Shop
The Elisa Prepaid webshop service https://lataa.elisa.fi/en/ partially meets the accessibility requirements of WCAG 2.2 level A and AA.
Non-accessible Content
We are working to resolve identified accessibility issues as part of our continuous development process.
Images of Text
- On the eSIM order confirmation page, the screen reader skips the QR code, so the information it contains is not conveyed accessibly to the user.
Accessibility criteria that are not met:
- 1.4.5 Images of Text
- 1.1.1 Non-text Content
Contrast and color
- If mandatory information is missing, input fields do not show a visible error message. Instead, the missing information is indicated only by a red border around the field. This may make it difficult for some users to identify and correct errors.
- When moving to the shopping cart, focus does not shift to the cart view as expected. This may make it difficult for keyboard and screen reader users to continue using the service.
- In the bank selection step, the currently selected option is not indicated in a clearly recognizable way. This may make it difficult for users to understand which bank has been selected.
Accessibility criteria that are not met
- 1.4.3 Contrast (Minimum)
- 1.4.1 Use of Color
- 1.4.11 Non-text Contrast
Visible focus and focus order, keyboard use
- The keyboard tab order has issues, and the reading order and focus order are sometimes incorrect. Focus also does not always move consistently or remain visible. This may make it difficult for keyboard users to navigate and understand where they are on the page.
Accessibility criteria that are not met
- 2.4.3 Focus order
- 2.4.1 Bypass Blocks
- 1.3.2 Meaningful Sequence
- 3.2.3 Consistent Navigation
- 2.1.1 Keyboard
- 2.4.7 Focus Visible
Text size
- On Android mobile devices, the page cannot be zoomed in using the browser. As a result, users who need to enlarge content may have difficulty accessing and using the service.
Accessibility criteria that are not met:
- 1.4.4 Resize text
Titles
- On the eSIM order page, the heading structure is not consistent. This may make it difficult for screen reader users to understand the page structure and navigate the content.
Accessibility criteria that are not met
- 2.4.6 Headings and Labels
- 1.3.1 Info and Relationships
- 2.5.3 Label in Name
Naming, Status messages and instructions
- In some situations, information is not conveyed to the screen reader correctly, or it is conveyed incompletely. As a result, screen reader users may not receive all the information needed to use the service.
- In some situations, the role or type of elements is conveyed incorrectly. This may make it difficult for screen reader users to understand the purpose and functionality of the elements.
Accessibility criteria that are not met
- 2.4.4 Link Purpose
- 4.1.3 Status Messages
- 4.1.2 Name, Role, Value
- 3.1.2 Language of Parts
- 3.3.2 Labels or Instructions
- 3.3.1 Error Identification
- 3.3.3 Error Suggestion
- 3.3.4 Error Prevention (Legal, Financial, Data)
Accessibility Status of Elisa Prepaid app
The Elisa Prepaid app partially meets the accessibility requirements of WCAG 2.2 level A and AA.
Non-accessible Content
We are working to resolve identified accessibility issues as part of our continuous development process.
Images of Text
- In the prepaid app, images do not provide information to screen reader users. As a result, screen reader users may miss content or meaning conveyed through the images.
Accessibility criteria that are not met:
- 1.4.5 Images of Text
- 1.1.1 Non-text Content
Contrast and color
- In some texts, the color contrast is not sufficient. This may make the content difficult to read, especially for users with low vision or color vision deficiencies.
Accessibility criteria that are not met
- 1.4.3 Contrast (Minimum)
- 1.4.1 Use of Color
- 1.4.11 Non-text Contrast
Visible focus and focus order, keyboard use
- When using a screen reader, focus may move behind the pop-up modal. As a result, users may have difficulty understanding which content is currently active and interacting with the modal correctly.
- Instruction texts for input fields are not programmatically associated with the relevant fields. As a result, screen reader users may not receive the instructions when navigating the form fields.
- In some parts of the product cards, the reading order is incorrect. This may make the content difficult to understand for screen reader users.
Accessibility criteria that are not met
- 2.4.3 Focus order
- 2.4.1 Bypass Blocks
- 1.3.2 Meaningful Sequence
- 3.2.3 Consistent Navigation
- 3.2.4 Consistent Identification
- 2.1.1 Keyboard
Text size
- Resizing text loses content
Accessibility criteria that are not met
- 1.4.4 Resize text
- 1.4.12 Text Spacing
Titles
- In some parts of the application, heading levels do not follow a logical hierarchy. This may make it difficult for screen reader users to understand the structure of the content.
- Some texts are not programmatically associated with the elements they relate to. As a result, assistive technologies may not convey the information correctly to users.
- The screen reader receives a different title than the one shown visually. This may cause confusion for users of assistive technologies.
Accessibility criteria that are not met
- 2.4.6 Headings and Labels
- 1.3.1 Info and Relationships
- 2.5.3 Label in Name
Naming, Status messages and instructions
- When selecting a subscription, removing a subscription, and interacting with accordion elements, the information conveyed to screen readers is incomplete or unclear. This may make it difficult for users of assistive technologies to understand the purpose, state, or result of these actions.
- In the prepaid app, validation errors may appear prematurely and may be presented for the wrong input field. As a result, users may have difficulty understanding which field contains the error and how it should be corrected.
Accessibility criteria that are not met
- 2.4.4 Link Purpose
- 4.1.3 Status Messages
- 4.1.2 Name, Role, Value
- 3.1.2 Language of Parts
- 3.3.2 Labels or Instructions
- 3.3.1 Error Identification
- 3.3.3 Error Suggestion
Accessibility Status of DeviceSIM
DeviceSIM service partially meets the accessibility requirements of WCAG 2.2 level A and AA.
Non-accessible Content
We are working to resolve identified accessibility issues as part of our continuous development process.
Images of text
- Images contain essential information that is presented only visually and is not conveyed to screen readers. As a result, screen reader users may miss important content needed to use the service.
- The screen reader does not inform users when a link opens in a new tab. As a result, screen reader users may not be aware that the browsing context has changed.
Accessibility criteria that are not met:
- 1.4.5 Images of text
- 1.1.1 Non-text content
Visible focus and focus order, keyboard use
- In some situations, the focus order is incorrect and focus does not move appropriately to the modal when it opens. This may make it difficult for keyboard and screen reader users to interact with the modal content.
- Accordion elements cannot be expanded using the keyboard. As a result, keyboard users may not be able to access all content.
- In deviceSIM, instructions about mandatory fields are provided too late. As a result, users may not receive the information in time to complete the form correctly.
- A bypass link is missing from all deviceSIM pages. This may make it difficult for keyboard and screen reader users to skip repeated content and move directly to the main content.
Accessibility criteria that are not met
- 2.4.3 Focus Order
- 2.4.1 Bypass Blocks
- 1.3.2 Meaningful Sequence
- 3.2.3 Consistent Navigation
- 2.1.1 Keyboard
Titles
- Heading levels are not used according to a logical hierarchy. As a result, users of assistive technologies may have difficulty understanding the page structure.
Accessibility criteria that are not met
- 2.4.6 Headings and Labels
- 1.3.1 Info and Relationships
- 2.5.3 Label in Name
Naming, status messages, instructions
- Error messages are not announced to screen readers. As a result, screen reader users may not become aware of errors when completing forms.
- The selected payment method is not indicated clearly enough. This may make it difficult for users to understand which payment method is currently selected.
- The checkbox does not have a programmatically associated label. As a result, assistive technologies may not convey its purpose correctly to users.
Accessibility criteria that are not met
- 2.4.4 Link Purpose (In Context)
- 4.1.3 Status Messages
- 4.1.2 Name, Role, Value
- 3.1.2 Language of Parts
- 3.3.2 Labels and Instructions
- 3.3.1 Error Identification
- 3.3.3 Error Suggestion
- 3.3.4 Error Prevention (Legal, Financial, Data)
PDF documents
- Some PDF documents are not tagged properly for screen readers.
- Reading order, language markings and headings are not always correctly structured.
Accessibility criteria that are not met
- 1.1.1 Non-text Content
- 1.3.1 Info and Relationships
- 1.3.2 Meaningful Sequence
- 1.4.10 Reflow
- 2.4.6 Headings and Labels
- 3.1.1 Language of Page
- 3.1.2 Language of Parts