The MOOC just got better!

I’ve just finished Stanford University’s HCI (Human-Computer Interaction) MOOC (see my previous post MOOC is not a dirty word… at least for the student). Personally, I’ve found it a very enjoyable, but challenging experience (due to my lack of skills, but isn’t that the whole point of learning?).

The course tutor rounded off the course with a short video of his reflections. For those of you who like facts and figures:

  • 29,568 students watched at least some of the video lectures
  • 20,443 students did at least one of the automatically marked multiple choice quizzes
  • 3,203 students completed at least one of the assignments
  • 765 students completed all 5 assignments
  • students came from all around the world, with at least 130 countries being represented.

As students, we’ve had ample opportunity to provide feedback to the teaching team about the Coursera platform and the course as a whole. That feedback has been acted on quickly with tweaks being made to class materials or assignments, while students are still working on them. MOOCs therefore offer an agile solution that takes the student’s needs into account.

It hasn’t just been a one-way transaction. As a student, I’ve learned a tremendous amount from both the teaching team and my peers. The teaching team has also learnt from the students, who have shared resources, reading lists, articles, etc and helped other students. Taking an online course doesn’t mean that the student is isolated. Many students have held their own meet-ups, either face-to-face or virtually. You could say, using the classic cybernetics term, that they were part of a self-organising system, building up communities to support and help each other long after the course has finished.

Just one year ago, there was no Coursera. So everything I’ve used on the course has been created over a very short period of time. But you wouldn’t know. Aside from a few bugs and minor niggles, the whole thing ran very smoothly. One thing to note is that Stanford doesn’t need to run this course. It already has a great reputation, but that hasn’t stopped the teaching team from working hard to pull together the content and make it freely available to everyone.

And now the MOOC has just got better. I’ve just had an email from Coursera to tell me that it now has a Career Service to help Coursera students find jobs. Should I wish to take part (and I may need to shortly), they will share my details with selected partner companies (likely to be US based). This could be good for me as a student, although it’s not without concerns. In the (probably very near) future, a company could cherry pick the best students from online courses, because they’ll be able to follow students with potential as they submit their coursework. They may even influence the course itself. Coursera will no doubt get its revenue from acting as a matchmaking service. However, this needs to be handled carefully. Issues could include companies bombarding students with advertising, a limited pool of companies being able to select students (but who wouldn’t be flattered to be offered a job by the likes of Google or Apple?), US only companies, companies that only support (financially?) Stanford (or other Coursera universities), etc. It’s not without its potential difficulties. However, from a student point of view, it seems like a great idea.

So did I finish the course? I certainly did and can now quite legitimately say that I have a Distinction from Stanford University!

Accessibility of e-Textbook Readers

Last night, I sat in on an EASI (Equal Access to Softtware and Information) webinar about the accessibility of e-textbook readers by Ken Petri from Ohio State University. It seems as though the device designers are really trying hard to get it right, although there’s still some way to go.

Photo of a paperback book.

After a short introduction to the legal context (Advocates for the Blind sued Arizona State University over their use of Kindle resulting in Amazon making changes to its software), Ken gave an overview of the current e-book formats on offer, which are mostly based on XML (eXtensible Meta-Language):

  • PDF (Portable Document Format) – common, but mostly inaccessible unless tagged correctly.
  • MOBI (Adobe).
  • AZW (Amazon) – ePub-like format for the Kindle, but lacks its rich structure.
  • XPS (XML Paper Specification) – designed to look like the original paper copy; only used by Blio.
  • DAISY (Digital Accessible Information System) – accessible standard for digital talking books; not much control over formatting.
  • ePub v3 – read by most readers (except Kindle); has a lot of DAISY’s accessibility features; rich formatting control, including video/audio embedding; full support for MathML (although no readers can read it just yet). It’s basically XHTML (eXtensible HyperText Markup Language) with super styling, i.e. CSS3 (Cascading StyleSheets) with SVG (Scalable Vector Graphics) and JavaScript.

He then followed this with an overview of e-book reader accessibility:

  • Kindle – has a free accessibility plug-in for PC; uses its own text-to-speech engine, so won’t work with screenreaders; not possible to copy and paste text; the finest grain of movement through the book is sentence by sentence; allows synching of different platforms so notes made using Kindle on the iPad can also be viewed on a PC. (Apparently it’s very easy to bypass the digital rights management and convert both MOBI (Adobe) and AZW (Kindle) formats to ePub and read the book on another device!)
  • iBooks 2 (Textbooks) on iPad – proprietary version of ePub v3, although authoring software, iBooks Author, is free; good for embedded graphics; can only be used on the iPad, not on the iPhone/iPod nor any other device; limited textbooks in the iBooks Store; possible to read ePub books using iBooks 2, but the fine-grained reading experience isn’t there; words highlighted as played; full typographic control (e.g. enlargeable text, high contrast, etc).
  • Blio – has incremental zoom for focussing on a small section of text and back out again.
  • ReadHear – a downloadable app for Mac or PC; uses DAISY; accessible maths equations; words highlighted as played; full typographic control (e.g. enlargeable text, high contrast, etc); rich screen reader access (for DAISY books only).
  • NookStudy – cross-referencing; synchronised highlighting for comparison purposes, where several books (or different pages of the same book) can be open at the same time; cut and paste; look-up using Wolfram Alpha.

For further information, see Ken Petri’s e-Book Reader Accessibility and Comparison Matrix (under development).

Although the presentation focussed on the accessibility of readers rather than on the content, some mention was made of authoring tools. For example, Calibre is a free, open-source tool that will convert across formats using RTF (Rich Text Format), e.g. from Word to DAISY (although it doesn’t do MathML). There is also a plugin for creating DAISY books from Word itself.

To sum up the importance of e-textbooks, Ken’s presentation included a quote from Eve Hill, Senior Counsellor to the Assistant Attorney General at the Department of Justice:

“In education, the current transition from print materials to digital materials creates and incredible opportunity for people with print disabilities to finally use the same products as their peers and to gain the same benefits as their peers who do not have disabilities.”

Of course, there are negatives, such as affordability of devices, proprietary formats, limited storage capabilities on some readers, possible short shelf-life as device OS’ (Operating Systems) move on, etc; and authors and publishers still need to be made aware that they need to make the content accessible. However, I think e-textbooks have much to offer everyone, not least the opportunity to present information in an interactive and engaging way in a format that almost everyone can access.