Accessibility

1. petsXL Website

Despite already implemented measures to improve digital accessibility, the following limitations still exist:

1. Barrier: color contrast in certain areas

• Description:
  In some cases, the color contrast between text and background is not fully optimized. This may reduce readability for users with visual impairments.

2. Barrier: empty or insufficiently labeled links

• Description:
  Occasionally, there are still empty or unlabeled links, which may not be self-explanatory for screen reader users.

3. Barrier: ARIA attributes

• Description:
  The use of ARIA attributes has been partially implemented. In some cases, the markup is incomplete or technically incorrect, which may impair accessibility for assistive technologies.

4. Barrier: anchor links lacking context

• Description:
  Some anchor links, such as “Click here” or “Continue,” are not sufficiently described in context.

5. Barrier: alternative texts for images (alt tags)

• Description:
  Some images are missing alternative texts (alt tags) or they are not formulated precisely enough.

6. Barrier: labels in newsletter subscription forms

• Description:
  The newsletter forms are functionally accessible. In some cases, however, programmatically assigned labels for input fields are missing, which may affect usability with assistive technologies. We use third-party software to produce our newsletters. Please note that we have no control over the accessibility of external services.

7. Barrier: cookie consent component

• Description:
  Currently, the cookie consent component is not fully operable via keyboard and is only partially usable with screen readers. Please note that we have no control over the accessibility of external services.

We are actively working on solutions to gradually eliminate these barriers and ensure the most accessible use of our website possible.

2. petsXL App

1. Barrier: limited tab navigation

• Description:
  Keyboard navigation (e.g., Tab key) is not fully functional in some parts of the app. Certain interactive elements are not or only partially reachable via keyboard (from app version 3.4.0).
• Reason:
  Technical challenges in implementing keyboard navigation as well as dependencies on existing business processes.
• Planned resolution:
  Full implementation of keyboard navigation is planned by the end of 2029.

2. Barrier: insufficient contrast in UI elements

• Description:
  Some UI elements (e.g., date picker, time picker) do not meet the required minimum contrast levels according to WCAG 2.1 (from app version 3.4.0).
• Reason:
  Technical challenges in visual design and existing business processes hinder immediate adjustments.
• Planned resolution:
  Adjustments to meet the applicable contrast requirements are planned by the end of 2029.

3. Barrier: incorrect heading structure

• Description:
  In the app (from version 3.4.0), headings are not arranged in a semantically correct order. This may hinder screen reader usability.
• Reason:
  Technical challenges in implementing structured content and dependencies on the existing app architecture.
• Planned resolution:
  The correction of the heading structure is planned by the end of 2029.

4. Barrier: missing or unclear link to the accessibility statement

• Description:
  In the app (from version 3.4.0), the accessibility statement is not consistently discoverable or clearly labeled as such.
• Reason:
  Technical limitations and transitional solutions in the current app structure, as well as existing content workflows.
• Planned resolution:
  Consistent and clearly labeled linking to the accessibility statement is planned by the end of 2029.

5. Barrier: missing translation of image alt tags in the Knowledge Hub

• Description:
  In some articles of the Knowledge Hub, alternative texts (alt tags) for embedded images are not fully translated into the selected language. This may lead to comprehension problems when using screen readers.
• Reason:
  Technical challenges in managing multilingual media content and existing editorial and translation processes.
• Planned resolution:
  Full translation and integration of alt tags in all available languages is planned by the end of 2029.

3. petsXL FAQ

1. Barrier: limited tab navigation

• Description:
  Keyboard navigation (e.g., Tab key) is not fully functional in parts of the FAQ section. Accordions and tabs are only partially accessible via keyboard.
• Reason:
  Technical challenges in implementing keyboard navigation.
• Planned resolution:
  Full implementation of accessible keyboard navigation is planned by the end of 2029.

2. Barrier: incorrect heading order

• Description:
  In the petsXL FAQ section, headings are not arranged in a semantically correct order. This may hinder screen reader usability.
• Reason:
  Technical challenges in structured implementation of content components and limitations of the current website architecture.
• Planned resolution:
  Correction of the heading structure is planned by the end of 2029.

3. Barrier: missing translation of alternative texts (alt tags)

• Description:
  On the homepage of the petsXL FAQ, alternative texts (alt tags) for embedded images are not fully translated into the selected language. This may lead to comprehension problems for screen reader users.
• Reason:
  Technical challenges in managing multilingual media content.
• Planned resolution:
  Full translation and integration of alternative texts in all available languages is planned by the end of 2029.

4. Barrier: missing labels in search forms

• Description:
  The search forms of the petsXL FAQ are not yet labeled using the HTML tag. This may lead to comprehension problems for screen reader users.
• Reason:
  Technical challenges in adapting provider-specific code.
• Planned resolution:
  Complete labeling of the search forms is planned by the end of 2029.

5. Barrier: missing indication of link targets

• Description:
  Links in the petsXL FAQ are not yet labeled to indicate whether a new page opens. This may lead to confusion for screen reader users.
• Reason:
  Technical challenges in adapting the code.
• Planned resolution:
  Full labeling of link targets is planned by the end of 2029.