Accessibility Statement
www.liwlig.com
Statement prepared on 10.4.2026
This accessibility statement describes the accessibility issues that have been identified on the website. The statement also explains how you can report accessibility issues to us and suggest improvements to the accessibility of the site.
The accessibility assessment is based on an evaluation conducted by Netello’s experts.
Accessibility status of the digital service
The service largely meets the accessibility requirements (WCAG 2.2 criteria at levels A and AA).
Non-accessible content
Missing form labels
Some form controls do not have corresponding programmatic labels. This may make it difficult for screen reader users to understand the purpose of form fields.
WCAG references:
- 1.1.1 Non-text Content (Level A)
- 1.3.1 Info and Relationships (Level A)
- 2.4.6 Headings and Labels (Level AA)
- 3.3.2 Labels or Instructions (Level A)
Empty form labels
Some form labels are present but do not contain any text content. As a result, assistive technologies may not provide sufficient information about the associated form controls.
WCAG references:
- 1.1.1 Non-text Content (Level A)
- 1.3.1 Info and Relationships (Level A)
- 2.4.6 Headings and Labels (Level AA)
- 3.3.2 Labels or Instructions (Level A)
Empty headings
Some heading elements do not contain any content. This may negatively impact the logical structure and navigability of the page for assistive technology users.
WCAG references:
- 1.3.1 Info and Relationships (Level A)
- 2.4.1 Bypass Blocks (Level A)
- 2.4.6 Headings and Labels (Level AA)
Broken ARIA references
Some ARIA attributes (aria-labelledby or aria-describedby) reference elements that do not exist. This may prevent assistive technologies from correctly determining the accessible name or description of components.
WCAG references:
- 1.3.1 Info and Relationships (Level A)
- 4.1.2 Name, Role, Value (Level A)
Insufficient color contrast
In some cases, the contrast between text and background colors does not meet the minimum contrast requirements, which may make content difficult to read for users with visual impairments.
WCAG references:
- 1.4.3 Contrast (Minimum) (Level AA)
Carousel navigation not fully keyboard accessible
The navigation controls of the carousel may not be fully usable when navigating the site using only a keyboard.
WCAG references:
- 2.1.1 Keyboard (Level A)
Hover-based content not keyboard accessible
Some content is revealed only when hovering over headings. This interaction may not be accessible to users who navigate the site using a keyboard only.
WCAG references:
- 2.1.1 Keyboard (Level A)
- 2.4.3 Focus Order (Level A)
Floating contact form not announced to screen readers
When the floating contact form is opened using the floating contact button, screen readers do not announce that new content has appeared. This may make the form difficult to perceive for screen reader users.
WCAG references:
- 4.1.2 Name, Role, Value (Level A)
- 3.2.2 On Input (Level A)
Redundant links in filter buttons
Some filter buttons contain redundant links. This may result in unnecessary repetition when navigating the site using a screen reader and keyboard.
WCAG references:
- 2.4.4 Link Purpose (In Context) (Level A)
Missing captions in videos
Some videos may not include captions or other equivalent text alternatives.
WCAG references:
- 1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
- 1.2.2 Captions (Prerecorded) (Level A)
- 1.2.3 Audio Description or Media Alternative (Level A)
Redundant alternative text
In some cases, image alternative text repeats the same information as nearby or adjacent visible text. This may cause unnecessary repetition for screen reader users.
WCAG references:
- 1.1.1 Non-text Content (Level A)
Redundant links
In some cases, adjacent links lead to the same URL. This may cause unnecessary repetition and make navigation more difficult for users who rely on screen readers or keyboard navigation.
WCAG references:
- 2.4.4 Link Purpose (In Context) (Level A)
Did you notice an accessibility issue?
If you would like to provide feedback about the accessibility of our website, please send an email to XXX. Remember to mention which page the issue occurs on and describe the problem as clearly and in as much detail as possible. You may also attach an image/screenshot of the accessibility issue.