Observation Summary

The primary accessibility issue identified through manual testing (MAIT) is the lack of a meaningful text alternative for a significant image. This violates WCAG 1.1.1 (Non-text Content), which requires that all meaningful images have a text alternative that serves an equivalent purpose.

Impact on Users with Disabilities

This issue significantly affects users with visual impairments who rely on screen readers to interpret web content. Without a meaningful text alternative, these users cannot understand the purpose or content of the image, leading to a loss of information and context. This can hinder their ability to navigate and comprehend the webpage effectively.

Recommendations for Fixing the Issues

1. Example 1: Meaningful Image Lacking Text Alternative (serious)

   Problem: The image has an alt attribute, but its current text ("Europäisches Patentamt") may not fully convey the purpose or content of the image. The text alternative should be more descriptive to provide equivalent information.

   Fix: Update the alt attribute to include a more descriptive text alternative that conveys the same information as the image.

   <img loading="lazy" decoding="async" width="180" height="90" src="https://piznet.de/wp-content/uploads/2024/06/73416a4c-c286-4d84-aec0-2.webp" class="attachment-medium_large size-medium_large wp-image-573" alt="Logo of the European Patent Office with text 'Europäisches Patentamt'">

Observation Summary

The key accessibility issues identified from manual testing (MAIT) are related to images not being properly coded as either meaningful or decorative. Specifically, images are missing appropriate alt attributes, which are crucial for screen readers to convey the purpose of the images to users with visual impairments.

Impact on Users with Disabilities

These issues significantly affect users with visual impairments who rely on screen readers to navigate web content. Without appropriate alt attributes, screen readers cannot describe the content or purpose of the images, leading to a poor user experience and making it difficult for users to understand the context of the images.

Recommendations for Fixing the Issues

1. Example 1: Every image must be coded as either meaningful or decorative (serious)

   Problem: The image is missing an alt attribute, making it inaccessible to screen readers.

   Fix: Add an appropriate alt attribute to describe the image. If the image is decorative, use an empty alt attribute (alt="").

   <img fetchpriority="high" decoding="async" width="300" height="169" src="https://piznet.de/wp-content/uploads/2025/04/IMG_7587-300x169.jpeg" class="attachment-medium size-medium wp-image-1748" alt="Description of the image" srcset="https://piznet.de/wp-content/uploads/2025/04/IMG_7587-300x169.jpeg 300w, https://piznet.de/wp-content/uploads/2025/04/IMG_7587-1024x576.jpeg 1024w, https://piznet.de/wp-content/uploads/2025/04/IMG_7587-768x432.jpeg 768w, https://piznet.de/wp-content/uploads/2025/04/IMG_7587-1536x864.jpeg 1536w, https://piznet.de/wp-content/uploads/2025/04/IMG_7587-2048x1152.jpeg 2048w" sizes="(max-width: 300px) 100vw, 300px">

2. Example 2: Every image must be coded as either meaningful or decorative (serious)

   Problem: The image is missing an alt attribute, making it inaccessible to screen readers.

   Fix: Add an appropriate alt attribute to describe the image. If the image is decorative, use an empty alt attribute (alt="").

   <img decoding="async" width="300" height="183" src="https://piznet.de/wp-content/uploads/2025/03/NZ8_1994-300x183.jpg" class="attachment-medium size-medium wp-image-1732" alt="Description of the image" srcset="https://piznet.de/wp-content/uploads/2025/03/NZ8_1994-300x183.jpg 300w, https://piznet.de/wp-content/uploads/2025/03/NZ8_1994-1024x623.jpg 1024w, https://piznet.de/wp-content/uploads/2025/03/NZ8_1994-768x467.jpg 768w, https://piznet.de/wp-content/uploads/2025/03/NZ8_1994-1536x935.jpg 1536w, https://piznet.de/wp-content/uploads/2025/03/NZ8_1994-2048x1246.jpg 2048w" sizes="(max-width: 300px) 100vw, 300px">

Observation Summary

The key accessibility issue identified from both automated testing (Baat) and manual testing (MAIT) is the lack of captions for pre-recorded multimedia content. This is a serious violation of WCAG 1.2.2, which requires that all pre-recorded multimedia content must have captions to ensure accessibility for users with hearing impairments.

Impact on Users with Disabilities

The absence of captions in pre-recorded multimedia content significantly impacts users with hearing impairments, making it difficult or impossible for them to understand the audio content. This can lead to exclusion from important information, entertainment, or educational content, thereby reducing their overall user experience and access to information.

Recommendations for Fixing the Issues

1. Example 1: Lack of Captions (serious)

   Problem: The pre-recorded multimedia content does not have captions, which is a requirement for accessibility compliance.

   Fix: Add captions to the multimedia content. This can be done by including a <track> element within the <video> tag to provide captions.

   
   <video controls>
     <source src="video.mp4" type="video/mp4">
     <track src="captions_en.vtt" kind="captions" srclang="en" label="English">
     Your browser does not support the video tag.
   </video>
       

Observation Summary

The key accessibility issue found from both automated testing (Baat) and manual testing (MAIT) is the lack of audio descriptions in pre-recorded videos with audio. This violates WCAG 1.2.3 (Audio Description or Media Alternative (Prerecorded)). The context of sounds is not clear, making the content inaccessible to users who rely on audio descriptions.

Impact on Users with Disabilities

This issue significantly affects users with visual impairments who rely on audio descriptions to understand the visual content of a video. Without audio descriptions, these users miss out on important information conveyed through visuals, which can lead to a lack of comprehension and engagement with the content.

Recommendations for Fixing the Issues

1. Example 1: Lack of Audio Description (serious)

   Problem: The pre-recorded video with audio does not have an audio description, making it difficult for visually impaired users to understand the context of the sounds and visuals.

   Fix: Provide an audio description track for the video. This can be done by adding an additional audio track that describes the visual content of the video.

   
   <video controls>
     <source src="video.mp4" type="video/mp4">
     <track kind="descriptions" src="audio-description.vtt" srclang="en" label="English descriptions">
     Your browser does not support the video tag.
   </video>
       

Observation Summary

The key accessibility issue identified from both automated testing (Baat) and manual testing (MAIT) is the lack of audio descriptions in pre-recorded videos with audio. This is a serious violation of WCAG 1.2.5 (Audio Description (Prerecorded)), as it prevents users with visual impairments from understanding the context of sounds in the video.

