Inaccessible content and functions in the service
Navigation, links and menus
- In practice, the navigation is accessible with the exception of very minor flaws. There are issues with using arrow keys to access the language menu (WCAG 2.1.1) and the clarity of the language menu’s label’s content. The user menu’s entire content is wrongly read even when under focus, you cannot access the menu with arrow keys and screen readers have no information about the menu being open (WCAG 3.3.2, 4.1.2).
- The mobile version’s menu does not yet allow moving the focus to the menu’s heading (WCAG 4.1.2). The chat’s closure notification is not read directly after being opened, the closing symbol’s aria is not clear enough and the pop-up notification cannot be accessed with arrow keys (WCAG 4.1.3, 1.3.2, 2.4.4).
- Keyboard focus does not show in some elements, such as link lists. In addition, the content of some elements is hidden from screen readers and removed from tabulator order, so links cannot be read using the screen reader or used from the keyboard. (WCAG 1.3.2 Meaningful Sequence, 2.1.1 Keyboard, 2.4.3 Focus Order and 2.4.7 Focus Visible)
- The names of all links are not descriptive enough, and text alternative is missing from some image links. (WCAG 1.1.1 Non-text Content and 2.4.4 Purpose of Link (In Context)
- Some of the links open in a new window, which has not been mentioned in connection with the link. (WCAG 3.2.1 Focus)
- No information is provided in connection with anchor links of their being such. (WCAG 2.4.4 Link Purpose (In Context), 2.4.6 Headings and Labels)
- The file type in the file links is not always part of the link text, so screen reader users do not receive information on file type. (WCAG 2.4.4 Link Purpose (In Context).
Visuality
- Colour contrasts do not fulfil accessibility requirements. (WCAG 1.4.3 Contrast (minimum) and 1.4.11 Non-text Contrast)
- There is no text alternative for all visual content that would indicate what the image, icon or graphic element represents. There are also unnecessary text alternatives in some illustrations. (WCAG 1.1.1 Non-text Content)
- There are videos embedded in an iframe element on the website. The element has no title attribute that would indicate to screen reader users whether element content should be examined or whether it can just be bypassed. (WCAG 2.4.1 Bypass Blocks)
Content of pages
- The carousel on the frontpage cannot be stopped or its paging control used with the keyboard. (WCAG 1.1.1, 2.1.1 Keyboard, 2.2.2 Pause, Stop, Hide, 1.4.11 Non-text Contrast and 4.1.2 Name, Role, Value)
- The headings levels do not proceed in order on all of the pages nor have all headings been indicated programmatically as headings. (WCAG 1.3.1 Info and Relationships)
- HTLM code has been used for content formatting on some content pages. (WCAG 1.3.1 Info and Relationships)
- Text effects have not been presented semantically but only as simple text font styles. Therefore, they do not differ from the body text. (WCAG 1.3.1 Info and Relationships)
- There are issues in table headings. Line and column headings, for example, have not been defined for some of the tables. (WCAG 1.3.1 Info and Relationships)
- The website’s HTML code has some issues in the start and end tags, element nestedness and the individuality of IDs. These defects may cause assisting tools to work in an unforeseen manner. (WCAG 4.1.1 Parsing)
Accordions
- The focus of accordions moves to the first interaction element inside the accordion. As a result, screen reader users may not notice texts preceding the accordion. (WCAG 2.4.3 Focus Order)
- Accordion headings are not HTML headings, so the hierarchy of the content and heading may be difficult to understand. They are not taken into consideration in screen reader functions, for example, by means of which all page headings can be listed. (WCAG 4.1.2 Name, Role, Value)
Press releases and news listings
- Drop-down menus on the page listing news and press releases are missing labels and the menu headings are not focused. (WCAG 1.3.1 Info and Relationships)
FAQ
Back to top buttons do not shift focus but only scroll the page to the top. WCAG 1.3.1 Info and Relationships, 1.3.2 Meaningful Sequence, 2.4.3 Focus Order and 4.1.2 Name, Role, Value)
Search
- Labels are missing from the search fields and the text alternative from the magnifying glass button. Keyboard focus does not show in the magnifying glass button or the search result links. (WCAG 1.1.1 Non-textual Content, 1.4.3 Contrast (minimum) and 3.3.2 Labels or Instructions)
- Role and status specifications indicating the existence of search proposals and whether the list is open or closed are missing from the search fields. (WCAG 4.1.2 Name, Role, Value)
- If non-permitted characters are entered in the search field, an error message is not shown to screen readers. (WCAG 4.1.3 Status Messages)
- The subheadings of search results do not proceed in order. Subheadings hidden as unnecessary are included in the reading sequence. (WCAG 1.3.1 Info and Relationships, 1.3.2 Meaningful Sequence, 1.4.3 Contrast (minimum) and 2.4.7 Focus Visible)
- The buttons on the search result page are not included in tabulator order. Focus remains at the button after the button is clicked. (WCAG 1.3.2 Meaningful Sequence, 2.1.1 Keyboard and 2.4.3 Focus Order)
List of service charges and fees
- The list of service charges and fees is a single-page application. Users on the page cannot detect page changes without programmatic changes. When the page changes, focus remains in a vague position on the page. (WCAG 1.3.2 Meaningful Sequence, 2.4.2 Page Titles and 2.4.3 Focus Order)
- The search field and button are not correctly positioned in the tabulator order. The search button is positioned before the search field in the reading sequence. The search field is also missing a clear label. (WCAG 1.3.2 Meaningful Sequence, 2.4.3 Focus Order, 3.3.2 Labels or Instructions, 4.1.3 Status Messages)
- The screen reader fails to give feedback on completed or failed price list searches without moving the focus. The notice that the search failed does not indicate how to correct the situation. (WCAG 1.3.2 Meaningful Sequence, 2.4.3 Focus Order, 3.3.2 Labels or Instructions, 4.1.3 Status Messages)
Use of cookies and online identifiers
On the use of cookies and online identifiers page, customers can manage the information we collect about them using cookies. The use of cookies and online identifier does not fulfil the requirements.
Content which is not accessible on the basis of disproportionate burden
Owing to accessibility requirements, the application for using cookies and online identifiers will be fully upgraded, and the alteration work is currently in progress. The changes will be completed during the first half of 2021.
There are several issues in using cookies and online identifiers in page accessibility, due to which it may be difficult or even impossible to use the function with assisting tools, such as the screen reader. Functions of this kind include the use of links, buttons and other components from the keyboard and with the screen reader, communicating the visual presentation of elements also programmatically or as text as well as the text alternatives of links, buttons and forms.
These issues are listed in more detail below.
- WCAG 1.4.3 Contrasts
- WCAG 1.4.11 Non-text Contrasts
- WCAG 1.3.1 Info and Relationships
- WCAG 2.4.3 Focus Order
- WCAG 2.4.7 Focus Visible
Search for a branch
Search for a branch does not fully meet the requirements. In search for a branch, there are issues with screen reader and keyboard use as well as general accessibility with regard to contrasts, for example. An alternative way to search for a branch is to call OP’s national telephone service.
Non-accessible content and issues:
- WCAG 1.3.2 Reading Sequence
- WCAG 2.4.2 Page Titles
- WCAG 2.4.3 Focus Order
- WCAG 4.1.2 Name, Role, Value
- WCAG 4.1.3 No feedback on search results from screen reader.
- WCAG 2.1.1 Keyboard Use
- WCAG 1.4.3 Contrasts
- WCAG 1.4.11 Non-text Contrasts
- WCAG 1.1.1 Non-text Content
- WCAG 1.3.1 Info and Relationships
- WCAG 2.4.6 Headings and Labels