Accessability in Edubuntu

[Steve Lee]

On 02/10/2007, Jude DaShiell <jdashiel at shellworld.net> wrote:
> I can tell you exactly how well orca will work in a thin client
> environment and I can explain why.  Orca requires a thick client to work
> at all, and it requires broad band access.  Without those two components
> in place it will not work at all.

I can't comment on Orca so I'll just make a couple of general points
as thin clients need to support AT as well. In the UK education
section (schoolforge.org.uk) thin client is one of the key advantages
of FOSS that can be promoted (saving cash, ease admin). I have limited
knowledge but believe the situation should not be as bad as you
present. I just needs some concentrated effort.

* X, (the linux display system) is naturally thin client. LTSP just
gets it going and in usual desktop situations the display happens to
be on the same box as the client software. Thus most programs will
'just work' thin client as far as display and common input is
concerned unless they have worked around it somehow. The Accessibility
APIs also work in this distributed model
* I understand sound now works with LTSP.
* As far as performance/bandwidth is concerned yes thin client pushes
the load onto infrastructure and servers. The X protocol is pretty
good and optimisations are available (NX, ndiyo). The graphics
packages that many programs and widget sets use work hard to reduce
bandwidth too (e.g cairo).

www.schoolforge.org.uk/index.php/Assistive_Technology_with_Terminal_Servers

-- 
Steve Lee
--
Open Source Assistive Technology Software
PowerTalk - your presentations can speak for themselves
www.fullmeasure.co.uk