gtk2/testsuite/a11y
Matthias Clasen f200eebfd6 Improve menubutton a11y
The button now claims its menu as a child for a11y purposes,
which makes it possible for ATs to see it when the navigate
the tree top-down.

Update the a11y test to match.
2013-12-20 13:31:08 -05:00
..
a11ychildren.test.in
a11yderive.test.in
a11ytests.test.in tests: Make a11ytests keep going on failure and be verbose 2013-07-26 13:33:40 +02:00
a11ytext.test.in
a11ytree.test.in
a11yutil.test.in
a11yvalue.test.in
about.txt Fix accessibility tests for real 2013-12-16 20:39:00 -05:00
about.ui
accessibile-name.txt
accessibility-dump.c accessibility-dump: Print diff by default 2013-08-06 11:22:59 +01:00
accessible-name.txt
accessible-name.ui
assistant.txt Fix up a11y tests again 2013-08-31 17:06:44 -04:00
assistant.ui
buttons.txt More a11y test updates 2013-09-16 23:29:42 -04:00
buttons.ui
calendar.txt
calendar.ui
children.c Don't use stock APIs in the testsuite 2013-06-24 19:53:08 -04:00
colorchooser.txt testsuite/a11y: Don't check minimum increment 2013-07-24 02:54:25 +01:00
colorchooser.ui
combos.txt Revert "a11y: Remove AtkSelection implementation from combobox" 2013-09-16 15:41:15 +02:00
combos.ui
derive.c
entries.txt testsuite/a11y: Don't check minimum increment 2013-07-24 02:54:25 +01:00
entries.ui
expander.txt
expander.ui
focus.c
headerbar.txt More a11y test updates 2013-09-16 23:29:42 -04:00
headerbar.ui Add GtkHeaderBar to the a11y tests 2013-06-30 22:33:12 -04:00
hello-world.txt
hello-world.ui
iconview.txt
iconview.ui
infobar.txt Update expected output for the infobar a11y test 2013-08-03 15:34:46 +02:00
infobar.ui
link.txt Small improvement to GtkLinkButton a11y 2013-09-21 20:51:21 -04:00
link.ui Small improvement to GtkLinkButton a11y 2013-09-21 20:51:21 -04:00
listbox.txt Add a GtkListBoxRow accessible 2013-09-21 20:51:22 -04:00
listbox.ui Add a GtkListBoxRow accessible 2013-09-21 20:51:22 -04:00
lockbutton.txt
lockbutton.ui
Makefile.am Add a menubutton to the a11y tests 2013-12-20 13:31:08 -05:00
menu.txt
menu.ui Don't use stock APIs in the testsuite 2013-06-24 19:53:08 -04:00
menubutton.txt Improve menubutton a11y 2013-12-20 13:31:08 -05:00
menubutton.ui Add a menubutton to the a11y tests 2013-12-20 13:31:08 -05:00
menus.txt Adjust the a11y testsuite to match expected output 2013-06-25 12:39:19 -04:00
menus.ui Adjust the a11y testsuite to match expected output 2013-06-25 12:39:19 -04:00
messagedialog.txt Fix up accessibility tests 2013-10-28 07:20:11 -04:00
messagedialog.ui
mnemonic.txt
mnemonic.ui
notebook.txt Adjust the a11y testsuite to match expected output 2013-06-25 12:39:19 -04:00
notebook.ui Don't use stock APIs in the testsuite 2013-06-24 19:53:08 -04:00
paned.txt testsuite/a11y: Don't check minimum increment 2013-07-24 02:54:25 +01:00
paned.ui
pickers.txt Revert "a11y: Remove AtkSelection implementation from combobox" 2013-09-16 15:41:15 +02:00
pickers.ui
placeholder-text.txt
placeholder-text.ui
progress.txt testsuite/a11y: Don't check minimum increment 2013-07-24 02:54:25 +01:00
progress.ui
range.txt testsuite/a11y: Don't check minimum increment 2013-07-24 02:54:25 +01:00
range.ui
README
scale-drawvalue.txt testsuite/a11y: Don't check minimum increment 2013-07-24 02:54:25 +01:00
scale-drawvalue.ui
spinner.txt Update expected results for some a11y tests 2013-10-25 16:39:49 -04:00
spinner.ui
stack.txt Add GtkStack and GtkStackSwitcher to the a11y tests 2013-06-30 22:33:12 -04:00
stack.ui Add GtkStack and GtkStackSwitcher to the a11y tests 2013-06-30 22:33:12 -04:00
statusbar.txt
statusbar.ui
testfocus.c
text.c testsuite: Add deprecation guards for ATK deprecations 2013-09-16 15:41:15 +02:00
text.txt
text.ui
tree-performance.c
tree-relationships.c
util.c
value.c

accessibility-dump is a test runner that can do tests of static
accessibility information. Run it like this:

./accessibility-dump [OPTIONS] TESTFILE [TESTFILES...]

where TESTFILE is a GtkBuilder .ui file. accessibility-dump creates
a textual dump of the accessibility information for the created
widget hierarchy and compares it to a preexisting .txt file.

To create an initial dump, you can use the --generate option with
a single .ui file. You should carefully inspect the output before
blessing it as the official .txt to compare against.

To find out details about a failure, you can use the --verbose
option to see differences between expected and actual output.

When run without any arguments, all the .ui files in the current
directory are tested.