forked from AuroraMiddleware/gtk
f200eebfd6
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. |
||
---|---|---|
.. | ||
a11ychildren.test.in | ||
a11yderive.test.in | ||
a11ytests.test.in | ||
a11ytext.test.in | ||
a11ytree.test.in | ||
a11yutil.test.in | ||
a11yvalue.test.in | ||
about.txt | ||
about.ui | ||
accessibile-name.txt | ||
accessibility-dump.c | ||
accessible-name.txt | ||
accessible-name.ui | ||
assistant.txt | ||
assistant.ui | ||
buttons.txt | ||
buttons.ui | ||
calendar.txt | ||
calendar.ui | ||
children.c | ||
colorchooser.txt | ||
colorchooser.ui | ||
combos.txt | ||
combos.ui | ||
derive.c | ||
entries.txt | ||
entries.ui | ||
expander.txt | ||
expander.ui | ||
focus.c | ||
headerbar.txt | ||
headerbar.ui | ||
hello-world.txt | ||
hello-world.ui | ||
iconview.txt | ||
iconview.ui | ||
infobar.txt | ||
infobar.ui | ||
link.txt | ||
link.ui | ||
listbox.txt | ||
listbox.ui | ||
lockbutton.txt | ||
lockbutton.ui | ||
Makefile.am | ||
menu.txt | ||
menu.ui | ||
menubutton.txt | ||
menubutton.ui | ||
menus.txt | ||
menus.ui | ||
messagedialog.txt | ||
messagedialog.ui | ||
mnemonic.txt | ||
mnemonic.ui | ||
notebook.txt | ||
notebook.ui | ||
paned.txt | ||
paned.ui | ||
pickers.txt | ||
pickers.ui | ||
placeholder-text.txt | ||
placeholder-text.ui | ||
progress.txt | ||
progress.ui | ||
range.txt | ||
range.ui | ||
README | ||
scale-drawvalue.txt | ||
scale-drawvalue.ui | ||
spinner.txt | ||
spinner.ui | ||
stack.txt | ||
stack.ui | ||
statusbar.txt | ||
statusbar.ui | ||
testfocus.c | ||
text.c | ||
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.