Re: GNOME Accessibility on by default, and Firefox
- From: "Steve Lee" <steve fullmeasure co uk>
- To: "Li Yuan" <Li Yuan sun com>
- Cc: Willie Walker <William Walker sun com>, dev-accessibility lists mozilla org, David Bolter <david bolter utoronto ca>, Aaron Leventhal <aaronlev moonset net>, Gnome Accessibility List <gnome-accessibility-list gnome org>
- Subject: Re: GNOME Accessibility on by default, and Firefox
- Date: Sat, 1 Nov 2008 16:36:07 +0000
2008/10/27 Li Yuan <Li Yuan sun com>:
> A way to do this in my mind is to create functions in atkmisc, to tell gail
> and other accessibility implementations to send out signal or not. If an AT
> is started, at-spi-registryd will call the function to tell applications
> "now it is time to send out the signals". But this require modification in
> all accessibility implementations (Firefix, OpenOffice, Gtk+ applications,
> Java applications).
What if that gets pushed down the stack a bit so the decision to
actually send on the wire is made even though ATK/FFx etc still call
and look for events? Would the over head of the function calls that
test and return with no a11y be too much to bear? It would be
localosed in one place and all appswould behave the same.
--
Steve Lee
Open Source Assistive Technology Software and Accessibility
fullmeasure.co.uk
[Date Prev][
Date Next] [Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]