People in an abstracted digital environment with clear contrasts.

From duty to freestyle: accessibility as a guiding principle for UX & UCD

Accessibility is more than just a duty: as a guiding principle for UX & UCD, it improves digital products from the ground up - for all users. This results in more inclusive experiences, better usability and measurable added value.

Accessibility is often seen as a compulsory exercise in the digital world. Properly understood, however, it is a design principle that improves products from the ground up. Accessibility ensures that content and functions can be used by as many people as possible - regardless of ability, situation or device. This is precisely where it connects with user experience (UX) and user-centered design (UCD): The needs of real people shape decisions along the entire product life cycle.

Why accessibility strengthens UX for everyone

Accessibility reduces friction and improves use for everyone:

  • High contrasts: helpful for visual impairments, but also for sunlight on the smartphone.
  • Generous click surfacesThe new features: make operation easier for people with limited motor skills, but also for anyone who types with one hand.
  • Subtitles and transcriptsIndispensable for deaf people, but just as practical on the train or in an open-plan office.

Such measures increase overall usability: orientation becomes clearer, processes more reliable, interruptions less frequent.

Accessibility as a common thread in the UCD process

User-centered design anchors user needs in every step - accessibility runs systematically:

  • ResearchDifferent perspectives uncover barriers. User tests are particularly valuable here because your own view as a developer or designer often differs from the actual use. What seems logical to us may appear completely different to other users.
  • PrioritizationBarriers are seen as business risks, not as a "nice to have".
  • Design & PrototypingReadability, clear hierarchies, understandable language and robust interactions are incorporated early on. A classic example from practice: error messages must be formulated in an understandable way, but must not reveal too many details for security reasons. The same applies to validations: "Invalid e-mail" is not enough - many people do not know exactly what format is expected.
  • Test & OperationRegular short tests - with a keyboard or screen reader, for example - ensure sustainable quality. Particularly informative are "high-end tests" in which we navigate through an application with our eyes closed and using only the keyboard and screen reader.

Practical experience

Accessibility is part of doubleSlash's understanding of quality. Reusable components in the living Styleguide support consistent and accessible interfaces. Accessibility aspects are incorporated into projects, from research and design reviews to checks during the release process.

A formative exampleOur brand color cyan was not contrasting enough for buttons and links. The introduction of an additional "click color" was initially a challenge because it meant a separation between brand identity and functionality. Today it is standard - and the legibility and perceptibility of clickable elements have improved significantly. Many users benefit from this, especially in bright sunlight.

Even seemingly small details such as Alt texts have a great effect: they not only help screen reader users, but also if an image does not load - and incidentally also improve the SEO ranking.

When adapting our navigation menu, we took the opportunity not only to improve accessibility, but also to revise the entire information architecture. The content is now clearer and easier to understand - a benefit for all users.

Another example: Accordion elements have been given a clear border or shadow when activated. This helps screen reader users with orientation, but also improves usability for everyone else because it is immediately clear which area is active and which elements are clickable.

Principles with a big impact

  • Languageshort sentences, clear action verbs, descriptive link texts.
  • Structure: meaningful headings, consistent navigation, recognizable states.
  • Readabilitysufficient contrasts, scalable typography, generous spacing.
  • Usabilityfull keyboard control, visible focus, sufficient target sizes.
  • FeedbackError messages with specific instructions - instead of "Invalid e-mail", it is better to say: "Please enter a valid e-mail address in the format name@mail.de".
  • MediaAlternative texts for images, subtitles/transcripts for audio and video.

Many aspects of accessibility are difficult to measure. Users experience interfaces subjectively - what is accessible for one person can still be a hurdle for another. This is why continuous feedback and iterative improvements are so important.

Economic benefit

Inclusive design brings measurable benefits: you extends the rangeas more people can take advantage of an offer. You Reduces support costsbecause clear feedback and comprehensible processes result in fewer queries. Many accessibility measures also have the following effects positive for SEO - for example through alternative texts or a clean headline structure - and thus improve visibility in search engines. Finally, the Conversion ratebecause barrier-free processes are simpler, clearer and more reliable.

Even if the initial outlay may be higher at the beginning, it pays off several times over in the long term: Through lower rework costs, faster development cycles, higher customer satisfaction and better scalability.

Conclusion

When accessibility goes from being mandatory to optional, UX quality and brand experience increase noticeably for everyone. UCD ensures that accessibility has a systematic rather than selective effect - from the initial idea through to operation. Personal experience from projects shows this: Those who test early, remain open to feedback and understand accessibility as an integral part of the design process create digital products that are reliable, comprehensible and inclusive.

Want to know more about accessibility?

In our previous article, we explained the basics and terms relating to digital accessibility - ideal for anyone who wants to delve deeper:

Official sources & further reading

Dominik Sasse

About ME

Dominik Sasse studied Business Informatics (B.Sc.) and has been working as a Software Developer at doubleSlash since 2019. His focus is in the area of Front-end development with Angular and the Data visualization with PowerBI.

All contributions from Dominik Sasse

Learn more

Further information on our website and in our newsletter

Arrow up