Impact on Users with Disabilities

The absence of audio descriptions significantly impacts users with visual impairments. These users rely on audio descriptions to understand visual content and context that is not conveyed through the video's audio track alone. Without audio descriptions, they miss out on important information, making the content inaccessible and excluding them from fully experiencing the video.

Recommendations for Fixing the Issues

1. Example 1: Lack of Audio Description (serious)

   Problem: The pre-recorded video with audio does not include an audio description, making it difficult for users with visual impairments to understand the context of the sounds.

   Fix: Provide an audio description track for the video. This can be done by adding a secondary audio track that includes descriptions of the visual content. Alternatively, you can use the track element to add a description.

   <video controls>
     <source src="video.mp4" type="video/mp4">
     <track kind="descriptions" src="descriptions.vtt" srclang="en" label="English descriptions">
     Your browser does not support the video tag.
   </video>

Observation Summary

The key accessibility issues identified include elements coded as headings that do not function as headings, text that visually appears as a heading but is not coded as such, and mismatched programmatic and visual heading levels. These issues were found through both automated and manual testing.

Impact on Users with Disabilities

These issues can significantly affect users with disabilities, particularly those who rely on screen readers. Incorrect heading structure can make it difficult for users to navigate the content efficiently, leading to confusion and a poor user experience. Users with cognitive disabilities may also struggle to understand the content hierarchy.

Recommendations for Fixing the Issues

1. Example 1: An element coded as a heading must function as a heading (serious)

   Problem: The element coded as an <h2> does not function as a heading because it is used incorrectly.

   Fix: Ensure that the <h2> element is used appropriately to denote a section heading.

   <h2 class="elementor-heading-title elementor-size-default">Unsere Mitglieder sind anerkannte Kooperationspartner <br>des Deutschen Patent- und Markenamtes (DPMA) und Teil des europäischen PATLIB‑Netzwerks.</h2>

2. Example 2: Text that looks like a heading must be coded as a heading (serious)

   Problem: The text visually appears as a heading but is not coded as such, leading to a mismatch between visual and programmatic structure.

   Fix: Code the text as a heading using the appropriate heading tag.

   <h2>Unsere Mitglieder sind anerkannte Kooperationspartner des Deutschen Patent- und Markenamtes (DPMA) und Teil des europäischen PATLIB‑Netzwerks.</h2>

3. Example 3: A heading's programmatic level must match the level that's presented visually (serious)

   Problem: The heading level <h2> does not match the visual hierarchy intended for the content.

   Fix: Adjust the heading level to match the visual hierarchy.

   <h3 class="elementor-heading-title elementor-size-default">Unsere Mitglieder sind anerkannte Kooperationspartner <br>des Deutschen Patent- und Markenamtes (DPMA) und Teil des europäischen PATLIB‑Netzwerks.</h3>

4. Example 4: A heading's programmatic level must match the level that's presented visually (serious)

   Problem: The <h4> element is used, but it does not match the visual hierarchy intended for the content.

   Fix: Adjust the heading level to match the visual hierarchy.

   <h3 class="elementor-icon-box-title">
     <a href="https://piznet.de/angebote/#analysen">
       Recherchen und Analysen
     </a>
   </h3>

Observation Summary

The primary accessibility issue identified from both automated testing (Baat) and manual testing (MAIT) is that the programmatic level of headings does not match the level presented visually. This inconsistency can cause confusion for users who rely on assistive technologies to navigate the content.

Impact on Users with Disabilities

Users with visual impairments who rely on screen readers and other assistive technologies may find it difficult to understand the structure and hierarchy of the content if the heading levels are not correctly implemented. This can lead to confusion and make it harder for users to navigate the page efficiently. Users with cognitive disabilities may also struggle with understanding the content structure when heading levels are inconsistent.

Recommendations for Fixing the Issues

1. Example 1: Heading Level Mismatch (serious)

   Problem: The heading is visually presented as a primary heading but is programmatically marked as an <h3> element.

   Fix: Ensure that the heading level matches the visual presentation. If the heading should be a primary heading, change it to an <h1> or the appropriate level.

   <h1 class="elementor-post__title">
     <a href="https://piznet.de/neuer-recherchestandard-verabschiedet/">
       Neuer Recherchestandard verabschiedet
     </a>
   </h1>

2. Example 2: Heading Level Mismatch (serious)

   Problem: The heading is visually presented as a primary heading but is programmatically marked as an <h3> element.

   Fix: Ensure that the heading level matches the visual presentation. If the heading should be a primary heading, change it to an <h1> or the appropriate level.

   <h1 class="elementor-post__title">
     <a href="https://piznet.de/rueckblick-auf-ip-enforcement-day-und-35-piznet-jahrestagung/">
       Rückblick auf „IP Enforcement Day und 35. piznet Jahrestagung“
     </a>
   </h1>

3. Example 3: Heading Level Mismatch (serious)

   Problem: The heading is visually presented as a primary heading but is programmatically marked as an <h3> element.

   Fix: Ensure that the heading level matches the visual presentation. If the heading should be a primary heading, change it to an <h1> or the appropriate level.

   <h1 class="elementor-post__title">
     <a href="https://piznet.de/example-url/">
       Example Heading Text
     </a>
   </h1>

Observation Summary

The key accessibility issues identified from both automated testing (Baat) and manual testing (MAIT) are related to insufficient color contrast between foreground and background elements. These violations fail to meet the WCAG 2 AA minimum contrast ratio thresholds, which impacts the readability and usability of the content for users with visual impairments.

Impact on Users with Disabilities

These issues primarily affect users with visual impairments, including those with low vision and color blindness. Insufficient color contrast can make text difficult to read, leading to a poor user experience and potentially causing users to miss important information. Ensuring adequate contrast is crucial for readability and accessibility.

Recommendations for Fixing the Issues

