Skip to content
Snippets Groups Projects
Closed (moved) Make BridgeDB's output compatible with both Vidalia & TorLauncher
  • View options
  • Make BridgeDB's output compatible with both Vidalia & TorLauncher

  • View options
  • Closed (moved) Issue created by Runa Sandvik

    A user reports that the text on bridges.torproject.org is confusing for blind users, and users with slow connections / users who block images.

    On bridges.torproject.org, blind users will be hearing a couple of references in their screen-readers to bridge entries and bridge addresses:

    • As an example, you'll get a bridge entry that looks like the following: bridge 141.[etc.]
    • Here are your bridge relays: bridge 60.[etc.]

    On bridges.html.en, we have an image illustrating how to add a bridge to Vidalia:

    • Add each bridge address one at a time in the Vidalia Network settings page, by pasting it into the 'Add a Bridge' window and then clicking the '+' sign. Adding a bridge is pictured below:

    ... but users will not see the picture and will not know whether to include bridge or not.

    Updating bridges.html.en is easy to do, but can we please do something about bridges.tpo as well? Is there a good reason for printing the bridge lines with the word bridge in front of each one?

    Linked items ... 0

  • Activity

    • All activity
    • Comments only
    • History only
    • Newest first
    • Oldest first
    Loading Loading Loading Loading Loading Loading Loading Loading Loading Loading