Everyone’s talking about accessibility these days and it can be daunting if you don’t know where to start. Let this workshop be your starting place.
Non-technical? No problem. This workshop is for everyone who wants to learn how to make accessible, ready-for-the-market ebooks, regardless of their department or previous experience with ebooks. Join us to get a plain language explainer of all the pieces of the ebook accessibility puzzle.
Link to workshop video: https://youtu.be/UIp7dq1eH58
Presented by BookNet Canada on June 16, 2022 with support from the Department of Canadian Heritage.
3. Accessible HTML
“When ebooks contain only generalized structures, reading
systems are limited to presenting only the basic visual form of the
book. Dumb data makes for dumb reading experiences, as reading
systems cannot play the necessary role of facilitator when given
little-to-nothing to work with. And that’s why not everyone can read
all digital content.
—from Matt Garrish’s Accessible EPUB 3 (O’Reilly)
8. Emphasis
I am glad you weren't late.
I am glad you weren't late.
This liquid is highly toxic.
I am counting on you. Do not be late!
9. Language
tags
Belong in three places: the OPF,
the root HTML element in every
HTML files, and marking language
shifts
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:epub="http://www.idpf.org/2007/ops" lang="en-US" xml:lang="en-US">
<head>
<title>Chapter 1</title>
<link href="css/idGeneratedStyles.css" rel="stylesheet" type="text/css"/>
</head>
10. Breakout Room Task
Format a basic chunk of text in validated HTML using Sigil. Using the supplied Peter
Pan ebook, add a third chapter in the shell HTML file. Watch for:
• Emphasis vs italics
• Headers and text
• A short list formatted as a list
• Editorial breaks marked accurately
• HTML 5 employed correctly
• Language shifts marked
• Add the chapter 3 HMTL file to the OPF
14. PRINCIPLES OF
EBOOK
ACCESSIBILITY
• Separate style and content
• Navigation
• Structure
• Semantics
• Images = picture, not tables or text
• Image Descriptions
• Page List
• Define Languages
• Accessible treatment of Math and
interactive content
• Accessibility metadata
15. Separation of Style and Content
“Style is just a layer between your markup and the
device that renders it, not an intrinsic quality you can rely
on to say anything about your content.”—Matt Garrish
18. Breakout Room Task
Use EPUB-Checker and ACE by Daisy to go through your own
errors with the TA, or test the Module 2 provided EPUB which has
been booby trapped with errors.
21. Accessibility
Summary
• Use plain language.
• Avoid jargon.
• Write out acronyms before using the
abbreviation, e.g. Web Content
Accessibility Guidelines (WCAG).
• Include all accessibility features.
AccessibilitySummary may be the only
piece of metadata that some users read.
• If you decide to use a template, make
sure the AccessibilitySummary is
customized for every book.
26. Example
<meta property=”schema:accessibilitySummary”>This Publication meets the
requirements of the EPUB Accessibility specification with conformance to WCAG 2.0 Level AA.
The content is screen-reader friendly. Images are described, long descriptions have been
included for complex images, a table of contents is present, and sections are introduced with
correctly-cascading headings. There are short audio clips of music at the start of each chapter
which readers can choose to play – they will not auto-play.</meta>
<meta property=”schema:accessMode”>textual</meta>
<meta property=”schema:accessMode”>visual</meta>
<meta property=”schema:accessModeSufficient”>textual,visual</meta>
<meta property=”schema:accessModeSufficient”>textual</meta>
<meta property=”schema:accessibilityFeature”>alternativeText</meta>
<meta property=”schema:accessibilityFeature”>longDescription</meta>
<meta property=”schema:accessibilityFeature”>structuralNavigation</meta>
<meta property=”schema:accessibilityFeature”>tableOfContents</meta>
<meta property=”schema:accessibilityFeature”>alternativeText</meta>
<meta property=”schema:accessibilityHazard”>noFlashingHazard</meta>
<meta property=”schema:accessibilityHazard”>noMotionSimulationHazard</meta>
<meta property=”schema:accessibilityHazard”>sound</meta>
29. Breakout Room Task
Write schema.org metadata for the Module 3-supplied ebook.
• Look through the ebook to see what it does and what it doesn’t.
• Use the supplied PDF of what’s required and what’s optional.
• Work as a group to work up a full set of values.
• Write an accessibility summary.
• If time allows, look at Codelist 196 and list out what values you would
include.