1. Example 1: color-contrast (serious)

   Problem: The paragraph text has insufficient color contrast of 1.92 (foreground color: #ffffff, background color: #73c5e9). The expected contrast ratio is at least 3:1 for large text.

   Fix: Adjust the background color to a darker shade to meet the minimum contrast ratio. For example, changing the background color to #0072a3 will provide sufficient contrast.

   <p style="color: #ffffff; background-color: #0072a3;">Weitere Informationen finden Sie direkt bei den PIZ in ihrer Region:</p>

2. Example 2: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The paragraph text has insufficient color contrast.

   Fix: Adjust the background color to a darker shade to meet the minimum contrast ratio. For example, changing the background color to #0072a3 will provide sufficient contrast.

   <p style="color: #ffffff; background-color: #0072a3;">Weitere Informationen finden Sie direkt bei den PIZ in ihrer Region:</p>

3. Example 3: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The heading text has insufficient color contrast.

   Fix: Adjust the background color to a darker shade to meet the minimum contrast ratio. For example, changing the background color to #0072a3 will provide sufficient contrast.

   <h2 class="elementor-heading-title elementor-size-default" style="color: #ffffff; background-color: #0072a3;">Hier finden Sie die Patentinformationszentren:</h2>

4. Example 4: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The link text has insufficient color contrast.

   Fix: Adjust the link color to a darker shade to meet the minimum contrast ratio. For example, changing the link color to #005580 will provide sufficient contrast.

   <a href="https://piznet.de/kontakt/" style="color: #005580;">Kontakt</a>

5. Example 5: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The link text has insufficient color contrast.

   Fix: Adjust the link color to a darker shade to meet the minimum contrast ratio. For example, changing the link color to #005580 will provide sufficient contrast.

   <a href="https://piznet.de/impressum/" style="color: #005580;">Impressum</a>

6. Example 6: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The link text has insufficient color contrast.

   Fix: Adjust the link color to a darker shade to meet the minimum contrast ratio. For example, changing the link color to #005580 will provide sufficient contrast.

   <a href="https://piznet.de/datenschutz/" style="color: #005580;">Datenschutz</a>

Observation Summary

The key accessibility issues identified from both automated testing (Baat) and manual testing (MAIT) are related to insufficient color contrast. Specifically, the foreground and background colors do not meet the WCAG 2 AA minimum contrast ratio thresholds. This includes text elements and links with insufficient contrast ratios, which are critical for readability and accessibility.

Impact on Users with Disabilities

These issues significantly affect users with visual impairments, including those with low vision and color blindness. Insufficient color contrast makes it difficult for these users to read text and interact with links, leading to a poor user experience and potential exclusion from accessing important information.

Recommendations for Fixing the Issues

1. Example 1: color-contrast (serious)

   Problem: The paragraph text has insufficient color contrast of 1.92 (foreground color: #ffffff, background color: #73c5e9).

   Fix: Adjust the background color to ensure a minimum contrast ratio of 3:1.

   Weitere Informationen finden Sie direkt bei den PIZ in ihrer Region:
       

2. Example 2: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The heading text has insufficient color contrast.

   Fix: Adjust the background color to ensure a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text.

   Hier finden Sie die Patentinformationszentren:
       

3. Example 3: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The link text "Kontakt" has insufficient color contrast.

   Fix: Adjust the link color to ensure a minimum contrast ratio of 4.5:1.

   Kontakt
       

4. Example 4: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The link text "Impressum" has insufficient color contrast.

   Fix: Adjust the link color to ensure a minimum contrast ratio of 4.5:1.

   Impressum
       

5. Example 5: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The link text "Datenschutz" has insufficient color contrast.

   Fix: Adjust the link color to ensure a minimum contrast ratio of 4.5:1.

   Datenschutz
       

Observation Summary

The key accessibility issues identified from both automated testing (Baat) and manual testing (MAIT) are related to insufficient color contrast between foreground and background colors. Specifically, the contrast ratio does not meet the WCAG 2 AA minimum threshold of 4.5:1. This issue affects several anchor elements on the page, which currently have a contrast ratio of 1.92:1.

Impact on Users with Disabilities

These issues significantly impact users with visual impairments, including those with low vision and color blindness. Insufficient color contrast makes it difficult for these users to read the text, which can hinder their ability to navigate the website effectively. This can lead to a poor user experience and may prevent users from accessing important information or completing tasks on the site.

Recommendations for Fixing the Issues

1. Example 1: color-contrast (serious)

   Problem: The anchor element with the text "Kontakt" has insufficient color contrast of 1.92:1 (foreground color: #ffffff, background color: #73c5e9).

   Fix: Adjust the background color to ensure a contrast ratio of at least 4.5:1. For example, changing the background color to #005a8b will provide sufficient contrast.

   Kontakt

2. Example 2: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The anchor element with the text "Impressum" has insufficient color contrast.

   Fix: Adjust the background color to ensure a contrast ratio of at least 4.5:1. For example, changing the background color to #005a8b will provide sufficient contrast.

   Impressum

3. Example 3: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The anchor element with the text "Datenschutz" has insufficient color contrast.

   Fix: Adjust the background color to ensure a contrast ratio of at least 4.5:1. For example, changing the background color to #005a8b will provide sufficient contrast.

   Datenschutz

Observation Summary

The key accessibility issues identified from both automated testing (Baat) and manual testing (MAIT) are related to insufficient color contrast. Specifically, the foreground and background colors of anchor elements do not meet the WCAG 2 AA minimum contrast ratio threshold of 4.5:1. This issue was found in multiple anchor elements on the page.

Impact on Users with Disabilities

These issues primarily affect users with visual impairments, including those with low vision and color blindness. Insufficient color contrast can make text difficult to read, leading to poor user experience and potentially causing users to miss important information or links.

Recommendations for Fixing the Issues

1. Example 1: color-contrast (serious)

   Problem: The anchor element has insufficient color contrast of 1.92 (foreground color: #ffffff, background color: #73c5e9). The expected contrast ratio is 4.5:1.

   Fix: Adjust the background color to ensure a sufficient contrast ratio. For example, changing the background color to #005b96 will provide a sufficient contrast ratio.

   <a href="https://piznet.de/kontakt/" style="color: #ffffff; background-color: #005b96;">Kontakt</a>

2. Example 2: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The anchor element for "Kontakt" does not meet the minimum color contrast ratio thresholds.

   Fix: Adjust the background color to ensure a sufficient contrast ratio. For example, changing the background color to #005b96 will provide a sufficient contrast ratio.

   <a href="https://piznet.de/kontakt/" style="color: #ffffff; background-color: #005b96;">Kontakt</a>

3. Example 3: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The anchor element for "Impressum" does not meet the minimum color contrast ratio thresholds.

   Fix: Adjust the background color to ensure a sufficient contrast ratio. For example, changing the background color to #005b96 will provide a sufficient contrast ratio.

   <a href="https://piznet.de/impressum/" style="color: #ffffff; background-color: #005b96;">Impressum</a>

4. Example 4: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The anchor element for "Datenschutz" does not meet the minimum color contrast ratio thresholds.

   Fix: Adjust the background color to ensure a sufficient contrast ratio. For example, changing the background color to #005b96 will provide a sufficient contrast ratio.

   <a href="https://piznet.de/datenschutz/" style="color: #ffffff; background-color: #005b96;">Datenschutz</a>

Observation Summary

The key accessibility issues identified from both automated testing (Baat) and manual testing (MAIT) are related to insufficient color contrast between the foreground text and background colors. Specifically, the contrast ratio of 1.92:1 does not meet the WCAG 2 AA minimum contrast ratio threshold of 4.5:1. This issue affects multiple anchor elements on the page.

Impact on Users with Disabilities

Insufficient color contrast can significantly impact users with visual impairments, including those with low vision and color blindness. These users may have difficulty reading text that does not stand out sufficiently from the background, leading to a poor user experience and potential accessibility barriers.

Recommendations for Fixing the Issues

1. Example 1: color-contrast (serious)

   Problem: The anchor element with the text "Kontakt" has a foreground color of #ffffff and a background color of #73c5e9, resulting in an insufficient contrast ratio of 1.92:1.

   Fix: Adjust the background color to a darker shade to increase the contrast ratio. For example, changing the background color to #005a8c will achieve a contrast ratio of 4.5:1.

   <a href="https://piznet.de/kontakt/" style="color: #ffffff; background-color: #005a8c;">Kontakt</a>

2. Example 2: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The anchor element with the text "Impressum" does not meet the minimum color contrast ratio thresholds.

   Fix: Adjust the background color to a darker shade to increase the contrast ratio. For example, changing the background color to #005a8c will achieve a contrast ratio of 4.5:1.

   <a href="https://piznet.de/impressum/" style="color: #ffffff; background-color: #005a8c;">Impressum</a>

3. Example 3: Elements must meet minimum color contrast ratio thresholds (serious)

   Problem: The anchor element with the text "Datenschutz" does not meet the minimum color contrast ratio thresholds.

   Fix: Adjust the background color to a darker shade to increase the contrast ratio. For example, changing the background color to #005a8c will achieve a contrast ratio of 4.5:1.

   <a href="https://piznet.de/datenschutz/" style="color: #ffffff; background-color: #005a8c;">Datenschutz</a>

Observation Summary

The key accessibility issue identified from manual testing (MAIT) is the insufficient contrast of visual information used to identify active user interface components and their states. This issue is serious as it affects the usability of the interface for users with visual impairments.

Impact on Users with Disabilities

Users with visual impairments, including those with low vision or color blindness, may have difficulty distinguishing active user interface components and their states due to insufficient contrast. This can lead to confusion and difficulty in navigating the website, reducing overall accessibility and user experience.

Recommendations for Fixing the Issues

1. Example 1: Insufficient Contrast for Active UI Components (Serious)

   Problem: The anchor element used as a thumbnail link does not have sufficient contrast to identify it as an active user interface component.

   Fix: Ensure that the visual information used to identify active user interface components has a contrast ratio of at least 3:1 against the adjacent colors. This can be achieved by adjusting the background color, border color, or text color of the component.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/neuer-recherchestandard-verabschiedet/" tabindex="-1" style="border: 2px solid #000; background-color: #fff; color: #000;">
     <!-- Content of the link -->
   </a>

Observation Summary

The key accessibility issues identified from both automated testing (Baat) and manual testing (MAIT) are related to insufficient contrast in visual information used to identify active user interface components and their states. This includes links that do not have sufficient contrast between their text and background colors, making it difficult for users to distinguish them, especially when they are in different states (e.g., hover, focus).

Impact on Users with Disabilities

These issues significantly impact users with visual impairments, including those with low vision or color blindness. Insufficient contrast can make it challenging for these users to identify interactive elements and understand their states, leading to difficulties in navigation and interaction with the website. This can result in a poor user experience and hindered accessibility.

Recommendations for Fixing the Issues

1. Example 1: Visual information used to identify active user interface components and their states must have sufficient contrast (serious)

   Problem: The link text does not have sufficient contrast against the background, making it difficult to identify.

   Fix: Ensure the link text color has a contrast ratio of at least 3:1 against the background color. For example, change the link color to a darker shade.

   <a href="https://piznet.de/kontakt/" style="color: #0056b3;">Kontakt</a>

2. Example 2: Visual information used to identify active user interface components and their states must have sufficient contrast (serious)

   Problem: The link text does not have sufficient contrast against the background, making it difficult to identify.

   Fix: Ensure the link text color has a contrast ratio of at least 3:1 against the background color. For example, change the link color to a darker shade.

   <a href="https://piznet.de/impressum/" style="color: #0056b3;">Impressum</a>

3. Example 3: Visual information used to identify active user interface components and their states must have sufficient contrast (serious)

   Problem: The link text does not have sufficient contrast against the background, making it difficult to identify.

   Fix: Ensure the link text color has a contrast ratio of at least 3:1 against the background color. For example, change the link color to a darker shade.

   <a href="https://piznet.de/datenschutz/" style="color: #0056b3;">Datenschutz</a>

4. Example 4: Any visual information that indicates a component's state must have sufficient contrast (serious)

   Problem: The link text does not have sufficient contrast against the background, making it difficult to identify its state (e.g., hover, focus).

   Fix: Ensure the link text color changes to a color with sufficient contrast when in different states. For example, change the hover color to a darker shade.

   <a href="https://piznet.de/kontakt/" style="color: #0056b3;">Kontakt</a>
   <style>
   a:hover {
     color: #003366;
   }
   </style>

5. Example 5: Any visual information that indicates a component's state must have sufficient contrast (serious)

   Problem: The link text does not have sufficient contrast against the background, making it difficult to identify its state (e.g., hover, focus).

   Fix: Ensure the link text color changes to a color with sufficient contrast when in different states. For example, change the hover color to a darker shade.

   <a href="https://piznet.de/impressum/" style="color: #0056b3;">Impressum</a>
   <style>
   a:hover {
     color: #003366;
   }
   </style>

6. Example 6: Any visual information that indicates a component's state must have sufficient contrast (serious)

   Problem: The link text does not have sufficient contrast against the background, making it difficult to identify its state (e.g., hover, focus).

   Fix: Ensure the link text color changes to a color with sufficient contrast when in different states. For example, change the hover color to a darker shade.

   <a href="https://piznet.de/datenschutz/" style="color: #0056b3;">Datenschutz</a>
   <style>
   a:hover {
     color: #003366;
   }
   </style>

Observation Summary

The key accessibility issues identified from both automated testing (Baat) and manual testing (MAIT) are related to insufficient contrast for visual information used to identify active user interface components and their states. This affects the links for "Kontakt," "Impressum," and "Datenschutz" on the website, making it difficult for users with visual impairments to identify these interactive elements.

Impact on Users with Disabilities

These issues significantly impact users with visual impairments, including those with low vision and color blindness. Insufficient contrast makes it difficult for these users to distinguish active interface components, which can hinder navigation and interaction with the website. This can lead to frustration and an inability to access important information or perform necessary actions.

Recommendations for Fixing the Issues

1. Example 1: Insufficient Contrast for "Kontakt" Link (serious)

   Problem: The "Kontakt" link does not have sufficient contrast to distinguish it as an active user interface component.

   Fix: Increase the contrast between the link text and its background. Ensure the contrast ratio is at least 3:1 for graphical objects and user interface components.

   <a href="https://piznet.de/kontakt/" style="color: #0056b3; background-color: #ffffff;">Kontakt</a>

2. Example 2: Insufficient Contrast for "Impressum" Link (serious)

   Problem: The "Impressum" link does not have sufficient contrast to distinguish it as an active user interface component.

   Fix: Increase the contrast between the link text and its background. Ensure the contrast ratio is at least 3:1 for graphical objects and user interface components.

   <a href="https://piznet.de/impressum/" style="color: #0056b3; background-color: #ffffff;">Impressum</a>

3. Example 3: Insufficient Contrast for "Datenschutz" Link (serious)

   Problem: The "Datenschutz" link does not have sufficient contrast to distinguish it as an active user interface component.

   Fix: Increase the contrast between the link text and its background. Ensure the contrast ratio is at least 3:1 for graphical objects and user interface components.

   <a href="https://piznet.de/datenschutz/" style="color: #0056b3; background-color: #ffffff;">Datenschutz</a>

Observation Summary

The key accessibility issues identified involve insufficient contrast for visual information used to identify active user interface components and their states. This issue was found in multiple anchor elements, making it difficult for users with visual impairments to distinguish these elements.

Impact on Users with Disabilities

Insufficient contrast affects users with visual impairments, including those with low vision or color blindness. These users may struggle to identify active links or buttons, making it difficult for them to navigate the website effectively. This can lead to a poor user experience and hinder their ability to access important information.

Recommendations for Fixing the Issues

1. Example 1: Insufficient Contrast for Active Links (serious)

   Problem: The anchor element for the "Kontakt" link does not have sufficient contrast between the text color and the background color.

   Fix: Ensure that the text color of the anchor element has a contrast ratio of at least 3:1 against its background. This can be achieved by adjusting the CSS styles.

   <a href="https://piznet.de/kontakt/" style="color: #0056b3; background-color: #ffffff;">Kontakt</a>

2. Example 2: Insufficient Contrast for Active Links (serious)

   Problem: The anchor element for the "Impressum" link does not have sufficient contrast between the text color and the background color.

   Fix: Ensure that the text color of the anchor element has a contrast ratio of at least 3:1 against its background. This can be achieved by adjusting the CSS styles.

   <a href="https://piznet.de/impressum/" style="color: #0056b3; background-color: #ffffff;">Impressum</a>

3. Example 3: Insufficient Contrast for Active Links (serious)

   Problem: The anchor element for the "Datenschutz" link does not have sufficient contrast between the text color and the background color.

   Fix: Ensure that the text color of the anchor element has a contrast ratio of at least 3:1 against its background. This can be achieved by adjusting the CSS styles.

   <a href="https://piznet.de/datenschutz/" style="color: #0056b3; background-color: #ffffff;">Datenschutz</a>

Observation Summary

The key accessibility issues identified from both automated testing (Baat) and manual testing (MAIT) include the following: 1) Links without discernible text, and 2) Links whose purpose is not clear from the link text alone or from the context. These issues affect the ability of screen readers to convey meaningful information about the links to users.

Impact on Users with Disabilities

These issues significantly impact users with visual impairments who rely on screen readers to navigate web content. Without discernible text, screen readers cannot provide users with information about the link's destination, making it difficult for them to understand the purpose of the link. This can lead to confusion and a poor user experience, as users may not be able to navigate the website effectively.

Recommendations for Fixing the Issues

1. Example 1: link-name (serious)

   Problem: The link does not have text that is visible to screen readers, making it impossible for users to understand its purpose.

   Fix: Add discernible text within the anchor tag to describe the link's purpose.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/neuer-recherchestandard-verabschiedet/" tabindex="-1">Read more about the new research standard</a>

2. Example 2: Links must have discernible text (serious)

   Problem: The link lacks discernible text, making it inaccessible to screen readers.

   Fix: Provide meaningful text within the anchor tag to ensure it is accessible.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/neuer-recherchestandard-verabschiedet/" tabindex="-1">Read more about the new research standard</a>

3. Example 3: The purpose of a link must be described by its link text alone, or by the link text together with preceding page context (serious)

   Problem: The link's purpose is not clear from the link text alone or from the context, making it difficult for users to understand where the link will take them.

   Fix: Ensure the link text is descriptive enough to convey the link's purpose.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/neuer-recherchestandard-verabschiedet/" tabindex="-1">Read more about the new research standard</a>

Observation Summary

The key accessibility issue identified from both automated testing (Baat) and manual testing (MAIT) is that the purpose of the links is not clearly described by their link text alone or by the link text together with the preceding page context. This violates WCAG 2.4.4 (Link Purpose (In Context)).

Impact on Users with Disabilities

These issues significantly affect users with disabilities, particularly those who rely on screen readers. Users with visual impairments or cognitive disabilities may find it difficult to understand the purpose of the links if the context is not clear. This can lead to confusion and difficulty in navigating the website effectively.

Recommendations for Fixing the Issues

1. Example 1: Link Purpose (serious)

   Problem: The link text "Unser Leitbild" does not clearly describe the purpose of the link.

   Fix: Add additional context or use a more descriptive link text.

   <a class="elementor-accordion-title" tabindex="0" href="leitbild.html">Unser Leitbild - Learn about our mission</a>

2. Example 2: Link Purpose (serious)

   Problem: The link text "Was sind die Aufgaben eines PIZ?" does not clearly describe the purpose of the link.

   Fix: Add additional context or use a more descriptive link text.

   <a class="elementor-accordion-title" tabindex="0" href="aufgaben-piz.html">Was sind die Aufgaben eines PIZ? - Learn about the tasks of a PIZ</a>

3. Example 3: Link Purpose (serious)

   Problem: The link text "An wen richtet ein PIZ seine Dienste?" does not clearly describe the purpose of the link.

   Fix: Add additional context or use a more descriptive link text.

   <a class="elementor-accordion-title" tabindex="0" href="dienste-piz.html">An wen richtet ein PIZ seine Dienste? - Learn about the services of a PIZ</a>

4. Example 4: Link Purpose (serious)

   Problem: The link text "Was möchten die Patentinformationszentren gemeinsam erreichen?" does not clearly describe the purpose of the link.

   Fix: Add additional context or use a more descriptive link text.

   <a class="elementor-accordion-title" tabindex="0" href="ziele-piz.html">Was möchten die Patentinformationszentren gemeinsam erreichen? - Learn about the goals of the PIZ</a>

5. Example 5: Link Purpose (serious)

   Problem: The link text "Wofür stehen die Patentinformationszentren ein?" does not clearly describe the purpose of the link.

   Fix: Add additional context or use a more descriptive link text.

   <a class="elementor-accordion-title" tabindex="0" href="werte-piz.html">Wofür stehen die Patentinformationszentren ein? - Learn about the values of the PIZ</a>

Observation Summary

The key accessibility issues identified from both automated testing (Baat) and manual testing (MAIT) are primarily related to links lacking discernible text and link text not clearly describing the purpose of the link. These issues are critical as they prevent screen readers from conveying the link's purpose to users, making navigation and understanding of the content difficult.

Impact on Users with Disabilities

These issues significantly impact users with visual impairments who rely on screen readers to navigate the web. Without discernible text, screen readers cannot provide meaningful information about the links, leading to confusion and difficulty in navigation. Users with cognitive disabilities may also struggle to understand the purpose of the links if they are not clearly described.

Recommendations for Fixing the Issues

1. Example 1: Ensure links have discernible text (serious)

   Problem: The link does not have text that is visible to screen readers.

   Fix: Add descriptive text within the anchor element to make the link purpose clear.

   <a href="https://piznet.de/mitglied/patent-und-normenzentrum-aachen/">Patent und Normenzentrum Aachen</a>

2. Example 2: Links must have discernible text (serious)

   Problem: The link lacks text that screen readers can discern.

   Fix: Include descriptive text within the anchor element.

   <a href="https://piznet.de/mitglied/informationszentrum-technik-und-patente-itp/">Informationszentrum Technik und Patente ITP</a>

3. Example 3: Links must have discernible text (serious)

   Problem: The link lacks discernible text for screen readers.

   Fix: Add descriptive text within the anchor element.

   <a href="https://piznet.de/mitglied/minesoft-ltd/">Minesoft Ltd</a>

4. Example 4: The purpose of a link must be described by its link text alone, or by the link text together with preceding page context (serious)

   Problem: The link text does not sufficiently describe the link's purpose.

   Fix: Ensure the link text or the surrounding context clearly describes the link's purpose.

   <a href="https://piznet.de/mitglied/patent-und-normenzentrum-aachen/">Learn more about Patent und Normenzentrum Aachen</a>

5. Example 5: The purpose of a link must be described by its link text alone, or by the link text together with preceding page context (serious)

   Problem: The link text does not provide enough information about the link's purpose.

   Fix: Add descriptive text to the link or ensure the surrounding context clarifies the link's purpose.

   <a href="https://piznet.de/mitglied/informationszentrum-technik-und-patente-itp/">Learn more about Informationszentrum Technik und Patente ITP</a>

6. Example 6: The purpose of a link must be described by its link text alone, or by the link text together with preceding page context (serious)

   Problem: The link text does not sufficiently describe the link's purpose.

   Fix: Ensure the link text or the surrounding context clearly describes the link's purpose.

   <a href="https://piznet.de/mitglied/patentinformationszentrum-hannover/">Learn more about Patent Informationszentrum Hannover</a>

7. Example 7: The purpose of a link must be described by its link text alone, or by the link text together with preceding page context (serious)

   Problem: The link text does not provide enough information about the link's purpose.

   Fix: Add descriptive text to the link or ensure the surrounding context clarifies the link's purpose.

   <a href="https://piznet.de/mitglied/patent-und-markenzentrum-saar/">Learn more about Patent und Markenzentrum Saar</a>

8. Example 8: The purpose of a link must be described by its link text alone, or by the link text together with preceding page context (serious)

   Problem: The link text does not sufficiently describe the link's purpose.

   Fix: Ensure the link text or the surrounding context clearly describes the link's purpose.

   <a href="https://piznet.de/mitglied/athena-technologie-beratung-gmbh/">Learn more about Athena Technologie Beratung GmbH</a>

Observation Summary

The key accessibility issues found from both automated testing (Baat) and manual testing (MAIT) include links without discernible text and links whose purpose is not clear from the link text alone or the surrounding context. These issues are serious and impact the usability of the website for users relying on screen readers.

Impact on Users with Disabilities

These issues significantly affect users with visual impairments who rely on screen readers to navigate the web. Links without discernible text or unclear link purposes make it difficult for these users to understand the content and navigate the website effectively. This can lead to confusion, frustration, and an inability to access important information.

Recommendations for Fixing the Issues

1. Example 1: link-name (serious)

   Problem: The link does not have text that is visible to screen readers.

   Fix: Add discernible text to the link using an aria-label attribute or by including text within the anchor element.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/neuer-recherchestandard-verabschiedet/" tabindex="-1" aria-label="Read more about Neuer Recherchestandard Verabschiedet"></a>

2. Example 2: Links must have discernible text (serious)

   Problem: The link does not have discernible text.

   Fix: Add discernible text to the link using an aria-label attribute or by including text within the anchor element.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/neuer-recherchestandard-verabschiedet/" tabindex="-1" aria-label="Read more about Neuer Recherchestandard Verabschiedet"></a>

3. Example 3: Links must have discernible text (serious)

   Problem: The link does not have discernible text.

   Fix: Add discernible text to the link using an aria-label attribute or by including text within the anchor element.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/rueckblick-auf-ip-enforcement-day-und-35-piznet-jahrestagung/" tabindex="-1" aria-label="Read more about Rueckblick auf IP Enforcement Day und 35 Piznet Jahrestagung"></a>

4. Example 4: The purpose of a link must be described by its link text alone, or by the link text together with preceding page context (serious)

   Problem: The purpose of the link is not clear from the link text alone or the surrounding context.

   Fix: Add more descriptive text to the link or use an aria-label attribute to clarify the link's purpose.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/neuer-recherchestandard-verabschiedet/" tabindex="-1" aria-label="Read more about Neuer Recherchestandard Verabschiedet"></a>

5. Example 5: The purpose of a link must be described by its link text alone, or by the link text together with preceding page context (serious)

   Problem: The purpose of the link is not clear from the link text alone or the surrounding context.

   Fix: Add more descriptive text to the link or use an aria-label attribute to clarify the link's purpose.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/rueckblick-auf-ip-enforcement-day-und-35-piznet-jahrestagung/" tabindex="-1" aria-label="Read more about Rueckblick auf IP Enforcement Day und 35 Piznet Jahrestagung"></a>

6. Example 6: The purpose of a link must be described by its link text alone, or by the link text together with preceding page context (serious)

   Problem: The purpose of the link is not clear from the link text alone or the surrounding context.

   Fix: Add more descriptive text to the link or use an aria-label attribute to clarify the link's purpose.

   <a class="page-numbers next" href="https://piznet.de/news/2/" aria-label="Go to next page">»</a>

Observation Summary

The key accessibility issues identified include: 1) An element coded as a heading must function as a heading, and 2) Text that looks like a heading must be coded as a heading. These issues were found through both automated testing (Baat) and manual testing (MAIT).

