Accessibility Statement

Allianz Assistance is committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone, and applying the relevant accessibility standards.

Efforts to support accessibility

Allianz Assistance takes the following measures to ensure accessibility:

  • Accessibility is part of our mission statement.
  • Accessibility is part of our internal policies.
  • Formal accessibility quality assurance methods exist within the organization.
  • Ongoing efforts to audit and remediate accessibility barriers occur at a regular cadence
  • Proactive efforts to prevent accessibility barriers and governance policies are in place and actively reviewed.
  • Invitation for feedback on barriers or requests for information from users to the organization

Conformance status

Current accessibility standard of the site: WCAG 2.2 level AA

Current content conformance status: Partially conformant (some parts of the content do not fully conform to the accessibility standard).

Known accessibility issues

Despite our best efforts users may experience some issues. This is a description of known accessibility issues. Please contact us if you observe an issue that is not listed.

Swipe to view more

Issue Issue Description Conformance
Link missing a text alternative Links should always have a text alternative. The link text can be inserted into the HTML - it does not need to be visible to pass this check. A

Colour contrast does not meet minimum requirement

 There is insufficient colour contrast between the text and background on this page to meet the minimum contrast requirement. AA
PDFs and documents

  • Some downloadable PDFs are not accessible via screen readers because they lack proper tagging, bookmarks or headings.

  • There are documents that cannot be navigated with keyboard controls or voice commands.

 A

Common Accessibility Issues in Global Sales Flow

Swipe to view more

Issue Issue Description Conformance
ARIA attribute unsupported or prohibited An ARIA attribute has been specified that is either not supported or is prohibited, on this type of element. Aria
Button missing a text alternative Buttons should always have a text label. The label can be inserted into the HTML - it does not need to be visible to pass this check. A
Colour contrast does not meet minimum requirement There is insufficient colour contrast between the text and background on this page to meet the minimum contrast requirement. AA
Container element is empty Some roles are designed to contain other roles. This element has this type of role, but it doesn't contain any required-owned elements. A
Content missing after heading

Headings are used to structure content in a hierarchy. This helps users to know where to start and how content sections relate to one another.

Content should appear as expected including between headings of the same level and after the last section or page heading.

 Best Practice
Empty headings This page contains one or more "empty" headings (heading tags with no text content). A
Form field missing a label Every form element should have a descriptive text label. A
Grouped form controls missing an accessible name

Grouped form controls can include elements such as checkboxes or radio buttons where the user needs to make a selection.

Each group should have an accessible name so that screen reader users can understand the group’s purpose.

 Best Practice
HTML element is deprecated or obsolete

HTML elements are updated over time and older versions are deprecated before becoming obsolete. If a deprecated or obsolete element is used, it may create usability issues.

 Best Practice
Headings are not structured One or more heading levels have been skipped. Best Practice
Hidden element has focusable content A page element with the attribute aria-hidden="true" contains focusable elements (elements that can receive focus from a keyboard). A
Interactive element does not meet minimum size nor spacing

Interactive elements, like buttons or links, should be large enough or be positioned, so they can easily be clicked or tapped by users.

Elements should be at least 24 by 24 pixels, or if smaller, be positioned with enough spacing to not intersect with other interactive elements.

 AA
Page does not start with a level 1 heading

A level 1 heading h1 tells the user what the page is about before they decide to navigate through the content.

Headings are used to structure content into a hierarchy of importance. If a page starts with a different heading level, it can cause confusion for the user.

 Best Practice
Page missing headings This page does not appear to have any heading tags (h1 through to h6), or any other elements with the role of heading. Best Practice
Page zoom is restricted The viewport element on this page prevents users from zooming in or scaling text content. AA
Required ARIA attribute is missing This element has a role that should be accompanied by specific ARIA attributes. A
Scrollable element is not keyboard accessible This page has a scrollable section that can't be operated by keyboard. A
Skip to main content link is missing The first item reached by keyboard should be a link to the main content of the page. This link should be visible when receiving focus from the keyboard. Best Practice
Table cell missing context

Data tables include header and data cells arranged in a grid.

Each data cell <td> should be assigned to at least one column or row header cell <th>. When this is done, a screen reader can announce each data cell in context.

 A
Text is clipped when resized

Visitors should be able to scale text to 200% without losing any information.

Problems often arise when overflow: hidden is used to prevent text from rendering outside of a specified area. This clips the content at the edge of its container and makes the overflow invisible.

 AA
Text not included in an ARIA landmark

All perceivable text content should be included in an ARIA landmark.

Perceivable text content refers to text that can be perceived by users of assistive technology — some of which may be invisible to sighted users.

 Aria
Visible label and accessible name do not match The accessible name of any interactive element should contain its visible text label. A

Technologies

Accessibility of this site relies on the following technologies to work:

  • HTML
  • CSS
  • Javascript

Assessment methods

Allianz Assistance assessed the accessibility of this site using the following method(s):

  • Self-evaluation: the site was evaluated internally by the company or organization.
  • External evaluation: the site was evaluated by an external entity not involved in the design and development process.

Feedback process

We welcome your feedback on the accessibility of this site. Please contact us via the following method:

E-mail: [email protected]

As soon as we identify any defects, we immediately raise a ticket in order to get this solved in a timely manner.

Formal complaints

If you are not satisfied with our response and as a consumer, you may take action under national law before the courts or before the competent administrative bodies to ensure that the national provisions transposing the Directive (EU) 2019/882 on the accessibility requirements for services (or the applicable international legislation) are complied with.

Statement updates

This statement was created on 25.06.2025.

Allianz Assistance reserves the right to modify this statement at any time. Updates will be published on this page.