(WCAG),
3
however, provide useful descriptions of what
makes an e-book or e-reader device or app accessible. In
his excellent chapter on e-book accessibility in No Shelf
Required 2, Ken Petri summarizes both:
Meeting Section 508’s Functional Performance
Criteria demands that a user-facing hardware
or software component have at least one mode
of operation and information retrieval that does
not require vision; that accommodates low visual
acuity; that does not require hearing and/or can
amplify produced sound to compensate for poor
hearing; that does not require fine motor control or simultaneous actions; and that is operable
with limited reach and strength. WCAG 2.0 is
organized around four broad principles:
1. Perceivable: that “information and user interface components must be presentable to users
in ways they can perceive.”
2. Operable: that “user interface components
and navigation must be operable.”
3. Understandable: that “information and
the operation of user interface must be
understandable.”
4. Robust: that “content must be robust enough
that it can be interpreted reliably by a wide
variety of user agents, including assistive
technologies (W3C 2010A).”
4
The rapid rise of e-reading makes it crucial for
librarians and library staff to become familiar with
the complex e-text accessibility landscape and learn
to understand and recognize these features in order to
support their disabled patrons with accessible collections, services, and peripherals. With the goal of facilitating accessible e-reading experiences, this chapter
provides an overview of the accessibility landscape of
major e-book publishing formats as well as e-reader
devices, apps, and software platforms.
E-book Formats
E-books are created in openand proprietary file formats. Open e-books formats such as DAISY and EPUB
are designed to be “device-independent”—in other
words, to be compatible with any e-reader that supports open formats. Proprietary format e-books such as
MOBI (Mobipocket), AZW (Amazon Kindle), and PDF
are usually originally based on an open format, but
then configured to be read by a specific e-reader and
not by other e-readers largely as a competitive marketing strategy. In general, open format e-texts are far
more accessible than proprietary formats.
Proprietary format e-books present several common accessibility problems. In order to facilitate the
(WCAG),
3
however, provide useful descriptions of what
makes an e-book or e-reader device or app accessible. In
his excellent chapter on e-book accessibility in No Shelf
Required 2, Ken Petri summarizes both:
Meeting Section 508’s Functional Performance
Criteria demands that a user-facing hardware
or software component have at least one mode
of operation and information retrieval that does
not require vision; that accommodates low visual
acuity; that does not require hearing and/or can
amplify produced sound to compensate for poor
hearing; that does not require fine motor control or simultaneous actions; and that is operable
with limited reach and strength. WCAG 2.0 is
organized around four broad principles:
1. Perceivable: that “information and user interface components must be presentable to users
in ways they can perceive.”
2. Operable: that “user interface components
and navigation must be operable.”
3. Understandable: that “information and
the operation of user interface must be
understandable.”
4. Robust: that “content must be robust enough
that it can be interpreted reliably by a wide
variety of user agents, including assistive
technologies (W3C 2010A).”
4
The rapid rise of e-reading makes it crucial for
librarians and library staff to become familiar with
the complex e-text accessibility landscape and learn
to understand and recognize these features in order to
support their disabled patrons with accessible collections, services, and peripherals. With the goal of facilitating accessible e-reading experiences, this chapter
provides an overview of the accessibility landscape of
major e-book publishing formats as well as e-reader
devices, apps, and software platforms.
E-book Formats
E-books are created in openand proprietary file formats. Open e-books formats such as DAISY and EPUB
are designed to be “device-independent”—in other
words, to be compatible with any e-reader that supports open formats. Proprietary format e-books such as
MOBI (Mobipocket), AZW (Amazon Kindle), and PDF
are usually originally based on an open format, but
then configured to be read by a specific e-reader and
not by other e-readers largely as a competitive marketing strategy. In general, open format e-texts are far
more accessible than proprietary formats.
Proprietary format e-books present several common accessibility problems. In order to facilitate the
การแปล กรุณารอสักครู่..
