Accessibility is not only essential for people with disabilities but also improves the overall usability of apps and websites by addressing issues like the fat-finger problem on touchscreens. The Web Content Accessibility Guidelines (WCAG) provide clear directives that often intuitively align with good usability, such as a perfect sized buttons or the use of labels for user input.
Accessibility! This term is currently popping up frequently on presentation slides and is often discussed in meetings. The reason for this is the Accessibility Strengthening Act (BFSG), which will come into effect next June and impact many companies. This law implements a European directive that, for the first time in EU history, prescribes minimum accessibility standards. However, the topic isn’t as new as the current hype might suggest: an initial directive, which made accessibility mandatory for the public sector, was already passed in 2016. In some cases, “accidentally” accessible designs were implemented without the designers even being aware of it. In the following, we will explore what accessibility is and how it relates to the concept of usability.
It is estimated that about 10% of the world’s population lives with a disability. Often, we think of severe disabilities such as blindness, cognitive or motor impairments, or even limb deformities. However, there are many ways in which a person can become limited over the course of their life: age-related impairments that develop over time, temporary disabilities such as a broken arm, or sensitivity after eye surgery are just a few examples. Virtually everyone will face at least one or more temporary limitations over the course of their life. It is all the more astonishing that the design of websites and apps is often far from accessible and instead caters primarily to the abilities of a completely healthy person. One reason for this lies in the origins of the internet, which was initially based on text protocols. Over time, technical advancements have created additional possibilities for web design and structuring. Implementations primarily focused on ensuring that websites were functional for the majority of users, thereby excluding a large portion of the population. Yet accessibility and good usability are not mutually exclusive – quite the opposite!
The BFSG is based on the Web Content Accessibility Guidelines (WCAG). Many of the criteria described in these guidelines are nothing new to designers: similar concepts have appeared in various design textbooks and are well-known in day-to-day design practice. For example, WCAG guideline 2.5.5 “Target Size” specifies that targets for pointer inputs (such as buttons or other clickable elements) must be at least 44 x 44 CSS pixels in size. This not only appears intuitive and logical but also aligns closely with several UX phenomena that deal with the minimum size of elements. The fat-finger problem, for instance, refers to the issue on touchscreen devices where fingers obscure UI elements, making them difficult to tap accurately. This requirement is not directly tied to physical impairments and is generally considered a best practice for usability.
On the left, the UI elements are large enough that the user can clearly identify which element will be selected. On the right, it is unclear which element receives the input, as the elements are so small that the cursor touches multiple targets at once.
Another example is guideline 3.2.2: “Labels or Instructions.” This rule requires labels or instructions whenever user input is needed. This requirement is so basic and straightforward that most people wouldn’t even associate it with the concept of accessibility. As you can see, the subjects of accessibility and usability are not antagonists. On the contrary, they complement each other. By adhering to specific accessibility standards, usability also improves for users who are not impaired.
The term accessibility causes headaches for many organizations and is often viewed as a risk. Many companies currently fear consequences if they fail to implement the directives. Instead, the focus should be on the improvements these guidelines bring for users and thus also for businesses. The requirements directly lead to better general usability. Additionally, they enable people with disabilities to use applications, thereby expanding the potential user base for companies. If existing users experience temporary impairments but still want to use the software, they will undoubtedly appreciate an accessible user experience and recommend the application to others. There is so much potential! Seize the opportunity!
You can also find the article at: https://sq-magazin.de/ & https://www.asqf.de/
