Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility for blind users #1343

Closed
cyberduck opened this issue Nov 20, 2007 · 13 comments
Closed

Accessibility for blind users #1343

cyberduck opened this issue Nov 20, 2007 · 13 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Nov 20, 2007

d14a9f0 created the issue

I am a blind Mac user using VoiceOver. I'm finding the program easy to use and for the most part, very accessible with the VoiceOver screen reader. There are, however, two areas I've thus far noticed that aren't readable with VoiceOver: The progress of transfers and any errors encountered during transfers. In both instances, VoiceOver sees the tables, however, the objects within the tables, i.e. the information, are unidentifiable resulting in VoiceOver saying, "unknown."

Unfortunately, I'm not familiar with Cocoa enough to suggest how this might be fixed. I am, however, willing to test newer versions for better VoiceOver compatibility. If I can help in any other way, please let me know steve@sawczyn.com

Thanks,

Steve

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 20, 2007

@dkocher commented

This has been reported before in #1146 but has not been resolved yet. I will try to identify the problem and let you know about the build to test it with.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 20, 2007

@dkocher commented

You reported against version 2.7.3. Have you also the same problem when running 2.8.1? I have just tested with Voice Over switched on and can get it to speak all text elements of a transfer (e.g. filename, status and progress).

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 20, 2007

d14a9f0 commented

My apologies, I'm using v 2.8.1 (3290) just downloaded last night. I'll update the ticket properties to reflect the correct version.
I'm using VoiceOver under Leopard 10.5.1 in case that throws another problem in the mix. I've been working more with it today and no matter what I try, can not get the information read as the table objects are identified as unknown and as such, VoiceOver won't allow me to "interact" with them. I even triednot allowing completed transfers to clear thinking that the text might become static and that VoiceOver might "see" it differently.
When you switched VoiceOver on, did you navigate to the transfer window using the mouse, or the VoiceOver commands? It might be possible for VoiceOver to read the text if the mouse is hovered over it, however, for a totally blind user, this won't work. I have seen otehr programs where this has been the case -- VoiceOver doesn't recognize an object, however, if it's clicked, it can see the data within the object. I'll keep testing, but so far, the major issue seems to just be the tarnsfers window, main window sems to work fine, remote file list works perfect, just the transfers and potential error messages aren't identified.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 20, 2007

@dkocher commented

Thanks for the additional information. As you describe, it only works when hovering over the transfer item with the mouse, but it will say 'unknown' if it gets focus by using the keyboard.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 20, 2007

@dkocher commented

Note to self. The problem is that a item in the transfer window table view is a custom view. Refer to http://developer.apple.com/ue/accessibility/accessibilityincocoa.html

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Feb 2, 2008

d14a9f0 commented

I've skipped a few versions, but find the issue with reading the transfer tables still exists. Maybe a temp work around might be to add a status line presenting the same information? A user could enable/disable this extra status line under view. Of course it's easy for me to suggest something like this as I have no idea how much work it would take to implement :).

Steve

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 13, 2009

@dkocher commented

Milestone 3.2 deleted

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 28, 2010

@dkocher commented

#5122 closed as duplicate.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 23, 2011

@dkocher commented

#6166 closed as duplicate.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Aug 23, 2011

@dkocher commented

Using NSTableCellView would resolve this issue but this is only available in Mac OS X v10.7 and later.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Nov 20, 2013

@dkocher commented

In 197f130.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 12, 2015

@dkocher commented

This was inadvertently reverted in 851f139.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 12, 2015

@dkocher commented

In 2f92b56.

Loading

@cyberduck cyberduck closed this May 12, 2015
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants