IOS 6 Accessibility Features Overview

At today’s World Wide Developer’s Conference (WWDC) Apple announced IOS 6 with a number of accessibility enhancements. I am not a developer (yet!) so I don’t have a copy of the OS to check out,  so this post is primarily about what I read on the Apple website and on social media. A few of these features (word highlighting for speak selection, dictionary enhancements, custom alerts)  were tucked away in a single slide Scott Forstall showed, with little additional information on the Apple website. So far, these are the big features announced today:

  • Guided Access: for children with autism, this feature will make it easier to stay on task. Guided Access enables a single app mode where the home button can be disabled, so an app is not closed by mistake. In addition, this feature will make it possible to disable touch in certain areas of an app’s interface (navigation, settings button, etc.). This feature could be used to remove some distractions, and to simplify the interface and make an app easier to learn and use for people with cognitive disabilities. Disabling an area of the interface is pretty easy: draw around it with a finger and it will figure out which controls you mean. I loved how Scott Forstall pointed out the other applications of this technology for museums and other education settings (testing), a great example of how inclusive design is for more than just people with disabilities.
  • VoiceOver integrated with AssistiveTouch: many people have multiple disabilities, and having this integration between two already excellent accessibility features will make it easier for these individuals to work with their computers by providing an option that addresses multiple needs at once. I work with a wounded veteran who is missing most of one hand, has limited use of the other, and is completely blind. I can’t wait to try out these features together with him.
  • VoiceOver integrated with Zoom: people with low vision have had to choose between Zoom and VoiceOver. With IOS 6, we won’t have to make that choice. We will have two features to help us make the most of the vision we have: zoom to magnify and VoiceOver to hear content read aloud and rest our vision.
  • VoiceOver integrated with Maps: The VoiceOver integration with Maps should provide another tool for providing even greater  independence for people who are blind, by making it easier for us to navigate our environment.
  • Siri’s ability to launch apps: this feature makes Siri even more useful for VoiceOver users, who now have two ways to open an app, using touch or with their voice.
  • Custom vibration patterns for alerts: brings the same feature that has been available on the iPhone for phone calls to other alerts. Great for keeping people with hearing disabilities informed of what’s happening on their devices (Twitter and Facebook notifications, etc.).
  • FaceTime over 3G: this will make video chat even more available to people with hearing disabilities.
  • New Made for iPhone hearing aids: Apple will work with hearing aid manufacturers to introduce new hearing aids with high-quality audio and long battery life.
  • Dictionary improvements: for those of us who work with English language learners, IOS 6 will support Spanish, French and German dictionaries. There will also be an option to create a personal dictionary in iCloud to store your own vocabulary words.
  • Word highlights in speak selection: the ability to highlight the words as they are spoken aloud by text to speech benefits many  students with learning disabilities. Speak selection (introduced in IOS 5) now has the same capabilities as many third party apps in IOS 6.

These are the big features that were announced, but there were some small touches that are just as important. One of these is the deep integration of Facebook into IOS. Facebook is one of those apps I love and hate at the same time. I love the amount of social integration it provides for me and other people with disabilities, but I hate how often the interface changes and how difficult it is to figure it out with VoiceOver each time an update takes place. My hope is that Apple’s excellent support for accessibility in built-in apps will extend to the new Facebook integration, providing a more accessible alternative to the Facebook app which will continue to support our social inclusion into mainstream society. You can even use Siri to post a Facebook update.

Aside from the new features I mentioned above, I believe the most important accessibility feature shown today is not a built-in feature or an app, but the entire app ecosystem. It is that app ecosystem that has resulted in apps such as AriadneGPS and Toca Boca, both featured in today’s keynote. The built-in features, while great,  can only go so far in meeting the diverse needs of people with disabilities, so apps are essential to ensure that accessibility is implemented in a way that is flexible and customized as much as possible to each person. My hope is that Apple’s focus on accessibility apps today will encourage even more developers to focus on this market.

Another great accessibility feature that often gets ignored is the ease with which IOS can be updated to take advantage of new features such as Guided Access and the new VoiceOver integration. As Scott Forstall showed on chart during the keynote, only about 7% of Android users have upgraded to version 4.0, compared to 80% for IOS 5. What that means is that almost every IOS user out there is taking advantage of AssistiveTouch and Speak Selection, but only a very small group of Android users are taking advantage of the accessibility features in the latest version of Android.

