<HTML>
<HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<p><font size="2">aloha!</font></p>
<p><font size="2">minutes from the 5 January 2010 Open Accessibility Workgroup
<br />teleconference are available as hypertext at:</font></p>
<p><font size="2"><a href="http://www.linuxfoundation.org/en/Accessibility/Minutes/Minutes20100105">http://www.linuxfoundation.org/en/Accessibility/Minutes/Minutes20100105</a></font></p>
<p><font size="2">and as plain text following my signature. as usual, please report any
<br />errors, mis-attributions, corrections, additions, and clarifications by
<br />replying-to this announcement on-list.</font></p>
<p><font size="2">the next Open A11y Workgroup Conference call will be held at 1600h UTC
<br />on 12 January 2010 - find the meeting time and date in your time zone
<br />using the following link:</font></p>
<p><font size="2"><a href="http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=12&year=2010&hour=16&min=0&sec=0&p1=0">http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=12&year=2010&hour=16&min=0&sec=0&p1=0</a></font></p>
<p><font size="2">a preliminary agenda for the 12 January 2010 Open A11y Conference call
<br />can be found at:</font></p>
<p><font size="2"><a href="http://www.linuxfoundation.org/en/Accessibility/Minutes/Agenda20100112">http://www.linuxfoundation.org/en/Accessibility/Minutes/Agenda20100112</a></font></p>
<p><font size="2">thank you, gregory.</font></p>
<p><font size="2">----- MINUTES OF THE 2010-01-05 OPEN A11Y WORKGROUP CONFERENCE CALL -----</font></p>
<p><font size="2">Open A11y Workgroup Conference Call (5 January 2010)</font></p>
<font size="2">
<p>
<br />Participants</p>
<p> * Janina Sajka (JS/chair)
<br /> + Pete Brunet (PB)
<br /> + Mark Doffman (MD)
<br /> + Mike Gorse (MG)
<br /> + Gregory J. Rosmaita (GJR/scribe)
<br /> + Brad Taylor (BT)
<br /> + Will Walker (WW)
<br /> o regrets: none logged</p>
<p>For Reference</p>
<p>* Agenda for the 5 January 2010 Open A11y Call:
<br /> [http://www.linuxfoundation.org/en/Accessibility/Minutes/Agenda20100105]</p>
<p>Open Action Items</p>
<p> * ACTION - GJR: work with Linux Foundation IT team to fix problems
<br /> with new content management system
<br /> + status: in progress; all links off of <a href="http://a11y.org/">http://a11y.org/</a> should
<br /> now lead to the correct destination, and the information
<br /> should be current; systemic problems still being addressed
<br /> with Linux Foundation staff</p>
<p>Announcements & News</p>
<p>AT-SPI2 0.1.4 Available for Download</p>
<p> AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
<br /> protocol for providing and accessing application accessibility
<br /> information. The project includes a library for bridging the D-Bus
<br /> protocol to the ATK API, allowing Gtk based applications to be made
<br /> accessible. It also contains a client (AT) side library in Python.</p>
<p> AT-SPI2, version 0.1.4 is available for download at:
<br /> * <a href="http://download.gnome.org/sources/pyatspi/0.1/">http://download.gnome.org/sources/pyatspi/0.1/</a>
<br /> * <a href="http://download.gnome.org/sources/at-spi2-core/0.1/">http://download.gnome.org/sources/at-spi2-core/0.1/</a>
<br /> * <a href="http://download.gnome.org/sources/at-spi2-atk/0.1/">http://download.gnome.org/sources/at-spi2-atk/0.1/</a></p>
<p>AT-SPI2 0.1.4 Release Notes</p>
<p> This is a development release of AT-SPI2, it has some unfinished
<br /> features.</p>
<p> A list of work required before a full release can be found at:</p>
<p> <a href="http://live.gnome.org/Accessibility/BonoboDeprecation">http://live.gnome.org/Accessibility/BonoboDeprecation</a></p>
<p> For more information about the release of AT-SPI2 0.1.4, please
<br /> consult:</p>
<p> <a href="https://lists.linux-foundation.org/pipermail/accessibility-atspi/2009-December/000603.html">https://lists.linux-foundation.org/pipermail/accessibility-atspi/2009-December/000603.html</a>
<br /> _________________________________________________________________</p>
<p>Meeting Minutes</p>
<p> NOTE: These minutes have not yet been finalized.</p>
<p>Topic 1: AT-SPI on D-Bus Port: Progress and Issues</p>
<p> * AT-SPI on D-Bus Port wiki page last updated 30 October 2009 by
<br /> Mike Gorse
<br /> + MikeG is maintaining the AT-SPI on D-Bus Port wiki page, and
<br /> will add info about AT-SPI2 development releases to the D-Bus
<br /> wiki page</p>
<p>Discussion of Topic 1: D-Bus Port Update</p>
<p> WW: had really good hack day a week or so ago -- addressed a lot of
<br /> bugs directly -- driving factor, Orca Regression test to flush out
<br /> problems</p>
<p> WW: MarkD to hack on stuff over holidays - progress with Orca
<br /> Regression test and AT-SPI2</p>
<p> MD: not yet -- finishing ATK side; next thing is to use Orca for
<br /> regression testing</p>
<p> WW: leasing large containers -- handle mangagedescendents problem too?</p>
<p> MD: 2 will go together;</p>
<p> WW: cool</p>
<p> WW: collections API?</p>
<p> MD: MikeG has been working on this; need to test</p>
<p> MG: running Orca regression tests with FF will help clear up remaining
<br /> issues</p>
<p> WW: structural navigation features of Orca - next heading, next div,
<br /> etc. -- if any failure, involves going back to install; may have Orca
<br /> say "collections broke" when not functioning</p>
<p> WW: can start hammering away at running regression tests in Orca and
<br /> fixing things as they come up</p>
<p> WW: scaffolding for CORBA versus D-Bus; buy in from participants; Luke
<br /> Yelavich (hereafter, "LukeY") had question about requirement using
<br /> CORBA -- ok with CORBA as default; will spend time creating patches
<br /> today to make this happen</p>
<p> WW: Accessibility API on D-Bus?</p>
<p> MD: need to reply to lee's email -- needs improvement, needs to take
<br /> part in session management; currently have registry doing that, when
<br /> don't need it to -- should be done by a11y d-bus</p>
<p> WW: need Lee to help on that?</p>
<p> MD: would be great -- at moment just a script for testing session
<br /> management</p>
<p> WW: my upcoming plan: relocation; when bus goes away need to connect
<br /> to new one</p>
<p> MD: working on that -- shouldn't be too big a deal; matter of sending
<br /> correct signals</p>
<p> WW: shake out bugs with Orca tests, document and fix</p>
<p> WW: this week: finish implementation and start doing bugs next week</p>
<p> MD: first release next monday -- after that can attend to smaller
<br /> stuff</p>
<p> WW: amazing that are in line with GNOME schedule -- ah, serendipity!</p>
<p> WW: drop email to Lee on a11y d-bus issues with CC to MarkD</p>
<p> MD: reconnection of bus; Orca regression tests for collections API</p>
<p> WW: GNOME panel needs to be investigated; will raise with Lee in email</p>
<p> BT: use new stuff for panel</p>
<p> MD: really big change on release, so want to start with subsets before
<br /> merging all</p>
<p> MG: fine with me; some sample applications that could use - have to
<br /> build with mono, though</p>
<p> MD: don't mind doing that -- should do today or tomorrow -- aim for
<br /> end of week; complete merge by monday</p>
<p> WW: MarkD, what about desktop files conditionally shipped with
<br /> makediff package?</p>
<p> WW: prevented a file from being shipped in distribution -- intent was
<br /> to keep from being installed by default, but not removed from shipped
<br /> package</p>
<p> MD: will try and work on that</p>
<p> WW: will be testing makefiles anyway, so can test that, too</p>
<p> MD: makefiles in pyspi?</p>
<p> WW: CORBA based ones to do conditional install;</p>
<p> WW: MD, please look at this -- i think it just needs a change in
<br /> makefile -- make and makeinstall may need revision</p>
<p> WW: not out of the woods, yet, but have implementations and
<br /> bug-finding and fixing -- just need to sit down and hammer things out</p>
<p> JS: very encouraging</p>
<p> JS: being in sync on dot five release is great</p>
<p> MD: how many to go?</p>
<p> WW: dot six, then final release within 2 weeks of another -- gnome
<br /> schedule in IRC -- March 16 is hard-code freeze, so need to be done by
<br /> the ides of march</p>
<p> WW: API changes needed?</p>
<p> MD: doing work in pyspi</p>
<p> WW: changes due by January 11 -- providing drop-in replacement; only
<br /> new API is plug-in stuff from Brad and Mike, which is already in
<br /> pipeline
<br /> _________________________________________________________________</p>
<p>New Business</p>
<p>SpeechDispatcher Update</p>
<p> JS: Bill Cox coding with LukeY on speech dispatcher on emacs list to
<br /> update support for speechdispatcher and emacspeak -- might finally get
<br /> integrated way to handle Orca, speakup, emacspeak for users who want
<br /> to use a combination of them</p>
<p> WW: push-back from raman?</p>
<p> JS: no, just no work being done on emacspeak except by raman -
<br /> friendly response</p>
<p> JS: concerns seem to have evaporated</p>
<p> WW: lisp libao module for speechdispatcher?</p>
<p> JS: libao as way of getting speech for particular OS</p>
<p> WW: have note to look at that on solaris; module optional - can build
<br /> without or with; introduce another layer between speech engine and
<br /> speech output?</p>
<p> JS: with linux can choose where integrate into rest of audio
<br /> environment</p>
<p> WW: eSpeak -- Ed from DecTalk project gave eSpeak developers some
<br /> ideas -- turn on and enable;</p>
<p> WW: less harsh sounding; still very computery - sounds like DecTalk or
<br /> eloquence</p>
<p> GJR: great localization support; personally consider speech quality
<br /> quite robust</p>
<p> JS: agree -- it is very easy to understand and to customize</p>
<p> For Reference:
<br /> * eSpeak Project Home Page
<br /> [http://espeak.sourceforge.net/]</p>
<p> * SourceForge download page for eSpeak
<br /> [http://sourceforge.net/project/showfiles.php?group_id=159649]</p>
<p> _________________________________________________________________</p>
<p>ISO 13.0.66 to 13.0.66-4</p>
<p>For Reference:
<br /> * ISO/IEC JTC 1/SC 35: User interfaces Sub-Committee Home Page
<br /> [http://www.open-std.org/jtc1/sc35/]</p>
<p> + area of work: Standardization in the field of user-system
<br /> interfaces in information and communication technology (ICT)
<br /> environments and support for these interfaces to serve all
<br /> users, including people having accessibility or other
<br /> specific needs, with a priority of meeting the JTC 1
<br /> requirements for cultural and linguistic adaptability.</p>
<p> + JTC 1/SC 35: User Interfaces ISO Technical Committee Catalog page
<br /> [http://www.iso.org/iso/iso_technical_committee.html?commid=45382]</p>
<p> * ISO/IEC CD 13066-1: Information Technology - Interoperability with
<br /> Assistive Technology (AT) -- Part 1: Requirements and
<br /> recommendations for interoperability
<br /> [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=53770]</p>
<p> JS: document spec in ISO specification 13.0.66 about assistive
<br /> technologies; produced in special working group on a11y with which we
<br /> have worked; sub-committee of committee on</p>
<p> JS: APIs on key operating systems - description of a11y interfaces on
<br /> linux; Peter Korn (hereafter, "PeterK") in last meeting promised to
<br /> follow up -- sent email to him to suggest he do it under a11y.org
<br /> umbrella</p>
<p> JS: will expect some help in making sure that what i write is correct</p>
<p> JS: need to find out what they expect and what format is best</p>
<p> JS: sub-committee meeting in Madrid after which work will get serious
<br /> on getting document done</p>
<p> PB: include IA2?</p>
<p> JS: IBM is covering that in windows spec - Andi doing that write-up</p>
<p> PB: dates? different versions of spec; have some documentation changes
<br /> to put in, but can port</p>
<p> JS: current 13.0.66 working on 13.0.66-4</p>
<p> WW: PeterK on vacation until next week</p>
<p> _________________________________________________________________</p>
<p>LSB certification</p>
<p>For Reference:
<br />* Linux Standard Base (LSB):
<br /> <a href="http://www.linuxfoundation.org/collaborate/workgroups/lsb">http://www.linuxfoundation.org/collaborate/workgroups/lsb</a></p>
<p> JS: once comfortable with D-Bus implementations, can go back to LSB
<br /> and say "lets move the a11y support into what LSB certification tests
<br /> for"</p>
<p> JS: not comfortable with CORBA plus D-Bus, but when totally D-Bus, can
<br /> be part of LSB</p>
<p> WW: require C-bindings for these?</p>
<p> JS: don't recall offhand</p>
<p> JS: machine testability also LSB concern</p>
<p> WW: we are machine testable through python and C-code, but need C-code
<br /> bindings for D-Bus</p>
<p> WW: need to figure out whether should move forward with it at what
<br /> stage and time; please check the following link: info on 2 point 29 is
<br /> available from GNOME:</p>
<p> <a href="http://live.gnome.org/TwoPointTwentynine">http://live.gnome.org/TwoPointTwentynine</a></p>
<p> JS: will re-grok LSB certification requirements</p>
<p> _________________________________________________________________</p>
<p>Licensing Issues (Redux)</p>
<p> JS: PB, i will push licensing issues with KarenC and JimZ of Linux
<br /> Foundation; have all permissions we need; no reason why can't get
<br /> top-level link to IA2 from Linux Foundation front page and in
<br /> LF news, etc.</p>
<p> _________________________________________________________________</p>
<p>Identify Topics for the 12 January 2010 Teleconferences</p>
<p> * D-Bus Port: Progress & Updates
<br /> * Getting Open Accessibility Documents to ISO Status
<br /> * Collaborative Work with JTC 1/SC 35: User interfaces Sub-Committee</p>
<p> _________________________________________________________________</p>
<p>Wrap Up</p>
<p> * meeting adjourned 1644h UTC
<br /> * next Open A11y conference call: 2010-01-12
<br /> _________________________________________________________________
<br /></p>
</font>
</BODY>
</HTML>