944e30d940
Add a11y state tests
...
This adds a new test which can be scripted to trigger various
event and action sequences, and record state changes in the
accessibility layer.
So far, there are a few tests verifying state changes when
focus changes.
Related to https://bugzilla.gnome.org/show_bug.cgi?id=715176
2014-08-04 09:58:58 +02:00
a6b8800531
Add a test for popover accessible parents
...
This tests the fix in the previous commit.
2014-07-30 23:14:49 +02:00
452f92c644
Update expected output for a11y tests
2014-07-21 19:21:02 -04:00
69b25a77aa
Update expected output for a11y test
2014-07-14 14:36:58 -04:00
5436438520
a11y: Update expected output for color chooser
2014-07-09 19:48:08 -04:00
c4e533ecd6
Fight deprecation warnings in test
...
This time, in installed tests.
2014-06-28 00:41:26 -04:00
b9bd7159c0
Disable deprecation warnings in tests
...
We want to test deprecated properties, so failing the tests with
warnings is not productive.
2014-06-25 16:29:08 -04:00
98cf67ddba
testsuite: put installed tests in the right place
...
Follow the prevailing practice and put the installed tests
into $libdir/installed-tests/$PACKAGE instead of
$pkglibdir/installed-tests.
2014-05-31 00:16:07 -04:00
70a5e66d2f
a11y tests: Avoid deprecation warnings
...
We can't drop the index-based AtkTable methods unless we change
the output format, so just ignore the deprecations for now.
2014-05-02 20:59:00 -04:00
1bf6ad314d
a11y tests: Update expected output
...
The new AtkValue interface aways returns doubles, which causes
the range to be printed out with decimals.
2014-05-02 20:53:02 -04:00
4fc256de8a
a11y tests: Use the new AtkValue interface
...
The old interface is deprecated, and we just implemented the
new one, so lets test it.
2014-05-02 20:52:56 -04:00
a2fb74c375
Update output of a11y tests
...
These are all affected by the addition of the action_box in
GtkDialog or by the switch to popovers in GtkMenuButton.
2014-04-28 22:55:44 -04:00
85855da946
Update expected output for assistant a11y test
...
The headerbar and its content now shows up, as it should.
2014-04-10 15:50:51 -07:00
1685877635
Minor update of a11y test output
2014-03-24 20:17:21 -04:00
8a9dab8e29
Update a11y test output
2014-03-17 18:14:53 -04:00
1779789f65
Update a11y test output
...
These harmless changes are a consequence of
66fae0330c
2014-03-12 23:43:28 -04:00
faa6db8485
testsuite: Update a11y/menubutton3.ui test expectations
...
Popover is now minimally accessible.
https://bugzilla.gnome.org/show_bug.cgi?id=725864
2014-03-10 23:02:23 +01:00
cabf0badfa
Update messagedialog a11y test
2014-03-03 23:37:53 -05:00
905a6aa2e8
about-dialog: link directly to the 3.0 version of GPL licenses
...
In the unlikely case that there is another GPL released in the future
it would be best if we link directly to the 3.0 version of the
license description instead of the alias to the latest
version.
2014-02-27 08:12:56 -05:00
71e46a0b0e
a11y tests: Add a tests for menu buttons with popovers
...
This shows that popovers currently lack accessibility.
2014-02-22 12:51:11 -05:00
349376f48f
a11y tests: Add a test for menubuttons with model
2014-02-22 12:31:19 -05:00
ac50e4e9df
a11y tests: Add a test for GtkActionBar
2014-02-22 12:31:18 -05:00
493ce0e291
a11y tests: add image buttons
2014-02-22 12:31:18 -05:00
5790831ecb
Update expected output of the messagedialog a11y test
2014-02-17 21:39:23 -05:00
fd1855c116
Update expected output of the colorchooser a11y test
2014-02-17 21:39:10 -05:00
4985c0d545
Update expected output for assistant a11y test
2014-02-04 13:15:46 -05:00
ddc7995a9f
Update expected output for accessible tests
2014-01-25 14:31:11 -05:00
1faf3a0aaa
Use the memory settings backend for make check
...
The color chooser test is constantly running into the
problem that the custom color setting is not empty.
Avoid that by using the memory settings backend.
2014-01-21 21:17:14 -05:00
3659f8fc90
a11y tests: Fix expected output of about.ui
2014-01-18 10:54:37 -05:00
b29e3d8ce0
a11y tests: Fix settings that affect a11y output
...
It would be nicer if we could have the tests specify what environment
their expected output was created in, then we could test multiple
scenarios. For now, just fix the setting to avoid test failures.
2014-01-18 10:53:22 -05:00
c2d7a74c0b
Update colorchooser.ui test output
...
These are expected changes from the last few commits.
2014-01-17 17:52:08 -05:00
fec99f3ee5
Update messagedialog.ui test output
...
These are expected changes from the last few commits.
2014-01-17 17:52:08 -05:00
d2eeaec3cc
Update expected output for tree.ui
...
Now that the utf8 actually appears...
2014-01-14 13:15:19 -05:00
e1f38f2c22
Run accessibility tests in en_US.utf8
...
Previously, we were just using the C locale, which breaks
some of our fancy utf8 output for checkmarks and so on.
2014-01-14 13:15:19 -05:00
61f0556cf7
Add some treeview a11y tests
2014-01-13 23:51:26 -05:00
29cd52c854
Emit a11y state change notification for color swatches
...
Improve the color swatch accessible to set a proper role
depending on whether the swatch is selectable or not, and
set the checked atk state when appropriate.
https://bugzilla.gnome.org/show_bug.cgi?id=721048
2014-01-05 10:54:43 -05:00
b962d7686a
Color chooser: More accessible names
...
Set the accessible name of the 'custom color' button too.
2014-01-05 09:21:32 -05:00
89e8624cb3
Update a11y tests to match the last change
...
Color swatches have names now, not descriptions.
2014-01-05 09:11:54 -05:00
01ad01a801
Drop custom colors from a11y output
...
These were inadvertedly included in the previous commit, but
no custom colors are present in the gnome-continuous test sessions.
2014-01-04 21:57:26 -05:00
9137b4ed8e
GtkColorSwatch: Set an accessible role
...
And update the colorchooser a11y test to a) use GtkColorChooser
instead of the deprecated GtkColorSelection and b) match this
change. Pointed out in
https://bugzilla.gnome.org/show_bug.cgi?id=721045
2014-01-04 18:52:46 -05:00
2f4b577165
GtkInfoBar: Set a more accurate accessible role
...
And update the a11y tests to match. Pointed out in
https://bugzilla.gnome.org/show_bug.cgi?id=721042
2014-01-04 17:44:14 -05:00
e904d1c97d
GtkDrawingArea: Set an accessible role
...
And update the a11y tests to match. Pointed out in
https://bugzilla.gnome.org/show_bug.cgi?id=721040
2014-01-04 17:41:23 -05:00
3bc5ab4fcd
a11y tests: Add a test for multi-link labels
2014-01-04 10:54:03 -05:00
5845356d66
GtkLabelAccessible: Implement AtkHypertext
...
This commit makes the label accessible implement AtkHypertext,
which returns a AtkHyperlink object for each link in the text.
At the same time, add AtkHyperlinkImpl objects as children
to the label accessible.
Also some private API to indicate that links have changed, and
call that from GtkLabel when needed.
Adjust expected output of the affected a11y tests.
https://bugzilla.gnome.org/show_bug.cgi?id=721410
https://bugzilla.gnome.org/show_bug.cgi?id=721421
2014-01-04 10:54:03 -05:00
3c5bb9722b
a11y tests: Prepare to dump AtkHypertext
...
This will be used for links in labels soon.
As a side-effect, the output for AtkHyperlinkImpl changes
slightly. Update expected output accordingly.
2014-01-04 10:54:03 -05:00
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
8a12a88b75
Add a menubutton to the a11y tests
2013-12-20 13:31:08 -05:00
30a4e4ca0f
Fix accessibility tests for real
...
The character count had to be updated as well.
2013-12-16 20:39:00 -05:00
dcff5295f7
Fix a11y testsuite for about dialog changes
2013-12-16 14:58:03 -05:00
70e7b1b06d
Fix up accessibility tests
...
The output had gotten debug spew in it.
2013-10-28 07:20:11 -04:00
