Wireshark-bugs: [Wireshark-bugs] [Bug 9284] Make Qtshark accessible?
Date: Sat, 07 May 2016 21:16:28 +0000

Comment # 7 on bug 9284 from
I can't check if that information is revealed to my reader since I don't know
the layout of the gui, so can't navigate to those elements.

As an example of what I experience, I captured the output from jaws, then added
some notes. All I did here was alt-tab into the main window, then press tab
until I cycled through all the elements back to the beginning. Each blank line
represents a tab.



Capture filter selector edit combo 
To set the value use the Arrow keys or type the value.

button menu 
Manage saved bookmarks. //not spoken
Press space to activate the menu, then navigate with arrow keys 
/* the menu opens, and I can select a protocol */
/*in the manage capture filters dialog, all the controls other than the initial
control, and the ok/cancel buttons are completely unaccessible */

Welcome screen list
To move through or expand items use the Arrow keys.
/* arrow keys have no decernible effect */

User’s Guide
·
Wiki
·
Questions and Answers
·
Mailing Lists
/* all of the above is spoken as if it were a  run on sentence, and I can't
interact with it */

/* there's about 5 tab elements that yield no speach when I tab to them */

/* there is a "split button" that only seems to appear when the first control
has a protocol selected */
/* maybe this is to display the packets */

Display filter selector edit combo 
Select from previously used filters.
To set the value use the Arrow keys or type the value.
/* typing here actually produces text in the box, but nothing else happens */


(In reply to Gerald Combs from comment #6)
> (In reply to Theodore from comment #5)
> > I have both the jaws and NVDA screen readers for windows. I can also test
> > using orca on Linux.
> > 
> > I'm struggling to navigate the source. Where do I find the QT code that
> > needs to be modified?
> 
> All of Wireshark's Qt widgets are defined in the ui/qt directory. Some of
> them call setAccessibleName, such as the packet list (ui/qt/packet_list.cpp)
> and protocol detail tree (ui/qt/proto_tree.cpp). Do either of those reveal
> themselves in JAWS or NVDA?


PS: both jaws and NVDA have features to display the text, so a sighted
developer doesn't need to worry about listening to the synthesizer.


You are receiving this mail because:
  • You are watching all bug changes.