Last review date: 04 December 2025

This is the accessibility statement for the Omniva Mobile mobile application of AS Eesti Post (Omniva), first published on 17 June 2025.
At Omniva, we value and actively listen to one another, as well as to our partners and customers. We encourage fresh and innovative ideas that help us develop and grow as people, experts, and as a company. Omniva is committed to complying with the European Accessibility Act and aims to meet the European accessibility standard for ICT products and services, EN 301 549, to improve accessibility for everyone, including people with special needs.
This accessibility statement is based on the accessibility audit of Omniva Mobile app version 1.0.55, conducted by an external evaluator. Some parts of the Omniva Mobile mobile application are not accessible (listed in the section “Known accessibility issues”), and Omniva is committed to fixing those issues that are required under applicable law to provide an accessible service for all.
 

Compatibility

Omniva Mobile app is designed and tested to be compatible at least with the following assistive technologies:

• Android phone with TalkBack screen reader;
• Android phone with a physical keyboard;
• Android phone with Voice Access voice commands;
• iOS phone with VoiceOver screen reader;
• iOS phone with Voice Control voice commands;
• iOS phone with a physical keyboard;
• Operation system zoom and font size increase options (up to 200%).

Contact

If you find accessibility issues on Omniva Mobile app, additional to those listed under “Known accessibility gaps” or require additional information, then our dedicated team is happy to help you. Please write to [email protected] or see more ways to contact us on our website.  

In Estonia, the accessibility of public service websites and applications is supervised by the Consumer Protection and Technical Regulatory Authority. Their contact details can be found on their website www.ttja.ee.  

Known accessibility gaps

Here is a list of accessibility issues we’re working to fix. We appreciate your patience and apologise for any inconvenience in the meantime!

General list

•    It is not possible to navigate the application with an external Bluetooth keyboard.
•    The application does not support landscape mode.
•    When device text size is increased, not all texts scale. In rare cases, text may overflow, become hidden, or be cut off.
•    The application does not fully respond to device visual settings such as bold text, custom fonts, high-contrast fonts, or Smart Invert.
•    On iOS devices, the “Send” web view does not respond to device zoom or text size settings.
•    On Android devices, the “Send” web view is not usable.
•    Heading elements are missing in the application.
•    The Omniva logo in the header has no text alternative.
•    In the “Shipment history” view, shipment status is conveyed only by icons. The icons have no text alternatives in the code.
 

Interactive elements

•    The main navigation tabs are at the bottom of the screen and are the last elements reached by assistive technology focus order.
•    Input fields lack labels and have only placeholders.
•    Placeholder text may have low contrast against its background and be difficult to read.
•    The “Notifications” (bell icon), “Add” (+ icon), “Expand” (down arrow icon), “Collapse” (up arrow icon), “Back” (left arrow icon), and “Close/Clear” (x icon) buttons have no text alternatives and are not accessible to assistive technologies.
•    The role of buttons and clickable cards cannot be programmatically determined. Screen readers do not identify them as clickable elements.
•    The map can only be moved up/down/left/right by dragging with a finger along a specific path.
•    The map can only be zoomed in/out using a multi-finger pinch gesture.
• The role and state of switches cannot be programmatically determined.
•    The role and state of tabs cannot be programmatically determined.
•    The role and state of radio buttons (language selections) cannot be programmatically determined.
•    The role, state, and options of checkboxes cannot be programmatically determined.
•    Links, numbers, or text have insufficient contrast in the following screen views: “Home,” “Shipment details,” “Search destination,” “Contact details,” “Overview and payment,” “Enter shipment number,” “Login view,” “Terms of service.”
•    On Android devices, focusable elements on the “Home” screen lack visible focus styles, and the “Track shipment” button in the “Track shipment” view lacks a visible focus style.
Keyboard:
(i)     On iOS devices
•    Focus moves only to the close (“x”) button in the “Send” view in the following screens: “Shipment details,” “Search destination,” “Contact details,” “Overview and payment,” “Terms for private customers,” “Contact for private customers.”
•    In the “Login” screen, keyboard focus moves only to the back button (“←”).
•    In the “Terms of service” screen, focus moves to links within the text, but they cannot be activated using Enter/Space.
•    In the “Home” screen, the app’s main navigation is at the bottom of the screen, but keyboard focus reaches those elements last (after going through the content area).

(ii)    On Android devices
•    On the “Home” screen, keyboard focus moves only to notifications, “Log in / Register,” and “Change language.” Focus cannot reach “Send with Omniva,” “Track shipments,” or the navigation elements.
•    In the “Language selection” and “Send with Omniva” screens, no elements can be focused with the keyboard.
•    In “Shipment details” and “Shipment history,” focus does not move to the close (“x”) button.
•    In “Search destination,” focus cannot activate search results.
•    In “Contact details,” focus does not move to the “x” close button in “Send,” nor to the edit button in “Shipment details,” nor to the “Add” button for the discount code.
•    In “Overview and payment,” “Terms for private customers,” and “Contact for private customers,” focus does not move to the “x” close button in “Send.”
•    In “Track shipment,” “Shipment info,” “Login view,” and “Terms of service,” focus does not move to the top back button (“←”).
•    In “Login view,” focus does not move to Smart-ID or Mobile-ID buttons, nor to the error-message close button (“x”).
•    In “Terms of service,” focus does not move to links in the content area.
•    In several views, upon entering the screen, keyboard navigation does not work until the user touches the screen once.
•    In “Contact details” and “Login view,” after the “Continue” button, focus is not visible and TAB / Shift+TAB do nothing; similarly when navigating backwards from the “First and last name” field.
•    In “Overview and payment,” focus becomes stuck on the discount code input; TAB / Shift+TAB do nothing.
•    In “Shipment details,” after the “Courier” button, focus disappears for one TAB press.
•    In “Terms for private customers” and “Contact for private customers,” after the “Cookies” link in the footer, focus is no longer visible.
 

