Mobile accessibility: the good, the bad and the ugly

Unfortunately when developing WCAG2, the Working Group did not envision the current world where mobile is almost ubiquitous. For example, on a mobile device there is no continual access to a keyboard (unless someone is using it as an add-on to the device – or using a Blackberry Classic). WCAG2 requires that all content be accessible to the keyboard interface, but it does not require that all content be accessible to a mouse or to a touchscreen user – which is essential on a mobile device. Gian Wild talks about the unique accessibility issues on a mobile site and mobile app, including hover traps, VoiceOver swipe traps and zoom traps.