- From: James Craig <jcraig@apple.com>
- Date: Thu, 4 Dec 2014 11:45:49 -0800
- To: Florian Rivoal <florian@rivoal.net>
- Cc: Daniel Weck <daniel.weck@gmail.com>, fantasai <fantasai.lists@inkedblade.net>, Alan Stearns <stearns@adobe.com>, www-style list <www-style@w3.org>, "Tab Atkins Jr." <jackalmage@gmail.com>, fantasai <fantasai@inkedblade.net>
> On Dec 4, 2014, at 1:23 AM, Florian Rivoal <florian@rivoal.net> wrote: > > >> On 04 Dec 2014, at 03:45, James Craig <jcraig@apple.com> wrote: >> >> On Dec 3, 2014, at 6:20 AM, Florian Rivoal <florian@rivoal.net> wrote: >>> >>> What would you think (naming aside) about a media feature like this: >>> speech: none | linear | screen-based >> >> Linear seems like a logical match for the existing media type, but it's still not mutually exclusive. For example, iOS includes a "Speak Screen" feature that effectively linearizes an iBooks EPUB (including turning the pages), but you can pause the output or change the speech speed. >> Perhaps: >> >> speech: none | linear | screen | linear-screen; >> >> "@media (speech: screen)" could match screen readers, zoom utils with speech, and linear-screen would match something more like the "Speak Screen" or "Speak Selected Text" features. Seems like this might not match a screen reader where speech was off temporarily or permanently (e.g. a deaf-blind user with a refreshable Braille display) > > Not sure I completely follow you. Do you mean that linear-screen is kind of like linear, except with pauses after each screen/page, as some sort of audio pagination? Could you explain a bit more the differences between the modes? linear -> "export to audiobook" (like print, except to an audio format) linear-screen -> "'read all' in a screen-based ebook reader" (like "Speak Screen" in iBooks) screen -> "interactive navigation of the screen" (like using VoiceOver to explore around the screen in a browser)
Received on Thursday, 4 December 2014 19:46:18 UTC