Impact on Users with Disabilities

These issues can significantly impact users with disabilities, particularly those who rely on screen readers. Screen readers use headings to navigate and understand the structure of the content. If elements are incorrectly coded as headings or if text that appears to be a heading is not coded as such, it can cause confusion and make navigation difficult for users with visual impairments or cognitive disabilities.

Recommendations for Fixing the Issues

1. Example 1: An element coded as a heading must function as a heading (serious)

   Problem: The element is coded as an <h2> heading but is used in a context where it does not function as a heading.

   Fix: Ensure that the <h2> element is used appropriately as a heading. If it is not meant to be a heading, use a different HTML element such as a <p> or <div>.

   <p class="elementor-heading-title elementor-size-default">Unsere Mitglieder sind anerkannte Kooperationspartner <br>des Deutschen Patent- und Markenamtes (DPMA) und Teil des europäischen PATLIB‑Netzwerks.</p>

2. Example 2: Text that looks like a heading must be coded as a heading (serious)

   Problem: The text "Unsere Mitglieder sind anerkannte Kooperationspartner des Deutschen Patent- und Markenamtes (DPMA) und Teil des europäischen PATLIB‑Netzwerks." appears to be a heading but is not coded as one.

   Fix: Ensure that the text is coded as a heading using the appropriate heading tag, such as <h2>.

   <h2>Unsere Mitglieder sind anerkannte Kooperationspartner des Deutschen Patent- und Markenamtes (DPMA) und Teil des europäischen PATLIB‑Netzwerks.</h2>

