Executive Summary

Full report

On this page

The 2IA site is a content‐rich WordPress site aimed at civil‐libertarian activists, but it currently functions more as a static research repository than an interactive platform. It features extensive “dossier” pages and issue analyses, but lacks obvious calls to action (CTAs) for donating or volunteering. There is no donation form or volunteer sign-up flow – activists are given instructions on how to help, but no easy way to act. The site’s UX suffers from dense text blocks and jargon-heavy language, with minimal visual hierarchy or engagement prompts. Key quick-win fixes include adding clear action buttons (“Donate Now”, “Join Our Volunteer Team”) as recommended by UX best practices【51†L158-L161】【107†L171-L179】, and improving accessibility (e.g. providing alt text for images and ensuring color contrast meets WCAG 2.1 standards【42†L492-L500】【44†L795-L803】). Medium‐term improvements involve building actual donation and volunteer workflows (forms, integrations with payment tools), reorganizing information architecture, and optimizing performance. Long-term work could include a refreshed theme or platform that better supports dynamic features (e.g. events, member accounts) and advanced security. The following report maps the site’s structure, evaluates its UX/UI and compliance, benchmarks six comparable activism/volunteer platforms, and presents prioritized recommendations with a phased roadmap.

1. Site Structure and Content Audit

Platform: The site is built on WordPress (“2IA – Two Identities Of Anonymous” – 2ia.org). It uses a custom theme (“twoia-intelligence”) and appears to have no user login or member areas. The homepage and top menu link to the main sections: Home, Start Here, Research Archive, Methodology, Support, and About. Subpages include “Volunteer” and “Donate” under Support, and numerous “Dossier” pages under About. A footer lists “Research areas” categories (e.g. Surveillance Architecture, Metadata and Identity, AI & Sentiment Analysis【91†L114-L121】) and legal links (Privacy, Ethics, Contact, etc). The “Research Archive” page outlines planned content areas, but currently all category pages (e.g. Surveillance Architecture) show no posts (empty archives). In short, the IA consists of static pages with editorial content rather than user-generated or dynamic content. There is a site-wide search box but no login, forum, or membership features.

graph TD
  Home["Homepage"] --> Start["Start Here"]
  Home --> Archive["Research Archive"]
  Home --> Methodology["Methodology"]
  Home --> Support["Support & Legal"]
  Home --> About["About 2IA"]
  Support --> DonatePage["Donate Page"]
  Support --> VolunteerPage["Volunteer Page"]
  Support --> Newsletter["Newsletter Signup"]
  About --> Ethics["Ethics & Civ. Liberties"]
  About --> Contact["Contact Info"]

Figure: Simplified site architecture (main pages and key flows).

Content Types: Almost all content is static editorial text. There are no blog posts or news items published yet (even “Archives: May 2026” appears empty). The site’s voice is formal and instructive (see e.g. “2IA exists to make… systems legible…”【91†L28-L36】). It uses longform prose and bullet lists (e.g. issue descriptions on Home【96†L52-L61】, Dossier lists on About【91†L30-L39】). Multimedia is sparse: the homepage contains an illustrative “Who Cares Wizard” widget and some hazard‐icon graphics, but no videos. No alt text is provided (e.g. the hazard sign image lacks a text label). Metadata appears minimal: pages have titles and headings, but likely no metadata beyond the visible headings (the theme claims not to use external assets【92†L28-L31】). There is a standard WP footer with copyright.

User Flows: With no login or form, the only flows are navigation-based. For example, a visitor can browse “Start Here”, read Dossiers, then click “Support” to see how to help. However, clicking “Volunteer” or “Donate” currently just shows analysis text, not an actual sign-up form. In practice, a volunteer would have to email or “lawfully contact” the project (instructions are given, but no form). A donation query is similarly unsupported (the “Donate” page is advice, not a payment page). Thus onboarding is non‐existent – users seeking to engage are given suggestions but no direct mechanism.

