[Tex2002ans]

Thanks for all this info everyone, this is great stuff!

Originally Posted by tomsem

Kindle is okay, but does not do the word highlighting at all, and doesn't support it in Scrolling mode. They want you to buy audiobooks and use immersion reading, which does these things (arguably it is a much better experience than TTS, but it shows what Amazon's priorities are).

No. Amazon was sued by the big publishers over completely idiotic "copyright" reasons. This is why TTS was removed from all Kindles.

In 2009, it was Text-to-Speech "infringing" on their audiobooks!

• Techdirt: "Amazon Gives In To Ridiculous Authors Guild Claim: Allows Authors To Block Text-To-Speech"
• New York Times: "Amazon Backs Off Text-to-Speech Feature in Kindle" by Brad Stone
• Ars Technica: "Amazon decides Kindle speech isn’t worth copyright fight"
• Techdirt: "Authors Guild Continues To Falsely Claim That Reading Aloud On A Kindle Violates Audio Rights"
• "Authors Guild Digs Itself In Deeper Concerning Kindle Text-To-Speech"

And in 2019, it was captions generated by Speech-to-Text "infringing" on their ebooks:

• Ars Technica: "Book publishers sue Audible to stop new speech-to-text feature"

Same exact thing is repeating again with Google's "Live Captions":

• 2011: Ars Technica: "Will copyright hamper IP closed captioning?"
• 2021: Ars Technica: "Chrome brings live-captioning to any web audio source"

But this time, it seems like those idiots will finally back off, since it's an Accessibility feature built directly into the entire OS/browser.

(And devices have gotten relatively powerful enough to auto-transcribe this stuff in real-time with a relatively high degree of accuracy.)

Originally Posted by tomsem

Kobo 'tries' to support it but it can't turn pages without going off track (I just tried it. In one case the page turned and SS just went away. In another, it turned page, started reading the middle of the next page, in a completely different voice.)

[...]

Screen Reading vs. Text-to-Speech

Screen Reading is an Accessibility feature. (TalkBack [on Android] + VoiceOver [on iOS])

It is meant to read out loud everything that's displayed on the screen:

• Buttons
• Menus
• Images
• Text
• [...]

Anything clickable/visible.

To see it in action, see the absolutely fantastic video/post from April 2022:

• Reddit.com: "This is how a blind person uses an iPhone"

Yes, most programs should definitely be supporting that better...

But Text-to-Speech is a completely different thing. It's meant to read Text on a page.

And, as a developer, TTS + Screen Reading require completely different workflows.

See:

• Developers.Android.com: "TextToSpeech"
• Android Develpers: "Adding accessibility features to apps for blind and visually-impaired users"

I'm surprised that Google Play Books acts relatively poorly in TalkBack.

Does Google Play Books not have a built-in TTS instead?

- - -

Side Note: What tends to happen is nearly all developers focus on getting the app/site to visibly work well for sighted users, while more obscure Accessibility features get shunted to the side.

There aren't enough people testing these "edge-cases", and even when they do, the people coding/implementing/testing aren't actually familiar with how features are actually used by the blind people who need it.

(See a similar problem I discussed in-depth about CSS's failed "Aural Stylesheets".)

- - -

What Programs/Apps Do Blind Readers Actually Use?

From what I can gather from:

• DAISY Consortium: "Ways People with Print Disabilities Read"
  
  • Especially 44 minutes in when she describes different devices/apps/programs for mobile/desktop.
    
  • Side Note: For even more info, see my recent posts here + and here.
    

many blind readers have been using:

• On Mobile
  
  • Voice Dream Reader
    
  • BARD
    
    • For audiobooks
  • (From what I can gather, iBooks is also very Accessible.)
    
• On Desktop
  
  • Thorium Reader
    
    • See their Github.
      
    • Note: This is made by Readium, the company that created the EPUB3 renderer that's used in most devices.
      
  • + all the actual Screen Readers, like JAWS + NVDA.
    

I don't know, I'm not an actual blind reader, but do read/write a lot about this stuff + like to keep Accessibility in mind.