Observation Summary

The key accessibility issue identified is that components, specifically within a map interface, do not provide a visible indication when they have input focus. This issue was found through both automated testing (Baat) and manual testing (MAIT).

Impact on Users with Disabilities

This issue significantly affects users with visual impairments, including those who rely on keyboard navigation. Without a visible focus indicator, these users may not be able to determine which element is currently focused, making it difficult to navigate and interact with the map interface effectively.

Recommendations for Fixing the Issues

1. Example 1: Focus Indication (serious)

   Problem: The map interface does not provide a visible indication when elements within it receive input focus.

   Fix: Ensure that all focusable elements within the map interface have a visible focus indicator. This can be achieved by using CSS to style the focus state of these elements.

   
   
   
   
   
   </code></pre></li></ol>
   
   

Observation Summary

The key accessibility issues identified from both automated testing (Baat) and manual testing (MAIT) include links without discernible text and anchor elements functioning as custom widgets without the appropriate ARIA widget roles. These issues violate WCAG 4.1.2 (Name, Role, Value) guidelines.

Impact on Users with Disabilities

These issues significantly impact users with disabilities, particularly those who rely on screen readers. Links without discernible text cannot be understood or navigated by screen reader users, making it difficult for them to access content. Additionally, anchor elements functioning as custom widgets without appropriate ARIA roles can confuse users who depend on assistive technologies, as the role and functionality of these elements are not properly conveyed.

Recommendations for Fixing the Issues

1. Example 1: link-name (serious)

   Problem: The link does not have text that is visible to screen readers, making it inaccessible.

   Fix: Add discernible text within the anchor element to ensure it is accessible to screen readers.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/neuer-recherchestandard-verabschiedet/" tabindex="-1">Read more about the new research standard</a>

2. Example 2: Links must have discernible text (serious)

   Problem: The link lacks discernible text, making it inaccessible to screen readers.

   Fix: Ensure the link contains text that can be read by screen readers.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/neuer-recherchestandard-verabschiedet/" tabindex="-1">Read more about the new research standard</a>

3. Example 3: If an anchor element functions as a custom widget, it must have the appropriate ARIA widget role (serious)

   Problem: The anchor element functions as a custom widget but does not have the appropriate ARIA widget role, making it inaccessible to assistive technologies.

   Fix: Add the appropriate ARIA role to the anchor element to ensure it is recognized correctly by assistive technologies.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/neuer-recherchestandard-verabschiedet/" tabindex="-1" role="button">Read more about the new research standard</a>

Observation Summary

The key accessibility issues identified include the use of unsupported ARIA attributes and the improper use of anchor elements as custom widgets without the appropriate ARIA roles. These issues were found both through automated testing and manual inspection.

