UX seems to be everywhere today. Large and small companies are learning the importance of it trough achieving better success if they dedicate more time understanding the user needs.

But personas, wireframes and workflow prototypes are not enough when you start UI implementation. Everything will end up in code, and if that segment of the UX is not taken care of, your hard UX design work might be wasted.

Although, the interactivity and desired visual appearance can be achieved with non-accessible client side output, or at least with screen-reader friendly or ARIA equipped markup, the final experience we are offering for accessibility is still poor and not of much help for users in need.

It is not enough to just read the navigation or page. It might be good enough for a blog or news page with static and linear content, but for web applications, tablet and mobile applications (direction it seems we are heading to) – it just doesn’t work.

We need designed workflows and audio interfaces that offers smooth experience for the users in need. Bombarding the user with audio output by just reading the whole page word by word is totally useless. Closest we should get in desigining and implementing accessible user experience are the traditional telephone bank services  (the best practices, of course, there are some bad ones out there as well). Your markup should be able to offer this alternative layer of accessibility and user experience, you just need to write it with accessible user in mind, or develop alternative audio widgets for your framework.