Private customer e-service

Last reviewed date: 17 June 2025

This is an accessibility statement for minu.omniva.ee from AS Eesti Post (Omniva), first published on 17 June 2025.

In Omniva, we value and actively listen to each other, our partners and our customers. We encourage fresh and innovative ideas which help us develop and grow as humans, experts, and as a company. Omniva is committed to the European Accessibility Directive and is determined 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 an accessibility audit of minu.omniva.ee done by an external evaluator. Parts of minu.omniva.ee portal are not accessible (listed under “Known accessibility gaps”) and Omniva is committed to fixing them to provide an accessible service for all.

Compatibility

Minu.omniva.ee is designed and tested to be compatible at least with the following assistive technologies:

Chrome browser on PC with JAWS screen reader and keyboard;
Safari browser in iOS with VoiceOver screen reader, Voice Control voice commands, and keyboard.

Contact

If you find accessibility issues on minu.omniva.ee, additional to those listed under “Known accessibility gaps” or require additional information, then our dedicated team is happy to help you. Please write to info@omniva.ee 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

The language code of the page doesn’t always change according to the selected language.
Language and country selectors are not marked as expandable elements for assistive technologies.
There is no skip link which would allow to navigate directly to the main content.
The page has multiple navigation regions which are not labelled for assistive technologies. Header with navigation is marked up as a menu bar.
On some pages, headings are not marked as headings for assistive technologies.
In a few places, some texts do not have enough contrast with their background.
When increasing font size in Chrome browser settings to 200%, texts on the page increase, but some content may become hidden or overlap when enlarged.
When increasing zoom on iPhone in Safari browser settings to 200%, depending on the screen size, user may need to scroll to the right to see all icons in the header.
In mobile, in landscape orientation, the “Cookies” modal cannot be scrolled to the top and therefore cannot be closed.
When some modal dialogs or the mobile menu are opened, keyboard and screen reader focus does not go into it. Focus can also sometimes move out of the dialog.
When error or warning messages, information dialogs or security codes appear, they are not read out automatically by screen readers.
When user session ends, they are logged out and there is a message displayed which disappears automatically after a time limit. The time limit is not extendable.
Interactive maps are not fully accessible with assistive technologies.
Preferred locations order is changeable only by dragging.

Icons

Some icon buttons do not have text alternatives.
In a few places, icon button may have a text alternative that is untranslated or does not fully describe it’s meaning.
In a few places, linked image may have a text alternative that slightly differs from what is written on the image.
Some icon buttons cannot be focused and clicked with assistive technologies.
Information tooltips (i or ? icons) cannot be opened with assistive technologies.
In the “Cookies” modal, user selections are shown with icons that do not have correct text alternatives.

Inputs

In a multi-step form, the current step and the completed steps are not announced with screen readers.
Some input fields do not have labels, just placeholders. Those may be hard to see due to their low colour contrast.
Most inputs are not connected to their labels programmatically. Some inputs have two labels but are connected to only one of them.
Some labels may not give enough information, e.g. the required format of the input.
Mandatory input fields are not marked as “required” visually nor in the code.
Some invalid fields are not marked or are marked only with colour.
Search fields are not marked up as search boxes for assistive technologies. Search suggestions are not marked up as options and are sometimes not usable with assistive technologies.
Select boxes are not always marked up as select elements for assistive technologies. Select box for how many items are shown per page cannot be opened with keyboard.
Tabs are not always marked up as tabs for assistive technologies. Screen readers may read content from the unselected tabs. Some tabs can be activated only with Enter key when navigating with keyboard.
Radio buttons are not always grouped for assistive technologies.
Date picker calendars are not accessible for assistive technologies.
In the log in process, when entering the security code, the code is automatically submitted after entering the last digit.