Big props to Apple for all the work they have done to include accessibility in their products, but more importantly for continuing to show people with disabilities in a positive light. I loved seeing a blind person in the last keynote video for Siri. At this keynote, Apple showed another  blind person “taking on an adventure” by navigating the woods near his house independently. As a person with a visual disability myself, I found that inspiring. I salute the team at Apple for continuing to make people with disabilities more visible to the mainstream tech world, and for continuing to support innovation through inclusive design (both internally and through its developer community).

Tecla Access Shield and VoiceOver

Jane Farrall has posted an excellent review of the new Tecla Shield from Komodo OpenLab. This is a new switch interface that allows one or more switches to communicate with the iPad. Switch access for the iPad has been available for some time, but only for certain switch compatible apps. I have to admit that I am not an expert in this area, but I enjoy learning about cutting edge technology and this is an area of accessibility where exciting new developments are still ahead of us.

Tecla Shield is one of a new generation of interfaces that promise full switch access to the iPad (another is the iPortal from Dynamic Controls with its Accessibility add-on). Alternative access (which includes access with switches) has been an issue since the iPad first came on the market, so it’s great to see creative solutions that focus on this area. As Jane noted, the Tecla Shield device depends on VoiceOver hooks in IOS to allow switch access to the iPad.

The fact that both Tecla Shield and iPortal rely on VoiceOver to provide alternative access to IOS devices presents a great opportunity for us as people with disabilities to come together and push for accessibility in the form of VoiceOver compatibility. Now it’s not just people with visual disabilities who benefit from an app that has been properly designed for VoiceOver compatibility. A whole new population of people with mobility, motor and cognitive impairments benefit as well. So many times even we as people with disabilities tend to adopt a “that’s not my problem” or “that doesn’t affect me” attitude. Thus, some people with visual disabilities don’t really care too much about captioning for those with hearing disabilities and some people with hearing disabilities don’t care too much about screen readers. Unfortunately, that shortsighted attitude keeps us from achieving the kind of unity that would give us a stronger presence to push developers into really paying attention to all of our accessibility needs.

iPhoto App and Accessibility

This weekend I finally had a chance to try out the new iPhoto app Apple released along with iPad 3 (or as they are calling it “the new iPad.”) As an aspiring photographer I was impressed with the many options for organizing, editing, and sharing photos Apple has packed into this app which only costs $4.99 in the App Store. There have been many reviews of the new app posted online already, so I will not add another one here. However, I do have a unique perspective on the new app that I would like to share. Not only do I like to take photos (calling myself a photographer might be a stretch but it’s a hobby I enjoy and continue to try to get better at every day), but I also have a visual disability so I am part of a small community of blind photographers.

When I opened the iPhoto app on my iPhone, the first thing I did was turn on the VoiceOver built-in screen reader to hear how it would do with the new photo editing app. Frankly, I was not surprised that the new iPhoto app would be as accessible with VoiceOver as it is. I have come to expect accessible products from Apple over last few years, and I’m proud to be associated with it as an Apple Distinguished Educator. However, as I dug deeper into the iPhoto app with VoiceOver, the level of attention to detail in providing accessibility was still pretty impressive. For example, the brushes used to retouch photos (repair, lighten, darken, etc) are all accessible through VoiceOver gestures, as are the exposure and color correction controls and the various effects, . When I selected the crop tool, VoiceOver told me to pinch to resize the photo and as I did so it told me how much as I was zooming in as well as how far the image was offset (“image scaled to 15X, image offest by 15% x and 48% y).

On the iPad, there is a dedicated help button that opens up a series of overlays indicating what each button does. Not only was every part of the overlay accessible, but so is the entire help built into the iPad version of the app. The attention to detail is more impressive to me because there are so few blind photographers who would take advantage of an app such as iPhoto. What it does show is the level of commitment Apple has to accessibility, because it will go to great lengths to add accessibility even when only a few people will benefit from it.

In a recent blog post, accessibility advocate Joe Clark called out a number of hot new apps (Readability, Clear, Path, and Flipboard) for what he called irresponsible web development that results in accessibility barriers. Well, to me this new iPhoto app shows that you can design an app that is not only visually appealing, feature-packed and easy to use and learn, but also accessible to people with visual disabilities. I hope more developers start to realize that accessibility does not have to compete with good design, but that both complement each other.

