Rich Schwerdtfeger
CTO Accessibility Software Group

[email protected] wrote on 06/22/2011
11:16:41 AM:

> From: Pete Brunet <[email protected]>
> To: IA2 List <[email protected]>
> Date: 06/22/2011 11:19 AM
> Subject: Re: [Accessibility-ia2] next changes to IAccessible2
> Sent by: [email protected]
>
>
> On 6/22/2011 8: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?
> Hi Rich, It's been a long time since I looked at accessibleDocument.
> (It's not part of IA2.)  I couldn't find a link in my archives.
> Please send it.  Would that discussion be better held on the parent
> LF a11y list at [email protected] ?  That
> will also be of interest to the Linux a11y architects.
>
I have no idea. I just found it odd that we would add only one method for a
document.

> 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.
> We've talked about adding something to get around the limitations of
> WinEvent, primarily the lack of an event payload so out of process
> AT don't have to use (and possibly get stale data) on a following
> call fetching event data.  It's not become enough of an issue that
> the group has pushed that change through though.
>
> For in process AT the callback happens on the same thread that fires
> the event.  Jamie might be able to comment on what problems there
> might be for out of process AT when handing a cue change event.
>

I think the difference here is we are trying to keep the video and audio
descriptions in synch. That adds an additional level of concern for me. I
will look to see what Jamie says. Descriptions could be quite long.
>
>
>
> Rich Schwerdtfeger
> CTO Accessibility Software Group
>
> [image removed] 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:
> Hi.
>
> I gathered ideas into one doc -
> https://wiki.mozilla.org/Accessibility/IA2_1.3. Please give feedback
> here and feel free to edit the wiki.
>
> Thank you.
> Alex.
>
> --
> 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
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2

Reply via email to