Non-accessible content
4. The website is not yet fully compliant
-
Perceivable: Poor table formatting
Non-accessible content and issues
Some tables are missing <th> tags, making it difficult for screen readers to understand which cells are headers.
Accessibility criteria not met
- 1.3.1 Info and Relationships
-
Perceivable: Insufficient contrast
Non-accessible content and issues
For users with visual impairments, it is important that the contrast between background and text is sufficient.
Accessibility criteria not met
- 1.4.3 Contrast (Minimum)
-
Operable: Link purpose (in context)
Non-accessible content and issues
Several links have similar text and context but lead to different destinations. This appears in cases like "Read more" and "See more".
Accessibility criteria not met
- 2.4.4 Link Purpose (In Context)
-
Operable: Clickable links must not have empty href attributes
Non-accessible content and issues
Some <a> tags behave like buttons, making it harder for screen readers to interpret their function correctly.
Accessibility criteria not met
- 2.1.1 Keyboard
-
Operable: Links must have accessible names
Non-accessible content and issues
Some <a> tags are missing aria-labels, aria-labelledby attributes, or inner text, making the link’s purpose unclear to screen readers.
Accessibility criteria not met
- 2.4.4 Link Purpose (In Context)
-
Operable: Labels are empty
Non-accessible content and issues
Some <label> tags lack descriptive content.
Accessibility criteria not met
- 2.4.6 Headings and Labels
-
Operable: Visible focus
Non-accessible content and issues
CSS styling makes it impossible to see which element currently has focus.
Accessibility criteria not met
- 2.4.7 Focus Visible
-
Robust: Keyboard accessibility to content
Non-accessible content and issues
Some links are missing the tabindex attribute, making them inaccessible via keyboard alone.
Accessibility criteria not met
- 4.1.2 Name, Role, Value