Last reviewed date: 17 June 2025

This is an accessibility statement for 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 omniva.ee done by an external evaluator. Parts of 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

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

Chrome browser on PC with JAWS screen reader;

Chrome browser on PC with a physical keyboard;

Safari browser in iOS with VoiceOver screen reader,  

Safari browser in iOS with Voice Control voice commands,  

Safari browser in iOS with a physical keyboard;

Browser and operation system zoom and font size increase options (up to 200%).

Contact

If you find accessibility issues on 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

On rare occasions, when page is zoomed in, some elements may overlap or become partially hidden.

There is no skip link which would allow to navigate directly to the main content.

Not all interactive elements are accessible with keyboard.

The headings do not always follow a hierarchical order. On rare occasions, headings are not marked as headings.

Screen readers may read out some decorative images as file names because they are not hidden in code.

Some icon buttons, e.g. closing buttons with “x” icons, are missing text alternatives in code so their names cannot be programmatically determined.  

The role of some buttons and clickable cards cannot be programmatically determined. They are not read out by screen readers as clickable elements.

Some buttons that hide and show additional content are focused two times when navigating with the keyboard. When additional content is shown, it cannot always be hidden again.

The role and state of some select elements that open a list of choices cannot be programmatically determined.

Some list items may be incorrectly announced as separate lists by screen readers.

When error messages appear, they are not read out automatically by screen readers.

On rare occasions, focus may unexpectedly move to the beginning of the page after activating a tab or choosing an option from a select element.

Links

Some links and buttons have ambiguous text and are not programmatically connected to more descriptive texts, so their purpose may not be clear.

Some links that open new pages look like and are marked up as buttons in code which may be unexpected.

External link icons do not have text alternatives in code, so assistive technologies do not know which links open in a new tab.

Links that open PDF documents are not marked accordingly.

Header and navigation

On desktop, when font size is increased in browser settings, the main navigation submenus may not fit on the screen and cannot be scrolled into view.

The search in the header is not marked up as a search region for assistive technologies. The search button opens the search field, but this behaviour cannot programmatically determined.

The main navigation menu is not marked up as a navigation region for assistive technologies.

In the desktop navigation menu, “Send” and “Track and receive” buttons open a submenu when clicked. This behaviour cannot be programmatically determined.

Clickable Omniva logo in the header does not have a text alternative in code.

Footer

In the footer, “Delivering happiness” and “We are hiring” texts are not contrasted enough and may be hard to read.

The headings in the footer are marked up as expandable elements in desktop although they cannot be expanded.

Omniva logo in the footer does not have a text alternative in code.

Slides on the home page

It is not possible to stop the movement of the automatically changing slides on the home page.

The automatically changing slides on the home page may be difficult to navigate with assistive technologies.

The text on the automatically changing slides on the home page is not read out by screen readers.

Cookie modal

When the Cookie modal is opened, screen reader doesn’t focus or announce it.

In the Cookie modal, there is a back arrow icon button shown after clicking “Customize”, but the button is missing a text alternative.

On small screens and when page is zoomed in, the cookie modal may not be fully visible and cannot be scrolled into view.

The role and state of the checkboxes "Necessary", "Functional", "Statistical" and "Marketing" cannot be programmatically determined.