Bug 73832
| Summary: | [Gtk] Expose 'read only' state of non-text widgets | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Joanmarie Diggs <jdiggs> |
| Component: | Accessibility | Assignee: | Nobody <webkit-unassigned> |
| Status: | UNCONFIRMED | ||
| Severity: | Normal | CC: | bugs-noreply |
| Priority: | P3 | Keywords: | Gtk |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| URL: | http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/form/test_CheckBox.html | ||
| Bug Depends on: | |||
| Bug Blocks: | 30796 | ||
Joanmarie Diggs
Certain non-text widgets can have a 'read only' state, such as cb4 on this test page [1]. Because this state is not exposed to ATs, ATs have no way to present this condition to the user.
While this *could* be done via an object attribute (for instance), I personally think that the read-only state is, well, a state. ;) For this reason I opened the following ATK/AT-SPI bugs: [2][3]. I also think that this condition/state is sufficiently rare that it would be worth waiting for the creation of the new ATK state rather than going the object-attribute (or similar) route.
[1] http://archive.dojotoolkit.org/nightly/dojotoolkit/dijit/tests/form/test_CheckBox.html
[2] https://bugzilla.gnome.org/show_bug.cgi?id=665598
[3] https://bugzilla.gnome.org/show_bug.cgi?id=665599
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |