In today’s society, digital technology has become a fundamental tool for education, work, communication, and accessing services. Yet, millions of people face daily barriers that exclude them from the digital world.
We’re talking about people with disabilities – one of the most diverse, yet often most overlooked, social groups when it comes to digital inclusion.
Who Are People with Disabilities?
Disability encompasses a wide range of permanent or temporary impairments that may affect a person’s ability to function in daily life. It’s important to understand that disability is not just a physical limitation – it can be:
- Physical – difficulties with movement, using hands, or motor coordination
- Sensory – vision or hearing impairment, or both
- Cognitive and neurological – dyslexia, attention disorders, autism
- Psychological – anxiety disorders, depression, and other mental health challenges
- Temporary – a broken arm, post-surgery recovery, fatigue, stress
Web accessibility is not meant for just one group but for a wide range of users with different needs. Some examples include:
- People with low vision rely on screen readers or enlarged text to access information.
- People with dyslexia benefit from simple, readable fonts and clearly organized content without distractions.
- People with color blindness depend on additional text or graphic markers because they can’t distinguish certain colors.
- People with motor impairments often use keyboards, switches, eye-tracking devices, or voice commands instead of a mouse.
- People sensitive to animations and flickering may experience discomfort, dizziness, or even seizures, so stable and predictable content is essential.
By including accessible solutions, we not only enable equal participation for people with disabilities but also improve the experience for all users, including older adults, those with poor internet connections, or people using a phone with one hand or in bright sunlight.
Statistics: How Many People Are Affected?
In Serbia, official statistics say around ~5–6% of citizens have some form of disability, while experts estimate the real number is closer to 10–15%. The truth is likely somewhere in between.
In the European Union, more than 87 million people (~20%) have some disability.
In Serbia, fewer than 5% of public administration websites meet basic accessibility requirements. In the EU, this percentage varies – some member states exceed 50%, but most still struggle with implementation.
That’s why the European Union adopted a comprehensive law in 2019 requiring digital service providers to ensure equal access for all.
What Is the European Accessibility Act (EAA)?
The European Accessibility Act (EAA), formally known as EU Directive 2019/882, aims to eliminate barriers and allow people with disabilities to participate equally in digital and physical environments.
The law comes into effect on June 28, 2025. From that date forward, all companies offering digital products and services within the EU market must comply with defined accessibility standards.
According to the EAA, implementation deadlines are divided into two phases:
- From June 28, 2025 – all new digital content and major updates to existing websites and apps must comply with the WCAG 2.1 AA standard.
- By June 28, 2027 – all remaining existing digital content must be fully compliant.
This allows for a gradual transition while setting a firm deadline for complete compliance.
What Does the EAA Apply To?
The law covers a broad range of digital and physical services, including:
- Websites and mobile applications
- E-commerce platforms
- Banking and financial services
- Ticketing systems for transportation
- Audio-visual media services
- Digital kiosks and self-service devices
- Smart devices, e-books, and other products with digital interfaces
Attached documents like PDFs and Word files must also be accessible, as they are part of the digital content users regularly interact with.
What Is the Law Based On?
The EAA relies on internationally recognized accessibility standards, primarily WCAG 2.1 (Web Content Accessibility Guidelines), level AA. These guidelines state that content should be:
- Perceivable – information must be presented in ways users can perceive
- Operable – interfaces must be usable via keyboard and other methods
- Understandable – content and navigation must be clear
- Robust – compatible with a wide range of user agents, including assistive technologies
Note: While WCAG 2.1 is currently the active standard, following the latest guidelines is recommended – WCAG 2.2 has already been released, and WCAG 3 is on the horizon.
Who Needs to Comply – and When Are Exemptions Possible?
Compliance is required not only for companies based in the EU but also for all domestic and international companies offering digital products and services to users in the EU market.
Microenterprises (fewer than 10 employees and low turnover) may be exempt from some rules, but must:
- Clearly document the reasons for the exemption
- Show a plan and timeline for improvements, where possible
- Justify any claims of “disproportionate burden,” which is evaluated based on employee count, revenue, and market position
Technical Standards: What Is and Isn’t Allowed?
In addition to the core WCAG 2.1 AA principles (perceivable, operable, understandable, robust), the law highlights the following:
- Alternative text for images and media is mandatory
- Keyboard focus indicators must be clear and consistent
- The page language must be explicitly declared so screen readers can interpret content correctly
- HTML must be valid, and ARIA should only be used when semantic HTML can’t achieve the desired result
- Form errors must be clearly explained and not confusing to the user
- Error messages, validations, or system notifications must be announced to users relying on assistive technologies
- All multimedia must include appropriate text alternatives – captions, transcripts, and, where needed, audio descriptions
Why This Matters – and Why It’s Not Optional
Failing to meet these legal requirements doesn’t just risk fines or lawsuits – it can mean losing access to the EU market and missed revenue opportunities.
On the other hand, a well-crafted accessibility statement, along with a phased compliance plan or a justified exemption, demonstrates seriousness, transparency, and responsibility toward users.
What Does This Mean for Developers, Designers, and Digital Product Owners?
Simply put, websites and applications must work for all users, regardless of their physical, sensory, or cognitive abilities. This isn’t just an ethical issue – it’s a legal obligation and a strategic advantage.
Practical Compliance Checklist for the EAA
1. Planning
- Integrate accessibility at the project planning stage
- Define WCAG 2.1 AA as the minimum standard
- Assign roles: who is responsible for design, development, and testing
- Train the team on accessibility fundamentals
2. Inclusive Design
- Text contrast ratio: minimum 4.5:1
- Don’t rely on color alone – use symbols, icons, or labels
- Typography must be scalable and easy to read
- Enable keyboard navigation
- Use clear and consistent layout structures
3. Accessible Development
- Use semantic HTML (e.g. <navigation>, <head>, <button> )
- Add descriptive ALT text for images
- Implement ARIA attributes for complex components
- Ensure forms are fully labelled and include clear error messages
- Dynamic content (pop-ups, AJAX) must be announced via ARIA live regions
4. Mobile Applications
- Ensure compatibility with screen readers (VoiceOver, TalkBack)
- Provide accessible gestures and alternative controls
- Clearly label controls and buttons
- Touch targets should be at least 44×44 pixels
- Avoid fixed screen orientation
5. Testing and Review
- Use tools like Lighthouse, Axe, and WAVE
- Conduct manual keyboard and screen reader tests
- Involve users with disabilities in testing
6. Accessibility Statement
- Publish a compliance statement on your website or app
- Describe how users can report issues
- Update the statement after each major change
7. Long-Term Strategy
- Regularly check accessibility during redesigns
- Analyze user feedback
- Integrate accessibility into CI/CD processes
Compliance Is Not Just a Legal Obligation – It’s a Business Opportunity
Meeting the EAA requirements isn’t just about avoiding fines or legal consequences. It:
- Improves SEO and overall user experience
- Reaches a broader audience (including older users and those with temporary impairments)
- Reduces customer support costs
- Enhances brand reputation and social responsibility
Digital accessibility for people with disabilities is something that our company takes very seriously when planning and developing websites and applications, and 6 years ago we developed our first web accessibility tool for the Politika website, through which users can easily and simply adjust the font size, choose different contrast options, highlight links and adjust text readability.
Don’t view accessibility as an added expense – it’s an investment in a better, more inclusive, and more professional digital product. It’s not just about legal compliance – accessibility builds trust, expands markets, and makes the digital world available to everyone.
The time to act is now.
