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.

Come and join us!

Paper cut-outs of people in a circle

Are you interested in improving your BCE CRM (Business and Community Engagement Customer Relationship Management) processes to help increase revenue streams? Do you want to find out about SLRM (Student Lifecycle Relationship Management) and putting the student at the heart of the process?

If so, come and join our RM in HE/FE Community of Practice discussion list, which is open to anyone who wants like to share their experiences of improving their relationship management in the tertiary education sector. We’d love you to ask questions, comment, suggest resources etc, or just follow the conversation.

We’ll be sharing our findings from the current JISC Relationship Management Programme, which is looking at three different areas:

  • Good Practice in CRM – delivering a comprehensive online handbook of good practice in CRM processes for HE and FE.
  • Student progression, retention and non-completion – using service desing to improve the quality of the student experience.
  • Alumni engagement – using web technologies to support mutally beneficial alumni engagement.

We have a range of resources available at both the JISC CETIS RMSAS (Relationship Management Support, Analysis and Synthesis) project website and at the Just Enough RM (Relationship Management (a dynamic resource to try and help anyone starting out on the RM path). We also have documents on using Service Design in HE and FE and an overview to RM in HE and FE to get you started.

So what are you waiting for? Come and join the RM in HE and FE Community – we’d love to see you there!

Relationship Management in UK HE and FE Report Now Available

Photo of a handshake

Relationship management is becoming increasingly important in the tertiary education sector as education institutions try to meet the challenges of funding cuts and increased student and community expectations. Customer relationships, if handled effectively, will bring benefits to both the organisation and the sector as a whole and it is in this area that JISC developed the Relationship Management Programme.

The first phase of the JISC Relationship Management Programme ran from July 2009 to April 2010. The Programme, supported by the JISC CETIS RMSAS (Relationship Management Support, Analysis and Synthesis) project, was divided into two strands and was :

  • BCE CRM (Business and Community Engagement Customer Relationship Management) Strand – aimed to improve business processes and to pilot and extend the BCE CRM SAF (Self-Analysis Framework). Twelve universities and one FE college used the SAF to examine factors affecting the people and processes that could affect the implementation or uptake of CRM (both as an approach and as a technology). BCE CRM includes employers and other external customers, who may have the potential to help the sector navigate through the current choppy waters of tertiary education sector funding. Good customer relationship management is vital in order to maintain and develop such relationships.
  • SLRM (Student Lifecycle Relationship Management) – focussed on improving the student experience by putting the student at the heart of the process. Six universities and one FE college trialled service design techniques at different stages of the student lifecycle in order to identify areas for improvement. As students clearly exhibit certain customer attributes, such as paying for a service and expecting higher levels of choice, quality and experience, it therefore seems appropriate to apply such commercial techniques, in order to improve the student experience, the institution’s efficiency and retention.

Whilst the two strands can be viewed as focusing on two different types of institutional stakeholder – external business contacts in the case of the BCE CRM strand and students in the SLRM strand – many of the issues regarding the way in which the relationship is managed by the institution are similar. For example:

  • BCE CRM
    • Ensure that an effective CRM strategy is in place, and that is disseminated to and understood by staff.
    • Use a framework to help your institution ask fundamental questions about the people, processes and systems currently in place, prior to making any decisions regarding improvements or attempting to purchase or implement a technical CRM system, because this will go a long way to help avoid potential pitfalls and dangerous assumptions.
    • Strong commitment from senior management is vital if CRM is to succeed.
  • SLRM
    • The institution should not assume that it knows what students want, need and expect.
    • Service improvements do not have to cover the whole service, e.g. enrolment, in one go – small adjustments can be made that can actually make a huge difference to the student experience.
    • Improving the effectiveness of a process can also improve efficiencies.

The current funding situation means that institutions need to become more cost-effective. Therefore, making the most of the systems already in place, improving processes, and ensuring that the student or BCE customer has a valuable experience may help achieve this goal.

This findings from this Programme are now available in PDF format: Relationship Management in UK Higher and Further Education – An Overview (Perry, S., Corley, L., and Hollins, P 2011). Phase 2 of the JISC Relationship Management Programme is now in full swing.