Part I. We will discuss how publishers, aggregators, and libraries can partner to provide a better experience for users. We will discuss the consolidated results of a number of studies and audits of eBook accessibility, limitations and options for creating accessible PDF and EPUB eBook files, the real-life impact of these limitations on users, and what skillsets we can help to develop and disseminate to help close the gap.
Part II. We will discuss the methods to assess accessibility of your eBooks, website or other electronic resources. We will look at both automated testing systems and usability testing. After this session we hope you will have an understanding of how these two approaches can be leveraged to help optimize the research experience for your users.
5. Accessibility of e-book resources is twofold
E-book Content
• Content creators need to include:
• Semantic tags for document
structure like <header>
• Alternative text for images
• Captions for figures
• Semantic markup for tables
like <figure>
• Consistent pagination
• Choose the best format: EPUB vs.
PDF
E-book platform
Websites or platforms need to:
• Retain publisher's accessibility
features
• Include meaningful structure
on webpages
• Provide options to skip to the
main content
• Develop and test with various
assistive technologies
6. EBSCO publisher content survey
Publishers creating EPUB 69%
Delivery volume from EPUB-providing publishers 87%
Publishers planning to meet WCAG 2.0 accessibility standards 49%
Lack of expertise / time
45%
Lack of knowledge
21%
Technical / system
limitations
20%
Budget restrictions
18%
7. Big 10 Academic Alliance evaluations
Most common accessibility issues across platforms
Scanned or
untagged
documents
Focus
management
problems
Keyboard
functionality
problems
Insufficient
color contrast
Missing image
descriptions /
alt text
Source data from Big 10 site
8. Jisc platform and publisher audit 2016
Assessment dimensions
Support documentation
Appearance
Navigation
Screen reader & text to
speech compatibility
Access
Images
Source data from Jisc site
10. What can we do?
Train our teams*
Perceivable P
Operable O
Understandable U
Robust R
Advocate and prioritize
Focus on EPUB
Involve our users
*More information on WebAIM's POUR principles
11. Production Workflow
• Challenges
• PDF as format more
challenging for accessibility
• Proper tagging of images
• Sending content to
aggregators, ensuring
features are included
• Author Guidelines
• Manuscript guidelines include
requirements for image captions,
tagging etc.
• Vendor Workflow
• Vendors take raw book files and
create final products, including
script writing for videos based on
written content
• Output Types
• Epub/PDF main output type
12. Epub vs PDF Comparison
Feature EPUB PDF
Integrates Web Standards – Dynamic
Linking
Y N
Reflowable Text (Optimized Display) Y N
Accessibility Standards Y Y*
Searchable Images, Formulas, Tables Y N
Support for Non-Roman Languages Y N
Adjustable Font Size, Background
Color, Text
Y N
Audio, Video, Quizzes Y N
Print-Corollary Pagination N* Y
13. 2018 Main Focus Areas
• EPub3/PDF
• Continuous improvement to get
closer to Benetech's Born Accessible
Certified
• Accessible book/journal content on
ScienceDirect
• Web Applications
• More teams integrating accessibility
testing before launch
• Enhanced reporting/scorecards
• WCAG 2.0 Level AA Compliance
• Customer – Facing Activity
• Continue to refine VPAT service package
• Streamline remediation process
• Staff Training
• Belting system rolled out to 100 staff
• Accessibility Guild – cross functional team
• Alt-Text
• Goal is alt-text in workflow as "business as
usual"
21. Automated tests can reliably
evaluate roughly 30% of
accessibility issues.
-Hiram Kuykendall, MicroAssist
Source:https://www.microassist.com/digital-accessibility/role-web-accessibility-testing-tools/
Part II : Accessibility Testing
22. What can be tested with Browser Extensions
• Presence of alt-text for images
• Presence of link text for links, redundant links
• Presence of form labels
• Presence of page title, language indicator
• Presence of landmarks
• Contrast ratios
• Proper table structure and tags
• Proper semantic structure, appropriately nested markup
Part II : Accessibility Testing
25. What can be tested with manual testing?
• Content within alt-text associated with figures and images
• Content of link text
• Tab order of content on the page
• Page structure using headings and landmarks
• Impact of resizing or magnifying the page
• Consistency of navigation and interactive elements across product
• Comprehension level of content on the page
36. Accessibility Challenges
• Multiple E-book platforms to
maintain and support
• More unusual type of content
(i.e. tableau data, animation,
video and audio)
• Lack of accessibility expertise in
open publishing platform by
developers and library staff
Accessibility testing
knowledge is important...
When adressing the
accessibility issues in the
publishing workflow as well as
encouraging authors to follow
accessibility best practice
38. Keyboard Trap :
Cannot access sub
menu items with
only a keyboard
Publishing Platform: Scalar
Part II : Accessibility Testing
Manual Testing
39. Focus lost in
Keyboard navigation:
Unable to find where
the focus is: to
activate the link or
the button
Publishing Platform: Pressbooks
Part II : Accessibility Testing
Manual Testing
40. Provide E-resources for Inclusive Learning and Research
Desirable Accessibility Knowledge
Preference to "Born
Accessible" digital content
Understanding (in)accessibility
and conveying that knowledge
to the authors
Auditor guidance for e-book,
Request accessibility
roadmap beyond VPAT
Accessibility testing methods,
tools (and guidelines)
Part II : Accessibility Testing
Feedback loop beyond bug
tracking system
with eBook publisher/developer
42. Demo: https://a11yfirst.library.illinois.edu/
• U of I library Innovation Fund Project
• Open Source WYSIWYG Editor which can be
added to an e-platform
• Accessibility is embedded in the design to
create accessible contents (Heading, Link,
Image, Style, Accessibility help content)
• Also utilizes the CKEditor Source Accessibility
Checker tool
A11yFirst Editor
Part II : Accessibility Testing
43. Decorative images do
not require alt text
(e.g., icons, borders
and corners, an image
that is part of a text
link)
Decorative Image Type
Part II : Accessibility Testing
44. Simple image require
Alt text (a short
description), less than
100 characters
Simple Image Type
Part II : Accessibility Testing
45. Complex images such as
graphs, diagrams, and
charts require both a text
alternative and a long
description
Complex Image Type
Part II : Accessibility Testing
46. Accessibility Help:
Why and How to
make accessible
images
Accessible Image Plugin
Part II : Accessibility Testing