2. UX/UI and Accessibility Evaluation

Usability and Clarity: The site’s visual design is very plain (black text on white background), which has good contrast but feels stark. Navigation is textual (no icons), so menus and headings dominate. Headings are well-used (H1, H2, etc.) for structure, and bullet lists break up content. However, key actions are buried or missing. For instance, the home page lists issues (“Policy laundered through procurement”), but no clear next-step like “Take Action” buttons. Nielsen/NNg guidelines emphasize that nonprofit sites should have immediate, clear CTAs (e.g. “Donate”, “Sign Up”)【51†L158-L161】. In 2IA’s case, the only calls on the homepage are internal (“Start Here”, “Methodology”), not external actions. Even on the Support page, “Dossier 03: Donate” is just a textual guide. Activists looking to volunteer or donate will not find the usual buttons or forms.

By contrast, benchmark examples use prominent CTAs. The ACLU’s PeoplePower page boldly displays “Sign Up for Our Volunteer Team” at the top【74†L25-L32】. MoveOn’s volunteer page includes “Join” buttons for communities【71†L50-L58】 and the donation page clearly labels “Donate to MoveOn Civic Action”【101†L13-L20】. These direct links to action (with action-oriented wording) are currently missing from 2IA. According to Giveffect/NNG, CTA labels should start with strong verbs like “Donate”, “Volunteer”, “Sign Up”【107†L112-L119】. The 2IA site would benefit from applying these tips: for example, adding a bold “Donate Now” or “Become a Volunteer” button on every page, as in conventional advocacy sites【51†L158-L161】【107†L171-L179】.

Information Architecture: Currently, information flows in large text blocks. The main menu groups content by type (Archive, Methodology), which is logical for research, but may confuse activists who want action links. A better IA could break content into “Issues” vs. “Take Action” sections, with quick links (e.g. “Volunteer”, “Donate”) highlighted. For example, many nonprofits place Donate and Volunteer links in the header/menu for easy access【51†L158-L161】. The footer on 2IA does list “Support → Donate” and “Support → Volunteer” under “Legal and ethics”, but these are text links styled small. A quick improvement is to re-arrange the menu so that “Support 2IA” (or “Get Involved”) is a main item containing Donate/Volunteer, rather than buried in legal links.

Content Clarity: The writing is thorough but highly technical (e.g. “metadata abuse”, “adverse-action notice”). For broader engagement, content should be more user-friendly. NNGroup advises using concise language and explaining the mission clearly【51†L158-L161】. 2IA’s mission (“Two Identities of Anonymous”) is explained on the About page, but the average reader might not grasp it quickly. We recommend adding a brief tag line or intro (e.g. “We help people hold surveillance systems accountable”) in plain language, and use short paragraphs and bullet points. The site already has some bullets (e.g. the section “What is broken” on the homepage【96†L52-L61】) which is good; more of these for actions ("Key Actions: X, Y, Z").

Accessibility (WCAG 2.1): The site lacks some basic accessibility features. For example, WCAG 2.1 SC 1.1.1 requires text alternatives for non-text content【42†L492-L500】. 2IA’s site has at least one meaningful image (the hazard sign [Image]) but it has no alt text, which would fail SC 1.1.1. We should ensure every image (e.g. logos, icons) has an alt="..." description. SC 1.4.3 requires 4.5:1 contrast for text【44†L795-L803】. The main text (black on white) meets this, but any gray or colored text (e.g. in menus or infographics) should be checked. For instance, the menu “Toggle” text on a gray background might not have sufficient contrast. It’s recommended to test with a tool (e.g. Lighthouse) and adjust colors as needed.

Keyboard navigation and screen-reader usability should be verified. The site appears to use standard HTML (menu toggle, search field), but we should confirm focus order, form labeling, and ARIA roles. For example, ensure the hamburger “Toggle menu” button is keyboard-accessible and labeled (aria-label) for screen readers. Altogether, improving alt attributes and color contrast will make the site WCAG-compliant.

