Hi Francois,, Thanks for the update. Here are a few thoughts. It would be good to indent four spaces instead of a full tab stop. This sems to be gaining favor, and it also makes the code easier to read on a Braille display. I'm thinking that I should give you commit privelege, so we can start testing your code for accessibility with various screenreaders. Unless you are already writing your code in a clone of the repository, you would have to create one and then copy the classes into the appropriate subdirectories. If you create new classes you will have to add them to the repository. Let me know if you have questions. John On Wed, Jul 11, 2012 at 11:07:41PM -0400, Francois wrote: > Hi guys, just an update on what I am doing. There were hard-to-catch > bugs in the UTD class, it seemed like all the navigation methods were > written to find XML elements as the first of every children list, and > that only one of them was expected! And because the search for > elements is done in a threaded way in order to keep the window free, > and methods are called recursively, things are tricky to debug. > Fortunately Eclipse is very good at helping the debugging. We are > getting there! > > Best regards, > > François -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities