On Fri, Mar 07, 2008 at 02:54:04PM -0600, Brian Cameron wrote: > >If the answer is yes, then that needs to be fixed. I'm guessing > >__wildly__ that it will be easier to make all the a11y infrastructure > >part of the trusted path. > > Yes, if it is a requirement to ensure that this sort of information > can not be manipulated, then it would be necessary to call the > text-to-speech and braille display engines directly from the > dialog. > > I don't think this means that we need to include "all of the a11y > infrastructure". It just means that we need to include those
"all ... needed by the screen lock program" > components needed to translate text to speech and braille display > output. > > This doesn't necessary mean that we need orca, we could call the > lower level interfaces directly. This could probably be done > without using at-spi-registryd at all, if we wanted. This is, effectively, a parallel a11y architecture for the trusted path. If that's easier, sure. It's not complete, just complete enough for the screen lock program. Will there be other trusted path consumers of a11y? Nico --
