You connect your physical keyboard to an Android device and start pressing the tab key. And then shift tab. And sometimes – you circle around the UI but can not reach all interactive elements. Is this a WCAG 2.1.1 failure? Maybe it is, maybe you need to try harder…
Tag: Keyboard
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…
After doing an audit of a webpage ,where navigation require horizontal scrolling, I decided to test what does that pattern mean for people with disabilities. Longer story short – be careful, maybe it’s not worth it for critical components like navigation.
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.
Do not forget about keyboard. It is essential for accessible web-sites and web applications.