International Digital Publishing Forum - EPUB Accessibility

Guidelines and FAQ

bill — Sun, 15 Jan 2012 15:46:20 +0000

Forums:

This "EPUB Accessibility" forum is intended for questions and discussion relating to EPUB accessibility. Questions and discussion related to making EPUB content available to individuals with visual impairment or other disabilities that impact their reading experience should be posted here. IDPF and DAISY Consortium staff will monitor this forum. General topics related to IDPF/EPUB or EPUB 3 should be posted in those forums.

Thanks!

Bill McCoy
Executive Director, IDPF

front-, body-, backmatter proper usage

Welblaud — Thu, 18 Oct 2018 08:07:24 +0000

Forums:

EPUB Accessibility

I am used to marking every part of the book with two attributes: 1) overall position in the book (e.g., "frontmatter") and 2) more specific type of the text (e.g., "chapter") in the child element.

Typically:
<body epub:type="bodymatter">
<section epub:type="chapter">

Here (https://idpf.github.io/epub-guides/epub-aria-authoring/) it is written the modifications of the body element with semantics 1) collide with the ARIA model, 2) is now discouraged even for the epub:type attributes.

It was always unclear how to use the general sectioning of the book if the book is chunked into several files. For ARIA, it is recommended to use the semantics just for the very first file in the range. With epub:type semantics it was often recommended to use the attribute (e. g., "backmatter") repeatedly for all the docs related to the backmatter. The first attitude is more logical for the reader and a book’s progress, whereas the latter attitude is (I guess) more logical for automatic parsing.

Is the trio front/body/backmatter slowly becoming obsolete? Or is it sufficient to just use it for the landmarks?

I would be very grateful if anyone cleared this a bit.

INTERNAL ERROR 4096

naonysan — Tue, 28 Feb 2017 06:28:55 +0000

Forums:

EPUB Accessibility

Hello team,

Only posting this because I couldn't find anything on google.

I get error message:

Results: The following problems were found in Ebook_Name.epub:

INTERNAL ERROR 4096

I don't have a clue what this means and how to fix it. Any ideas? thanks!

Curl Animation

nagarjuna — Wed, 21 Dec 2016 06:05:37 +0000

Forums:

EPUB Accessibility

Hi,

Can anyone tell me How to do a Curl Animation of a Book.

Thanks,

Diff. in packaging OPS Vs OEBPS

shyamusingh — Tue, 06 Dec 2016 10:58:36 +0000

Forums:

EPUB Accessibility

Hi,

Is there any difference between OPS Vs OEBPS when we create ePub2.0.1?

Suggest please.

01 - LABEL usage for common term in a product

afzalr81 — Wed, 30 Nov 2016 12:56:41 +0000

Forums:

EPUB Accessibility

Hi everyone, I feel very elevated to start a forum and would need your support to resolve my query:

Book Instance:

SOLUTION
STEP 1 The international ....
STEP 2 The national ....
STEP 3 The international ....

Semantic Mark-up:

<section id="steplist1" class="procedure">
<header>
<h4 class="title" epub:type="title">
<span epub:type="label">SOLUTION</span>
</h4>
</header>
<ol class="steplist">
<li class="step">STEP 1 The population ...</li>
<li class="step">STEP 2 The sample ....</li>
<li class="step">STEP 3 The variable ....</li>
</ol>
</section>

I would like to know if the above mark-up is fine.

mail me with your suggestion or clarification at: afzal@codemantra.co.in

Page number located near in all the heading levels in contents page

sureshkaasi — Fri, 04 Nov 2016 07:00:24 +0000

Forums:

EPUB Accessibility

Hi Team,

I have one doubt. Normally we won't capture the page number appearing near headings levels in contents page. I think in Accessibility ePub too, no need to capture the page. Am i correct or wrong?

Please answer this question

Suresh

Error while parsing file 'element "strike" not allowed anywhere

siamdave — Sun, 17 Jul 2016 07:48:19 +0000

Forums:

EPUB Accessibility

the error message:
Error while parsing file 'element "strike" not allowed anywhere; expected the element end-tag, text or element "a", "abbr", "acronym", "applet", "b", "bdo", "big", "br", "cite", "code", "del", "dfn", "em", "i", "iframe", "img", "ins", "kbd", "map", "noscript", "ns:svg", "object", "q", "samp", "script", "small", "span", "strong", "sub", "sup", "tt" or "var" (with xmlns:ns="http://www.w3.org/2000/svg")'.

the offending bit:
ERROR OEBPS/Text/pts-004.xhtml 25 55

As a non-expert, but using Sigil to create epubs, I cannot find for sure where this line is - in the (automatically generated) toc-ncx file, line 25 is '<content src="Text/pts-acknow.xhtml" />'

In the (again auto-generated) content-opf file, line 25 is ' <item href="Text/pts-007.xhtml" id="pts-007.xhtml" media-type="application/xhtml+xml" />'

In my own TOC file, line 25 is '<a href="../Text/pts-010.xhtml">10. EEE 8</a><br />'

- there seem to be a lot of lines using the 'offending' pattern that are exactly the same except for beein 003 or 005 etc - I do HTML coding for my website so while not an expert am not a complete know-nothing either,and I cannot find anything that looks like it needs correcting, or that has set the 'error finder' off.

Any ideas would be appreciated
Thanks

E-Reader Devices Statistics

vnazar — Wed, 06 Jul 2016 21:32:45 +0000

Forums:

EPUB Accessibility

Hello,

Does anyone know where can I get information about E-Book Device Statistics? Specifically I'm looking for the data that would show top 5 devices that are most popular in reading ebooks and how they compare with other less popular devices? For example, let's say, what's the (%) of online readers use Kindle Paperwhire, Kindle Fire, Nook, iPad and so on....?

Thanks,

ePub3 Accessibility query

Nandagopal — Thu, 09 Jun 2016 06:57:26 +0000

Forums:

EPUB Accessibility

1. We have used the following page number content element “<span epub:type="pagebreak" id="page14">14</span>” in our accessible epub3 file and screen readers (JAWS/Voiceover/Natural reader) just read only the number. Which content elements should be used to read the Page number link for example “Page 14”?

2. We have used the “aria-describedby” attribute to hide the description but the hidden elements are not read by the screen readers (JAWS/Voiceover/Natural reader). Please see the below example and advice.

<figure><img src="../images/f0014-01.jpg" aria-describedby="ch01altext12" alt="This graph shows the declining number."/>
<figcaption>Figure 1-1 The impact of deinstitutionalization.
<aside id="ch01altext12" class="hidden">
<p>Year 1950</p>
<p>Inpatients in Public Mental Hospitals ...</p>
</aside>
</figcaption>
</figure>

Any advise on this will be very helpful, Thanks in advance.