Mobile Web Strategies Blog

How Our CSS Framework Helps Enforce Accessibility by Ian McBurnie  Spot the difference….You can’t! To a sighted user it appears we have two identical button elements. A user interface control not only needs to look like a certain control, it must be described as that control too. Take for example a button, one of the simplest of controls. There are many ways you can create something that looks like a button, but unless you use the actual button tag (or button role – more on roles later), it will not be described as a button. Why does it need to be described as a button? Users of AT (assistive technology), such as a screen reader, may not be able to see what the control looks like visually; therefore it is the job of the screen reader to describe it aurally. A screen reader, such as VoiceOver for Mac OSX and iOS, can do this job only if we, the developers, ensure the correct semantics are present in our HTML code. Semantics In the table below, compare and contr

I am constantly hearing people to ask what is really the difference between UX designer and UI Designer. Into words is really hard to answer this questions because people just are not able to grasp all the small differences between what UX designer do and the skills it has to have to do what he or she does compared with what are requested from UI designers. I found this infographic in the internet by Anna Harris and it is so well explained with picture that anyone can really understand. So here it is: