Accessibility statement of the 112 Suomi application
Accessibility Statement for the 112 Suomi Application
This accessibility statement applies to the 112 Suomi mobile application. It was originally prepared on 24 June 2021 and updated on 11 November 2025. The service is subject to the Act on the Provision of Digital Services, which requires that public web services and mobile applications be accessible.
The application was released in June 2015 and last updated in October 2025.
The 112 Suomi application was assessed through an external audit in June 2021 (iOS and Android interfaces).
The 2025 inspection was conducted using the VoiceOver screen reader on iPhone. Keyboard testing was performed using an external Bluetooth keyboard.
Accessibility monitoring has been comprehensively carried out for the 112 Suomi application in 2021, 2023, and 2025.
Accessibility Status of the Digital Service
The application partially meets accessibility requirements. The user interface is simple, and its contrast generally meets accessibility standards.
Non-accessible Content
The application does not yet fully comply with all requirements. The accessibility goal is to meet level AA of the WCAG 2.1 standard. If you need assistance using the application, you can contact the Communications Unit of the Emergency Response Centre Agency at [email protected].
Findings General observations related to application use
The application does not adapt to all user settings
It does not respond to the operating system’s user setting for contrast.
Applicable requirement: The user interface must follow the operating system’s user settings unless overridden by the user: units of measurement, colors, contrast, font type, font size, and focus cursor. EN 301549 v3.2.1 clause 11.7 User Preferences
The application language is not programmatically defined
The interface language is not set in a way that assistive technology can detect it programmatically.
Applicable requirement: The default natural language of the application must be programmatically determinable. EN 301549 v3.2.1 clause 11.3.1.1.1 (WCAG 2.1 Success Criterion 3.1.1 Language of Page)
Bottom navigation is not programmatically marked
The bottom of the application contains tab buttons for navigating between content sections. This area is not programmatically marked as separate from other content.
Applicable requirement: Structure and relationships conveyed visually must be programmatically determinable. WCAG 2.1 Success Criterion 1.3.1 Info and Relationships (Level A)
Content cannot be scrolled using a keyboard
No method was found to scroll page content via the keyboard interface.
Applicable requirement: All functionality must be operable through a keyboard interface. WCAG 2.1 Success Criterion 2.1.1 Keyboard (Level A)
Name, role, value (where applicable)
The application must make the names and roles of UI elements programmatically determinable for assistive technologies.
EN 301549 v3.2.1 clause 11.5.2.5
Findings Related to Notifications
Correct reading order cannot be programmatically determined
When selecting the buttons "By distance", "By time", or the close button in the sorting options window, the window closes and focus moves to the heading "Notifications near you" instead of returning to the button that opened the window.
Applicable requirement: When the presentation order affects meaning, the correct reading order must be programmatically determinable. WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence (Level A)
Content structure cannot be programmatically determined
Visually, it is clear which text fragments belong to a single notification. These visual structures and relationships are not programmatically determinable.
Applicable requirement: Structure and relationships conveyed visually must be programmatically determinable. WCAG 2.1 Success Criterion 1.3.1 Info and Relationships (Level A)
Correct reading order cannot be programmatically determined
When viewing an individual notification and selecting the back button in the top left corner, focus moves to the heading "Notifications near you" instead of returning to the component that opened the individual notification view.
Applicable requirement: When the presentation order affects meaning, the correct reading order must be programmatically determinable. WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence (Level A)
Observations Related to the Services Section
Incorrect Programmatic Role for UI Component
In the views within this section, there are components that have been programmatically assigned the role of "button", although based on their function, the correct role should be "link".
This issue appears in the following cases:
On the tabs "I need help" and "Other", below the heading "Assess your symptoms": component "Go to Omaolo service"
On the tabs "I need help" and "Other", after the heading "Travel notification to the Ministry for Foreign Affairs": component "Submit travel notification"
On the tab "Instructions", after the heading "Guide for disruptions and crisis preparedness": component "Go to the guide"
Applicable requirement: The role of all user interface components must be programmatically determinable.
EN 301549 v3.2.1 clause 11.4.1.2.1 (WCAG 2.1 Success Criterion 4.1.2)
Observations Related to Instructional Content
Lists Not Programmatically Marked
The numbered list under "Initial fire" is not programmatically marked as a list.
- The lists under "Initial extinguishing is possible" and "Initial extinguishing is not possible" are not programmatically marked as lists.
- The list at the top of "Cerebral hemorrhage" is not programmatically marked as a list.
Applicable requirement: Structure and relationships conveyed visually must be programmatically determinable.
WCAG 2.1 Success Criterion 1.3.1 Info and Relationships (Level A)
UI Component Role and Accessible Name Not Programmatically Determinable
In content sections 5 and 6, there are UI components whose role and accessible name cannot be determined programmatically by assistive technologies. These components include: "Emergency notification instructions", "Instructions for abandoning the vessel", "Call 0294 1000", "Call 112"
Applicable requirement: The name and role of all UI components must be programmatically determinable.
EN 301549 v3.2.1 clause 11.4.1.2.1 (WCAG 2.1 Success Criterion 4.1.2)
Text Content Not Programmatically Determinable
Text fragments such as "Emergency notification instructions", "Instructions for abandoning the vessel", "Call 0294 1000", and "Call 112" are not programmatically determinable by assistive technologies. Also, the fragments "Call 112" and "Read more about stroke on the Aivoliitto website" are not programmatically determinable.
Applicable requirement: The application must make text content programmatically determinable for assistive technologies.
EN 301549 v3.2.1 clause 11.5.2.1
Observations Related to Settings
Correct Reading Order Cannot Be Programmatically Determined
When opening a subview from the Settings view (e.g., "Language" or "Device orientation") and selecting the back button in the top left corner, focus moves to the heading "Settings" instead of returning to the component that opened the subview.
Applicable requirement: When the presentation order affects meaning, the correct reading order must be programmatically determinable.
WCAG 2.1 Success Criterion 1.3.2 Meaningful Sequence (Level A)
Observations Related to Notifications
Labels Not Programmatically Associated
In the "Traffic notifications" section, the labels for toggle buttons are not programmatically associated with the buttons. As a result, structure and relationships conveyed visually cannot be determined programmatically.
Applicable requirement: Structure and relationships conveyed visually must be programmatically determinable.
WCAG 2.1 Success Criterion 1.3.1 Info and Relationships (Level A)
Functionality Not Operable via Keyboard Interface
In the sections "Hazard notifications", "Authority notifications", and "Traffic notifications", it is possible to adjust the volume. However, no method was found to do this via the keyboard interface.
Applicable requirement: All functionality must be operable via the keyboard interface.
WCAG 2.1 Success Criterion 2.1.1 Keyboard (Level A)
Text Content Not Programmatically Determinable
In the "Traffic notifications" section, the text fragments "Notifications enabled" and "Notifications disabled" are not programmatically determinable by assistive technologies.
Applicable requirement: The application must make text content programmatically determinable for assistive technologies.
EN 301549 v3.2.1 clause 11.5.2.10
Text Changes Not Announced to Assistive Technologies
In the "Traffic notifications" section, there are two toggle buttons. Changing their settings causes a change in the nearby text content, but this change is not announced to assistive technologies.
Applicable requirement: The application must notify assistive technologies of changes to text content.
EN 301549 v3.2.1 clause 11.5.2.15
Did You Notice an Accessibility Issue in Our Digital Service?
Let Us Know and We’ll Do Our Best to Fix It. Submit feedback using the Emergency Response Centre Agency’s feedback form or email: [email protected]
Supervisory Authority
If you notice accessibility issues on the site, please first give feedback to us—the site administrator. You will receive a response within 14 days. If you are not satisfied with the response or receive no reply within two weeks, you can submit a complaint to the supervisory authority, Traficom.
Detailed instructions on how to submit a complaint and how it will be handled are available on Traficom’s website.
Contact Information for the Supervisory Authority:
Finnish Transport and Communications Agency Traficom / Unit for Monitoring Digital Accessibility
https://saavutettavuusvaatimukset.fi
[email protected]
029 534 5000 (switchboard)
We Are Committed to Improving the Accessibility of Our Digital Services
The application’s accessibility was assessed by an external party in June 2021, and comprehensive monitoring was conducted in 2021, 2023, and 2025. The accessibility issues identified in 2025 will be corrected by the end of 2026.