Mobile/Responsiveness: The theme seems responsive (menus collapse on small screens). However, important CTAs are not above the fold on mobile. It would be best to place at least one clear CTA button (“Donate” or “Join”) high on the homepage and Support page, so mobile users see it immediately without scrolling. Touch targets (buttons/links) should be large enough per mobile guidelines. We should also verify the site’s viewport meta (so it scales correctly) and that fonts are legible on small screens.

3. Privacy, Security, Hosting, Performance & Compliance

Privacy: 2IA prides itself on privacy. Its Privacy Policy explicitly states the WordPress theme “does not add analytics, tracking pixels, external fonts, CDN assets, or unnecessary cookies”【92†L28-L31】. In other words, visitor reading is not being tracked. Comments are disabled, and any future forms are advised to minimize data【92†L33-L42】【92†L47-L55】. This is an excellent baseline: it means basic compliance with GDPR/CCPA (no third-party tracking). However, if new features are added (e.g. newsletter or donation forms), the policy notes these must be reviewed for consent and data minimization【92†L63-L66】【92†L67-L70】. In practical terms, any email sign-ups or donation gateways should explicitly state their privacy handling (e.g. no selling data, retention period).

According to GDPR guidance, charities must collect only the personal data needed and protect it【103†L377-L384】【103†L449-L452】. For example, if 2IA introduces a volunteer application form, it should only ask for necessary information (name, email, interest area) and explain how it will be used. Tools like Mailchimp (for newsletters) or ActBlue (for donations) already have GDPR-compliant features, but this needs to be documented in the Privacy Policy. We should also add a cookie/consent banner if any analytics or targeted ads are introduced. Currently, the site likely only sets a basic PHP session cookie; even that should be disclosed. Adding a simple banner (“This site uses no tracking cookies by default – read our Privacy Policy”) would align with the transparent practice already signaled by the theme.

Security: The site uses HTTPS (as seen in the URL) so data in transit is encrypted. Given it’s WordPress, we must follow WP security best practices. Nonprofit Tech for Good recommends keeping WordPress core, plugins, and themes updated and deleting unused plugins【94†L88-L96】. Since 2IA currently has few plugins, any new plugin (e.g. a donation or form plugin) should be vetted for vulnerabilities. Changing the default “admin” username and using strong passwords (or two-factor auth) is also crucial【94†L88-L96】. We should enforce HTTPS and consider a Web Application Firewall or CDN (e.g. Cloudflare) for DDoS protection, especially if the site grows. The hosting environment matters: low-cost hosts often have weaker security, whereas managed WordPress hosts (WP Engine, Flywheel) include automatic backups and malware scanning【94†L110-L118】. Investing in premium hosting can prevent downtime or hacks. As a precaution, the site should have regular backups, and file permissions locked down.

Performance: As a primarily text site, 2IA is not media-heavy, but performance still matters. Running a Lighthouse audit could reveal opportunities. We should minify CSS/JS, enable Gzip compression, and leverage browser caching. Any images (like the hazard icon or the “Who Cares Wizard” graphic) should be optimized (compressed) for web. Lazy-loading for below-the-fold images is advisable. If we keep WordPress, a caching plugin (e.g. WP Super Cache) is a quick win. For scale, a CDN could help load times globally. According to performance best practices, above-the-fold content and CTAs should load first【107†L171-L179】 – this means the menu and key buttons should render quickly. We should ensure critical CSS is inlined and scripts don’t block rendering.

Legal/Compliance (GDPR/CCPA): Legally, if 2IA ever processes data on EU or California residents, GDPR/CCPA apply. The usercentrics guide emphasizes that nonprofits do need a lawful basis for all personal data (even volunteer sign-ups)【103†L377-L384】. In practice, this means implementing data subject rights: an easy way to access or delete one’s info. The Privacy Policy already covers many GDPR principles (e.g. data minimization【103†L377-L384】, transparency【103†L377-L384】). For CCPA (California), if the site remains as-is (no paid data collection), risk is low. But we should avoid “selling” data (easy to note “We do not sell personal info”). In short, keep the site data footprint minimal, add cookie consent if we ever place trackers, and maintain clear privacy notices. 2IA’s existing policy and ethos align well with GDPR’s goals of transparency and minimalism【103†L377-L384】【103†L449-L452】, which should be explicitly reinforced as features are added (e.g. a note on the volunteer form: “Your info is confidential and only used to contact you”).

