Yes, I read a general, not specific application case. I would agree it's not a good idea application by application. That doesn't make sense to me.
Bill Haneman writes: > Unless I misunderstood Ashu, his complaint was about a _particular_ > window, since he said that he "tried setting the window's role..." which > meant that he was modifying the application's ATK implementation. > > This seems inadvisable, since it should be up to the screenreader to > report or not report the window's creation, and for an application which > posts a window to consciously attempt to suppress the notification seems > like a bad idea. > > Janina's point is well taken however, but it applies I think to the > general case of windows being posted/unposted, focussed, etc. As far as > I know gnopernicus doesn't yet support 'earcons' but you can at least > modify the verbosity of window presentation. Currently this is possible > only be editing an XML file - try changing > '/usr/share/gnopernicus/presentation/default.xml', in particular this > line in element <event name="window:create"> : > > <literal voice="system">create window</literal> > > (if you are in a locale other than 'C', change the literal line > appropriate to your LANG, for instance the element having xml:lang="fr" > if you are using a French locale). If you removed these <literal> > elements, the creation of windows would no longer be announced. > Similarly, you could modify <event name="window:switch"> to change the > famous "switch to window" message from gnopernicus to something else. > As long as you leave the line > <attribute voice="name" type="string">name</attribute> > then the name of the window will still be announced. > > This editing is probably "unsupported" currently, but it could be > useful. Patches having customized presentations other than the current > "default.xml" and "verbose.xml" would be welcome - if you wish to create > a patch, please modify default.xml.in (i.e. the unlocalized version) > from GNOME CVS module gnopernicus, instead of the localized version. > > I would expect that earcons would be specified in these files, if and > when they are introduced, by something like this: > > <earcon file="/path-to-file/ping.wav"/> > > If someone wants to write a patch to implement this it would probably be > nice :-) > > regards > > - Bill -- Janina Sajka Phone: +1.202.494.7040 Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com Chair, Accessibility Workgroup Free Standards Group (FSG) [EMAIL PROTECTED] http://a11y.org If Linux can't solve your computing problem, you need a different problem. _______________________________________________ Gnome-accessibility-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
