On 19/08/16 15:45, MENGUAL Jean-Philippe wrote: > Hi, > > Actually it is a general introduction to devs I will do about: how to fix > some accessibility bugs, test them and test your fixes?
Yes for that, accerciser can be useful. > Also, when you submit a patch, how to ensure it does not break accessibility, > presenting to acessibility bus the proper information? No, for that it would be better a regression test. > > For this, I imagine to say: use accerciser, it avoids you to learn using an > assistive technology and will enable ou to code properly your subjects and > ensure you send the proper tree. Would it be correct? No. Accerciser is mostly a accessibility debugging tool. In order to know how to use it, you need a basic knowledge of assistive technologies. For example, Accerciser allows you to view the accessible objects of the application hiearchy tree, and examine the accessibility interfaces that implements. So you need to know what it is an accessible object, that there are an accessibility hiearchy and that there are specific interfaces (Text, EditableText, etc). > > Regards > > > Jean-Philippe MENGUAL > > HYPRA, progressons ensemble > > Tél.: 01 84 73 06 61 > > Mail: cont...@hypra.fr > > Site Web: http://www.hypra.fr > > ----- Alejandro Piñeiro <apinhe...@igalia.com> a écrit : >> >> >> On 19/08/16 10:06, MENGUAL Jean-Philippe wrote: >>> Hi, >>> >>> COuld you tell me if, to help working on Libreoffice, Accerciser could be a >>> relevant test tool? >> >> Accerciser is more a debugging tool, useful when you are implementing >> accessibility support for some application. >> >> So if you want to use it while improving Libreoffice accessibility >> support: yes, it can be useful. >> >> If you want to use it to create a test suite or a regression test suite, >> I think that there are other better options. >> >>> I know Libreoffice uses GTK but I dont know wether accerciser could be >>> enough to help making the User interface more accessible. >> >> AFAIK, Libreoffice uses GTK for some stuff, but most of the UI is non-GTK. >> >> In any case, Accerciser doesn't require the application being tested to >> use GTK. Accerciser needs the relevant application to expose the >> accessibility information through at-spi. For example, if you use >> accerciser with Firefox, you could see the content from objects that in >> origin are not GTK widgets. >> >> >>> An idea? Or LO code would be more complex and accerciser not relevant? >> >> See my previous comment. As I said it depends on your specific needs. >> >>> >>> Thanks for your reply >>> >>> Regards, >>> >>> Jean-Philippe MENGUAL >>> >>> HYPRA, progressons ensemble >>> >>> Tél.: 01 84 73 06 61 >>> >>> Mail: cont...@hypra.fr >>> >>> Site Web: http://www.hypra.fr >>> _______________________________________________ >>> gnome-accessibility-list mailing list >>> gnome-accessibility-list@gnome.org >>> https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list >>> >> >> -- >> Alejandro Piñeiro <apinhe...@igalia.com> >> _______________________________________________ >> gnome-accessibility-list mailing list >> gnome-accessibility-list@gnome.org >> https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list > > -- Alejandro Piñeiro <apinhe...@igalia.com> _______________________________________________ gnome-accessibility-list mailing list gnome-accessibility-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-accessibility-list
