Re: accessible epub

Well actually I might be wrong thinking about it, as I've never used any
screenreader or anything with an epub, perhaps I am just migrating my
experiences from how things work in browsers to how they work with epub -
do most people use some sort of screenreader for reading epub or do they
convert?

Also perhaps inaccessible is too strong a word, perhaps the phrase should
instead be probably accessibly annoying or something because , just looking
through what was generated, My feeling was:

1. Generated lot of empty paragraphs for spacing, some people may get
'blank' announcements, want to avoid that. However I could probably fix
that relatively easily if epub accepts aria-hidden, because I could just
search replace > </ and put an aria-hidden in.

2. images and design elements that have an aesthetic purpose but no
informational purpose would be announced. There's not a lot of those so I
guess I could fix those tonight.

3. things that are for design reasons should either be dropped or put
together in some way that makes sense, for example some parts are put
together like a deck of cards, with numbers in a suit, like the 3 of spades
etc. The markup that is generated for this is generally something like
<span>3</span><span>unicode character for spade</span>

4.  when I used drop caps and looked at the markup it is
<span>M</span><span>ore</span> which I assume might end up read as M  ore
depending on how you were running the reader, maybe that is however because
I am used to using it for testing and in real world usage you would be able
to read without that problem?

So - when you convert an epub do problems like this go away?

Thanks,
Bryan Rasmussen

On Sat, Jul 9, 2022 at 1:32 AM Karen Lewellen <klewellen@shellworld.net>
wrote:

> May I ask what it is about the pages created epub that is not accessible?
> Personally I use the epub convert option via robobraille.
> www.robobraille.org
> converting epubs into my preferred format..
> which is part of why I am asking what makes your file not accessible, for
> whom exactly?
> Best,
> karen
>
>
>
> On Fri, 8 Jul 2022, kerscher@montana.com wrote:
>
> > Hi,
> >
> >
> >
> > Any chance you could use the WordToEPUB tool? Daisy.org/wordtoepub
> >
> >
> >
> > It does a great job and the HTML is clean.
> >
> >
> >
> > Best
> >
> > George
> >
> >
> >
> >
> >
> > From: bryan rasmussen <rasmussen.bryan@gmail.com>
> > Sent: Friday, July 8, 2022 3:00 PM
> > To: WAI IG <w3c-wai-ig@w3.org>
> > Subject: accessible epub
> >
> >
> >
> > So, I have a book I was writing and I used Pages to format it. Then I
> generated the Epub naively expecting Pages would do a reasonable job of
> making the epub accessible. But it didn't, and I do not have the extra time
> to fix it (it's a side project, I really do not have the month that it
> would take to fix the awful XHTML that Pages generates, in fact whenever I
> look at the markup I think it would be easier to rewrite it all by hand, or
> even create my own framework)
> >
> >
> >
> > It would be easier for me to provide a screen reader only version of the
> document, that is to say unformatted since it is the formatting that mainly
> has created the problems. Does anyone have any suggestions for this -
> especially regarding platform discoverability - can it just be that I
> specify in metadata for one that it is an accessible version and the other
> one that it is not accessible?
> >
> >
> >
> > Thanks,
> >
> > Bryan Rasmussen
> >
> >
>