We have the concept of designing for accessibility for the disabled, but we need to include the idea of designing on the web for accessibility to those who are reaching us through national firewalls, or simply concerned with privacy and security. In cooperation with Reporters without Borders, I’m putting together a guide for safer anonymous use of the Internet, this summer.<\/p>\n
Right now, we’re documenting and collecting methods that compromise privacy even with the use of anonymity software such as Tor.<\/p>\n
Use of some technologies will make a site inaccessible to people practicing “safe surfing.” For example, people with concerns about strong anonymity will surf with javascript turned off in their browsers. If you are concerned that your site should be accessible particularly to users in countries with free speech restrictions, you need to design a site that does not use javascript for anything crucial to navigation or understanding the site.<\/p>\n
Javascript can be “leaky” — as a server-side technology (code that is sent from the web site to be run on the surfer’s machine) the user has no control over what a bit of javascript code will ask for. Javascript can reveal the true IP number of a user shielded by a proxy, among other information.
\nAnother piece of code we advise anonymity users to bypass is the Adobe PDF plug in. At the time I write this, this plug in ignores the proxy settings on the user’s machine, and fetches the file to display in the browser window directly. I’ve sent email to Adobe hoping they’ll fix this problem before we publish our guide in the fall.<\/p>\n
If you are a person who plays with network security, we’d like you to find ways that plug-ins, applications and system settings can by-pass proxy settings and compromise user anonymity. Comment here contact us through http:\/\/tor.eff.org\/<\/a>. Thanks!<\/p>\n","protected":false},"excerpt":{"rendered":" We have the concept of designing for accessibility for the disabled, but we need to include the idea of designing on the web for accessibility to those who are reaching us through national firewalls, or simply concerned with privacy and security. In cooperation with Reporters without Borders, I’m putting together a guide for safer anonymous […]<\/p>\n","protected":false},"author":354,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-10","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/anonymous\/wp-json\/wp\/v2\/posts\/10","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/anonymous\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/anonymous\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/anonymous\/wp-json\/wp\/v2\/users\/354"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/anonymous\/wp-json\/wp\/v2\/comments?post=10"}],"version-history":[{"count":0,"href":"https:\/\/archive.blogs.harvard.edu\/anonymous\/wp-json\/wp\/v2\/posts\/10\/revisions"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/anonymous\/wp-json\/wp\/v2\/media?parent=10"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/anonymous\/wp-json\/wp\/v2\/categories?post=10"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/anonymous\/wp-json\/wp\/v2\/tags?post=10"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}