Hi Angela: Can you tell me more about the GUI installation automatic test that you mention below? Is it something that needs to be done from a Live CD/USB, or is it something that can be done from an installed system? If it's the latter, you can have an account that has accessibility support enabled.
If it is the former, I think you *might* be able to get away with something like "-B assistive_tech=testing". The SMF code that handles accessibility (a11y) for the live CD is in slim_source/usr/src/cmd/slim-install/svc/live-a11y. It has constructs that enable a11y support if assistive_tech is defined to anything, and additional specific things to start the screen reader or magnifier depending upon if the assistive_tech value is "reader" or "magnifier". So, setting assistive_tech to "testing" looks like it should enable a11y, but not start any assistive technologies. Hope this helps, Will angela wrote: > Hi Will, > > The behavior I met is not quite the same with CR6801596, because > demon at-spi-registryd did be started. > > In our testing, we only need to enable AT-SPI, with demon > at-spi-registryd started. > > I added option "-B assistive_tech=reader" in Grub menu, and boot to LiveUSB, > it can start demon at-spi-registryd, but at the same time it also starts > reader, and the system becomes very slow. > > Is there any plan to seperate them? Such as add some option or option value > that allow me only start at-spi-registryd demon, and do not start reader? > > Thanks, > Angela > > > Willie Walker ??: >> Hi Angela: >> >> The below is pretty much the minimal thing you can do. In any case, the >> behavior you are seeing might be a bug that cropped up somewhere around >> b107, but which should be fixed in b109. I believe it was tracked via >> bugster CR 6801596. >> >> Hope this helps, >> >> Will >> >> angela wrote: >> >>> Hi William, >>> >>> I need to enable AT-SPI for GUI installation automatic test. >>> >>> I used the method you mention in this email and found that it can enable >>> AT-SPI, but at the same time, it enables other features which seems make >>> the system very slow. >>> >>> I wonder is there any option in Grub menu that only enable AT-SPI? >>> >>> Thanks, >>> Angela >>> >>> Willie Walker ??: >>> >>>> Hi All: >>>> >>>> With the exception of development releases, the accessibility >>>> infrastructure is not enabled in GNOME by default. >>>> >>>> As part of the accessible install, we plan to set up GRUB with a "-B >>>> assistive_tech=ader" option to indicate accessibility should be >>>> enabled for the live CD (I sent out a separate e-mail on this). As >>>> mentioned in that mail, one use of this option will be to tell the >>>> system to generate beeps prior to presenting the keyboard and language >>>> screens. >>>> >>>> I'd also like to use this option to tell the live CD to enable >>>> accessibility for the jack and root users. There are two main steps to >>>> enable accessibility so that the desktop and installer can be accessible: >>>> >>>> 1) Modify the gconf setting to enable accessibility (requires >>>> /usr/bin/gconftool-2 to be available and /etc to be writable): >>>> >>>> gconftool-2 ?direct ?config-source >>>> xml:readwrite:/etc/gconf/gconf.xml.defaults ?type bool ?set >>>> /desktop/gnome/interface/accessibility true >>>> >>>> 2) Create a ~root/.orbitrc file (requires /root to be writable): >>>> >>>> cat << \ORBITRC_EOF > /root/.orbitrc >>>> ORBIIOPIPv4=ORBIIOPUNIX=0 >>>> ORBITRC_EOF >>>> >>>> I'm curious if live-fs-root might be the place to do both of these >>>> operations. The place I'm thinking about in the 'else' block at the end >>>> of the file (i.e., the block contains the line "/usr/sbin/svcadm enable >>>> application/graphical-login/gdm"). Is the system in an appropriate >>>> state for this work to be done at that point? >>>> >>>> Will >>>> _______________________________________________ >>>> caiman-discuss mailing list >>>> caiman-discuss at opensolaris.org >>>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >>>> >>>> >> >
