After attending last year’s outstanding Accessibility Summit, I couldn’t see how Environments for Humans could present an even better conference.
But they did, kudos to Ari Stiles and Christopher Schmitt for all their work planning the summit!
The second annual Accessibility Summit online conference didn’t disappoint, bringing together experts from around the world to share their latest research, tips and development.
In her Integrating Accessibility Across Devices presentation, Henny Swan provided detailed information about mobile APIs, tools, testing and resources.
Here are my notes and key takeaways from her talk:
Notes
Mobile Platform APIs
- Less mature on mobile than desktop
- iOS has best support
- Android working on it
Assistive technology: Text to speech application Proloquo2Go: http://t.co/KWyHXNZJ #a11ysummit
— Deborah Edwards-Onoro (@redcrew) September 27, 2011
RT @redcrew Link to compatibility tables for #HTML5, WAI-ARIA, @iheni recommended: http://t.co/LA73Kop8 #a11ysummit
— Karen Mardahl (@kmdk) September 27, 2011
WebAIM mobile screen reader survey: http://t.co/pXRP1vOb #a11ysummit
— Deborah Edwards-Onoro (@redcrew) September 27, 2011
There are no definitive universally accepted set of #mobile #accessibility guidelines, says @iheni. #a11summit
— Deborah Edwards-Onoro (@redcrew) September 27, 2011
Use blocks of color rather than outlines or shades. Avoid using color alone to convey information.
Quick tests for mobile screen readers:
- All functional/content related elements have an alternative
- Eye candy is ignored
- Elements that need explanation have a longer description
- Alternatives do not describe the type (button, checkbox)
- Page/screens have titles
- Layout changes are announced
- Changes of state are announced
Whoa. Lots of great tips & advice from @iheni‘s preso. I know I’ll be watching recording more than once. #a11ysummit
— Deborah Edwards-Onoro (@redcrew) September 27, 2011
Two reasons to use consistent alternatives across desktop and mobile:
- Developers do the work once
- User can have the same experience across devices
#a11ysummit so… what I am hearing from @iheni build it simple, meaningful, neat.
— theWendee (@thewendee) September 27, 2011
Mobile browser support for HTML5 currently not good – but future may be bright #a11ysummit
— Evelyn Lee Barney (@elbinfodesign) September 27, 2011
Key Takeaways
- Develop agnostic mobile accessibility guidelines
- Build an accessible HTML mobile website, then add accessible native applications
- Create shared inventories for alternatives, headings and labels.
- Test – talk is cheap. You all have a screen reader in your pocket (on your smart phone).
- Do your best, share your findings. There’s not a critical mass of knowledge out there. More people need to share.
Wow, what an amazing write up THANK YOU. I’m now going to lazily redirect folk from my blog to yours!
Henny
@Henny, you’re welcome. Loved your presentation, I learned a lot. Thank you for sharing all the great information and tips.
I want to add two more links from Henny that she shared back in September on Twitter.
Media accessibility user requirements from the HTML5 Task Force
http://www.w3.org/WAI/PF/media-a11y-reqs/
And the Media Accessibility Checklist
http://www.w3.org/WAI/PF/HTML/wiki/Media_Accessibility_Checklist
Now I can make do with one tweet and include these two links! 🙂
Thanks Karen, appreciate you adding the great resources.
It risk of shamelessly plugging my stuff a lot of what is covered in my talk is covered in more depth on my blog in the mobile category: http://www.iheni.com/category/mobile/
Thanks all!
@Henny,
No worries. Thank you for all the information and resources you share on your blog.
Hello again…I presented a similar set of slides at CSUN 12 which hopefully will be of interest. You can find them on Slideshare at http://www.slideshare.net/iheni/mobile-accessibility-moba11y
@Henny,
Thanks for the update and great resources in your slides. Interesting to see the mobile browser global market share change from 2011 to 2012 with Opera still leading, and Android taking over 2nd place from iPhone. I wonder how many web professionals realize smartphones sold in the US must have an accessible web browser by October 2013?