Bug 517380 - [GTK3] Improve support for accessibility
Summary: [GTK3] Improve support for accessibility
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.7   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: triaged
Depends on: 158794 220025 220031 221909 312105 318786 405813 424983 470031 527965 543949 543988
Blocks:
  Show dependency tree
 
Reported: 2017-05-29 10:26 EDT by Eric Williams CLA
Modified: 2021-05-27 00:35 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Williams CLA 2017-05-29 10:26:07 EDT
As the title implies, general overarching bug for GTK3 accessibility work in 4.8.
Comment 1 Eric Williams CLA 2017-08-02 13:25:23 EDT
Current state of affairs: 

GTK3 accessibility seems to be non-working all together. Orca crashes and hangs when trying to read anything SWT on GTK3.

GTK2 support works well until Mars (4.5) and then stops working reliably. There are bits and pieces that work well past Mars but nothing consistent.
Comment 2 Eric Williams CLA 2017-11-23 16:43:56 EST
Update:

Basic accessibility should work now in SWT-GTK3. I estimate this will cover 80% of all use cases. I am in the process of opening other accessibility bugs for more fine-tuned issues, as well as evaluating the validity of currently open bugs.

If you encounter an accessibility issue that isn't fixed and is currently not being tracked, please file a new bug and I will add it here as a dependency.
Comment 3 jose vilmar estacio de souza CLA 2017-11-26 05:47:01 EST
When time allows, would it be possible to investigate bugs #314996, #424983, #319467 and #318786?
Thanks.
Comment 4 jose vilmar estacio de souza CLA 2017-11-26 06:02:11 EST
One more bug that could be investigated: #322396
Comment 5 Eric Williams CLA 2017-11-27 10:10:07 EST
(In reply to jose vilmar estacio de souza from comment #3)
> When time allows, would it be possible to investigate bugs #314996, #424983,
> #319467 and #318786?
> Thanks.

(In reply to jose vilmar estacio de souza from comment #4)
> One more bug that could be investigated: #322396

Absolutely!
Comment 6 Eric Williams CLA 2019-06-06 15:47:33 EDT
Unassigning myself as this is an umbrella bug.
Comment 7 Eclipse Genie CLA 2021-05-27 00:35:44 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.