EU Accessibility Act: why digital accessibility is now essential
The EU Accessibility Act (Directive 2019/882) is no longer optional. Starting June 28, 2025, all digital services in the EU must be accessible to people with disabilities. This is not just a legal obligation - it's also an enormous opportunity to expand your audience and improve your services for everyone.
What is the EU Accessibility Act?
The European Accessibility Act (EAA) is European legislation that ensures products and services are accessible to people with disabilities. For websites and applications, this means full compliance with the Web Content Accessibility Guidelines (WCAG) 2.1 level AA.
Key deadlines
- June 28, 2025: EU Accessibility Act becomes mandatory
- From this date: all new digital services must be fully accessible
- Existing services: must be adapted to the new requirements
- Non-compliance: can lead to fines and legal consequences
Who must comply with the law?
The EU Accessibility Act applies to a wide range of digital services and products:
Mandatory services
- E-commerce websites and webshops
- Banking and financial services
- E-books and digital media
- Transport and travel bookings
- Government websites
- Telecommunication services
Exempted
- Micro-enterprises (<10 employees)
- Organizations with annual revenue <€2M
- Archive material (published before 2025)
- Live video/audio streams (with exceptions)
Why is digital accessibility important?
Accessibility goes beyond compliance. It improves the user experience for everyone:
- Elderly people can use your services better
- People with temporary disabilities (broken arm, eye surgery) benefit
- Better SEO rankings - search engines value accessible websites
- Higher conversion rate - accessible sites are easier to use
- Fewer legal risks and better brand perception
- Larger market reach - 15% extra potential customers
WCAG 2.1 Level AA: the technical standard
The EU requires compliance with WCAG 2.1 level AA via the European standard EN 301 549 v3.2.1. This standard includes four core principles:
The 4 WCAG principles (POUR)
- Perceivable: content must be visible to all users, including via screen readers
- Operable: interface must be usable with keyboard, mouse, or assistive tools
- Understandable: content and operation must be clear and consistent
- Robust: content must work with current and future assistive technologies
How SEMSIT achieved full compliance
At SEMSIT, we have fully adapted our own website to the EU Accessibility Act. This process included more than 83 pages and components. Here's how we approached it:
1. Complete accessibility infrastructure
We laid a solid foundation with reusable components and utilities:
2. ESLint automation
We configured 14 strict ESLint jsx-a11y rules that automatically detect accessibility violations during development. The build fails if there are issues - enforcing compliance.
3. Made all components accessible
- Headers with full keyboard navigation and aria-expanded attributes
- Forms with aria-required, aria-invalid and aria-describedby
- Modals with focus trapping, Escape key handlers and aria-modal
- Accordions with correct ARIA roles and aria-controls
- Buttons with aria-labels and keyboard event handlers
- Clickable cards with role="button" and tabIndex support
4. Optimized every page
All 83+ pages have been systematically adapted with:
Practical accessibility checklist
Want to make your website accessible? Use this checklist to get started:
Accessibility audit checklist
- ✓ Keyboard navigation: can your entire site be used without a mouse?
- ✓ Screen reader test: test with NVDA (Windows) or VoiceOver (Mac)
- ✓ Color contrast: minimum 4.5:1 for text, 3:1 for UI elements
- ✓ Focus indicators: are they clearly visible during Tab navigation?
- ✓ Alt text: do all images have descriptive alt attributes?
- ✓ Heading hierarchy: logical structure H1→H2→H3?
- ✓ Form labels: all inputs with <label> or aria-label?
- ✓ ARIA attributes: correct use of aria-expanded, aria-controls, etc?
- ✓ Error handling: are errors announced to screen readers?
- ✓ Skip links: skip to main content link present?
Tools for accessibility testing
Automated testing
- axe DevTools (browser extension)
- WAVE Evaluation Tool
- Lighthouse (Chrome DevTools)
- ESLint jsx-a11y plugin
- Pa11y CI for automated testing
Manual testing
- NVDA screen reader (Windows)
- JAWS screen reader (Windows)
- VoiceOver (macOS/iOS)
- TalkBack (Android)
- Keyboard navigation
The business case for accessibility
Accessibility is not just compliance - it's an investment that pays off:
- Better SEO: Google rewards accessible websites with higher rankings
- Larger audience: Reach 15% extra potential customers
- Lower bounce rate: Accessible sites are more user-friendly for everyone
- Brand reputation: Shows social responsibility
- Legal protection: Avoid fines and lawsuits
- Future-proof: Ready for new legislation and technologies
Legal consequences of non-compliance
The EU Accessibility Act is binding legislation. Non-compliance can lead to:
Risks of non-compliance
- Administrative fines imposed by national authorities
- Civil lawsuits from users with disabilities
- Mandatory website adjustments within short timeframe
- Reputation damage and negative publicity
- Loss of government contracts and subsidies
- Exclusion from EU tenders
Implementation timeline
This is how long it typically takes to make a website fully accessible:
For SEMSIT's own website (83+ pages), the complete implementation took approximately 6 weeks from planning to production.
Steps to compliance
Follow this roadmap to make your website accessible:
- 1. Audit: conduct an accessibility audit with automated tools
- 2. Prioritize: identify critical issues that need immediate fixing
- 3. Infrastructure: implement basic accessibility components and hooks
- 4. Components: create reusable accessible components (buttons, forms, modals)
- 5. Pages: fix heading hierarchy, alt text and ARIA labels on all pages
- 6. Testing: test with real screen readers and keyboard navigation
- 7. Training: train your team in accessibility best practices
- 8. Monitoring: set up continuous testing with ESLint and CI/CD checks
- 9. Documentation: publish an accessibility statement at /accessibility
- 10. Maintain: keep testing accessibility with new features
SEMSIT's accessibility statement
As part of our compliance, we published a comprehensive accessibility statement. This includes:
You can view our full accessibility statement at: https://semsit.nl/accessibility
Quick win: basic accessibility fixes
Want to start quickly? Begin with these high-impact, low-effort improvements:
HTML & semantic
- Add alt text to all <img> tags
- Use <button> for buttons, not <div>
- Use <nav>, <main>, <header>, <footer>
- Logical heading order (H1→H2→H3)
- Labels on all form inputs
CSS & interaction
- Visible focus indicators (:focus-visible)
- Minimum 4.5:1 color contrast
- No information through color alone
- Text zoomable to 200%
- Click targets minimum 44x44px
Conclusion: accessibility is essential
The EU Accessibility Act is more than legislation - it's an opportunity to improve your digital services for everyone. At SEMSIT, we've proven that full WCAG 2.1 AA compliance is achievable, even for complex websites with dozens of pages.
By starting early, working systematically, and using the right tools, you can not only make your website compliant but also better, faster, and more user-friendly for all visitors.
“Accessibility is no longer optional - it's a fundamental part of modern web development. Companies that ignore this not only run legal risks but also miss an enormous opportunity to expand their audience.”
Make your website accessible
SEMSIT helps companies with full EU Accessibility Act compliance. From audit to implementation and testing - we ensure your website is WCAG 2.1 AA compliant before the June 28, 2025 deadline.
Request accessibility audit