Web Content Accessibility Guidelines touch keyboard accessibility in a couple of success criteria. It’s essential for your native app to support keyboard interactions for it to be accessible. But how?
Tag: Keyboard accessibility
Latest posts:
Everybody knows that we must not use aria-hidden on interactive elements. But why is that a problem? I decided to check for myself, so that I can explain it better the next time I will be asked.
Stumbled upon a e-commerce that required hundreds of key-presses to get below the navigation. Reminded me, again, about the importance of skip links…
Sometimes developers have good intentions and want to make their products more accessible, but can fake accessibility and make things even worse.
Some accessibility issues originate in code. And when design is being recreated with code it may seem to work but when thinking about accessibility we may notice that it only works for some users and not for others. I’ve decided to describe some common accessibility fails that are on developers.
Sometimes people claim that accessibility is the responsibility of development and code. I disagree. It is a team effort and it can only succeed when whole team knows what to do. Content is king and if we start and end with content it can make the teams accessibility efforts much more effective.
I organized an accessibility workshop for our front-end and full-stack developers, user interface and user experience designers and others involved in digital production. This post will concentrate on screen-reader (SR) users way of navigation because it may surprise non-screen-reader users quite a lot.
Just a short explanation to all the developers out there that may not understand the need for skip to content links.
When in need for a custom widget / control er even basic site element – it is easier than ever before to just get it from the web or maybe even create one from scratch. This post tries to explain what has to be considered.
User agents are sometimes going beyond their own guidelines and helping to improve accessibility with smart accessible defaults.