4. Benchmarking & Best Practices

Best Practices: Common successful patterns include prominent, action-oriented CTAs (“Donate Now”, “Sign Up”) and minimizing friction between interest and action【107†L112-L119】【51†L158-L161】. All benchmarks have clear donation links (in header or sidebar) and dedicated volunteer sections. They often profile volunteer roles or events, making it easy to see what volunteers will do. For example, Amnesty explicitly lists roles (with Apply links)【99†L189-L193】, while MoveOn connects volunteers to “Mobilizer” communities【71†L50-L58】. Many sites also use progressive engagement: short form sign-ups (“Join our newsletter”), followed by deeper involvement (event RSVPs, training, leadership roles). Visual design highlights CTAs: bold colors and whitespace are used so buttons “pop”【107†L171-L179】. In summary, 2IA should emulate these practices by creating distinct entry points for volunteering and donating, using strong verb-driven labels, and ensuring forms are easy to find.

5. Prioritized Recommendations and Roadmap

Quick Wins (Low Effort):

• Add Clear CTAs: Place bold “Donate” and “Volunteer” buttons on the homepage and all section pages. Use verbs like “Donate Now”, “Join Our Volunteer Team”【51†L158-L161】【107†L112-L119】. For example, move the current “Dossier 03: Donate” text into a button linking to a real form.
• CTA Design: Make CTA buttons high-contrast and above-the-fold【107†L171-L179】. Use a consistent color (e.g. a bright accent) so users can quickly spot them.
• Improve Text Clarity: Rewrite key messages in plain language. Add short summaries of 2IA’s mission (e.g. a tagline on Home). Use bullet lists to break up complex content. For instance, a one-page “How to Help” summary could bullet-step involvement options.
• Accessibility Fixes: Add alt text to all images (e.g. alt="Hazard symbol graphic"). Ensure link text is descriptive (avoid generic “click here”). Check and fix color contrast as needed.
• Mobile UI Tweaks: Ensure the mobile menu is labeled for screen readers. Increase font sizes slightly and make touch targets (buttons, links) large enough. Verify responsiveness on popular devices.

Medium Effort:

• Donation Flow: Integrate a real payment form. This could be an embedded ActBlue/PayPal or a custom form. Example: a simple HTML form could be:

  <form action="https://donate.2ia.org/process" method="POST">
    <label for="amount">Donation Amount:</label>
    <input type="number" id="amount" name="amount" min="1" required>
    <button type="submit">Donate Now</button>
  </form>

(In practice, the action URL would point to a payment gateway.) Ensure the form is accessible (labels tied to inputs) and secure (uses POST over HTTPS).

• Volunteer Signup: Build a volunteer interest form (or integrate a tool like Airtable/form-builder). Capture basic info: name, email, skills/interests. For example:

  <form id="volunteerForm">
    <label for="volunteer-name">Name:</label>
    <input type="text" id="volunteer-name" name="name" required>
    <label for="volunteer-email">Email:</label>
    <input type="email" id="volunteer-email" name="email" required>
    <label for="volunteer-skills">Skills:</label>
    <textarea id="volunteer-skills" name="skills"></textarea>
    <button type="submit">Join Our Team</button>
  </form>

Implement form handling (e.g. email notifications to organizers). Ensure privacy notice (“We will not share your info”).

