diff --git a/a11y-meta-display-guide/2.0/draft/guidelines/index.html b/a11y-meta-display-guide/2.0/draft/guidelines/index.html index 4c93f293..72178da4 100644 --- a/a11y-meta-display-guide/2.0/draft/guidelines/index.html +++ b/a11y-meta-display-guide/2.0/draft/guidelines/index.html @@ -1,4 +1,6 @@ + +
@@ -30,13 +32,13 @@ "name": "Gautier Chomel", "company": "EDRLab ", "companyURL": "https://www.edrlab.org", - "w3cid": 136660 + "w3cid": 136660 }, { "name": "George Kerscher", "company": "DAISY Consortium", "companyURL": "https://daisy.org/", - "w3cid": 1460 + "w3cid": 1460 } ], processVersion: 2020, @@ -72,8 +74,8 @@ width: 100%; height: auto; } - - + + .fake-issue { padding: .5em; border: .5em; @@ -81,7 +83,7 @@ page-break-inside: avoid; margin: 1em auto; } - + .fake-issue { border-color: #e05252; border-color: var(--issue-border); @@ -92,19 +94,19 @@ counter-increment: issue; overflow: auto; } - + .fake-issue::before, .fake-issue > .marker { color: #831616; color: var(--issueheading-text); } - + .fake-issue::before, .fake-issue > .marker { text-transform: uppercase; padding-right: 1em; } - + .fake-issue a.respec-gh-label { padding: 5px; margin: 0 2px 0 2px; @@ -124,7 +126,7 @@The accessibility of a publication is useful to know regardless of a person's abilities, as features such as the ability to make visual adjustments make for a better reading experience for everybody. These guidelines - document proposes a shared framework for presenting publication accessibility metadata declarations in a + document a shared framework for presenting publication accessibility metadata declarations in a user-friendly manner — to offer the information to end users in a way that is easy to understand regardless of their technical knowledge and is consistent across different publications and different digital catalogs.
@@ -134,53 +136,51 @@Reading a digital publication is a very personal experience. For most people this is routine, and little - consideration is given to how the title was obtained before it is read. Users may go to a bookstore, + consideration is given to how the title was obtained before it is read. Users may go to a bookstore or library, search for the title to purchase online, or have the title selected for them by an instructor for a class.
Now consider that the person is blind and relies on assistive technology. The user needs that technology to assist them in the purchase process as well as to read the e-book. The person may wonder: will the screen reader work with this title; are there image descriptions that will be spoken to describe - these images; are there page numbers which are accessible; is the reading order correct so a caution - after reading a paragraph which could be dangerous will be announced? All of these, and more - accessibility concerns are potential issues consumers have when trying to purchase and ultimately read a + these images; are there page numbers which are accessible; is the reading order correct so a caution will be announced before reading the paragraph which could be dangerous? All of these accessibility concerns are potential issues consumers have when trying to purchase and ultimately read a digital publication in any format.
The good news is more and more publishers are creating digital publications that are Born Accessible (i.e., accessible from the outset, not fixed later) and getting the accessibility validation or audit done by independent organizations.
- +There are several terms used in these guidelines that should be defined for clarity:
- +The term digital publication is used in this document to refer to publications produced in any number of digital formats. Digital publications are not limited to books, but encompass any written, visual, or audio work distributed and read in digital form.
Some examples of digital publications include ebooks, audiobooks, manga, comic books, journals, digital textbooks, picture books, and children's picture books with accompanying audio. The formats they come in include EPUB, PDF, and Digital Talking Books (DTB).
The term dynamic braille is used to denote content that is generated as braille on the fly, as opposed to preformatted digital braille formats. This dynamic rendering of content is sometimes referred to as electronic braille or refreshable braille.
- +Dynamic braille is typically rendered on a separate device from the reading system, one with pop-up pins to present the braille on a tactile screen. These devices, commonly referred to as refreshable braille displays, can be attached to a personal computer, or they may be a self-contained multipurpose note taker with a refreshable braille display.
The term read aloud speech is used to denote content that is generated into synthetic speech on the fly, as opposed to prerecorded narration. Read aloud functionality is often a feature of reading systems, but can be provided by a separate assistive technology.
All digital publications require a reading system to present the publication to the end user. Reading Systems may be Apps that run on a smart phone or tablet. There are Reading Systems which are applications that run on personal computers. There are also Reading Systems that are integrated in to dedicated devices devoted to a single purpose, for presenting a publication. There are even skills that run on smart speakers that can be considered Reading Systems.
@@ -194,7 +194,7 @@These guidelines help those who wish to render accessibility metadata directly to users understand how to represent the accessibility claims inherent in machine-readable accessibility metadata in a user-friendly User Interface / User Experience (UI/UX). This document targets implementers such as - bookstores, retailers, distributors etc. Content creators will benefit from reading these guidelines and + bookstores, libraries, retailers, distributors etc. Content creators will benefit from reading these guidelines and are encouraged to follow EPUB Accessibility 1.1 Conformance and Discoverability Requirements section and its techniques.
@@ -206,12 +206,10 @@Metadata found either inside a digital publication or in a corresponding external record may have - important accessibility claims that helps end users find and determine if the publication can meet their + important accessibility claims that help end users find and determine if the publication can meet their specific accessibility needs.
-All accessibility metadata is meant to be machine-readable – except for the accessibility summary - in - this way accessibility metadata can be extracted and displayed uniformly across different publications - and localized to different user interface languages.
+This accessibility metadata uses controlled vocabularies to allow it to be extracted and displayed uniformly across different publications and localized to different user interface languages. The one exception is the accessibility summary, which allows accessibility statements that are unique to a publication and that adds information not covered by other metadata entries.
One important aspect is that the role of the Accessibility Summary metadata has changed in the latest
version of the EPUB Accessibility specification, so a more in-depth analysis in the General overview
This document offers guidance on how to aggregate and display claims inherent in metadata to end users;
these are not strict guidelines, but suggestions for providing a consistent experience for users through
different portals. Different implementers may choose to implement these guidelines in a slightly
- different way, some examples can be seen in the Implementations section
+ different way. Some examples can be seen in the Implementations section
of the document.Metadata processing overview
external metadata record formats (ONIX and MARC) that accompany a digital publication as it moves
through the supply chain.
In some cases, digital publication may include both internal and external metadata (e.g., an EPUB +
In some cases, a digital publication may include both internal and external metadata (e.g., an EPUB could have accessibility metadata in it package document and also be provided to a vendor with an ONIX record). In these cases, vendors and reading system developers determine for themselves which set of metadata they will use to display to users.
This guide assumes the metadata is already in one of the formats described in the diagram, but - depending on how the metadata is submitted it may need to be transformed (e.g. , if a vendor - prefers to handle only ONIX metadata for display they would need to preprocess the metadata - embedded in an EPUB or PDF file).
+ depending on how the metadata is submitted it may need to be transformed. For example, if a vendor + prefers to handle only ONIX metadata for display Then they would need to preprocess the metadata embedded in an EPUB or PDF to create the ONIX.The process of transforming metadata is not it scope for this document nor is how to reconcile
metadata when it is provided in multiple forms. The guide assumes any processing has already
occurred. For information on mapping between formats, refer to the Why this information is important for accessibility
Key accessibility information
-
+
Introduction to key accessibility information
@@ -372,7 +369,7 @@ Introduction to key accessibility information
to them. When images have text descriptions (alt text), they are assured that they will be not
missing out on essential information. Blind users will greatly benefit from this information as
well as individuals who use the read aloud feature in Reading Systems.
- Examples
Foo's Accessibility Testing
The certifier's credential is"Enterprise Accessibility Rating."
- +Detailed conformance information
This publication reports (Publisher's in-house specification.)
The publication was certified @@ -1110,7 +1107,7 @@