Does the one-size-fits-all approach of “One Web” meet the needs of all groups of web users, as web content becomes more complicated? We will discuss strategies for improving accessibility across different devices, covering current issues with mobile accessibility, and potential solutions such as geolocation and CSS3 media queries.

• 2:25 PM: AndreG Presenter – Chris Mills – Opera Software
• 2:33 PM: AndreG How do we extend Accessibility across all of the web enabled devices out there?
• 2:33 PM: AndreG What opportunities do new technologies offer us? (HTML5 and CSS3 in terms of accessibility)
• 2:33 PM: AndreG Accessibility as Universal Design
• 2:34 PM: AndreG Improve things for everyone from a screen reader to a tiny little mobile phone
• 2:35 PM: AndreG We are now building for smartphones, tablets, TVs, game consoles, etc. The web is everywhere now
• 2:36 PM: AndreG iPhone paved the way for a great standards based UX support for phones
• 2:36 PM: AndreG There is even a good screenreader on the iPhone 3GS
• 2:37 PM: AndreG WAI-ARIA support is making its way into mobile browsers
• 2:37 PM: AndreG Mobile IE is the big exception to mobile accessibility
• 2:38 PM: AndreG Android has great standards support thanks to Webkit
• 2:39 PM: AndreG If you have a mobile device based on Webkit you are probably going to be in an OK situation with accessibility. Need to be careful though since there are a lot of fragmented version of Webkit out there at the moment.
• 2:41 PM: AndreG Outside of the rich west, most “feature phones” are pretty crappy. We are not the same as our users. Need to really make sure we are targeting our mobile dev for our target market.
• 2:43 PM: AndreG A lot of TVs and consumer products have chosen to leverage Webkit or the Opera SDK. Good accessibility in the background but not implemented on the front end.
• 2:43 PM: AndreG Beyond browsers there are lots of problems with the actual devices they run on
• 2:44 PM: AndreG General lack of assistive technology on most devices. Mobile devices are almost like where we were ten years ago in terms of desktop support.
• 2:44 PM: AndreG Screen sizes are ALL over the place.
• 2:45 PM: AndreG Devices cannot support heavy processing or bandwidth intensive activities at the moment
• 2:45 PM: AndreG Controls tend to vary pretty widely across devices…
• 2:46 PM: AndreG Current mobile devices not supporting plugins, but not a huge deal thanks to forward thinking support for HTML5
• 2:46 PM: AndreG Overall Accessibility on alternative devices is “a real pain in the ass”
• 2:47 PM: AndreG How are we addressing this and solving things? Going back to the old school.
• 2:47 PM: AndreG Since ARIA Javascript is not widely supported we need to think about fallbacks. Nice clean HTML that works without JS
• 2:47 PM: AndreG Must make core content still accessible
• 2:48 PM: AndreG Always create a baseline of content that is accessible without things like JS
• 2:48 PM: AndreG Layer on enhancements
• 2:49 PM: AndreG If you want to use AJAX that is great but you need a fall back to a full page refresh
• 2:51 PM: AndreG If you are going to support a mobile version of your site make sure it is a quality experience. Should always give users option to jump over to the full non mobile site.
• 2:51 PM: AndreG Graded support…
• 2:53 PM: AndreG No need to write a mobile app that is iPhone only. If you keep layouts fluid and degrade nicely they should work everywhere. Keep graphics minimal, keep data entry to a minimum, test across as many devices as you can. Users are most likely to select from lists as they work the most consistently across devices.
• 2:53 PM: AndreG Keep HTTP requests to a minimum, user CSS Sprites, minimize JS as much as possible. Keep it LEAN.
• 2:54 PM: AndreG W3C mobile best practices are very similar to WCAG best practices.
• 2:59 PM: AndreG WAI-ARIA 2 is supposed to focus more on Mobile once it gets rolling.