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!

10 thoughts on “Accessibility in iBooks 2 and iBooks

  1. Hi Luis,

    Great post. Thanks for sharing. I have a question I’m hoping you can answer.

    I made an iBook using iBooks Author, but can’t get the speak selection to work in it on my iPad. Any suggestions? Is there a publishing feature in iBooks Author that I am missing?

    Sue Hardin

    1. Have you turned on the feature in the accessibility settings? Speak selection has to be turned on in the settings before it can be used. You should then be able to select text in iBooks and hear it read aloud with the VoiceOver voice.

    1. iBooks is a fixed layout format. The text size is determined by the author when the book is created with iBooks Author on the Mac. You can’t resize the text like you can with ePub on the iPad, but you can still use the Zoom accessibility feature if you need the text to be larger.

  2. Hi Luis,

    Thanks for this useful post – a great addition to my IBA research. I just added you to my IBA research file at:

    I’m working on a free iBook text for students to explore that American Homefront during WWII. I’d like to include videos – there’s some great copyright free US gov’t films from the era found on Such at “It’s Murder”

    To make my iBook useable to the widest audience of students, I want be mindful of accessibility. And with lots of media, I need to think about final file size of the iBook.

    I’ve played around with some of the US gov’t films on I tried converting them from mp4 to m4v files using Handbrake. That worked, but then I needed to run them through QT to make them acceptable to IBA. That bloated their file size.

    I’ve been thinking of investing in Compressor. (though it seems like a product designed for FInal Cut Pro – which is far more horsepower than I need)

    Now I see your strategy here for using MovieCaptioner to create the caption and use Compressor to “combine” caption and video.

    So after all that intro, two questions:

    1. Before I plunk down $50 for Compressor and $100 for MovieCaptioner … can I use them both to create captioned videos acceptable to IBA with compressed file sizes that will allow me to put more videos in my iBook?

    2. If the answer is yes, can you offer a few tips on settings and work flow, so I don’t have to struggle through it. (I’m a curriculum design guy who doesn’t go too far “under the hood” with technology. I just try to figure out how to get it to do what I want).


    1. Hi Peter,

      Compressor is what Apple recommends for building the closed captioned files for iBA. I have not been able to figure out why it causes the file sizes to explode though. I used to be able to export a QT movie right out of MovieCaptioner with the SCC captions embedded, but the files created by MovieCaptioner in this way will not import into IBA. I will keep you posted as I continue to play around with this.

      One way around the file size issue is to include the videos using the YouTube widget from Class Widgets. You would upload the videos to YouTube and then use the free YouTube widget from Class Widgets to embed them in IBA. Problem is that even though YouTube supports captions, there is no way to turn them on with the mobile version. Also, because the videos would be streaming, they would only work when there is an active Internet connection.

      Another thing you can do is find some place to upload a closed captioned video file exported directly from MovieCaptioner (which should retain its small size) and link to it within your IBA book so that it opens with the mobile Safari web browser. That will play the captions as long as they are turned on in the Settings (Video > Turn on Captions). Not an elegant solution, as the whole point is to have content embedded online, but it does work.

      I’ll keep you posted when I find a good solution.

  3. Thanks Luis,

    Just so I’m clear. You say “Compressor is what Apple recommends for building the closed captioned files for iBA. I have not been able to figure out why it causes the file sizes to explode though”

    I thought Compressor was supposed to make files smaller- and acceptable to IBA. Is that true?

    Or is it only when you use Compressor to add closed captions, that the file sizes explode.?


    I agree with you about YouTube – I thought of that option, but I also fear it’s too often blocked by school filters.


    Option 3 is interesting. Do you mean the un-captioned video would be in the iBook and 2nd captioned version would be online somewhere else?

    …. If yes, that brings me back to my first question above about using Compressor for shrinking file size in IBA friendly way.

    1. Hi Peter,

      Yes, compressor is supposed to make the files smaller and I’ve had great luck with it for that purpose in the past. I think the issue is that my editing program (I use Screenflow to create my tutorials) is exporting the files in a way that they have to be converted in some way by Compressor to make them acceptable to IBA. I don’t think it has anything to do with the captions, but rather with the file format. Screenflow exports as MP4 for the iPad preset, but as you know MP4 is a wrapper and supports many types of encoding (from what I know, I’m no video expert).

      I decided to try this with a short clip exported from iMovie at 1280 X 720, H.264, AAC audio and then used Compressor to export with the iPad preset (H264, AAC audio, same dimensions). The file size went up just slighting each time (with and without captions). This leads me to believe that the closer you can get the file format to match the requirements for IBA when you export out of your video program the easier it will go. I’m going to do some more reading about this this week and will keep you posted on what I find.

      I love MovieCaptioner by the way. I have not found an easier way to do captions.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s