Accessibility Statement

The order of the page header levels may be partially incorrect. This may make it difficult for the screen reader to navigate the page. The html code of the page may contain extra header layers without text below them. These layers appear to screen readers as empty headers. (WCAG 1.3.1).

There may be iframe images on the site that are missing textual responses, or frames with the same textual response. Screen readers will not be able to describe the content or purpose of the frame to users if frames are not named correctly. (WCAG 1.3.1, 4.1.2.).

The content contains tables that may contain header and data cells, which are in grid format. The absence of header cells causes users of a screen reader to experience a lack of programmatic relationship between the header and data cells. (WCAG 1.3.1).

• The content pages may contain some text or other informative images or non-decorative images that may have incomplete textual counterparts. Essential information is not conveyed because of inadequate textual responses, for example in infographics. (WCAG 1.1.1, 1.4.5).
• Content may include images or diagrams with text. (WCAG 1.4.5).
• Images and diagrams may also contain text where the contrast between text and background colour is not sufficiently high. (WCAG 1.4.3).
• Content may include, for example, diagrams that use colour as the sole visual means of conveying information. (WCAG 1.4.1).

There may be links in the content which names are not descriptive enough, for example "read more" or "see here" links. Not all titles may be descriptive enough. (WCAG 1.3.1).

There may be labels on the site, e.g. aria-label attributes, that are not translated into the language of the page. Users of screen readers may be unclear what content is in the area or, for example, what the purpose of the element is. (WCAG 4.1.2).

The site may have HTML elements such as <section> landmarks, <ul> or <ol> lists, header layers, or <a> link elements that are missing content altogether. (WCAG 2.4.4, 2.4.9, 2.1.4).

There are documents or other files published on the website after September 23, 2018 that have accessibility deficiencies:

• Files may contain visual elements and diagrams that lack textual correspondences. (WCAG 1.1.1).
• Files may contain text where the contrast between text and background colour is not high enough. (WCAG 1.4.3).
• Files may contain, for example, diagrams that use colour as the sole visual means of conveying information. (WCAG 1.4.1).
• Files may contain formatting deficiencies that hinder screen reader use, such as empty line breaks and unmarked headings. (WCAG 1.3.1).
• Files may contain table structures that may have deficiencies that hinder screen reader use, e.g. table structures used for text layout, missing programmatic column headings, and splitting similar data into multiple tables. (WCAG 1.3.1).
• Files may contain alignment order that may differ from the visual order. (WCAG 1.3.2).
• Files may contain footnotes that are not linked to the text and are difficult for the screen reader to interpret. (WCAG 1.3.1).
• Files may have missing metadata, such as missing titles or incorrect language and author information. (WCAG 1.3.1).

In individual cases, HTML code may have been used to format the content. Bread text formatting may contain incorrect tags in the html code. Tags such as bold, font, u and strike may have been used incorrectly. These may appear as errors to assistive technology users. (WCAG 1.3.1).

The site has a Cookiehub cookie banner that allows users to customize their cookie settings. The cookie setting element is developed by a third party.

• The cookie banner and settings view contain buttons or links whose cursor style colour contrasts do not pass the minimum requirements for all browsers. (WCAG 1.4.11).
• Alignment may be partially hidden. (WCAG 2.4.11).
• Alignment order differs from visual order. (WCAG 2.4.3).
• Increasing the text size by 200% in the browser will cause the structure of the cookie banner and settings content to be broken, with text drifting partially out of view or overlapping, causing loss of functionality and content. (WCAG 1.4.10, 1.4.4).
• The cookie settings have accordion components, the button of which is implemented as a link and thus cannot be opened by pressing the space bar.
• The cookie settings module cannot be closed by pressing the ESC key.

• Increasing the text size by 200% in the browser will cause the text of the buttons not to fit into the button and therefore to be unreadable. (WCAG 1.4.10, 1.4.4).
• When a button is activated with the screen reader and the text field for feedback appears, the keyboard highlighting will go directly to the text field. The alignment should remain on the button. Content such as a link to a feedback service that is not read by the screen reader in the WAI-ARIA aria-live area may thus be missed by screen reader users. (WCAG 2.4.3, 1.3.2).

The site uses the Cludo search function, which is developed by a third party and contains accessibility deficiencies.

• There is a button in the search box that allows you to remove typed text from the search box. The button does not work on a keyboard or screen reader because it does not receive a keyboard assignment. (WCAG 2.1.1).
• Screen readers do not read the number of search results after the "Search" button or the selected search term is activated. The number of search results for the search term used is not within the aria-live range. (WCAG 1.3.1).
• Search terms are highlighted with bold tags in search results instead of strong tags, causing the highlighting not to be conveyed to screen reader users. (WCAG 1.3.1).
• The search results and the page element contain aria-label labels, which are also in English on other language pages. (WCAG 3.1.2).
• The page element contains buttons, the accessible text of which does not match the visible text. (WCAG 2.5.3).

The accessibility audit of the chat was conducted in February 2024. Some of the content and functionality in the chat is not yet accessible:

• The jump link to the chat does not work correctly, the targeting remains on the jump link and does not jump to the chat as it should. (WCAG 1.3.2, 2.4.3).
• The reading order of the screen reader is partly illogical and does not correspond to the visual presentation as primarily recommended. (WCAG 1.3.2).
• The keyboard also targets some elements that are not interactive, i.e. should not receive keyboard targeting. (WCAG 2.4.3).
• Some elements of the site have visible keyboard alignment that does not contrast well enough with the background or adjacent elements. (WCAG 1.4.11).
• The logo lacks a descriptive textual response. (WCAG 1.1.1). The accessible names of some buttons and elements are not descriptive or do not correspond to the language of the language version. Some elements have accessible names for no reason. (WCAG 4.1.2).
• Some element entities are not programmatically marked as entities, e.g. the message, the author of the message and the time. (WCAG 1.3.1, 1.3.2).