|
From: | Gregory J. Rosmaita |
Subject: | [Accessibility] AT-SPI2 To Do wiki page at a11y.org |
Date: | Wed, 11 Aug 2010 16:40:52 +0100 |
aloha,
API!
there is a AT-SPI2 "to do" list compiled by mark doffman and mike gorse available at: http://a11y.org/atspi-todo your and everyone/anyone else's contributions to and/or comments on that document are quite welcome... by the way, AT-SPI materials at the Open Accessibility Workgroup's web site can be found using the following URI: http://a11y.org/atspi the URI http://a11y.org/at-spi also points to the same resource (hopefully the short URIs are as easy for others to remember as they are to me!) further information on ATK/AT-SPI can also be found at: http://accessibility.linuxfoundation.org/a11yspecs/atspi/adoc/ which contains 2 Recommendations for Application Developers: 1. Implementing Accessible Document Interfaces using ATK http://a11y.org/adoc-atk 2. Accessible Document Navigation using AT-SPI http://a11y.org/adoc-atspi and the following Reference Materials: * Table of AT-SPI events http://accessibility.linuxfoundation.org/a11yspecs/atspi/adoc/atspi-events.html * Accessibility and Document Object Model (DOM) API Comparisons http://a11y.org/a11y-dom-apis gregory. ----------------------------------------------------------------- Accessibility, Internationalization, and Interoperability are not "features", "overlays" or "add-ons". Rather, they are core components of any architecture -- programmatic or otherwise. ----------------------------------------------------------------- Gregory J. Rosmaita, address@hidden Vice-Chair, WebMaster & Listmaster, Open Accessibility Workgroup http://a11y.org/ http://a11y/specs ----------------------------------------------------------------- ---------- Original Message ----------- From: Piñeiro <address@hidden> To: address@hidden Cc: address@hidden, address@hidden, address@hidden, address@hidden Sent: Wed, 11 Aug 2010 17:12:39 +0200 (CEST) Subject: Re: [Access-activists] Re: [Accessibility] Accessibility Status: Swamped > From: Joanmarie Diggs <address@hidden> > > > We need to remedy this Orca problem independent of the CORBA/D-Bus > > problem. That way, once things are fixed in both, Orca can become the > > screen reader of choice due to the compelling, competitive, performant, > > and free access it provides. > > Yes of course. Sorry, my previous mail was not clear enough. > > I was not trying to say that in order to improve Orca > performance, we should focus *only* in improve at-spi2 > performance. I was trying to say that Orca performance issues > can also be improved if at-spi2 performance at-spi2 is improved. > > Probably being too optimistic, I was trying to say that if we > have enough resources, it would be good to a) have people > assigned to improve Orca performance b) have people assigned to > improve at-spi2 performance > > As b) would mean a indirect way to improve Orca performance. > > Of course, now we need to decide the priorities. As Mike Gorse (and > Mark Doffman?) is already using part of his time on at-spi2, probably > new teams can start working directly on Orca. > > Sorry for not explain myself properly in my previous mail, and sorry > for the noise. > > BR > > === > API (address@hidden) > > _______________________________________________ > Accessibility mailing list > address@hidden > http://lists.gnu.org/mailman/listinfo/accessibility ------- End of Original Message ------- |
[Prev in Thread] | Current Thread | [Next in Thread] |