With the compliance period for the European Accessity Act (EAA) The companies quickly try to ensure that their websites meet the requirements of the EU directive.
An appealing solution are barrier-free widget-small add-ons with functions such as text change, contrast adjustments and text-to-language functions.
Although these widgets promise quick and inexpensive compliance, they often do not tackle the actual problems of accessibility. In fact, you can even make websites difficult for people with disabilities to navigate.
Here is the reason why rely on widgets, a short -sighted solution and the web developers, which should be created instead really accessible digital spaces.
What does the European accessibility act for developers mean?
TNW conference – The Agenda 2025 has just landed
Discover the insightful and car we say controversial meetings that will take place from June 19 to 20.
The EAA issued in 2019 requires that large e-commerce websites and private companies will comply with a number of accessibility standards by June 28, 2025 (the period for the public sector institutions has already passed). The rules apply to every company This performs business in the EU, with the exception of microcentrats with less than 10 employees or less than 2 million euros in annual sales.
These regulations are intended to make websites more accessible to users with disabilities and cover aspects such as text alternatives for images, keyboard navigation and compatibility for screen readers. While EAA primarily has a large company, it has also sharpened the general awareness of accessibility and encouraged smaller companies to check the accessibility of its websites.
While the deadline is approaching, the pressure to comply with the EAA has caused some companies to pursue quick solutions. Accessibility widgets offer an easy way to check the boxes.
Unfortunately, these tools often lead companies to the wrong way, which creates a wrong feeling of security and gives the opportunity to fix the underlying accessibility problems of their websites.
Why widgets are considered a suitable solution
This does not mean that the accessibility widgets are bad by default. Your attraction is easy to understand. They are inexpensive to implement quickly and in many cases deal with general accessibility requirements, e.g. B. the options for adapting the font sizes and contrast settings.
As a result, these tools can often be sufficient for websites that have relatively few elements, do not handle high traffic volumes or do not request any visitors to carry out important measures – for example in their bank account information. For such websites, widgets can provide an accessible level without the existing design and code required considerable overhaul.
For some companies, especially for people with limited resources, the promise of a widget is difficult to resist. Adding a widget to your website is considerably cheaper than ongoing test, fixed and maintenance processes. However, the dependence on widgets can not only delay the correction of the underlying problems with the website, but also lead to additional problems of accessibility caused by the widgets themselves.
Widgets can cause more problems than they solve them
A major problem with widgets is that they tend to work as overlays – they act as levels above the original website – instead of doing structural improvements in the code. This layering can affect the existing site functionality and cause problems with navigation, interactive functions or screen readers on which many users rely on disabilities.
For example, my team at TestDevlab examined the big fashion retailer Zara, who uses accessibility on his website. We have identified several problems caused by these tools. To name just a few:
- Site visitors who only use their keyboard for navigation cannot all elements after typing to the “Registration” button, since the focus jumps on the links of accessibility widget.
- If you select the dark option with high contrast in the widget of accessibility, the Hamburg menu button and the side logo are no longer visible.
- A number of problems were recognized in the adaptation and visibility of text when increasing the font size by the widget.
Since widgets usually absorb problems on the surface level, you do not have to deal with the underlying accessibility requirements such as keyboard navigation and properly labeled images. Instead of solving these deeper problems, widgets often become long -term crutches that prevent real progress, so that companies can overlook the fundamental changes that are necessary for sensible accessibility.
Whether a widget works often depends on how the original website was built and structured. If there are problems in the HTML code of the website, it may not have a difference in terms of accessibility or, even worse, break other elements that make the website more difficult to navigate than without the widget. Other factors that influence the widget performance are browsers and operating system of each site visitor. While the widget may work for some, it can fail for others.
Build the accessibility from scratch
Real web barrier freely requires long-term, local improvements than in superficial corrections. Developers should not consider accessibility as a central component of the design and development process, not as a subsequent thought. This means building the accessibility in every phase of the life cycle of a website from design to test.
Elements such as keyboard navigation, text alternative, logical heading structures and reaction-quick design should be taken into account from the start, which means that the website is accessible on its foundation and not via add-ons.
Tests are essential in this process. Accessibility is a continuous effort – it requires regular audits and adjustments to ensure continuous compliance if technology and accessibility standards develop.
Comments are closed.