Reading a publication is a very personal experience. For most - of us this is routine, and give little - consideration to how we obtained the title before we read - it. We may go to a bookstore, search - for the title to purchase online, or have the title selected - for us by an instructor for a class.
- -Now consider you are blind and rely on an assistive - technology. You need that technology to assist you - in the purchase process as well as to read the publication. - You may wonder: will my 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 I don't hear a caution - after reading a paragraph which could be dangerous? All of - these, and more accessibility concerns are - potential issues consumers have when trying to purchase and - ultimately read a digital publication.
- -The good news is more and more publishers are creating - 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.
- -This document proposes a shared framework for presenting - publication accessibility metadata in a - user-friendly manner, so as to offer the information to end - users in a way that is easy for them to understand (even for - the less technical) and consistent across different - publications and different digital catalogs.
-This document helps those who wish to render accessibility - metadata directly to users understand how to - represent machine-readable accessibility metadata in a - user-friendly User Interface / User Experience - (UI/UX).
- -This document presents high-level principles without - going into technical issues related to the - different metadata standards in the publishing industry. -
-Therefore, techniques are - available that illustrate to developers how to - retrieve data to show the information outlined in this - document.
-Metadata found either inside a digital publication or in a - corresponding external record may have - important accessibility information that helps end users - find and determine if the publication can meet - their specific accessibility needs.
- -All accessibility metadata is meant to be machine-readable – - apart from the accessibility summary - in this way - accessibility metadata can be extracted and displayed - uniformly across different publications and localized to - different user interface languages.
- -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 Accessibility summary - section is recommended.
- -This document offers guidance on how to aggregate and display - 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 a slightly different way, some - examples can be seen in the Implementations section of - the document.
- -To assist developers in implementing these guidelines, - in-depth notes are available to explain how to - extract information from publishing industry metadata - standards.
- -At the time of publishing this document the available - techniques for metadata standards are:
- -Reading a publication is a very personal experience. For most of us this is routine, and give little + consideration to how we obtained the title before we read it. We may go to a bookstore, search for the + title to purchase online, or have the title selected for us by an instructor for a class.
+ +Now consider you are blind and rely on an assistive technology. You need that technology to assist you in + the purchase process as well as to read the publication. You may wonder: will my 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 I don't hear a caution after reading a + paragraph which could be dangerous? All of these, and more accessibility concerns are potential issues + consumers have when trying to purchase and ultimately read a digital publication.
+ +The good news is more and more publishers are creating 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.
+ +This document proposes a shared framework for presenting publication accessibility metadata in a + user-friendly manner, so as to offer the information to end users in a way that is easy for them to + understand (even for the less technical) and consistent across different publications and different + digital catalogs.
- The product details provide precious information about the - usability of the book in relation to specific user needs. - The following informations should always be displayed: -
When the content creator does not provide any - accessibility metadata for a publication, the three - pieces of key information that should always be present - can still be shown (with an indication that the - information is missing): Supports - nonvisual reading, Visual adjustments - and Conformance.
-This document does not define the order in which to show - the key accessibility information; each implementer can - decide the preferred order for showing the accessibility - information that follows.
-This document helps those who wish to render accessibility metadata directly to users understand how to + represent machine-readable accessibility metadata in a user-friendly User Interface / User Experience + (UI/UX).
This key information should always be displayed, even - if there is no metadata (with the relevant wording). -
+This document presents high-level principles without going into technical issues related to the + different metadata standards in the publishing industry.
+Therefore, techniques are available that illustrate to developers how to + retrieve data to show the information outlined in this document.
Indicates whether all content required for comprehension - can be consumed in text and therefore is - fully available to assistive technologies and reading - systems using text-to-speech or electronic braille - functionality.
-The term "electronic braille" and "refreshable - braille" are used interchangeably, which denotes a - device with pop-up pins to present the braille on a - tactile screen.
-This field answers whether nonvisual reading is possible, - not possible, or unknown.
- -Digital publications with essential content included in - non-textual form (such as graphs, tables or - equations presented as images, videos, etc.) must - include textual alternatives to ensure that users - reading with other senses than sight (mainly auditory - and tactile) have access to the same - information as visual readers. These textual - alternatives can include extended descriptions, - transcripts, captions, etc. depending on the nature of - the nonvisual content.
- -The examples are provided as lists of possible - descriptive and compact explanations for - flexibility of adoption.
- - +Metadata found either inside a digital publication or in a corresponding external record may have + important accessibility information that helps end users find and determine if the publication can meet + their specific accessibility needs.
- -All accessibility metadata is meant to be machine-readable – apart from the accessibility summary - in + this way accessibility metadata can be extracted and displayed uniformly across different publications + and localized to different user interface languages.
+ +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 Accessibility summary section is recommended.
+ +This document offers guidance on how to aggregate and display 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 a slightly different way, some examples + can be seen in the Implementations section of the document.
-To assist developers in implementing these guidelines, in-depth notes are available to explain how to + extract information from publishing industry metadata standards.
+ +At the time of publishing this document the available techniques for metadata standards are:
The product details provide precious information about the usability of the book in relation to specific + user needs. The following informations should always be displayed:
-This key information can be hidden if metadata is - missing.
-Indicates the presence of pre-recorded audio and - specifies if this audio is standalone (an - audiobook), accompanies text (embedded audio and video - clips), or represents an alternative to the - text (synchronized text-audio playback).
+Audiobooks created for mainstream use provide important - access for many users with disabilities even - though they are not accessible to all. As they grow in - popularity, audiobooks may provide more - accessibility options in the future.
+George asks why is details used here?
-Some publications provide audio (including in video) in - addition to text. In this case, it is - important that the user is informed that they may not be - able to access all content in the book.
+Some publications provide pre-recorded audio with text - synchronization. - Users with hearing impairments still can access the full - content of these books.
+When the content creator does not provide any accessibility metadata for a publication, the three + pieces of key information that should always be present can still be shown (with an indication that + the information is missing): Supports nonvisual reading, + Visual adjustments and Conformance.
+The examples are provided as lists of possible - descriptive and compact explanations for - flexibility of adoption.
+This document does not define the order in which to show the key accessibility information; each + implementer can decide the preferred order for showing the accessibility information that + follows.
+This key information should always be displayed, even if there is no metadata (with the relevant + wording).
+Indicates whether all content required for comprehension can be consumed in text and therefore is + fully available to assistive technologies and reading systems using text-to-speech or electronic + braille functionality.
+The term "electronic braille" and "refreshable braille" are used interchangeably, which denotes a + device with pop-up pins to present the braille on a tactile screen.
+This field answers whether nonvisual reading is possible, not possible, or unknown.
+ +Digital publications with essential content included in non-textual form (such as graphs, tables or + equations presented as images, videos, etc.) must include textual alternatives to ensure that users + reading with other senses than sight (mainly auditory and tactile) have access to the same + information as visual readers. These textual alternatives can include extended descriptions, + transcripts, captions, etc. depending on the nature of the nonvisual content.
+ +The examples are provided as lists of possible descriptive and compact explanations for + flexibility of adoption.
+ + + + +This key information can be hidden if metadata is missing.
+Indicates the presence of pre-recorded audio and specifies if this audio is standalone (an + audiobook), accompanies text (embedded audio and video clips), or represents an alternative to the + text (synchronized text-audio playback).
-This key information should always be displayed, even - if there is no metadata (with the relevant wording). -
-Audiobooks created for mainstream use provide important access for many users with disabilities even + though they are not accessible to all. As they grow in popularity, audiobooks may provide more + accessibility options in the future.
-Indicates if users can modify the appearance of the text - and the page layout according to the - possibilities offered by the reading system.
+Some publications provide audio (including in video) in addition to text. In this case, it is + important that the user is informed that they may not be able to access all content in the book.
-This field answers whether visual adjustments are - possible, not possible, or unknown.
+Some publications provide pre-recorded audio with text synchronization. Users with hearing + impairments still can access the full content of these books.
-Readers with visual impairments or cognitive disabilities - need the ability to change the color of - text and its background (contrast), the font family and - font size used, as well as spacing between - letters, words, sentences, or paragraphs.
+Knowing - that a publication can reflow to fit the - reading system's display area is not sufficient to know - that modifications to the font, spacing, and - colors are possible or that the changes will not cause - other readability issues (e.g., text being - clipped by its container).
+The examples are provided as lists of possible descriptive and compact explanations for + flexibility of adoption.
-The examples are provided as lists of possible - descriptive and compact explanations for - flexibility of adoption.
+ +This key information should always be displayed, even if there is no metadata (with the relevant + wording).
+Indicates if users can modify the appearance of the text and the page layout according to the + possibilities offered by the reading system.
+ +This field answers whether visual adjustments are possible, not possible, or unknown.
+ +Readers with visual impairments or cognitive disabilities need the ability to change the color of + text and its background (contrast), the font family and font size used, as well as spacing between + letters, words, sentences, or paragraphs.
+ +Knowing that a publication can reflow to fit the + reading system's display area is not sufficient to know that modifications to the font, spacing, and + colors are possible or that the changes will not cause other readability issues (e.g., text being + clipped by its container).
+ +The examples are provided as lists of possible descriptive and compact explanations for + flexibility of adoption.
+ + + + +