NVRA provides free NVDA remote relay servers around the world, so everyone can have low-latency remote access. We currently have 17 locations available.
What's the point of this thing? How do I use it?
When you control another computer using NVDA Remote, you'll often connect to a relay server. The most common one is NVDARemote.com. when you do this, you're sending your key presses to that server, which forwards them on to the controlled machine. The controlled machine sends back speech, which goes through the relay server once again before being forwarded back to you.
When one or both machines are far away from the relay server, it takes longer for the key presses and speech data to get from one machine to the other. Using a screen-reader is a very unpleasant process when latency is high, since we often need to press several keys in quick succession and listen to the responses. This latency is also present on mainstream remote access solutions and on the internet in general, but screen-reader usage is a more interactive process than looking at a screen. A sighted person can glance at a screen, process the information, and move the mouse to the button they need. A screen-reader user may need to navigate through many controls before reaching that button, and will need immediate feedback for all of them. NVRA aims to solve this problem by supplying relay servers in many common locations around the world, making it easy for NVDA Remote users to find a nearby location that provides low latency.
To use any of these servers, simply enter the domain (such as tx.nvra.io) in the host field of the connect dialog.
US and Canada
- Los Angeles: ca.nvra.io
- Denver: co.nvra.io
- Miami: fl.nvra.io
- Atlanta: ga.nvra.io
- Chicago: il.nvra.io
- New York City: ny.nvra.io (or just nvra.io)
- Dallas: tx.nvra.io
- Seattle: wa.nvra.io
- Toronto: can.nvra.io
- Sydney, Australia: au.nvra.io
- Frankfurt, Germany: de.nvra.io
- Bangalore, India: in.nvra.io
- Tokyo, Japan: jp.nvra.io
- Amsterdam, Netherlands: nl.nvra.io
- Singapore: sg.nvra.io
- Johannesburg, South Africa: za.nvra.io
- London, United Kingdom: uk.nvra.io
Get In Touch
Please use the contact page on TTHub.org for any feedback or questions.
If these servers are not working well for you and you have a suggestion for a new location, I'd love to hear from you. This project runs off the TTHub infrastructure, so more remote servers also means more TeamTalk locations.