Rich, Sylvia, all,
I think we have identified the key use case for extended
descriptions in HTML video playback: for blind people who can hear.
Deaf-blind would simply obtain all of the text (captions &
extended descriptions) and read them at their own speed.
All of this API discussion is predicated on the assumption that the
blind user's screen reader should read these extended descriptions,
with some programmatic means of pausing/continuing video playback
while the screen reader reads the text (at a speed unknown to the
video player).
But is this really the right answer? We are seeing more and more
TTS engines available, many in the cloud. Why not simply have the
video player optionally read the extended description, pausing the
video while it does so? This is how we do DAISY book playback - we
don't expect the screen reader to read the book, we expect the book
player to read the text. Also doing it this way makes the result
much more universally available. And it opens things up for a human
being to read the extended descriptions - again similar to DAISY.
Regards,
Peter
On 6/22/2011 6:27 AM, Richard Schwerdtfeger wrote:
Pete,
I am looking at
accessibleDocument. Should we not do more than that for a
document interface? Should we also have features to collect
and access specific objects with a specific element type -
filtering mechanisms?
Note: I am in favor of not
unnecessarily growing the API. API changes cause a lot of
churn. However, with the FCC adopting creating new laws based
on the 21st Century Communication and Video act there is a
need for infrastructure to better support the HTML 5 changes
Silvia is working on to support video and audio.
I am looking at the
notification mechanism for media MEDIA_TEXT_QUEUE_CHANGE.
Would it be better to have a callback registry for ATs similar
to what we did in Java? I am concerned about potential OS
scheduling issues caused by posting events to the message
queue.
Rich Schwerdtfeger
CTO Accessibility Software Group
 Pete Brunet ---06/06/2011
11:12:32 PM---Hi all, Please take a look at this and provide
your feedback: https://wiki.mozilla.org/Accessibility
From: Pete Brunet
<[email protected]>
To: IA2 List
<[email protected]>
Date: 06/06/2011 11:12 PM
Subject: Re: [Accessibility-ia2] next
changes to IAccessible2
Sent by: [email protected]
Hi all, Please take a look at this and
provide your feedback:
https://wiki.mozilla.org/Accessibility/IA2_1.3
Thanks, Pete
--
Pete Brunet
a11ysoft - Accessibility Architecture and Development
(512) 238-6967 (work), (512) 689-4155 (cell)
Skype: pete.brunet
IM: ptbrunet (AOL, Google), [email protected] (MSN)
http://www.a11ysoft.com/about/
Ionosphere: WS4G
On 3/11/2011 11:10 PM, Alexander Surkov wrote:
Hi, Jamie. I missed Mick suggestion
on the list. It's sounds reasonable and I agree we should try
it before getting new API for this since the issue is mostly
about events.
Thank you.
Alex.
On Sat, Mar 12, 2011 at 11:43 AM,
James Teh <[email protected]> wrote:
Hi.
Nice work; good to get the discussion going. :)
I still don't see a need for this registry API. Why not just
use IsWinEventHookInstalled(), as Mick suggested on the IA2
list?
Thanks.
Jamie
On 12/03/2011 3:48 AM, Alexander Surkov wrote:
--
James Teh
Vice President, Developer
NV Access Inc, ABN 61773362390
Email: [email protected]
Web site: http://www.nvaccess.org/
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
--
Peter Korn | Accessibility Principal
Phone: +1 650 5069522
500 Oracle Parkway | Redwood City, CA 94065
Oracle is committed to developing practices and
products that help protect the environment
|
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
