Accessible Design for Tor Onion Sites: Usability Over Latency

Tor hidden service visitors span a wide spectrum of access conditions. Users in censored countries with limited bandwidth (Venezuela, Cuba, Yemen) experience compounded latency from their slow national connections plus Tor's circuit latency. Users with Tor Browser's Security Level set to Safest have JavaScript disabled - entire sections of JavaScript-dependent sites are invisible to them. Users in countries with aging device infrastructure use older browsers with limited CSS support. Designing with these constraints in mind is not just ethical - it directly expands the audience that can access your service. A site requiring JavaScript and 5+ MB of resources to load might reach 30% of potential visitors; a well-optimized text-first site might reach 95%.

Prioritize content delivery before decoration and interactivity. HTML renders without CSS or JavaScript; CSS renders without JavaScript. Structure your content so that a user receiving only HTML sees all essential information clearly organized. Add CSS as progressive enhancement (improves layout but is not required for core function). Add JavaScript as progressive enhancement (improves interactivity but is not required for core function). Test your site by disabling CSS, then disabling JavaScript, in Tor Browser. If core content is inaccessible without JavaScript, rewrite it as server-side rendered HTML. Static site generators (Hugo, Jekyll) produce HTML-first content naturally.

Images are the largest contributor to page weight for most sites. Optimization strategies: use WebP format (better compression than JPEG/PNG), serve appropriately sized images (not full-resolution images scaled down by CSS), lazy-load images below the fold (defer loading until the user scrolls to them), provide alt text for all images (for users in Safest mode who see images in some cases), and consider whether images are necessary at all for content-heavy sites. For video, avoid inline video players that require JavaScript. Provide download links for video content instead. Audio similarly - provide downloads rather than HTML5 audio players for sites where music or podcast content is important.

Some JavaScript interactive patterns have CSS-only alternatives that work with JavaScript disabled. Accordion/disclosure: CSS checkbox hack or

/

HTML elements provide accordion behavior without JavaScript. Modal dialogs: CSS-only modals using :target or checkbox hack work without JavaScript. Dropdown navigation menus: CSS :hover-based dropdowns work without JavaScript (though accessibility for keyboard users requires consideration). Tabs: CSS-based tabs using :target work for simple tab content. These CSS-only alternatives are not as flexible as JavaScript implementations but provide functional versions that work in Safest mode.

Ensure all content is server-side rendered - no content that requires JavaScript API calls to load. Dynamic content (comments, user-submitted content) should be rendered by the server and included in the initial HTML response. Infinite scroll patterns should be replaced with traditional pagination (HTML links to page 2, page 3). Search results should be rendered server-side from URL parameters. Authentication-gated content still requires JavaScript for secure forms but the content returned after authentication should be server-rendered. This approach serves content to all users regardless of JavaScript capability while still allowing JavaScript to enhance the experience for users who have it enabled.