Notifications

•    Notification view and delete buttons can only be used via swipe gestures.
•    Read and unread notifications are distinguished visually but not by assistive technologies.
•    Notifications may be displayed in a language different from the app language.
•    UI elements are not as usable with assistive technologies as they are without them:
(i)    When Smart-ID or Mobile-ID control code is displayed, the screen reader does not read it automatically; the user must navigate further to hear it.
(ii)    The screen reader does not read the Omniva logo at the top of the screen.
(iii)    On iOS devices, the purpose of input fields cannot be determined by the screen reader (various views listed).
(iv)    On Android, in “Enter shipment number,” the purpose of the input field cannot be determined.
(v)    The relationship between input fields and their labels cannot be determined by the screen reader.
(vi)    The screen reader does not indicate that links under “Terms” and “Additional information” are downloadable.
(vii)    There are 9 “Submit” buttons on the screen that are not programmatically associated with their headings. The screen reader only says “Submit, button,” making it unclear what will be submitted.
(viii)    On iOS, under “Payment,” the screen reader reads SEB as “AS SEB Bank, radio button …”; the accessible name does not match the visible one.
xi) On Android, in “Shipment info,” the accessible name does not start the same as the visible one (“Shipment number …”).
(ix)    If no destination is selected but “Continue” is activated, an error appears but is not automatically read by the screen reader.
(x)    On Android, in “Enter shipment number,” if an error occurs after pressing “Track shipment,” the error is not automatically read.
(xi)    When typing in the search box, results appear after the third character, but the screen reader does not announce them.
(xii)    If an identification error occurs, the screen reader does not read the error automatically.
(xiii)    After the last element on the screen, focus jumps below the modal (“Shipment details” view). Navigating backwards also moves focus below the modal.
(xiv)    In “Shipment details,” app content does not match what the screen reader reads.
(xv)    The screen reader announces buttons as images, making their purpose unclear.
(xvi)    The screen reader announces radio buttons as plain text (e.g., “English – EN”) and does not indicate which is selected.
(xvii)    Countries are read as images (e.g., “Estonia, image”) and not as clickable elements.
(xviii)    “Baltic countries” and “International” are read as links, and the screen reader does not indicate which is selected.
(xix)    For input fields, the screen reader reads only the placeholder.
(xx)    The screen reader does not announce that headings are headings.
(xxi)    In “Search destination,” the screen reader reads a long description of numbers after each item, which is incomprehensible.
(xxii)    The screen reader does not indicate which history point is the latest/active.
(xxiii)     On Android, in “Search destination,” focus only moves to the “Send” heading and its close button.
(xxiv)    On Android, in “Search destination” and “Contact details,” focus does not move to the input field.
(xxv)    Voice commands cannot activate bottom navigation elements (“Dashboard,” “Shipments,” “Send,” “Profile”).
(xxvi)    In “Send with Omniva,” voice commands cannot activate the on-screen buttons.
(xxvii)    In “Terms of service,” voice commands cannot activate content-area links.
(xxviii)    In “Language selection,” the screen reader does not indicate which radio button is selected nor when selection changes.
(xxix)    In “Shipment details,” the screen reader does not indicate whether “Baltic countries” or “International” or “Omniva locations” or “Courier” is selected, nor when the status changes.
(xxx)    On iOS, in “Search destination,” the screen reader does not indicate which of “Omniva locations” or “Courier” is selected, nor when selection changes.
(xxxi)    In “Terms for private customers,” the screen reader does not indicate which tab (“Parcel,” “Letter,” “Periodicals,” “Estonian Post and others”) is selected, nor changes to selection.
(xxxii)    On iOS, in “Language selection,” voice commands cannot activate language-selection radio buttons.
(xxxiii)    On Android, in “Overview and payment,” voice commands cannot select the payment method nor check the checkboxes at the end of the modal.
(xxxiv)    On Android, in “Terms for private customers,” voice commands cannot activate the tabs.
(xxxv)    On Android, in “Login view,” voice commands cannot select between Smart-ID and Mobile-ID.

•    Error messages disappear automatically after 5 seconds. The display time cannot be extended.
•    If the user enters an invalid email address (e.g., “test”), clicking “Continue” displays an error “E-mail address is invalid” near the input field. The error message does not provide guidance on how to fix it.
•    No textual error message appears (background or text turns red instead) in the following cases:
(i)    If the user does not check the checkboxes at the end of the modal (“I agree with the General Terms …”, “I confirm that I am sending the shipment myself …”) and activates “Continue.”
(ii)    If the user does not select a payment method but activates “Continue,” the backgrounds of the payment methods turn red but no text error message is shown.
•    If Mobile-ID is selected as the identification method and the user enters only one of the required fields (only the personal identification code or only the phone number), an error message appears saying “Mobile phone number and personal ID code are required.” This error message is incorrect because the user has already entered one of them.