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.
Tag: Screen-reader
Latest posts:
Some people can treat an image as decorative and therefore skip the alternative text, but there are others that may treat same image in same context as more than just decoration. Maybe it is best to just add text for images that are potentially decorative and then let users decide for them selves.
2020 was a special year and not only negative, it was especially positive for the accessibility, both for the world and for me as well.
A link should navigate and a button should do something is the basic idea. Semantics will be rewarded with usability and even search engines will like it, so why break the pattern.
Just a short explanation to all the developers out there that may not understand the need for skip to content links.
It is possible that our website is 100% WCAG compliant and still not accessible to an assistive technology user. WCAG alone is not enough, we must test manually as well.
Scaling down web browser is not enough. We should really test with physical devices and with at least Android and iOS based devices. UI and UX tests are important but so is testing accessibility with mobile screen-readers.
A bit personal post, but I really do think that empathy builds our awareness about accessibility and by at least trying to think about others we can be better at it.