When I first loaded the iPhoto app on my iPhone (that was the first device I installed the app on) I was too impatient to go on the Web and read about the app before I started to work with it. That’s just the kind of user I am, I like to get right in and try things out. Well, on the iPhone app the Help button from the iPad version of the app is missing. Most of the icons make sense, but in some cases I was unsure, so what I did was turn on VoiceOver and move my finger around the screen to have it announce what each button was for (or to at least give me a better idea). In that case, compatibility with VoiceOver helped me learn the app much faster without having to consult the help, and that got me to thinking. As these devices (phones, tablets, and whatever comes next) continue to get smaller and the interfaces start to use more visuals (tiles, buttons, etc.) and less text, the ability to hear the help may become an essential aspect of learning how to use the interface. In this way, features like VoiceOver would actually enhance the usability of a particular app for everyone – what universal design is all about.

 

Accessibility in iBooks 2 and iBooks

Today’s post will focus on some of the lessons I have learned about the accessibility of ebooks created with iBooks Author and accessed on the iPad with iBooks 2.

I was pleasantly surprised to learn that Apple included an option for adding a description for images and other objects when it released iBooks Author. I don’t remember this feature being discussed much at the event where Apple unveiled iBooks 2 and iBooks Author, and only found out about it while test driving the software.

An even better surprise was learning that closed captions are now supported for any video that is embedded in an iBook. This is a great feature that will benefit a range of different learners (not only those with hearing disabilities). I think these new accessibility features of iBooks Author and iBooks 2 will go a long way toward facilitating the adoption of iBooks in the schools by meeting legal requirements for accessibility set by the U.S. government (for a summary of the legal requirements, please see the Dear Colleague letter and the follow-up clarification from the U.S. Department of Education).

Apple has published a support document  with  advice for making iBooks created with iBooks Author more accessible.  However, the article focuses mostly on the accessibility of images and other visual content, and does not include any information about closed captions. I would add a couple of bullet points to the advice given in the Apple support document:

  • the article suggests adding descriptions for all images, including background images. Web accessibility guidelines state that decorative images should have a null or empty alt attribute so that they are skipped by a screen reader, but there is currently no way in iBooks Author  to indicate that an image should be skipped by VoiceOver on the iPad. In my testing, I found that when you leave the description field for an image empty in iBooks Author, VoiceOver will read the entire file name when it comes across the image in iBooks 2. This is a problem because most people don’t use very descriptive file names before they add their images to a document. In my test iBook, I forgot to add a description for one of the placeholder images included in the iBooks Author template I selected. When I accessed the iBook on my iPad, VoiceOver read the following: “1872451980 image”. Imagine how confusing this would be to someone who is blind and relies on the VoiceOver screen reader to access content in iBooks.  For the time being, I would suggest following the guidance from Apple and marking up all images, including those that are used for decorative purposes, but I would recommend marking up  decorative images (those that don’t add any content that is essential for understanding) with the word “Background” in the description. By default, VoiceOver will say the word “image” so it is not necessary to add that to the description. While it would be better for the image to be skipped by VoiceOver if it is not essential, I would rather hear a quick, single-word announcement that is much easier to ignore than a long number read aloud in its entirety by VoiceOver, or an unnecessary description for an image that does not add in any way to my understanding of the content.
  • as much as possible, image descriptions should focus on the function of each image rather than its visual appearance. Writing descriptions (or alternative text as it is more commonly known in the web accessibility world) is as much an art as it is a science, and much of it is subjective. There are many sites that provide information on how to write good alt text for images on websites, but I have found very little guidance on how to write descriptions for other online content such as ebooks. My recommendation would be to focus on three C’s when writing descriptions for images in iBooks Author: Context, Content and Conciseness. First, I would ask myself if the image is properly described in the surrounding text. If it is, then it might be more appropriate to mark it up as a decorative image (“Background”). Next, I would ask myself “what information does this image convey?” and focus on the key idea or concept supported by the image rather than its visual details. There could be a few exceptions where you might need to focus on the visual details of the image, but these cases should be the exception rather than the rule. The final consideration is to keep the description as brief and concise as possible. I would try to keep it to no more than 8-10 words if possible.

The second aspect of accessibility supported in iBooks Author is closed captioning. If a movie added to an iBook in iBooks Author has been captioned, you can view the captions in iBooks 2 on the iPad by going to Settings, Video and making sure Closed Captions is set to On. If you know a file has been captioned and you don’t see the captions on the iPad, you may need to go into the Settings app and turn the captions off and then on for the captions to show up. This appears to be a bug that will likely get fixed in a future update to iBooks or IOS.