• Navigation & IA: Reorganize menus so that “Get Involved” (or similar) groups Donate, Volunteer, Newsletter signup. Remove redundant links. Rename “Support” to “Get Involved” or “Support 2IA” for clarity. Add a top-level Donate link (using a button style).
• Performance Improvements: Enable a caching plugin and optimize assets. Compress images (use WebP or SVG for icons). Defer any non-critical JavaScript. Run Google Lighthouse to identify any slow elements (e.g. large CSS files).

Long-Term (High Effort):

• Site Redesign: Consider a refreshed theme or rebuilding to modernize the look and support new features. This might include responsive templates (e.g. Bootstrap-based), a CMS overhaul, or even migrating to a static site generator if dynamic features remain minimal.
• Volunteer Community Features: Build a member area or forum where volunteers can sign in, share reports, and collaborate. Integrate calendar/events (e.g. mobilizations, FOIA filing workshops). Possibly use dedicated volunteer-management software or a CRM (e.g. NationBuilder or CiviCRM).
• Donation Infrastructure: If donations scale up, implement a formal donation management system for receipts, recurring gifts, and donor tracking. Ensure PCI compliance (for credit cards).
• Content Expansion: Hire or solicit volunteer writers to regularly publish “issue hubs” and toolkits. Add visual content (infographics, short videos) to explain complex topics. Consider accessible formats (transcripts for any multimedia).
• Legal Compliance: Audit all data collection under GDPR/CCPA. Appoint a data custodian to handle requests for data export/deletion. Possibly implement a Consent Management Platform if analytics/marketing are added.

Phased Roadmap: Below is a sample timeline:

Throughout, ensure monitoring (traffic, Lighthouse scores, conversion rates) to iterate. Quick design prototyping and user testing with actual activists can validate each change.

6. Content Strategy and Volunteer Engagement

Messaging & Tone: Emphasize transparency and empowerment. The content should clearly tie 2IA’s research to real-world actions. For example, after each investigation, end with specific “What You Can Do” steps (e.g. “Submit this FOIA request”, “Share this report with your local council”). This aligns with the “ladder of engagement” concept – move people from reading to acting. Usercentrics notes that nonprofits should “collect only what you need” and treat supporters like customers【103†L449-L452】. In practice, this means being very clear about how volunteer or donor data will be used, which builds trust. Highlight success stories (“We helped pass X regulation”) to motivate contributors.

Volunteer Features: Suggestions include:

• Email List/Newsletter: Implement a regular newsletter with updates; feature an easy signup (perhaps with Mailchimp). Make it private (no public signup form visible means currently none).
• Community Platform: Create a forum or Slack channel for volunteers to discuss tactics. This fosters a sense of community (MoveOn and Indivisible use volunteer networks for peer support【71†L50-L58】【62†L129-L133】).
• Recognition: A volunteer “wall of fame” or shoutouts for contributions can boost engagement (common in nonprofits).
• Training/Events: Offer occasional webinars or local meetups (virtual or in person) for volunteers to learn skills (record setting, journalism, digital security). List these on the site (e.g. calendar of events).

Moderation/Publishing Workflows: Currently, content appears to be authored by a core team. As contributors grow, establish roles: e.g. editor, fact-checker, social media manager. Use the site’s CMS (WordPress) roles to grant limited access to volunteer writers. Create a clear “Corrections” page (the nav has one) and process where volunteers can submit errata or FOIA outcomes. Provide guidelines (tone, citation style) so that guest content meets quality standards.

Technical Stack Options: Sticking with WordPress is viable given its familiarity and plugin ecosystem (forms, donation, SEO, backups). WP can be secured and scaled. Alternatively, a static site generator (Hugo/Jekyll) could be considered if the site remains content-centric, offering speed and security (no DB). If budget allows, using a headless CMS with a React/Next.js front end could add interactivity, but has overhead. For now, open-source WordPress plus plugins (WP Super Cache, Security Scanner) is a practical choice. For payments, integrate ActBlue or Stripe (no monthly fee). For email, use a reputable ESP (Mailchimp, SendinBlue) with explicit opt-in forms. All tools chosen should align with the privacy-first approach (many give GDPR settings for forms).

