Your SlideShare is downloading. ×

SSB BART Group Mobile Accessibility

647

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
647
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Mobile Accessibility Overview
  • 2.
    • SSB Background
    • Current Landscape
    • Smart Phones
    • User Demographics
    • iOS based products
    • Android ®
    • Windows Phone ® /Mobile
    • Blackberry ®
    • Symbian ® and WebOS ®
    • Strategies for accessible Apps
    • User Impact
    • App Development
    • References
    AGENDA
  • 3. BACKGROUND & EXPERIENCE
    • BACKGROUND
    • Founded in 1997 by engineers with disabilities
    • Over 750 commercial and government customers
    • 1,500 enterprise projects successfully completed
    • Over fifty percent staffing mix of individuals with disabilities
    • Pioneers of commercial accessibility validation tools
    • Investment of 10 years and 8.7M dollars into AMP platform
    • EXPERIENCE
    • Nine hundred individual accessibility best practices (915)
    • Seventeen core technology platforms (17)
    • Eight thousand audits (8,408)
    • Four million accessibility violations (4,126,249)
    • Forty-eight thousand human validated accessibility violations (48,536)
    • (Statistics provided as of December 2009)
  • 4.
    • Platforms
    CURRENT LANDSCAPE
    • Smartphones:
    • Typically have features such as email, web browsing, instant messaging, multimedia, calendar, voice dialing, and other capabilities
    • Platforms powering smartphones used today
    • by persons with disabilities and individuals without
    • disabilities
    • iOS (iPhone®, iPad®, iPod Touch® from Apple)
    • Android® (open-source OS from Google)
    • Windows Phone® and Windows Mobile®
    • from Microsoft
    • Blackberry® from Research in Motion (RIM)
    • Symbian® from Nokia.
    • WebOS ® from HP (previously Palm)
  • 5.
    • Additional Smartphone benefits
    • Apps designed for or that indirectly benefit users with disabilities
      • Light detector, color identifier, money identifier, barcode reader, video magnifier, Flashlight,, OCR, daisy book reader, GPS, point of sale services, voice memos, grocery finder/prices
    • Feature Phones (not included in this presentation):
    • Generally contain enhanced capabilities such as text messaging (SMS), contacts, voice dialing, and other standard phone features.
    • Platforms Continued
    SMART PHONES AND FEATURE PHONES
  • 6.
    • WebAIM Survey for Screen reader accessibility
      • Three surveys include mobile accessibility
      • Latest in December 2010
    • iOS based products have become widely used by people who are blind and visually impaired.
    • iOS percentage of users with disabilities compared to population is lower but increasing
    • Number of users who are blind/visually impaired dropping for feature/smart phones using Symbian or Windows Mobile
    • Percent of Android users who are blind/visually impaired is less than the general population using Android devices
    USER DEMOGRAPHICS
  • 7.
    • Launched in June 2007
    • iPhone 3gs began offering screen reader and
    • enlargement in June of 2009 as part of OS
    • Includes iPad, iPad2, iPod Touch 3 rd and 4 th gen.
    • Many of the same ATs found in Mac OS
      • VoiceOver
      • Zoom and pinch zoom within some apps
      • White on Black (Color inversion)
      • Captioning for iTunes based multimedia
      • Hearing Aid compatibility, TTY support through adapter
      • Visual notification of sounds
    • Assistive Technology
    iPHONE AND iOS
  • 8.
    • When the iOS is upgraded the assistive technology is upgraded as well
      • Cannot upgrade AT without upgrading OS
    • Assistive technologies can be activated/deactivated directly on the phone by users with disabilities or via iTunes.
    • Provides access to standard phone features such as placing a call, contacts, voicemail, and text messaging.
    • Access to large number of third party apps as well as other built in apps
      • iOS has the largest number of accessible third party applications of any mobile device
      • Websites devoted to rating the accessibility of apps
    • Continued
    iPHONE AND iOS
  • 9.
    • Primary input method is capacitive touch screen
      • Alternative gestures when VoiceOver is active
    • Alternative methods of input include Bluetooth keyboards and Bluetooth braille display entry, and styli designed to work with the touch screen
      • One handed operation may requires special case or mounting but most gestures are accessible with one stylus
      • Speech recognition capabilities to voice dial, look up contacts, and play iTunes tracks. Third party apps for text dictation
    • Third party assistive technology is limited to app specific (self-voicing)
    • Input
    iPHONE AND iOS
  • 10.
    • Open source screen reader developed by Google
    • Many manufacturers and models of Smartphones use Android
    • Assistive technology such as the Talkback screen reader is included in Android 3.0 OS but can be installed on older versions such as Android 2.2
    • Input may consist of phone with keyboard and or directional pad (D-pad) or touchscreen only devices
      • Types of touchscreens vary with manufacturer and may require special styli if the user is unable to use a finger
      • Apps must be keyboard accessible with trackball or D-pad to be used by users of a screen reader
    • Overview
    ANDROID
  • 11.
    • Provides basic screen reading capabilities to the phone and some third party applications
    • Does not support gestures that are not keyboard accessible.
    • On-screen Talkback keyboard was recently added to allow keyboard control of devices such as tablets that do not have a directional keypad
    • Many of the built-in phone features and apps are not accessible with Talkback including the web browser, mail, and home screen.
      • Many third party apps have been designed to compensate for this
    • Other third party screen readers available
      • Have similar limitations with Talkback
    • Talkback and Input
    ANDROID CONTINUED
  • 12.
    • Screen magnifier
      • There is no built-in magnifier
      • IDEAL Group has created a third party magnifier that works in some applications
    • Hearing aid compatibility and TTY is supported in the OS
      • Requires support from manufacturer of device
    • Dictation and Speech Control
      • Google offers some cloud based services
        • Speech-to-text
        • Voicemail to text
      • Third party applications from Nuance
        • Support voice dictation to text and web search
    • Access for users with Low vision, mobility impairments, and Hearing impairments
    ANDROID
  • 13.
    • Windows Phone replaces Window Mobile
    • Windows Phone OS does not including an accessibility layer
      • Silverlight and XNA applications can’t expose accessibility without the accessibility layer
      • No assistive technologies exist at this time for it
    • Windows Mobile provided some inherent accessibility
      • Third party screen readers (MobileSpeak and Talks)
        • Offer some touch screen support via gestures
        • Offer access via Bluetooth braille display
      • Mobile Magnifier by Code factory magnified screen
      • Captioning for Media Player
      • Keyboard accessibility such as sticky keys/filter keys
    WINDOWS PHONE/MOBILE
  • 14.
    • Popular due to security settings and compatibility
    • with Microsoft Exchange server
    • Added in an accessibility API in version 4.6 and above
    • Third party screen reader created with CodeFactory and Humanware
      • Provides access to phone features & standard apps
      • Limited access to HTML content (web and email)
      • Little or no support for third party applications
      • Limited support of models – limited updates
    • Provides color inversion as well as gray scale color mode
    • Provides text enlargement for many built-in screens and menus
    • One handed operation including sticky keys
    BLACKBERRY
  • 15.
    • Hearing Aid compatibility
    • Visual, audible, and vibration notifications
    • Closed captioning support for multimedia
    • Support for connection to a TTY device
    • Browser Zoom
    • Voice dialing
    • Tactilely discernable keyboard
    • Continued
    BLACKBERRY
  • 16.
    • Both of these OSes are effectively at end of life.
    • Symbian
    • Nokia plans to use Windows Phone 7 going
    • forward although a final release of the Symbian
    • OS is planned to bridge the gap
    • Third party screen readers Talks and MobileSpeak are available for the Symbian OS
    • HP
    • HP decided to discontinue WebOS and it’s tablet line this summer
    • Interest in the tablet remains and may continue through use of the Android OS
    SYMBIAN AND WEB OS
  • 17.
    • Mobile Apps
      • iOS and Android based app accessibility
      • targeted going forward to reach the most users
      • Use mobile best practices for creating
        • Best practices should be based on WCAG 2 and Section 508
    • Web Apps
      • RIA web apps
        • Use HTML 5 and ARIA based mobile web apps
        • Support is still emerging for HTML5 and ARIA support in mobile browsers and with mobile assistive technologies
    STRATEGIES FOR ACCESSIBLE APPS
  • 18.
      • Embedded Web Apps (WebView)
        • Supported with Talkback under OS 3.x Honeycomb
        • Supported with iOS
      • Web based best practices
        • WCAG 2 and Section 508
        • Take into account the W3C Mobile
        • Web Best Practices
    • Use Case Testing
      • End users with disabilities
      • Core tasks of the app
      • Cover different end user personas
    • Continued
    STRATEGIES FOR ACCESSIBLE APPS
  • 19.
    • Blind
      • Keyboard/accessible touchscreen access
      • Name, role, state, and properties of components
      • Dynamically updating content.
    • Low vision
      • Keyboard access and visual focus,
      • Use of Color and contrast
      • Complexity of layout/size of content
      • Dynamically updating content.
    • Mobility impairment
      • Touch-screen/D-pad access and visual focus,
      • Alternative input, one handed operation
    USER IMPACT
  • 20.
    • Reading disabilities
      • Complexity of page
      • Amount of information conveyed at one time
      • Spacing, color and size of elements. 
      • Dynamically updating content
    • Seizure
      • blinking and moving content
    • Deaf/Hard of hearing:
      • Use of multimedia and audio messages/content
      • Auditory feedback (sound notifications)
    • Continued
    USER IMPACT
  • 21.
    • iOS
      • Cocoa objective C based using XCode on the Mac
      • Use Inspector to inspect accessibility properties in iOS emulator
      • Use or subclass standard controls and follow Apple’s Human Interface Guidelines
      • Set label, traits, hint, frame, and value
    • Android OS
      • Ensure all UI elements are D-pad accessible (no screen reader cursor)
      • Label widgets
      • Send accessibility events for custom view components
      • Use the accessibilityService class of the Android SDK
    APP DEVELOPMENT
  • 22.
    • Designing for Accessibility (Android)
    • http://developer.android.com/guide/practices/design/accessibility.html
    • iOS Accessibility
    • http://developer.apple.com/technologies/ios/accessibility.html
    • Blackberry Accessibility Overview
    • http://us.blackberry.com/support/devices/blackberry_accessibility/
    • WebAIM Survey for Screen reader accessibility
    • http://webaim.org/projects/screenreadersurvey3/
    • AMP – Accessibility Management Platform
    • http://amp.ssbbartgroup.com
    REFERENCES
  • 23.
    • SSB BART Group
    • www.ssbbartgroup.com
    • For Sales assistance:
    • (800) 889-9659
    • [email_address]
    • For Partnering assistance:
    • Debra Ruh, CMO
    • (804) 749-3565
    • [email_address]
    CONTACT US

×