To create a captioned file, I have found that a workflow using MovieCaptioner and Compressor has worked well for me. I like MovieCaptioner for creating the captions because it is affordable and easy to learn. To learn more about how to create captions with MovieCaptioner you can view this tutorial I have made available on the Tech Ease website at the University of South Florida.

The only difference with my current workflow is that rather than exporting a captioned QuickTime video file from MovieCaptioner I’m only using the software to create the SCC file that has the caption text and timecodes. I then use Compressor to make sure the video file is in the correct format for the iPad and to add the captions. I found that when I exported the movie from MovieCaptioner I would get an error message in iBooks Author and the software would refuse to import the movie. Once I have exported my SCC file (Export > SCC in MovieCaptioner), I use Compressor to combine the two as follows:

  1. Open Compressor and choose Add File from the toolbar, then locate the desired video on your hard drive.
  2. In the Settings pane (Window > Settings) choose the Destinations tab, then find Desktop (or your preferred destination ) and drag it into the Batch window.Drag Destination from Settings pane to Batch window.
  3. Switch to the Settings tab and choose Apple Devices, H.264 for iPad and iPhone, then drag that setting on top of the destination in the Batch window.
    Drag H.264 for IPad and iPhone setting into the Batch window
  4. With your movie selected, open the Inspector (Window > Inspector or click the Inspector button on the toolbar), select the Additional Information tab and then Choose to find the SCC file on your computer.
    Select Choose from the Additional Information tab in the Inspector
  5. Select Submit to start the export process.

Once your movie has been exported from Compressor you should be able to drag it right into your iBook in iBooks Author to add it as a widget. As with images, make sure you provide a description in the Inspector.

Students with disabilities have traditionally had a difficult time with access to textbooks. iBooks Author provides a platform for making textbooks more accessible for all learners as long as a few accessibility principles are kept in mind. What an exciting time to be working in educational technology and accessibility!

2012: The Year I Quit Photography?

Well, not quite. But it will definitely be the year I make a major transition in my photography. As I will explain below, 2012 will be the year that I begin to take most of my photos with my iPhone. Since I purchased my iPhone 4S this fall, I’ve been using it more and more as a replacement for my Nikon D3100 DSLR camera. The improved camera specs of the iPhone 4S (8 megapixels at F2.8), along with the new features in IOS 5 (such as quick access to the Camera app from the home screen, the ability to use the volume up button to take a photo and VoiceOver compatibility) make the iPhone the ideal device to “capture the moment” for someone like me.  As Chase Jarvis has stated, it is the camera that’s always with you, always at the ready to document those fleeting moments in life.

However, it’s not only the convenience and ease of use of the iPhone that’s drawing me away from using a traditional camera to capture images. As most of you reading this know, I have a visual impairment and I’m slowly losing my vision to a condition called retinitis pigmentosa, or RP for short. At the moment, I have less than 10 degrees of vision left (less than 20 degrees qualifies you as being legally blind). RP leads to progressive vision loss starting with peripheral and low light vision. In my case, my low light vision is what has been most affected by my RP, but the usual closing in of the field of the vision is also there.

I’ve been lucky that my progression with vision loss has been pretty slow, but the last few times I’ve gone out to shoot with my camera, I’ve noticed some changes in my remaining eyesight. It’s ironic that it is photography that is helping me judge these changes in my vision. I’m not sure if these changes are really there or if it’s just my mind playing tricks on me. Much of what I’ve read about RP states that people with the condition lose most of their peripheral vision around the age of 40, and guess what, I turn 40 in a few days. So, maybe it’s all in my mind, but the last few times I’ve gone out with my camera I’ve ended up with some major eye fatigue and pain afterwards. I think what’s happening is that since I can’t see that much of the frame through the viewfinder, I’m having to move my eyes a lot to make sure I have framed the shot properly. All of this eye movement is probably fatiguing my eye muscles, so that when I get home I have pain in my eyes and the area around them. It usually takes a few doses of pain relief medicine and some warm compresses for the eye pain to subside, and I would rather avoid it if at all possible.

