Accessibility Statement

Status of compatibility with the requirements

The website www.hansemerkur.ch is partly accessible according to the requirements mentioned above. The known barriers and their causes are listed below.

a) Non-facilities Barrier-free Content

The following content is not barrier-free for the following reasons:

General entry aids (WCAG 2.2, success criteria 1.3.5 Identify Input Purpose)

• For some form entries/transactions, there is no support in error prevention. If the same content is entered repeatedly, errors can arise. 
• Some form fields do not support "autocomplete".

Cognitive Limitations (WCAG 2.2, Success Criteria 2.2.1 Timing Adjustable, 3.2.1 On Focus, 3.2.2 On Input)

• Some forms have a time limit and reset after 30 minutes without input. The remaining duration is not displayed. 
• Some selection spaces open new browser windows without informing them.

Motor restrictions (WCAG 2.2, success criteria 1.1.1 Non-text content, 2.5.1 Pointer Gestures)

• On some pages, elements are used that can only be operated by wipe movement. 
• No alternatives such as dots or arrow keys are currently offered.

Sounds and moving content (WCAG 2.2, success criteria 2.2.2 Pause, Stop, 1.2.5 Captions (Prerecorded)

• Individual videos do not have full subtitles or audio descriptions.

Contrast Ratio & Color Blindness (WCAG 2.2, Success Criteria 1.4.1 Use of Color, 1.4.3 Contrast (Minimum), 1.4.11 Non-Text Contrast)

• The contrast ratio is sometimes not sufficient. This applies to text, graphics and operating elements. 
• Some error messages are only reported about the color. This applies to checkboxes and some buttons in application routes.

Content comprehensibility (WCAG 2.2, success criteria 2.4.2 Page Titled, 2.4.4 Link Purpose (In Context), 2.4.6 Headings and Labels, 3.3.2 Labels or Instructions, 3.3.3 Error Suggestion, 1.1.1 Non-text content)

• Some stored labels are sometimes not available or are not meaningful. This applies to link texts, document titles, headings and other elements, such as checkmarks. 
• Some error messages are not formulated in an understandable way. In some cases, embedded documents are not barrier-free and do not contain any content about the file format.

Programmatic availability of content and dynamic content (WCAG 2.2, success criteria 1.3.1 Info and Relationships, 3.3.1 Error Identification, 2.5.3 Label in Name, 4.1.3 Status messages)

• In some final routes, wrong clicks are possible, for example if the 'Next' button is active before a tariff has been selected or an input has been made. Unbulable information is allowed in some closing quarters. The following error messages therefore do not seem conclusive. 
• Some error messages and labels are not implemented correctly. Furthermore, some errors cannot be available from assistive technologies. Some elements are not correctly linked to the label or headline.

Navigation (WCAG 2.2, success criteria 2.4.1 Bypass, 3.2.3 Consistent Navigation, 3.2.4 Consistent Identification, 3.2.6 Consistent Help)

• The navigation is not consistent or correctly installed on some pages. In some application routes, navigation is completely absent.
• In some application routes, different terms are used for the same context. This can lead to confusion.
• Some elements are not correctly excellent. This means that areas cannot be skipped and makes navigation more difficult with assistive technologies.

Customizability (WCAG 2.2, success criteria 1.4.4 Resize text, 1, 1.4.12 Text Spacing, 1.3.2 Meaningful Sequence, 11.7 Custom Settings)

• Some content, for example in accordions, is not sufficiently hidden for screen readers. 
• Some content is not reproduced in the correct order or incorrect. 
• With a text augmentation of 200%, some texts are truncated and cannot be reached by scrolling. 
• When the text spacing is adjusted, there are partly overlaps. 
• When using user-defined settings in the browser, some elements are not displayed or adjusted correctly. This concerns visibility and the correct adaptation to the custom settings of different elements and texts.

Faulty award of tables (WCAG 2.2, success criteria 1.3.1 Info and Relationships)

• Some table elements are not clearly understandable by screen reader. This concerns missing alternative texts for checkmarks, tooltips and missing column or row headings.
• Drop-down elements can be controlled as an interactive element, but are not read by screen readers. 
• Tariff updates are not announced. 
• In tables you cannot switch between the tariffs via a screen reader. 
• Tables are not implemented with scope, th and ID.  
• In the progress bar, greyished steps can also be read out.

Missing or incorrect HTML content award (WCAG 2.2, success criteria 1.3.1 Info and Relationships, 2.4.6 Headings and Labels)

• Some headlines, lists, quotes and paragraphs are not always used as such in HTML.

Various terminals/viewports (WCAG 2.2, success criteria 1.4.10 Reflow)

• Some content is not displayed correctly on some devices.

Alternative texts (WCAG 2.2, success criteria 1.1.1 Non-text content)

• Some teaser images and icons are deposited alternative texts, although they are decorative elements.  
• Some elements are missing alternative texts, although they are information-bearing graphics or operating elements. This applies to various icons, link goals, buttons, seals, logos and pictures.

Missing keyboard control (WCAG 2.2, success criteria 2.1.1 Keyboard, 2.1.2 No Keyboard Trap, 2.1.4 Character Key Shortcuts, 2.4.7 Focus Visible and 1.4.11 Non-Text Contrast, 2.4.11 Focus Not Obscured (Minimum), 4.1.2 Name, Role, Value, 1.4.13 Content on Hover or Focus, 1.3.2 Meaningful Sequence, 4.1.3 Status messages, 3.3.1 Error Identification)

• The focus is not recognizable for interactive elements. 
• Not all elements can be operated via keyboard
• There are some keyboard traps. This means that you can't close some open elements with Esc.

b) Disproportionate burden

Currently, there are no content that is considered disproportionate.

c) Content outside the scope of application

The following content is outside the scope, but is not listed in the list.

• Contract documents such as insurance confirmations, damage notices, stand notifications and similar documents, which are created on the basis of other legal requirements, are not affected by the scope of the EAA.
• Individual customer letters and notifications for the execution of the contract are also not covered by the requirements of the EAA.

The removal of the known defects is currently being planned. Once this plan is completed, it will be published on this page.

Status of this declaration

The statement was last checked on June 23, 2025.