Digital accessibility will be a legal requirement from June 2025. It applies to companies launching a new website or digital service and requires everything to comply with the WCAG 2.1 standard. Despite this, most websites make mistakes that prevent people with disabilities from accessing them.
Digital accessibility will be a legal requirement from June 2025. It applies to companies launching a new website or digital service and requires everything to comply with the WCAG 2.1 standard. Despite this, most websites make mistakes that prevent people with disabilities from accessing them.
In this article, you will find the five most common problems that cause websites to fail both legal requirements and user expectations—along with specific recommendations on how to fix them in accordance with WCAG 2.1 and Act No. 424/2023 Coll.
Not sure what exactly an "accessible website" means?
Read the article: A functional website ≠ an accessible website. How to tell the difference — and why it matters.
1. Images without alternative descriptions
Why this is a problem:
A screen reader will only announce "image" – without context or meaning.
How to fix it:
Add an alt attribute to meaningful images that summarizes the meaning of the image (not its appearance). For example, instead of "graph," write: "Year-on-year traffic increased by 18%."
2. Buttons without text or description
Why it's a problem:
Icons without text (shopping cart, magnifying glass) don't make sense to users who navigate the web using a reader.
How to fix it:
- Add aria-label, title, or accompanying text.
- It's best to combine the icon with a visible label.
3. Poor text contrast
Why it's a problem:
Gray text on a white background can be unreadable — not only for the visually impaired, but also on mobile devices or in sunlight.
How to fix it:
- The minimum contrast for normal text is 4.5:1 (according to WCAG).
- Check using the WebAIM Contrast Checker tool.
4. Forms without labeled fields
Why it's a problem:
Without labels, screen readers don't know what users should type into the fields.
How to fix it:
- Every field must have a label (visible or aria-label).
- Don't use placeholders as a substitute — they disappear when clicked and aren't readable by screen readers.
5. Non-functional keyboard controls
Why it's a problem:
People who cannot use a mouse cannot access all elements of the website – or lose track of where they are.
How to fix it:
- The website must be fully controllable using the Tab and Enter keys.
- Every active element must have visible focus.
- Actions (e.g., buttons) must be predictable.
What next?
If your website contains one or more of these errors, it may mean that:
- it does not meet WCAG 2.1 requirements,
- it does not comply with Act No. 424/2023 Coll. and Act No. 99/2019 Coll.
- it excludes some users – and thus customers.
Are you interested in what specifically you risk if you do not correct the errors?
Read: What you risk if you ignore the accessibility law
Would you like to check your website?
See: 3 ways to find out if your website is accessible.
What we can do for you
Consultation with an expert
You will receive an answer to the question of whether the law applies to you – and how to proceed.
Order a consultation
Accessibility audit
We will verify whether your website complies with WCAG 2.1 and legal requirements.
Get an audit quote
Design or redesign of an accessible website
We will design a website that is accessible, functional, and ready for 2025.
I want an accessible website
Digital accessibility is now standard—not just a bonus.
Get the advantage before the law or your customers force you to.
Read: Accessibility as an advantage: UX, SEO, and higher conversion rates