Tolerance in the digital world: from a moral idea to EAA and WCAG compliance
16 November is the International Day for Tolerance, a chance to think about how our communities give everyone an equal chance. Online, tolerance is no longer just an abstract value. It shows in how we design websites, apps and online shops. A public building needs a ramp for people who use a wheelchair, and a modern website needs clear digital accessibility measures so that every visitor can use it without barriers.
Making the web inclusive has moved beyond voluntary corporate social responsibility. Today, accessibility standards are a core technical requirement, a European legal obligation and a large business opportunity for companies ready to serve the roughly 90 million people with disabilities in the European Union.
What does digital tolerance mean in practice?
Many companies see online inclusion as a goodwill gesture. From a UX and software point of view, digital tolerance means removing the unintended discrimination caused by poorly written code or by design decisions that ignore how different users are.
When a website uses weak color contrast, people with low vision can't read the content. When an online shop can't be used with the keyboard alone, a person with a motor disability can't complete an order. A video without captions or a form without clear labels shuts out people with hearing or cognitive disabilities, causes frustration and makes them leave.
Building accessibility measures into your platform's code means following the four principles of an inclusive web, known as POUR:
- Perceivable: Content and interface components must be presented in ways people can perceive with the senses they use. That includes alternative text for images, captions for audio and video, and enough contrast between text and background.
- Operable: Everyone must be able to use the interface and the navigation. An operable site works fully with the keyboard, gives people enough time to read and use content, and avoids flashing content that can trigger seizures.
- Understandable: Information and the way the interface works must be easy to understand. Forms need clear error messages and suggestions for fixing them, and navigation must be predictable across the site.
- Robust: Content must work reliably across a wide range of browsers, apps and assistive technologies, such as screen readers, braille displays and voice control software.
The W3C's Web Accessibility Initiative (WAI), the international initiative that sets the direction for an internet open to everyone, explains how to evaluate all of this in detail.
A new legal reality: the European Accessibility Act (EAA)
One of the strongest reasons for business leaders, legal teams and marketing teams to act now is the change in the law. The European Accessibility Act (EAA) turns web accessibility from an ethical recommendation into a legal obligation.
Since 28 June 2025, the EAA has required a wide range of products and services to meet minimum accessibility requirements. These include e-commerce websites and apps, consumer banking services, e-books and e-readers, and passenger transport services with their ticketing platforms. Companies that don't comply face the penalties set by the national laws that apply the directive.
For companies selling in the EU, adapting to the EAA is a crucial technical and legal step. Those that start early reduce the risk of non-compliance, protect their market share and avoid the high cost of rebuilding a platform in a rush. Our European Accessibility Act guide covers the details.
The business opportunity: around 90 million Europeans with disabilities
Beyond compliance, an accessible platform is a strategic business decision. According to the Council of the European Union, around 90 million people in the EU, or one adult in four, had some form of disability in 2024 (Eurostat estimate). On top of that comes a growing older population with declining sight, hearing or dexterity.
That adds up to tens of millions of European consumers with real spending power who run into barriers on inaccessible websites every day. An accessible online shop or SaaS platform lets these customers buy without help, instead of going to a competitor.
The business benefits of adopting these standards include:
- Higher conversion rates (CRO): A simple, clear interface without technical errors gives every visitor a smooth buying experience and reduces cart abandonment at checkout.
- Better SEO: Search engines read a page much like a screen reader does. Clean semantic structure, a clear heading hierarchy and alt text on images are accessibility requirements and SEO best practice at the same time.
- Brand reputation and differentiation: Today's consumers favor responsible brands that show real inclusion and respect for all their customers, which gives you a clear edge over competitors who aren't ready.
The EU's official view is set out on the European Commission's European Accessibility Act page, which explains its goals for removing barriers in the single market.
How do different disabilities affect shopping on an e-commerce website?
To understand how to build an accessible online shop, look at how different groups of people use a digital platform:
- Visual disabilities (blind people, low vision, color blindness): Blind people use screen readers, which read text aloud or show it in braille. If a product image has no alt text, or a button is only an icon, the user won't know what they're buying. Low contrast also affects people with low vision or color blindness.
- Motor disabilities (paralysis, tremor, limb differences): These users can't use a standard mouse and rely on the keyboard, special switches or voice commands. An inaccessible site traps keyboard focus in pop-ups or doesn't show where focus is on the page.
- Hearing disabilities (deaf and hard of hearing people): Audio and video without captions or a transcript are inaccessible. In e-commerce, product videos need a text alternative.
- Cognitive disabilities and neurodivergence (ADHD, dyslexia, autism): Cluttered layouts, aggressive animations that can't be stopped, urgency timers and complicated forms create too much cognitive load, and people leave the site.
How do you meet WCAG 2.1 requirements, from plan to execution?
Aligning with international standards needs a structured, hybrid approach. For the EAA, the technical reference is the European standard EN 301 549, which is based on the Web Content Accessibility Guidelines (WCAG) at level AA. The new edition, EN 301 549 v4.1.1, published in September 2026, moves to WCAG 2.2, so it makes sense to work directly toward WCAG 2.2 AA. Our article on EN 301 549 v4.1.1 explains what changed.
Real WCAG conformance on a complex platform can't come from installing an automatic overlay widget alone. A sustainable approach has three stages:
1. A hybrid technical audit (automated and manual)
An automated tool can find only some code errors, such as missing alt attributes or obvious contrast problems. In a 2017 test by the UK Government Digital Service, the best automated tool found 41% of the barriers planted on a test page, and all 10 tools together found 71%. Only manual testing by accessibility specialists and by people who use assistive technology can judge navigation logic, the checkout flow and complex forms.
2. Fixing the source code and the UI/UX
Your development team needs to work directly in the code to correct the semantic HTML (<header>, <main>, <nav>, <button>), use ARIA attributes correctly (aria-expanded, aria-live) and make keyboard navigation work smoothly.
3. Content guidelines and team training
Accessibility is an ongoing process. Marketing and content teams need training to write useful alt text for new products, keep a correct heading hierarchy (H1 to H6) and avoid images with text baked into the graphic.
The official WCAG specification, with every success criterion for levels A, AA and AAA, is published by the World Wide Web Consortium (W3C).
Frequently asked questions about the EAA and digital accessibility
1. What is the European Accessibility Act (EAA) and who does it apply to?
The EAA is an EU directive (Directive (EU) 2019/882) that sets mandatory accessibility requirements for certain products and services. Among others, it covers e-commerce services, consumer banking services, e-books, electronic communications and passenger transport services offered in the European Union.
2. Are microenterprises exempt from the EAA?
Yes. Microenterprises that provide services, meaning companies with fewer than 10 employees and an annual turnover or balance sheet total of no more than 2 million euros, are exempt. Accessibility is still strongly recommended so you don't lose customers to accessible competitors.
3. Is installing an accessibility widget (plugin) enough?
No. Widgets can offer visual adjustments, such as changing font size or colors, but they can't fix broken source code, make a complex checkout work with the keyboard or add correct, context-aware image descriptions. An audit and code fixes are still necessary steps toward compliance.
4. What is the difference between WCAG 2.1 levels A, AA and AAA?
WCAG has three conformance levels:
- Level A: The minimum requirements. Without them, a site is almost impossible for many people with disabilities to use.
- Level AA: The level used as the reference for the EAA, through EN 301 549, and by most laws worldwide. It removes the most common barriers.
- Level AAA: The highest level of accessibility, usually aimed at specialized platforms.
International Day for Tolerance: the right moment to start
16 November is a good moment for business leaders to look past statements of intent and check the real state of the digital platforms they run. Moving to an inclusive online shop doesn't happen overnight. It's a strategic investment in code quality and in the experience you offer every user.
Turning your site from a place full of technical barriers into a digital space open to everyone is the most concrete way for a business to mark the International Day for Tolerance.
If you want to know where your platform stands and what to do next to meet European law, explore Wawsome's accessibility audit services for businesses getting ready for the digital future.
Sources
- Disability in the EU: facts and figures (Council of the European Union, 2025)
- Directive (EU) 2019/882 on accessibility requirements (EUR-Lex)
- Web Content Accessibility Guidelines (WCAG) 2.1 (W3C)
- What we found when we tested tools on the world's least-accessible webpage (GDS, 2017)
- International Day for Tolerance (UNESCO)