I love photography, and I would hate to give it up. However, when I got into this hobby I knew that the day would eventually come when my vision loss would make photography really difficult. I have no regrets for having spent a considerable amount of money on my DSLR and my lenses and other accessories over the last couple of years. I would not give up the joy that the hobby has brought me over that time. My photography has allowed me to experience a lot of beauty around me that I would normally miss with my own eyes (the camera has a far better range of vision than my own eyes). I also saw photography as a challenge, not only for myself but also for all of us who have visual impairments. I have always enjoyed the expression on people’s faces (when I can see them) when I step up to a spot with my white cane and pull out a camera to take a photo. I know they look, and I know they probably ask themselves “wait, isn’t he blind, why is he taking a photo?” If I have forced anybody to confront their preconceived ideas of the meaning of blindness and disability, then it has been all worth it to me. I can continue to make a similar statement through my use of the iPhone as a video and still camera.

So the thought that has been on my mind for the last few days of 2011 and the first few of 2012 is, where do I go from here? Well, I would say that for 95-99% of the time I will be using the iPhone to take photos. The large, bright, sharp display on the device will make it easier for me to frame shots without having to stress my eyes as much. I also plan to use a trick I recently learned that makes it easier to take a photo by pressing the center button on the Apple headphones. I’ve looked at other options, but for now the iPhone appears to be the best one for me. The wide selection of apps with filters also means that even if I don’t quite get a picture right, I can apply a few filters and turn my failures into “creative experiments.” In some ways, I find not having to know so much about my camera sort of freeing, in that I can now focus on getting the best composition and less on what my camera is doing. In some ways, that’s exciting.

My DSLR camera does have a LiveView mode that allows you to use the LCD screen to frame a shot, but that mode is very slow (defeating the purpose of having a DSLR) and it is difficult to get sharp photos if you’re not using a tripod. Having said that, I have no plans to sell my camera and lenses. I could still use the LiveView mode for recording the videos I use in my tutorials on mobilelearning4specialneeds (after all, video is the reason that mode is in the camera in the first place). I could also use the camera for some brief shoots in a favorable lighting conditions. Limiting my time using the viewfinder will be the key, as will be making sure I take frequent breaks to let my eyes rest in between shots. At the very least, I will keep my camera and lenses as a nice present for my daughter when she gets older (though I’m sure there will be much better technology for her to choose from at that time).

I’m so grateful to Apple for taking the iPhone in the direction that it has by making it such as great portable camera (it is now surpassing traditional point and shoot cameras in the number of uploads on Flickr, one of the most popular photo sharing sites). Without the iPhone 4S, I think 2012 really would be the year I end my journey as a photographer. The way I see it, without digital I would have never gotten into photography in the first place (too costly considering the number of photos I have to take for a few good ones to turn out), and without the iPhone I would not be able to now continue in the hobby. It has been a beautiful journey with its usual ups and downs (times when I have gotten really frustrated when I couldn’t take the photos I wanted to, either because of my lack of technical expertise or the limitations of my eyesight), but I wouldn’t change a thing. There is a saying well known to those who follow Apple, “here’s to the crazy ones.” Well, I guess photography helped me see myself as one of those crazy ones who can change the world one small step at a time. It is crazy for someone with my kind of visual impairment to invest the money and time I have in pursuing a hobby like photography, but I hope that my crazyness has inspired somebody else to take on their own crazy adventure into whatever hobby fills them with joy and passion.

This long blog post is really the inspiration for the video I submitted for my application to the 2012 ADE Global Institue in Cork, Ireland, which is available below:

VoiceOver and Dictation on iPhone 4S

I finally got an iPhone 4S after waiting in line for almost two hours at my local Apple Store. Entering text with VoiceOver is a lot easier on the new iPhone because I can now use the dictation feature available with the onscreen keyboard. To use dictation with VoiceOver, I move my finger on the screen until I find the dictation button, then double-tap with one finger anywhere on the screen and start my dictation. When I’m finished, I can double-tap with two fingers or move the phone away from my face and it will stop the dictation. This is such a great feature that will be a huge productivity boost for those of us who use VoiceOver on IOS devices. This quick YouTube video shows how the feature works:

Authoring ePub documents for the iPad with Automator, TextEdit and Text to Speech

