The web-site is now in readonly mode. Login and registration are disabled. (28 June 2019)

Mobile Accessibility / a11y workshop

15 October 2013

An internal OU workshop, in the Jennie Lee Labs, organized by Chetz Colwell.

Cloud created by:

Nick Freear
24 October 2013

 

Speakers

Book

"Don't Panic: Mobile Developer's Guide to the Galaxy", 13th edition, Editors: Marco Tabor & Julian Harty | http://enough.de/products/mobile-developers-guide (Enough.de/fileadmin/uploads/dev_guide_pdfs/Mobile_DevGuide_13.pdf) (.../Developers_Guide_8th.pdf)

Notes

Eyes Free - TV Ramen, Charles Chen:

  • * Uses relative positioning for gestures;


Android accessibility API

3 layers:

  • * Surface / top level - meaningful "label", content descriptions, hints - basic controls - buttons, edit boxes;
  • * "Talkback" - accessibility service on Android;
  • * Middle layer - virtual DOM - navigation - swipe, calendar, +- to change;
  • * Third layer - write your own accessibility service;
  • * Register: "I'm the preferred screen reader for 'uk.ac.open' (Java) namespace";
  • * Do your own TTS;
  • * Package your own MP3/ OGG resource files with the App.;



FB reader J - Java, e-Book reader, accessibility, DAISY;


3 outputs, 2 inputs - communication:

* Output: visual, audio, haptic/ vibration/ touch;

* Input: touch, speech;



iOS: "Screen curtain"

http://caniuse.com/#feat=wai-aria

http://google.co.uk/#q=mobile+accessibility+guidelines&start=10

Test automation - UI test automation on Android - use "labels" for testing - side-effect benefits for accessibility?! Or vice-versa.


Test automation - Selenium 2 - uses Test Driver - becoming W3C standard..!!


iOS: Instruments - works like Voice Over;

Android: UI Automator View;

Extra content

Embedded Content

Contribute

Contribute to the discussion

Please log in to post a comment. Register here if you haven't signed up yet.