I would like to share with you a problem with Wireshark for blind users.
@NVAccess NVDA, jaws, and a bit of narrator are not accessible using the Wireshark GUI.
I think that nvda is accessible with the command line, but I could be wrong on that one.
probably because the command line is more text base rather than visuals and or selection based.
@adisonverlice @NVAccess Yeah its been this way forever.
@andrew @adisonverlice It would be worth reaching out to Wireshark. If no screen reader is working with it, then it is almost certainly an issue with Wireshark itself. They are of course, welcome to download NVDA to test with. Two questions to tackle first: 1) Can you get everywhere with the keyboard (with shortcut keys as well as tab / arrows etc) - and 2) Does anything not read correctly when you get to it (eg does everything have a label & identify as the type of control it is, etc)
@NVAccess @adisonverlice Yeah this has been a longstanding issue and I haven't done anything about it myself. Not sure what others have done.
@andrew @adisonverlice I had a look through our correspondence, and I can tell you that about the only record I have is in a couple of forum posts from the old TechTalk list lamenting about the lack of accessibility of it back in 2016... While it is definitely still worth raising this with Wireshark, perhaps another avenue we could pursue is.... what do you use (or want to use) Wireshark for? Perhaps we can find a more accessible alternative to it?
@NVAccess @andrew @adisonverlice Difficulty is wireshark is the industry standard Troubleshooting tool. I found some jfw scripts that allowed some basic usage but it’s still not fully usable.
@klittle667 @andrew @adisonverlice Actually it looks like they're here on Mastodon - @wireshark are you able to give us any info about your accessibility please? We (@NVAccess) make the FOSS NVDA screen reader used to access the PC, and we've got some mutual users who are unable to use Wireshark because it is inaccessible. We would love to be able to recommend you
@NVAccess @klittle667 @andrew @adisonverlice
Hi, thank you for reaching out! We have a long standing ticket for accessibility issues: https://gitlab.com/wireshark/wireshark/-/issues/9284.
Since Wireshark is open source and is primarily developed by volunteers, development times can be slow. Feel free to add more comments to that Gitlab issue, or join our Discord (https://discord.com/invite/ts9GZCjGj5) and discuss there with the core developers.
@wireshark in that case, what can I do?
I am blind and am required to use wireshark
@adisonverlice It would be great if you could add a comment on the Gitlab thread I linked describing your concern or join our Discord (https://discord.com/invite/ts9GZCjGj5) and mention it there as well.