The website Mac OS  X Automation has a great tutorial on how to use some of the new text to ePub automator actions that are available in Mac OS X Lion, and they have even put together a few automator workflows to make the process easier. I was inspired by the information they had on their website to see if I could create my own ePub document using the information they provided, but I added a twist: I added a recording of the text at the beginning of each chapter and this recording was created using the excellent Alex voice available with the Text to Speech feature in Mac OS X. The tutorial is now available on YouTube (and it is closed captioned). I think having an audio version could be beneficial for students with learning disabilities by providing the content in another modality. While the iPad and other IOS devices already include a great screen reader in VoiceOver, the voice available on those devices is not as good as Alex is, so this is why I decided it might be a good idea to provide the text to speech recording created on the Mac. Along the way to making this tutorial, I also learned about  new automator actions for converting video and audio files into the correct formats for ePub (and iTunes U). To use these actions, select your file(s), right-click on them and choose Services, Encode Selected Video (or Audio) Files. For audio this will result in an .m4a file saved to the same location as the original, and for video the format of the converted file will be .m4v.

Services, Encode Selected Video Files option when you right-click on a video file.

Overview of new accessibility features in IOS 5

With IOS 5, Apple has introduced a number of features to make their mobile devices even more accessible to people with disabilities:

  • VoiceOver enhancements: IOS 5 includes an updated voice for VoiceOver, the built-in screen reader for people who have visual disabilities. I have found the new voice to be a great improvement over the old one, especially when reading long passages of text in apps such as iBooks. Another improvement is that the triple-click home option is set to toggle VoiceOver by default. Along with the PC-free setup introduced with IOS 5, this small change has made it possible for someone with a visual disability to independently configure his or her IOS device out of the box, without any help from a sighted person. The Mac-cessibility website has an excellent overview of the many new changes in VoiceOver that I highly recommend reading.
  • Camera app compatibility with VoiceOver: this is a neat feature that will make photography more accessible to people with low vision and those who are blind. With VoiceOver on, if you launch the Camera app it will announce how many faces are in the frame. In my testing this worked pretty well, and I’ve used it successfully on the iPad and the iPod touch. It should work even better on the iPhone, which has a better sensor and optics. Combined with the ability to turn on the camera app from the lock screen on some devices (iPhone and iPod touch) by double-tapping the home button and the fact that you can use the volume up button as a shutter release, Apple has done a lot to make photography more accessible to people with visual disabilities.
  • Text selection showing Speak menu option.Speak selection (text to speech): This is one of my favorite features introduced with IOS 5. It provides another modality for students with learning disabilities who can benefit from hearing the text read aloud to them. To use it, go into Settings, General, Accessibility, tap Speak Selection and choose On. Once you’ve enabled this feature, when you select text a popup will show the option to Speak the text using the VoiceOver voice. Note that you can control the speaking rate for the speak selection feature independently from VoiceOver.
  •  Balance controls for audio: In addition to mono-audio, which combines both channels of stereo audio into a single mono channel, there is now an option for controlling the  left/right balance for stereo sound. On the iPhone, there is now also a special Hearing Aid mode that is supposed to make the device more compatible with hearing aids.
  • Handling of incoming calls: you can choose to automatically route incoming calls to the speaker phone feature of the phone, or to a headset.
  • New alert types: on the iPhone, you can use one of five unique vibration patterns to identify who is calling if you have a hearing disability, or you can create your own pattern by tapping it on the screen. These custom vibration patterns can be assigned in the Contacts app by opening a contact’s information, choosing Edit, Vibration and then Create New Vibration. There is also an option to have the LED  flash go off when you get a notification, a new message, and so on.
  • Assistive touch: this was one of the most anticipated accessibility features in IOS 5. Assistive touch was designed to make IOS devices easier to use for people with motor difficulties. For example, someone who is not able to tap the Home button to exit an app can now bring up an overlay menu with icons for many of the hardware functions of their device, including the Home button. Overlay menu for assistive touch.Assistive touch also includes options allowing for single finger use of many of the multi-touch gestures (including the new four finger gestures available only for the iPad and the pinch gesture used for zooming). To use assistive touch, choose Settings, General, Accessibility and turn on Assistive Touch. You will know assistive touch is enabled when you see a floating circular icon on the screen. Tapping this icon will open the overlay menu with the assistive touch options. Note that you can move the assistive touch icon to another area of the screen if it gets in the way. Please note that Assistive Touch is not compatible with VoiceOver. I really wish the two features could work in tandem. This would be helpful to users with multiple disabilities.
  • Custom gestures: assistive touch includes an option to create your own gestures. Update: I was able to create a few useful gestures after watching this video from Cult of Mac. I created one for scrolling up on a page and one for scrolling down. Now when I’m reading a long web page, instead of having to swipe up or down to scroll I can bring up the assistive touch overlay menu, select the new gesture from the Favorites group and tap once on the screen to scroll.
  • Typing shortcuts: under Settings, General, Keyboard you can create shortcuts for common phrases. For example, you could create a shortcut that would enable you to enter an email signature by simply typing the letters “sig” and pressing the space bar. This feature should provide a big productivity boost to anyone who has difficulty entering text on their mobile device.
  • Siri and dictation (iPhone 4S only): the new personal assistant uses voice recognition and artificial intelligence to respond to a range of user queries that can be made using everyday language rather than preset commands. The Apple website has a video that demos some of the capabilities of Siri.  One of the amazing things about Siri is that it works without any training from the user. Along with Siri, the iPhone 4S also includes an option to dictate text by tapping a microphone button on the keyboard.  The ability to use your voice to control the device can be helpful to many different types of disabilities, including those who have disabilities that make it difficult to input text. One of the things I have found especially frustrating when using VoiceOver on IOS devices is inputting text, so I hope this new dictation feature makes that easier. I will have a chance to test it out more thoroughly once I get my own iPhone 4S (currently out of stock in my area). Update: I finally got my hands on an iPhone 4 and I tried using the dictation feature with VoiceOver. It is working really well for me. I find the microphone button on the onscreen keyboard by moving my finger over it, double-tap to start dictation (as indicated by a tone) and then I double-tap with two fingers to stop it. Even better, after I’m done dictating the text, if I move the phone away from my mouth,  it automatically stops listening! I love this feature.
  • Word selection showing Define menu option.Dictionary: While it is not listed as an accessibility feature, having a system dictionary is a new feature that is great for providing additional language supports to students with learning disabilities. To use this feature, select a word and a popup will show the Define option that will allow you to look it up using the same dictionary that has been previously available only in iBooks.
  • iMessages: a new  add-on for the Messages app makes it possible to send free MMS messages to any owner of an IOS device. Many people with hearing disabilities rely on text messaging as a convenient means of communication. The iMessages will be especially helpful to those who are on a limited text messaging plan.
  • Reminders app: The new Reminders app has a simple interface that will make it a nice app for people who need help with keeping track of assignments and other tasks. On the iPhone 4 or iPhone 4S, tasks can be tied to a location using the phone’s GPS capabilities. One use of this feature could be to set up a reminder for a person to take their medication when they get to a specific location, for example.
  • Airplay mirroring (iPad 2, requires an Apple TV): along with IOS 5, a recent firmware update for the Apple TV enables mirroring to a projector or TV using Airplay. I can see this option being helpful in a class where there are students in wheelchairs who have difficulty moving around the room. Using air mirroring, the teacher could bring the iPad 2 to the student and the rest of the class could still see what is displayed by the projector or TV.
The new accessibility features make IOS 5 a must-have update for anyone who has a disability, as well as for those who work with individuals with disabilities. For schools and other educational institutions, the accessibility features of IOS make Apple mobile devices an ideal choice for implementing mobile learning while complying with legal requirements such as Section 504, Section 508 and the Americans with Disabilities Act.
Disclosure: I am an Apple Distinguished Educator.

Two new features for screencasting in OS X Lion

As I was looking through the list of 250 new features in OS X Lion, I came across two that I think will be helpful to teachers and anyone who creates screencasts (screen recordings). QuickTime in OS X Lion includes the ability to record a region of the screen, not just the full screen. This feature is helpful when you just want to record one application window. Another feature that is helpful is the ability to show mouse clicks while recording. This feature will make it easier to follow the action on the screen as you watch a screen recording. Now if only Apple would add a pointer to the iPad when it is in mirroring mode that should be a big help for classroom demonstrations.

Slimming Down Video Files, Part 2

Well, after finding out that Miro does not really handle WMV files on Windows, I had to look for another option for video compression on that platform. Fortunately, one of my co-workers suggested Quick Media Converter HD. QMC is a Windows only freeware program that converts to a number of formats, including H.264 MP4 for iPhone. I tried converting the sample HD video (which is in WMV format) that ships with Windows 7 and it reduced the video from 25MB to 4MB using the MP4, 640 X 380 preset. The performance in terms of the time it took to do the conversion was pretty good, even though this was a short clip. The interface for QMC is not the prettiest, but I think it’s a good tool to have if you work with videos and need to support teachers using Windows.