7. Visual Mockups and Diagrams

【86†L187-L195】 Nonprofit web templates typically highlight “Donate” and “Get Involved” sections prominently. The example homepage wireframe below (from Visily’s nonprofit template) illustrates these conventions. Notice the large “Donate Now” button and clear navigation – 2IA should aim for similar clarity.

【87†embed_image】 Figure: Sample homepage wireframe (nonprofit template) with prominent Donate/Volunteer CTAs.

【86†L187-L195】 A typical “About Us” page emphasizes mission and team, followed by an email signup or small CTA. The mockup below shows an About page with a mission statement, team photos, and a “Join Us” button. 2IA’s About page could adopt a similar structure (e.g. short intro + profile + link to volunteer form).

【88†embed_image】 Figure: Example “About Us” page wireframe (with mission, team, and CTA).

【86†L187-L195】 For donation pages, one common pattern is a list of projects or funding goals. The wireframe below shows donation “projects” with descriptions and join/donate buttons. 2IA could use this layout to feature multiple campaigns (e.g. “Support FOIA research”, “Fund server hosting”).

【89†embed_image】 Figure: Sample donation/projects page wireframe (list of giving opportunities).

【86†L187-L195】 Even “Contact” pages benefit from clear design: a brief intro, a form, and social links. The example below has a contact form on the left and staff info on the right. For 2IA, a simple “Volunteer Interest” form or secure submission box could follow this pattern.

【90†embed_image】 Figure: Example “Contact Us” page wireframe (contact form and info panel).

graph LR
    subgraph Donation_Flow
      A[Visitor] --> B(Home)
      B -->|Clicks Donate CTA| C(Donate Page)
      C --> D[Donation Form Submission]
      D --> E(Thank You Page)
    end
    subgraph Volunteer_Flow
      A -->|Clicks Volunteer CTA| F(Support Page)
      F --> G(Volunteer Info Section)
      G --> H[Volunteer Form Submission]
      H --> I(Confirmation & Email)
    end

Figure: Simplified user flows. (Top: Donation flow; Bottom: Volunteer sign-up flow.)

The diagrams above illustrate how a user’s journey should proceed with the recommended improvements. By adding prominent “Donate” and “Volunteer” CTAs on the homepage, a visitor can directly reach the respective form, submit it, and receive confirmation. Ensuring these flows are short and clear is key: for instance, NN/g notes that simplified donation processes keep users on track【51†L65-L69】.

Conclusion: By reorganizing information architecture, adding clear CTAs, and implementing actual engagement workflows, 2IA can transform from a static archive into a participatory platform. These changes—guided by nonprofit web best practices【51†L158-L161】【107†L112-L119】 and accessibility standards【42†L492-L500】【44†L795-L803】—will make the site far more welcoming to civil-libertarian volunteers and donors. The phased roadmap above breaks these tasks into achievable steps. With improved UX design, compliance measures, and volunteer features, the revamped site will better fulfill its mission of empowering the public with intelligence and action.

Sources: W3C WCAG 2.1 guidelines【42†L492-L500】【44†L795-L803】; Nielsen Norman Group on nonprofit UX【51†L158-L161】; Giveffect on CTA design【107†L112-L119】【107†L171-L179】; 2IA site pages (2ia.org)【91†L114-L121】【92†L28-L31】; ACLU PeoplePower【74†L25-L32】; EFF volunteer page【73†L37-L40】; Amnesty USA volunteer page【99†L189-L193】【99†L239-L242】; Indivisible site【62†L129-L133】【62†L135-L140】; MoveOn volunteer page【71†L50-L58】 and donate info【101†L13-L20】; Idealist/VolunteerMatch page【79†L7-L10】; Nonprofit Tech for Good (WordPress security)【94†L88-L96】【94†L110-L118】; Usercentrics (nonprofit GDPR)【103†L377-L384】【103†L449-L452】.