Usability has come a long way since the dark days before "Designing with Web Standards". Now nearly all companies see the value of UX in their digital designs. But despite heightened focus on the user and a growing awareness of accessibility concerns, implementation of accessibility standards have often fallen victim to time pressures and obsolete design practices. Disabled users struggle through sites missing alt tags, keyboard inputs or text alternatives. Enter devices like the iPhone & Android … and the iPad.
With the proliferation of non-desktop devices and browsers like tablets and gestural smartphones, suddenly more people are finding that the web isn't as nice and clean as they remembered: broken formatting, too small text, hover functionality that doesn’t work, and entire swaths of the web rendered as Flash-based wastelands that millions can’t access.
We've now discovered that by solving for many of the issues that iOS and other mobile users face, we can also solve for the most prevalent accessibility issues. Using side-by-side examples and case studies, I'll show how we can make sites more accessible and more usable by mobile devices. Through combinations of better markup, HTML5 and CSS3 functionality and better scripting, we can serve two masters at once. Better yet, in some cases, we can take advantage of the accessibility capabilities built into newer mobile devices to make the digital experience even better than they would get on the 'old web'.
As the rise of iOS, Android, and the Mac App Store brings more web developers into the world of native applications can our existing processes and best practices survive the transition? How can we release early and often in an environment where each update must pass through a review process? How do we aggressively refactor code when outdated clients must be supported? Can we iterate efficiently on features when design changes require more than a stylesheet update? A group of experienced web, mobile, and native app designers and developers will discuss our experiences working on native applications. We will explain what unexpected challenges we encountered coming from a web background, what strategies have helped us design and develop native applications, what did not work, and what we should learn from experienced native application developers.
9th–13th March 2012