1. Mobile Accessibility: Next Generation Techniques & Tools Tim Springer, SSB BART Group Bill Curtis-Davidson, IBM

2. Agenda Key Concepts Mobile Accessibility in the SDLC AMP® for Mobile Demo Q&A

3. Key Concepts

4. Market Snapshot Mobile Customer Experience is Key “…mobile should be the only strategy.” Analyst Brian Solis – Altimeter Study “IT orgs will dedicate at least 25% of their software budget to mobile app development, deployment and management by 2017.” Analyst Firm IDC – Worldwide Mobile Enterprise Applications and Solutions Predictions for 2015 “Between 2013 and 2017, mobile phone penetration will rise from 61.1% to 69.4% of the global population.” eMarketeer – Worldwide Mobile Phone Users Report: H1 2014 Forecast & Comparative Estimates “In the US alone, $83 billion is lost each year as a result of poor customer experiences. That's more than all US e-commerce revenue.” IBM Institute for Business Value – How Marketing is taking charge: leading the customer experience Over 1B people worldwide live with some kind of disability, and 285M have visual impairments…” MobiForge – Why mobile Web accessibility matters 72% of respondents used mobile devices in January 2014… Only 12% reported using a mobile screen reader in January 2009 compared to 82% just five years later.” WebAIM – Screen Reader User Survey #5 Results

5. Digital Accessibility Maturity Model (DAMM) Program maturity is measured along ten key dimensions: Governance, Risk Management, and Compliance Communications Policy and Standards Legal and Regulatory Fiscal Management Development Lifecycle Testing and Validation Support and Documentation Procurement Training Dimensions

6. Relevant DAMM Dimensions Governance, Risk Management, and Compliance Policy and Standards Legal and Regulatory Development Lifecycle Testing and Validation Training

7. Mobile Accessibility in the SDLC

8. Key Best Practices Design and Implementation Design Ensure accessible use of color and contrast Ensure consistent labeling and navigation Ensure discoverability or indicators of interactions and status changes Design and Implementation Keyboard interface, alternative input access, and device gestures Responding to touch end or touch up events, touch target size, inactive space between controls Implementation Expose accessibility properties Interoperability with platform accessibility features

9. Mobile Accessibility and the SDLC Waterfall Requirements Gathering –Legal, Regulatory, Market, CSR What accessibility requirements and standards are relevant? –How does WCAG 2 apply to mobile? Design –Designing an accessible UI –Input and control Develop –Implement accessibility API for UI objects –Implement accessibility unit tests

10. Mobile Accessibility and the SDLC Waterfall Test QA testing of accessibility Primary QA testing Primary UAT testing with AT Deploy Support communication needs for PwD Provide accessible documentation

11. Mobile Accessibility and the SDLC Agile with a Scrum Flavor Definition of Ready includes consideration of accessible design requirements –Know how we are going to implement accessibility in user story Definition of Done includes accessibility testing –Scrum team must have ability to test for accessibility –In practice – tiered testing = a bit of both Release level UAT testing –Functional testing as part of release hardening –Not particularly agile - what you practically see

12. Mobile Accessibility and the SDLC Test Driven Development Relevant to both Agile and waterfall approaches Automated Testing (AMP) Automated Testing (Selenium, other) Validate accessibility in unit tests

13. QA and Issue Reporting Reporting Approaches for Logging Issues Need for technical and functional testing Automated results sent automatically to AMP® for sharing Manually test screens Test with assistive technology Perform use case testing (core tasks) by users with disabilities

14. AMP® for Mobile

15. Existing Tool Limitations … and Resulting Ecosystem Challenges Existing Tool Limitations Geared toward manual vs. more automated inspection Limitations in integration with compliance systems Not integrated into continuous development and different phases of the development life cycle Private vendors have a static code validation focus Ultimately fall short in helping application providers comply with legal requirements Ecosystem Challenges Android™ and iOS® platform vendors provide limited tools for accessible mobile app development Application providers need to have easier and more efficient ways to produce accessible apps Accessibility and quality assurance services providers need to be able to better serve a growing market need

16. Precursor Technology - IBM AbilityLab™ MAC Overview Description Mobile Accessibility Checker (MAC) Automated, on-device testing for accessibility Self-contained technology used as web service or software component Unified approach for accessibility analysis of multi-platform mobile apps (Native iOS®, native Android™, hybrid mobile) Supports analysis of native and hybrid apps: iOS® 7.1 / 8 Native Apps (except Swift), and Android™ 4.4.2 / 5 Native Apps; Apache® Cordova based hybrid apps. By 30-June- 2015, will support iOS® Swift Components Validation engine (based on a11y standards’ requirements) Downloadable library for xCode for iOS® development environment Downloadable library for Android™ development environments (Eclipse Juno SR2 or Kepler with ADT for Android™) IBM AbilityLab™ Mobile Accessibility Checker

17. IDE Libraries are downloaded by developers into the xCode for iOS® or Android™ development environment. They use the libraries to quickly assess the accessibility of various mobile UI components. The IDE Libraries automatically submit requests to Service Layer which utilizes evaluation and reporting engines. The engines are configured to check mobile app accessibility hierarchies against rules derived from compliance law and standards. The results of the evaluation are reported back from the service via AMP. SSB BART Group has used the IBM technology to build AMP® for Mobile. Precursor Technology - IBM AbilityLab™ MAC Technology Implementation

18. AMP® for Mobile How It Works Download relevant library to your local computer 1 Unzip and then add the AMP for Mobile library files to the relevant IDE 2 Run the app with the AMP for Mobile libraries in an emulator or on a device. 3 Check out the results in AMP 4

19. Feature Compared A11y Inspector for iOS® (Apple) Lint for Android™ (Google) AMP® for Mobile (IBM & SSB) Checks Dynamic App Runtime in SimulatorXX Checks A11y in App Source Code (Static)X Inspects UI objects for accessibility attributesXXX Checks accessibility notificationsXX Checks against robust set of rules mapped to external standards X Checks for blind screen reader useXX Checks color and contrast (Low Vision)X Checks multiple UI objects at same timeX Checks usability – button size/spacingX Produces report of a11y issues across multiple UI objects X Can be run as a web serviceX Can be integrated – via SDK or API – into other applications & tools X AMP® for Mobile Approach Comparison

20. Demo

22. Thank You Contact Us Tim Springer tim.springer@ssbbartgroup.com Bill Curtis-Davidson wacurtis@us.ibm.com Download Slide Deck info.ssbbartgroup.com/CSUN2015 Follow Us @SSBBARTGroup linkedin.com/company/ SSB-BART-Group facebook.com/ SSBBARTGroup SSBBARTGroup.com/blog

23. About SSB BART Group Unmatched experience Focus on accessibility Solutions that manage risk Real-world strategy Organizational strength and continuity Dynamic, forward-thinking intelligence Fourteen hundred organizations (1445) Fifteen hundred individual accessibility best practices (1595) Twenty-two core technology platforms (22) Fifty-five thousand audits (55,930) One hundred fifty million accessibility violations (152,351,725) Three hundred sixty-six thousand human validated accessibility violations (366,096)