Posted on

How to develop a keen sense for Digital Accessibility

“I would like to be able to look at a mockup for a website and immediately know: This is not accessible!” – A colleague of mine expressed this wish a few days ago. He has been working for many years as a web developer, but still has little experience with digital accessibility.

His question got me thinking: What can newbies do to develop a keen sense for accessibility?

Fingers touch the page of a book in Braille. Photo: © Eren Li /

Responsive Design? What's that good for?

Younger colleagues may find it hard to imagine: But web content didn't always fluidly adapt to different screen sizes. Even in the 2000s it was still common to optimize websites for specific screen sizes only. The following article provides a good summary: “A Brief History of Responsive Web Design”.

This changed when smartphones became more and more popular. Today, users expect websites to look good and work on all devices. Responsive design is explicitly defined as a requirement for web projects. UI/UX experts create designs and prototypes for different screen sizes. Developers test implemented features on desktop and mobile devices.

Now what does that have to do with accessibility? For me, the triumph of responsive design clearly shows that the more people use websites in a certain way, the more these needs are taken into account in web development.

Accessible Design? What's that good for?

Most people use their smartphone or a computer mouse to surf the Internet. They click a button and notice the visual feedback on the page. They're not dependent on a screen reader being able to read the web content in a meaningful way or on interactive elements being accessible with the keyboard.

Web developers are users too. Their everyday experiences influence their perception of what makes a good, usable website. For example: If you've never used a screen reader, it's hard to imagine why the semantic markup of web content is so important.

This brings me back to the central question: What can newbies do to develop a keen sense for accessibility as quickly as possible? Very simple: Change perspective!

Take on the perspective of people with disabilities

If you want to understand the needs of people with disabilities, the best way is to just ask them how they use digital content. Have a blind or partially sighted person show you how to shop online using a screen reader. Talk with a deaf person about watching the news with closed captions or in sign language.

If you don't know any people with disabilities, you can organize a workshop in your company, for example. Contact an organization of persons with disabilities in your country. Some organizations also offer specific trainings, e.g., the Sensing Journey (in German).

Practice makes perfect

As a web developer, you are constantly confronted with new requirements that result from rapid technological change. That's why we live by the principle of "learning by doing". This approach also helps us when it comes to digital accessibility: Just do it!

For a start, you should read up on the "Web Content Accessibility Guidelines" (WCAG). They're already a legal requirement for the public sector in all EU member states. The WCAG cover a wide range of needs from different user groups. They provide very detailed online resources, with concrete examples of accessible implementations, as well as common mistakes.

My recommendation: Most web content can be made accessible with semantic HTML and CSS alone. I often come across websites that make excessive use of ARIA attributes, creating more barriers than they remove. It makes sense to use ARIA for complex UI components, as illustrated by the WAI-ARIA Authoring Practices.

Take your time

Digital accessibility is complex and multi-layered. For newbies, this means a steep learning curve and a lot of potential for frustration. You should approach the topic step by step and be open to new perspectives. Then you will develop a keen sense for accessibility over time all by yourself.

Posted on

Imprint: Content by Alexander Lehner, Vienna/Austria.