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.

Sign up for GitHub

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

Jump to bottom

noVNC is inaccessible #675

Open
johrstrom opened this issue Sep 11, 2020 · 4 comments
Open

noVNC is inaccessible #675

johrstrom opened this issue Sep 11, 2020 · 4 comments
Labels
area/accessibility component/dashboard enhancement This is functionality that builds upon existing functionality.
Milestone
Backlog

Comments

@johrstrom
Copy link
Contributor

johrstrom commented Sep 11, 2020 •
edited by sync-by-unito bot

noVNC is basically completely inaccessible because it's a <canvas> element with no text alternative.

It would be a huge undertaking to fix it or port to a different solution. So this ticket is likely just going to be a discussion forum for the team & community to chime in on what alternatives we could take (if any).

┆Issue is synchronized with this Asana task by Unito
@oscwiag oscwiag added this to the Needs Triaged milestone Sep 11, 2020
@johrstrom johrstrom modified the milestones: Needs Triaged, Backlog Sep 29, 2020
@johrstrom
Copy link
Contributor Author

Native VNC clients should be used if they're accessible. This means that we should probably update the native tabs to provide a link with the correct URL. We provide osc:// for our osc VNC viewer, but I wonder if say Windows/Mac will open tigerVNC when vnc:// URLs are clicked.

@johrstrom
Copy link
Contributor Author

If they have the network connectivity to a compute node.

The OSC VNC client was a bit before my time, but we may have to dig into how it worked because we do not now have connectivity to compute nodes so I don't believe it would even work now unless we proxy the tcp connection through apache...

@johrstrom
Copy link
Contributor Author

a quick read of the osc-connect docs indicates it uses an ssh tunnel so I suppose the current panels are actually as correct as they can be.

https://github.com/OSC/osc-connect/

@johrstrom
Copy link
Contributor Author

Apparently VNC clients like TigerVNC or REAL VNC are also inaccessible. Another option to investigate is X11 forwarding.

@lukew3 lukew3 added the enhancement This is functionality that builds upon existing functionality. label Jun 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/accessibility component/dashboard enhancement This is functionality that builds upon existing functionality.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@johrstrom @oscwiag @lukew3