Impact on Users with Disabilities

These issues can significantly impact users with disabilities, particularly those who rely on assistive technologies such as screen readers. Unsupported ARIA attributes can cause confusion or misinterpretation of the element's purpose, while anchor elements functioning as custom widgets without proper roles can lead to navigation difficulties and a lack of clarity regarding the element's functionality.

Recommendations for Fixing the Issues

1. Example 1: aria-allowed-attr (critical)

   Problem: The div element uses ARIA attributes that are not supported by its role.

   Fix: Remove unsupported ARIA attributes or change the role to one that supports the attributes.

   <div id="elementor-tab-title-2841" class="elementor-tab-title elementor-active" data-tab="1" role="button" aria-controls="elementor-tab-content-2841" aria-expanded="true" tabindex="0">

2. Example 2: Elements must only use supported ARIA attributes (serious)

   Problem: The div element uses ARIA attributes that are not supported by its role.

   Fix: Ensure that the ARIA attributes used are supported by the element's role.

   <div id="elementor-tab-title-2841" class="elementor-tab-title elementor-active" data-tab="1" role="tab" aria-controls="elementor-tab-content-2841" aria-expanded="true" tabindex="0" aria-selected="true">

3. Example 3: If an anchor element functions as a custom widget, it must have the appropriate ARIA widget role (serious)

   Problem: The a element functions as a custom widget but lacks the appropriate ARIA role.

   Fix: Add the appropriate ARIA role to the anchor element.

   <a class="elementor-accordion-title" tabindex="0" role="button" aria-expanded="false">Unser Leitbild</a>

4. Example 4: If an anchor element functions as a custom widget, it must have the appropriate ARIA widget role (serious)

   Problem: The a element functions as a custom widget but lacks the appropriate ARIA role.

   Fix: Add the appropriate ARIA role to the anchor element.

   <a class="elementor-accordion-title" tabindex="0" role="button" aria-expanded="false">Was sind die Aufgaben eines PIZ?</a>

5. Example 5: If an anchor element functions as a custom widget, it must have the appropriate ARIA widget role (serious)

   Problem: The a element functions as a custom widget but lacks the appropriate ARIA role.

   Fix: Add the appropriate ARIA role to the anchor element.

   <a class="elementor-accordion-title" tabindex="0" role="button" aria-expanded="false">An wen richtet ein PIZ seine Dienste?</a>

6. Example 6: If an anchor element functions as a custom widget, it must have the appropriate ARIA widget role (serious)

   Problem: The a element functions as a custom widget but lacks the appropriate ARIA role.

   Fix: Add the appropriate ARIA role to the anchor element.

   <a class="elementor-accordion-title" tabindex="0" role="button" aria-expanded="false">Was möchten die Patentinformationszentren gemeinsam erreichen?</a>

7. Example 7: If an anchor element functions as a custom widget, it must have the appropriate ARIA widget role (serious)

   Problem: The a element functions as a custom widget but lacks the appropriate ARIA role.

   Fix: Add the appropriate ARIA role to the anchor element.

   <a class="elementor-accordion-title" tabindex="0" role="button" aria-expanded="false">Wofür stehen die Patentinformationszentren ein?</a>

Observation Summary

The key accessibility issues identified from both automated testing (Baat) and manual testing (MAIT) are related to links that lack discernible text. This means that the anchor elements (<a>) do not contain text that is visible to screen readers, making it difficult for users relying on assistive technologies to understand the purpose of these links.

Impact on Users with Disabilities

These issues significantly affect users with visual impairments who rely on screen readers to navigate web content. Without discernible text, screen readers cannot convey the purpose of the links, leading to confusion and a poor user experience. This can also affect users with cognitive disabilities who may rely on clear and descriptive link text to understand the context and destination of the links.

Recommendations for Fixing the Issues

1. Example 1: link-name (serious)

   Problem: The anchor element does not have text that is visible to screen readers.

   Fix: Add discernible text within the anchor element to describe the link's purpose.

   <a href="https://piznet.de/mitglied/patent-und-normenzentrum-aachen/">Patent und Normenzentrum Aachen</a>

2. Example 2: Links must have discernible text (serious)

   Problem: The anchor element does not have text that is visible to screen readers.

   Fix: Add discernible text within the anchor element to describe the link's purpose.

   <a href="https://piznet.de/mitglied/patent-und-normenzentrum-aachen/">Patent und Normenzentrum Aachen</a>

3. Example 3: Links must have discernible text (serious)

   Problem: The anchor element does not have text that is visible to screen readers.

   Fix: Add discernible text within the anchor element to describe the link's purpose.

   <a href="https://piznet.de/mitglied/informationszentrum-technik-und-patente-itp/">Informationszentrum Technik und Patente ITP</a>

4. Example 4: Links must have discernible text (serious)

   Problem: The anchor element does not have text that is visible to screen readers.

   Fix: Add discernible text within the anchor element to describe the link's purpose.

   <a href="https://piznet.de/mitglied/minesoft-ltd/">Minesoft Ltd</a>

Observation Summary

The key accessibility issues identified from both automated testing (Baat) and manual testing (MAIT) are related to links that lack discernible text. Specifically, there are multiple instances where anchor elements do not have text that is visible to screen readers, which violates WCAG 4.1.2 (Name, Role, Value).

Impact on Users with Disabilities

These issues significantly affect users with disabilities, particularly those who rely on screen readers. Without discernible text, screen readers cannot convey the purpose of the links to users, making navigation and content comprehension difficult. This impacts users with visual impairments, cognitive disabilities, and those who use assistive technologies.

Recommendations for Fixing the Issues

1. Example 1: link-name (serious)

   Problem: The anchor element does not have text that is visible to screen readers.

   Fix: Add discernible text within the anchor element to ensure it is accessible to screen readers.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/neuer-recherchestandard-verabschiedet/" tabindex="-1">Neuer Recherchestandard Verabschiedet</a>

2. Example 2: Links must have discernible text (serious)

   Problem: The anchor element does not have text that is visible to screen readers.

   Fix: Add discernible text within the anchor element to ensure it is accessible to screen readers.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/neuer-recherchestandard-verabschiedet/" tabindex="-1">Neuer Recherchestandard Verabschiedet</a>

3. Example 3: Links must have discernible text (serious)

   Problem: The anchor element does not have text that is visible to screen readers.

   Fix: Add discernible text within the anchor element to ensure it is accessible to screen readers.

   <a class="elementor-post__thumbnail__link" href="https://piznet.de/rueckblick-auf-ip-enforcement-day-und-35-piznet-jahrestagung/" tabindex="-1">Rückblick auf IP Enforcement Day und 35 PIZnet Jahrestagung</a>