Wiki source code of Gap Analysis
Last modified by Robert Schaub on 2026/02/08 08:24
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | = Gap Analysis - User Needs & Requirements = |
| 2 | |||
| 3 | **Status:** ✅ Analysis Complete | ||
| 4 | **Purpose:** Identify missing features by comparing against global research and best practices | ||
| 5 | |||
| |
1.4 | 6 | ---- |
| |
1.1 | 7 | |
| 8 | == 1. Analysis Framework == | ||
| 9 | |||
| 10 | === 1.1 Importance Formula === | ||
| 11 | |||
| 12 | **Importance = f(risk, impact, strategy)** | ||
| 13 | |||
| 14 | * **Risk:** What are the consequences if we don't have this feature? | ||
| 15 | * **Impact:** How many users affected? How severe? | ||
| 16 | * **Strategy:** How well does this align with FactHarbor's mission and strategic goals? | ||
| 17 | |||
| 18 | **Importance Levels:** | ||
| |
1.3 | 19 | |
| |
1.1 | 20 | * **VERY HIGH:** Critical to mission, high risk if missing, affects majority of users |
| 21 | * **HIGH:** Important for success, significant impact, strong strategic alignment | ||
| 22 | * **MEDIUM:** Valuable but not critical, moderate impact | ||
| 23 | * **LOW:** Nice-to-have, limited impact | ||
| 24 | |||
| |
1.4 | 25 | ---- |
| |
1.1 | 26 | |
| 27 | === 1.2 Urgency Formula === | ||
| 28 | |||
| 29 | **Urgency = f(fail fast and learn, legal, promises made)** | ||
| 30 | |||
| 31 | * **Fail fast and learn:** Do we need to validate assumptions quickly? | ||
| 32 | * **Legal:** Are there legal requirements or external deadlines? | ||
| 33 | * **Promises made:** Have we committed this to stakeholders, funders, or partners? | ||
| 34 | |||
| 35 | **Urgency Levels:** | ||
| |
1.3 | 36 | |
| |
1.1 | 37 | * **HIGH:** External deadlines, legal requirements, or critical testing needed |
| 38 | * **MEDIUM:** Strategic opportunity, growing trends, competitive pressure | ||
| 39 | * **LOW:** No external pressure, can add anytime | ||
| 40 | |||
| |
1.4 | 41 | ---- |
| |
1.1 | 42 | |
| 43 | === 1.3 Context Matters === | ||
| 44 | |||
| 45 | **Important principle:** Importance and urgency change based on milestone context. | ||
| 46 | |||
| 47 | * **POC:** Only basic features urgent | ||
| 48 | * **Beta:** More features become urgent for user testing | ||
| 49 | * **Release:** Legal/compliance becomes critical | ||
| 50 | |||
| 51 | **Priorities are not absolute - they're contextual.** | ||
| 52 | |||
| |
1.4 | 53 | ---- |
| |
1.1 | 54 | |
| 55 | == 2. Gap Categories == | ||
| 56 | |||
| 57 | We identified **18 gaps** across **8 categories**: | ||
| 58 | |||
| 59 | === Category 1: Accessibility & Inclusivity === | ||
| |
1.3 | 60 | |
| |
1.1 | 61 | * Gap 1.1: WCAG 2.1 Compliance |
| 62 | * Gap 1.2: Multilingual Support | ||
| 63 | |||
| 64 | === Category 2: Platform Integration & Distribution === | ||
| |
1.3 | 65 | |
| |
1.1 | 66 | * Gap 2.1: Browser Extensions |
| 67 | * Gap 2.2: Embeddable Widgets | ||
| 68 | * Gap 2.3: ClaimReview Schema | ||
| 69 | |||
| 70 | === Category 3: Media Verification === | ||
| |
1.3 | 71 | |
| |
1.1 | 72 | * Gap 3.1: Image/Video/Audio Verification |
| 73 | |||
| 74 | === Category 4: Mobile & Offline Access === | ||
| |
1.3 | 75 | |
| |
1.1 | 76 | * Gap 4.1: Mobile Apps / PWA |
| 77 | * Gap 4.2: Offline Access | ||
| 78 | |||
| 79 | === Category 5: Education & Media Literacy === | ||
| |
1.3 | 80 | |
| |
1.1 | 81 | * Gap 5.1: Educational Resources |
| 82 | * Gap 5.2: Media Literacy Integration | ||
| 83 | |||
| 84 | === Category 6: Collaboration & Community === | ||
| |
1.3 | 85 | |
| |
1.1 | 86 | * Gap 6.1: Professional Collaboration Tools |
| 87 | * Gap 6.2: Community Discussion | ||
| 88 | |||
| 89 | === Category 7: Export & Sharing === | ||
| |
1.3 | 90 | |
| |
1.1 | 91 | * Gap 7.1: Export Capabilities |
| 92 | * Gap 7.2: Social Sharing Optimization | ||
| 93 | |||
| 94 | === Category 8: Advanced Features & Analytics === | ||
| |
1.3 | 95 | |
| |
1.1 | 96 | * Gap 8.1: User Analytics |
| 97 | * Gap 8.2: Personalization | ||
| 98 | * Gap 8.3: Media Archiving | ||
| 99 | * Gap 8.4: Advanced Search | ||
| 100 | |||
| |
1.4 | 101 | ---- |
| |
1.1 | 102 | |
| 103 | == 3. Critical Gaps == | ||
| 104 | |||
| 105 | === 3.1 Gap: WCAG 2.1 Accessibility Compliance === | ||
| 106 | |||
| 107 | **Status:** ❌ Not addressed in current requirements | ||
| 108 | **Importance:** VERY HIGH | ||
| 109 | **Urgency:** HIGH (legal requirement) | ||
| 110 | |||
| 111 | **Why Important:** | ||
| |
1.3 | 112 | |
| |
1.1 | 113 | * **Risk:** CRITICAL |
| |
1.3 | 114 | * Legal liability (European Accessibility Act enforced June 28, 2025) |
| 115 | * Lawsuits, fines up to $250,000 (Accessible Canada Act) | ||
| 116 | * Cannot operate in EU market without compliance | ||
| 117 | * Retrofitting is 100x more expensive than building in from start | ||
| |
1.1 | 118 | * **Impact:** 15-20% of population (1+ billion people) excluded without accessibility |
| |
1.3 | 119 | * Affects blind, low-vision, deaf, motor impairments, cognitive disabilities |
| 120 | * "86% of companies report improved customer satisfaction after implementing accessibility" (Forrester) | ||
| |
1.1 | 121 | * **Strategy:** CRITICAL ALIGNMENT |
| |
1.3 | 122 | * Mission: "empower users to make informed judgments" - cannot empower if inaccessible |
| 123 | * Vision: "a world where decisions are grounded in evidence" - for ALL people | ||
| 124 | * Inclusivity is core to nonprofit mission | ||
| |
1.1 | 125 | |
| 126 | **Why Urgent:** | ||
| |
1.3 | 127 | |
| |
1.1 | 128 | * **Legal:** VERY HIGH |
| |
1.3 | 129 | * European Accessibility Act (EAA) enforced June 28, 2025 |
| 130 | * Americans with Disabilities Act (ADA) - ongoing requirement in US | ||
| 131 | * Accessible Canada Act - penalties up to $250,000 | ||
| 132 | * Cannot launch in EU without compliance | ||
| |
1.1 | 133 | * **Fail fast:** Not applicable (accessibility is proven requirement, not experimental) |
| 134 | * **Promises:** Depends on public mission statements and funding commitments | ||
| 135 | |||
| 136 | **Missing Requirements:** | ||
| |
1.3 | 137 | |
| |
1.1 | 138 | * WCAG 2.1 Level AA compliance |
| 139 | * Screen reader compatibility (ARIA labels, semantic HTML) | ||
| 140 | * Keyboard navigation (no mouse required) | ||
| 141 | * Color-blind friendly design (not relying solely on color) | ||
| 142 | * Adjustable text size and contrast | ||
| 143 | * Captions/transcripts for video content | ||
| 144 | * Alternative text for images and visualizations | ||
| 145 | |||
| 146 | **Recommended New Requirements:** | ||
| |
1.3 | 147 | |
| |
1.1 | 148 | * **NFR6: Accessibility** - Platform must conform to WCAG 2.1 Level AA standards |
| 149 | * **NFR7: Assistive Technology Support** - Compatible with screen readers, voice navigation, keyboard-only usage | ||
| 150 | * **FR14: Accessibility Settings** - User-configurable contrast, text size, reduced motion options | ||
| 151 | |||
| 152 | **When to Address:** Must be built into platform from start (retrofitting prohibitively expensive) | ||
| 153 | |||
| 154 | **Research Evidence:** | ||
| |
1.3 | 155 | |
| |
1.1 | 156 | * "72% of organizations have digital accessibility policy, 85% see it as competitive advantage" (Level Access 2024) |
| 157 | * European Accessibility Act (EAA) enforcement begins June 28, 2025 | ||
| 158 | * "Accessible websites see 20% increase in traffic and engagement" (W3C WAI) | ||
| 159 | * "86% of companies report improved customer satisfaction after implementing accessibility" (Forrester) | ||
| 160 | |||
| |
1.4 | 161 | ---- |
| |
1.1 | 162 | |
| 163 | === 3.2 Gap: Educational Resources & Onboarding === | ||
| 164 | |||
| 165 | **Status:** ❌ Not addressed in current requirements | ||
| 166 | **Importance:** VERY HIGH | ||
| 167 | **Urgency:** HIGH (critical for adoption) | ||
| 168 | |||
| 169 | **Why Important:** | ||
| |
1.3 | 170 | |
| |
1.1 | 171 | * **Risk:** CRITICAL |
| |
1.3 | 172 | * Platform fails if users cannot understand Evidence Models |
| 173 | * Misinterpretation of scenarios/verdicts undermines mission | ||
| 174 | * High abandonment rate without onboarding (industry standard: 75% drop-off without onboarding) | ||
| 175 | * Wasted investment if no one can use the platform | ||
| |
1.1 | 176 | * **Impact:** Affects 100% of new users |
| |
1.3 | 177 | * "Fact-checking organizations increasingly provide media literacy education" (Mesquita et al. 2024) |
| 178 | * Determines whether platform succeeds or fails | ||
| |
1.1 | 179 | * **Strategy:** CRITICAL ALIGNMENT |
| |
1.3 | 180 | * Mission: "help people make sense of complex, contested information" |
| 181 | * Vision: Requires users to understand methodology | ||
| 182 | * Cannot achieve transparency without explaining concepts | ||
| |
1.1 | 183 | |
| 184 | **Why Urgent:** | ||
| |
1.3 | 185 | |
| |
1.1 | 186 | * **Fail fast:** VERY HIGH |
| |
1.3 | 187 | * Must validate that Evidence Models are comprehensible to users |
| 188 | * Need to test if onboarding actually works | ||
| 189 | * Quick iteration needed based on user confusion | ||
| 190 | * Test with beta users before full launch | ||
| |
1.1 | 191 | * **Legal:** None |
| 192 | * **Promises:** HIGH if public statements include "user-friendly" or "accessible to all" | ||
| 193 | |||
| 194 | **Missing Requirements:** | ||
| |
1.3 | 195 | |
| |
1.1 | 196 | * Onboarding tutorial (interactive walkthrough) |
| 197 | * Video tutorials explaining concepts | ||
| 198 | * FAQ section | ||
| 199 | * Glossary (scenarios, confidence scores, verdicts, assumptions) | ||
| 200 | * Example analyses with explanations | ||
| 201 | * "How to read a FactHarbor analysis" guide | ||
| 202 | * Best practices documentation | ||
| 203 | |||
| 204 | **Recommended New Requirements:** | ||
| |
1.3 | 205 | |
| |
1.1 | 206 | * **UN-23: Learn How to Fact-Check** - Educational resources for understanding methodology |
| 207 | * **FR26: Onboarding Tutorial** - Interactive first-time user walkthrough | ||
| 208 | * **FR27: Educational Resources Hub** - Guides, videos, FAQs, glossary | ||
| 209 | * **FR28: Curriculum Materials** - Resources for educators to use FactHarbor in classrooms | ||
| 210 | |||
| 211 | **When to Address:** Basic onboarding at launch (POC needs 1-page explainer, Beta needs comprehensive resources) | ||
| 212 | |||
| 213 | **Research Evidence:** | ||
| |
1.3 | 214 | |
| |
1.1 | 215 | * "Critical media literacy fosters resilience against misinformation" (McDougall 2019) |
| 216 | * Teen Fact-Checking Networks operating globally (MediaWise 2024) | ||
| 217 | * "Fact-checking organizations increasingly provide media literacy education" (Mesquita et al. 2024) | ||
| 218 | |||
| |
1.4 | 219 | ---- |
| |
1.1 | 220 | |
| 221 | == 4. High Importance Gaps == | ||
| 222 | |||
| 223 | === 4.1 Gap: Browser Extensions === | ||
| 224 | |||
| 225 | **Status:** ❌ Not addressed | ||
| 226 | **Importance:** HIGH | ||
| 227 | **Urgency:** MEDIUM | ||
| 228 | |||
| 229 | **Why Important:** | ||
| |
1.3 | 230 | |
| |
1.1 | 231 | * **Risk:** MEDIUM - Competitive disadvantage, reduced adoption |
| 232 | * **Impact:** MEDIUM-HIGH - Significantly improves UX for active fact-checkers | ||
| 233 | * **Strategy:** HIGH ALIGNMENT - Meet users where misinformation spreads (in their browsers) | ||
| 234 | |||
| 235 | **Why Urgent:** | ||
| |
1.3 | 236 | |
| |
1.1 | 237 | * **Fail fast:** MEDIUM - Should validate that users actually want browser extensions |
| 238 | * **Legal:** None | ||
| 239 | * **Promises:** LOW unless explicitly promised to early adopters | ||
| 240 | |||
| 241 | **Missing Requirements:** | ||
| |
1.3 | 242 | |
| |
1.1 | 243 | * Chrome/Firefox/Safari browser extensions |
| 244 | * Right-click context menu for selected text | ||
| 245 | * Inline highlighting of claims on any webpage | ||
| 246 | * Quick verdict tooltips without leaving page | ||
| 247 | * Save/bookmark fact-checks | ||
| 248 | |||
| 249 | **Recommended:** | ||
| |
1.3 | 250 | |
| |
1.1 | 251 | * **UN-18: In-Context Fact-Checking** - Browser extension for real-time verification |
| 252 | * **FR17: Browser Extensions** - Chrome, Firefox, Safari with context menu | ||
| 253 | * **FR18: Cross-Site Highlighting** - Highlight and analyze claims on any website | ||
| 254 | |||
| 255 | **When to Address:** Test web platform first, then build extension MVP if user demand validated | ||
| 256 | |||
| 257 | **Research Evidence:** | ||
| |
1.3 | 258 | |
| |
1.1 | 259 | * "3-click verification: Select → Right-click → Verify" is standard UX pattern |
| 260 | * Extensions like UnCovered, Pino, InVID/WeVerify widely adopted | ||
| 261 | * NewsGuard browser extension demonstrates market acceptance | ||
| 262 | |||
| |
1.4 | 263 | ---- |
| |
1.1 | 264 | |
| 265 | === 4.2 Gap: Media Verification (Images/Videos/Audio) === | ||
| 266 | |||
| 267 | **Status:** ❌ Not addressed | ||
| 268 | **Importance:** VERY HIGH | ||
| 269 | **Urgency:** MEDIUM | ||
| 270 | |||
| 271 | **Why Important:** | ||
| |
1.3 | 272 | |
| |
1.1 | 273 | * **Risk:** HIGH - Cannot address major category of misinformation (visual/audio) |
| 274 | * **Impact:** VERY HIGH - Visual misinformation is primary vector | ||
| 275 | * **Strategy:** CRITICAL ALIGNMENT - Mission incomplete without multimedia fact-checking | ||
| 276 | |||
| 277 | **Why Urgent:** | ||
| |
1.3 | 278 | |
| |
1.1 | 279 | * **Fail fast:** VERY HIGH - Should test approach quickly (partner vs. build?) |
| 280 | * **Legal:** None | ||
| 281 | * **Promises:** MEDIUM (depends on mission statements) | ||
| 282 | |||
| 283 | **Missing Requirements:** | ||
| |
1.3 | 284 | |
| |
1.1 | 285 | * Reverse image search integration |
| 286 | * Video frame extraction and analysis | ||
| 287 | * Audio deepfake detection | ||
| 288 | * EXIF metadata extraction | ||
| 289 | * Synthetic media detection (AI-generated content) | ||
| 290 | |||
| 291 | **Recommended:** | ||
| |
1.3 | 292 | |
| |
1.1 | 293 | * **UN-20: Media Verification** - Image, video, audio fact-checking |
| 294 | * **FR22: Image Verification** - Reverse search, EXIF, synthetic detection | ||
| 295 | * **FR23: Video Verification** - Frame analysis, metadata, deepfake detection | ||
| 296 | * **FR24: Audio Verification** - Voice deepfakes, audio forensics | ||
| 297 | |||
| 298 | **When to Address:** Pilot with existing tools (InVID, TinEye) before building in-house | ||
| 299 | |||
| 300 | **Research Evidence:** | ||
| |
1.3 | 301 | |
| |
1.1 | 302 | * "Most deception relies on decontextualization" of images (Cazzamatta 2025) |
| 303 | * "Deepfakes targeting political figures raise concerns" (Corsi et al. 2024) | ||
| 304 | * InVID/WeVerify used by professional fact-checkers (AFP 2024) | ||
| 305 | |||
| |
1.4 | 306 | ---- |
| |
1.1 | 307 | |
| 308 | === 4.3 Gap: Multilingual Support === | ||
| 309 | |||
| 310 | **Status:** ❌ Not addressed | ||
| 311 | **Importance:** HIGH | ||
| 312 | **Urgency:** MEDIUM | ||
| 313 | |||
| 314 | **Why Important:** | ||
| |
1.3 | 315 | |
| 316 | * **Risk:** HIGH - Mission limited to English speakers (20% of world) | ||
| |
1.1 | 317 | * **Impact:** VERY HIGH - Excludes 80% of world population |
| 318 | * **Strategy:** CRITICAL ALIGNMENT - Vision of "a world where decisions are grounded in evidence" - not just English-speaking world | ||
| 319 | |||
| 320 | **Why Urgent:** | ||
| |
1.3 | 321 | |
| |
1.1 | 322 | * **Fail fast:** MEDIUM - Test which languages users need, validate translation quality early |
| 323 | * **Legal:** None | ||
| 324 | * **Promises:** MEDIUM-HIGH if mission statement emphasizes "global" or "world" | ||
| 325 | |||
| 326 | **Missing Requirements:** | ||
| |
1.3 | 327 | |
| |
1.1 | 328 | * Interface available in multiple languages |
| 329 | * Content translation/analysis in non-English languages | ||
| 330 | * Right-to-left (RTL) language support (Arabic, Hebrew) | ||
| 331 | * Locale-specific formatting (dates, numbers, currencies) | ||
| 332 | * Character encoding for non-Latin scripts | ||
| 333 | |||
| 334 | **Recommended:** | ||
| |
1.3 | 335 | |
| |
1.1 | 336 | * **FR15: Multilingual Interface** - UI in 10+ languages |
| 337 | * **FR16: Multilingual Content Analysis** - AKEL analyzes claims in multiple languages | ||
| 338 | * **NFR8: Internationalization (i18n)** - RTL support, character encodings, locale formatting | ||
| 339 | |||
| 340 | **When to Address:** Plan early, prove English platform first, start with 2-3 strategic languages | ||
| 341 | |||
| 342 | **Research Evidence:** | ||
| |
1.3 | 343 | |
| |
1.1 | 344 | * 443 fact-checking projects operate in 70+ languages globally (Duke 2025) |
| 345 | * "LLMs better at fact-checking in low-resource languages than expected" (ACL 2024) | ||
| 346 | * "Multilingual capabilities essential for global inclusivity" (O3 World 2024) | ||
| 347 | |||
| |
1.4 | 348 | ---- |
| |
1.1 | 349 | |
| 350 | === 4.4 Gap: Mobile Apps / PWA === | ||
| 351 | |||
| 352 | **Status:** ❌ Not addressed | ||
| 353 | **Importance:** HIGH | ||
| 354 | **Urgency:** LOW | ||
| 355 | |||
| 356 | **Why Important:** | ||
| |
1.3 | 357 | |
| |
1.1 | 358 | * **Risk:** MEDIUM - Reduced engagement, poor mobile experience |
| 359 | * **Impact:** HIGH - 90%+ users access news on mobile | ||
| 360 | * **Strategy:** MEDIUM - Better UX but not core to methodology | ||
| 361 | |||
| 362 | **Why Urgent:** | ||
| |
1.3 | 363 | |
| |
1.1 | 364 | * **Fail fast:** MEDIUM - Test if mobile users behave differently, PWA first |
| 365 | * **Legal:** None | ||
| 366 | * **Promises:** LOW unless specified in grants/partnerships | ||
| 367 | |||
| 368 | **Missing Requirements:** | ||
| |
1.3 | 369 | |
| |
1.1 | 370 | * iOS/Android native apps |
| 371 | * Progressive Web App (PWA) capabilities | ||
| 372 | * Camera submission for visual claims | ||
| 373 | * Push notifications | ||
| 374 | * Offline mode | ||
| 375 | |||
| 376 | **Recommended:** | ||
| |
1.3 | 377 | |
| |
1.1 | 378 | * **UN-21: Mobile-Native Experience** - Native apps for iOS/Android |
| 379 | * **FR25: Native Mobile Apps** - Full mobile capabilities | ||
| 380 | * **NFR9: Progressive Web App** - Installable, offline, push notifications | ||
| 381 | |||
| 382 | **When to Address:** Responsive web first, PWA to test mobile patterns, native apps if validated | ||
| 383 | |||
| 384 | **Research Evidence:** | ||
| |
1.3 | 385 | |
| |
1.1 | 386 | * "Mobile apps with accessibility features experience 30% higher engagement" (MMA 2024) |
| 387 | * 90%+ of adults access news via mobile devices (Pew 2024) | ||
| 388 | |||
| |
1.4 | 389 | ---- |
| |
1.1 | 390 | |
| 391 | === 4.5 Gap: ClaimReview Schema === | ||
| 392 | |||
| 393 | **Status:** ❌ Not addressed | ||
| 394 | **Importance:** HIGH | ||
| 395 | **Urgency:** LOW | ||
| 396 | |||
| 397 | **Why Important:** | ||
| |
1.3 | 398 | |
| |
1.1 | 399 | * **Risk:** LOW-MEDIUM - Reduced discoverability (won't appear in Google search) |
| 400 | * **Impact:** MEDIUM-HIGH - Affects all users via SEO | ||
| 401 | * **Strategy:** MEDIUM - Distribution mechanism, not core methodology | ||
| 402 | |||
| 403 | **Why Urgent:** | ||
| |
1.3 | 404 | |
| |
1.1 | 405 | * **Fail fast:** LOW - Already proven by 200,000+ fact-checks globally |
| 406 | * **Legal:** None | ||
| 407 | * **Promises:** None | ||
| 408 | |||
| 409 | **Missing Requirements:** | ||
| |
1.3 | 410 | |
| |
1.1 | 411 | * ClaimReview structured data markup |
| 412 | * Submit to Google Fact Check Explorer | ||
| 413 | * MediaReview for multimedia content | ||
| 414 | |||
| 415 | **Recommended:** | ||
| |
1.3 | 416 | |
| |
1.1 | 417 | * **FR20: ClaimReview Schema** - Structured data markup |
| 418 | * **FR21: Search Engine Integration** - Submit to fact-check indexes | ||
| 419 | |||
| 420 | **When to Address:** Add anytime after content library exists (can be retroactive) | ||
| 421 | |||
| 422 | **Research Evidence:** | ||
| |
1.3 | 423 | |
| |
1.1 | 424 | * 200,000+ fact-checks use ClaimReview globally (Duke 2024) |
| 425 | * Enables appearance in Google/Bing search results | ||
| 426 | |||
| |
1.4 | 427 | ---- |
| |
1.1 | 428 | |
| 429 | == 5. Medium Importance Gaps == | ||
| 430 | |||
| 431 | === 5.1 Gap: Embeddable Widgets === | ||
| 432 | |||
| 433 | **Importance:** MEDIUM | ||
| 434 | **Urgency:** LOW | ||
| 435 | |||
| 436 | **Missing:** JavaScript widgets for publishers to embed fact-checks | ||
| 437 | |||
| 438 | **When:** Only if publishers commit to using it | ||
| 439 | |||
| |
1.4 | 440 | ---- |
| |
1.1 | 441 | |
| 442 | === 5.2 Gap: Export Capabilities === | ||
| 443 | |||
| 444 | **Importance:** MEDIUM | ||
| 445 | **Urgency:** LOW | ||
| 446 | |||
| 447 | **Missing:** PDF export, print optimization, CSV/JSON data export | ||
| 448 | |||
| 449 | **When:** Based on user requests | ||
| 450 | |||
| |
1.4 | 451 | ---- |
| |
1.1 | 452 | |
| 453 | === 5.3 Gap: Professional Collaboration Tools === | ||
| 454 | |||
| 455 | **Importance:** MEDIUM | ||
| 456 | **Urgency:** LOW | ||
| 457 | |||
| 458 | **Missing:** Organization workspaces, claim assignment, internal discussion | ||
| 459 | |||
| 460 | **When:** Only if organizations commit | ||
| 461 | |||
| |
1.4 | 462 | ---- |
| |
1.1 | 463 | |
| 464 | === 5.4 Gap: Social Sharing Optimization === | ||
| 465 | |||
| 466 | **Importance:** MEDIUM | ||
| 467 | **Urgency:** LOW | ||
| 468 | |||
| 469 | **Missing:** Open Graph tags, Twitter Cards, short URLs, WhatsApp optimization | ||
| 470 | |||
| 471 | **When:** Iterative improvement based on usage | ||
| 472 | |||
| |
1.4 | 473 | ---- |
| |
1.1 | 474 | |
| 475 | === 5.5 Gap: Media Archiving === | ||
| 476 | |||
| 477 | **Importance:** MEDIUM | ||
| 478 | **Urgency:** LOW | ||
| 479 | |||
| 480 | **Missing:** Automatic archiving of sources, Wayback Machine integration, media preservation | ||
| 481 | |||
| 482 | **When:** After launch, retroactive archiving is fine | ||
| 483 | |||
| 484 | **Research Evidence:** | ||
| |
1.3 | 485 | |
| |
1.1 | 486 | * "Images/videos often disappear after fact-checking" (MediaVault 2024) |
| 487 | * IFCN DisinfoArchiving uses WACZ format (InVID 2024-2025) | ||
| 488 | |||
| |
1.4 | 489 | ---- |
| |
1.1 | 490 | |
| 491 | == 6. Lower Priority Gaps == | ||
| 492 | |||
| 493 | === 6.1 Gap: User Analytics === | ||
| 494 | |||
| 495 | **Importance:** MEDIUM | ||
| 496 | **Urgency:** LOW | ||
| 497 | |||
| 498 | **Missing:** Privacy-respecting usage analytics, feedback systems | ||
| 499 | |||
| |
1.4 | 500 | ---- |
| |
1.1 | 501 | |
| 502 | === 6.2 Gap: Personalization === | ||
| 503 | |||
| 504 | **Importance:** LOW | ||
| 505 | **Urgency:** N/A | ||
| 506 | |||
| 507 | **Strategic Decision Needed:** How much personalization without creating filter bubbles? | ||
| 508 | |||
| 509 | **Recommendation:** Limited only (language, accessibility preferences) - NO content filtering | ||
| 510 | |||
| |
1.4 | 511 | ---- |
| |
1.1 | 512 | |
| 513 | === 6.3 Gap: Community Discussion === | ||
| 514 | |||
| 515 | **Importance:** LOW | ||
| 516 | **Urgency:** N/A | ||
| 517 | |||
| 518 | **Strategic Decision Needed:** Should FactHarbor allow public comments or remain evidence-focused? | ||
| 519 | |||
| 520 | **Question to resolve:** Evidence platform vs. community platform? | ||
| 521 | |||
| |
1.4 | 522 | ---- |
| |
1.1 | 523 | |
| 524 | === 6.4 Gap: Advanced Search === | ||
| 525 | |||
| 526 | **Importance:** MEDIUM | ||
| 527 | **Urgency:** LOW | ||
| 528 | |||
| 529 | **Missing:** Elasticsearch, faceted search, advanced filters | ||
| 530 | |||
| 531 | **When:** Only when PostgreSQL search becomes bottleneck | ||
| 532 | |||
| |
1.4 | 533 | ---- |
| |
1.1 | 534 | |
| 535 | === 6.5 Gap: Offline Access === | ||
| 536 | |||
| 537 | **Importance:** LOW | ||
| 538 | **Urgency:** LOW | ||
| 539 | |||
| 540 | **Missing:** Offline mode, service workers, cached content | ||
| 541 | |||
| 542 | **When:** If user research shows demand | ||
| 543 | |||
| |
1.4 | 544 | ---- |
| |
1.1 | 545 | |
| 546 | |||
| |
1.4 | 547 | ---- |
| |
1.1 | 548 | |
| 549 | == 7. Existing Requirements Reference == | ||
| 550 | |||
| 551 | **Before proposing new requirements, here's what already exists in the FactHarbor Specification:** | ||
| 552 | |||
| 553 | === 7.1 Existing Functional Requirements (FR1-FR13) === | ||
| 554 | |||
| 555 | **From Specification/Requirements.WebHome:** | ||
| 556 | |||
| 557 | * **FR1:** Claim Intake - Users submit claims via form or API | ||
| 558 | * **FR2:** Claim Normalization - Standardize to clear assertion format | ||
| 559 | * **FR3:** Claim Classification - Domain, type, risk score, complexity | ||
| 560 | * **FR4:** Scenario Generation - AKEL analyzes claim and generates scenarios | ||
| 561 | * **FR5:** Evidence Linking - Automated evidence discovery and relevance scoring | ||
| 562 | * **FR6:** Scenario Comparison - Side-by-side comparison interface | ||
| 563 | * **FR7:** Automated Verdicts - AKEL generates verdict based on evidence | ||
| 564 | * **FR8:** Time Evolution - Claims update as new evidence emerges | ||
| 565 | * **FR9:** Publication Workflow - Simple automated flow (no multi-stage approval) | ||
| 566 | * **FR10:** Moderation - Focus on abuse, not routine quality | ||
| 567 | * **FR11:** Audit Trail - All edits logged, version history public | ||
| 568 | |||
| 569 | **From User Needs Document (UN-17):** | ||
| 570 | |||
| 571 | * **FR12:** Two-Panel Summary View - Analysis + Article side-by-side | ||
| 572 | * **FR13:** In-Article Claim Highlighting - Visual claim markers in original text | ||
| 573 | |||
| 574 | **Total Existing:** FR1-FR13 (13 functional requirements) | ||
| 575 | |||
| |
1.4 | 576 | ---- |
| |
1.1 | 577 | |
| 578 | === 7.2 Existing Non-Functional Requirements (NFR1-NFR5) === | ||
| 579 | |||
| 580 | **From Specification/Requirements.WebHome:** | ||
| 581 | |||
| 582 | * **NFR1:** Performance - Processing <30s, search <2s, page load <3s, 99% uptime | ||
| 583 | * **NFR2:** Scalability - Handle 10K claims initially, scale to 1M+, 100K+ concurrent users | ||
| 584 | * **NFR3:** Transparency - All algorithms open source, all data exportable, all decisions documented | ||
| 585 | * **NFR4:** Security & Privacy - Follow privacy policy, secure authentication, data encryption, regular audits | ||
| 586 | * **NFR5:** Maintainability - Modular architecture, automated testing, CI/CD, comprehensive documentation | ||
| 587 | |||
| 588 | **Total Existing:** NFR1-NFR5 (5 non-functional requirements) | ||
| 589 | |||
| |
1.4 | 590 | ---- |
| |
1.1 | 591 | |
| 592 | === 7.3 Requirement Numbering Summary === | ||
| 593 | |||
| 594 | **Existing Requirements:** | ||
| |
1.3 | 595 | |
| |
1.1 | 596 | * Functional: FR1 through FR13 |
| 597 | * Non-Functional: NFR1 through NFR5 | ||
| 598 | |||
| 599 | **Proposed New Requirements (from Gap Analysis):** | ||
| |
1.3 | 600 | |
| |
1.1 | 601 | * Functional: FR14 through FR43 (30 new) |
| 602 | * Non-Functional: NFR6 through NFR10 (5 new) | ||
| 603 | |||
| 604 | **Total After Gap Analysis:** | ||
| |
1.3 | 605 | |
| |
1.1 | 606 | * Functional: FR1-FR43 (43 total) |
| 607 | * Non-Functional: NFR1-NFR10 (10 total) | ||
| 608 | |||
| |
1.4 | 609 | ---- |
| |
1.1 | 610 | |
| 611 | |||
| 612 | Based on gap analysis, we recommend adding: | ||
| 613 | |||
| 614 | **8 New User Needs (UN-18 through UN-25):** | ||
| |
1.3 | 615 | |
| |
1.1 | 616 | * UN-18: In-Context Fact-Checking (browser extension) |
| 617 | * UN-19: Publisher Integration (embed widgets) | ||
| 618 | * UN-20: Media Verification (images/videos/audio) | ||
| 619 | * UN-21: Mobile-Native Experience (native apps) | ||
| 620 | * UN-22: Offline Access (PWA) | ||
| 621 | * UN-23: Learn How to Fact-Check (education) | ||
| 622 | * UN-24: Professional Collaboration (team tools) | ||
| 623 | * UN-25: Export & Save (PDF, CSV) | ||
| 624 | |||
| 625 | **30 New Functional Requirements (FR14-FR43):** | ||
| |
1.3 | 626 | |
| |
1.1 | 627 | * FR14: Accessibility Settings |
| 628 | * FR15-16: Multilingual (Interface, Content Analysis) | ||
| 629 | * FR17-18: Browser Extensions, Cross-Site Highlighting | ||
| 630 | * FR19-20: Embeddable Widget, ClaimReview Schema | ||
| 631 | * FR21: Search Engine Integration | ||
| 632 | * FR22-24: Media Verification (Image, Video, Audio) | ||
| 633 | * FR25: Native Mobile Apps | ||
| 634 | * FR26-30: Education (Onboarding, Resources, Curriculum, Critical Thinking, Pre-bunking) | ||
| 635 | * FR31-33: Professional Collaboration (Workspaces, Assignment, Discussion) | ||
| 636 | * FR34-36: Export (PDF, Print, Data) | ||
| 637 | * FR37-39: Social Sharing (Open Graph, Short URLs, Multi-Channel) | ||
| 638 | * FR40: User Feedback System | ||
| 639 | * FR41-43: Archiving (Automatic, Archive.org, Media Preservation) | ||
| 640 | |||
| 641 | **5 New Non-Functional Requirements (NFR6-NFR10):** | ||
| |
1.3 | 642 | |
| |
1.1 | 643 | * NFR6: Accessibility (WCAG 2.1 AA) |
| 644 | * NFR7: Assistive Technology Support | ||
| 645 | * NFR8: Internationalization (i18n) | ||
| 646 | * NFR9: Progressive Web App (PWA) | ||
| 647 | * NFR10: Privacy-Respecting Analytics | ||
| 648 | |||
| |
1.4 | 649 | ---- |
| |
1.1 | 650 | |
| 651 | == 11. Priority Matrix == | ||
| 652 | |||
| 653 | **Priority based on Importance + Urgency:** | ||
| 654 | |||
| 655 | **CRITICAL (Must Address):** | ||
| |
1.3 | 656 | |
| |
1.1 | 657 | 1. Accessibility (WCAG) - Legal + High Impact |
| 658 | 2. Educational Resources - Adoption Critical | ||
| 659 | |||
| 660 | **HIGH (Strategic Priority):** | ||
| 661 | 3. Browser Extensions - User Expectation | ||
| 662 | 4. Media Verification - Mission Critical | ||
| 663 | 5. Multilingual - Global Strategy | ||
| 664 | |||
| 665 | **MEDIUM (Plan For):** | ||
| 666 | 6. Mobile Apps/PWA - User Convenience | ||
| 667 | 7. ClaimReview Schema - Discoverability | ||
| 668 | 8. Export Capabilities - Professional Users | ||
| 669 | 9. Embeddable Widgets - Publisher Adoption | ||
| 670 | 10. Professional Collaboration - Organizational Users | ||
| 671 | |||
| 672 | **LOW (Consider Later):** | ||
| |
1.3 | 673 | |
| |
1.4 | 674 | 1. \\ |
| |
1.1 | 675 | 11. Social Sharing Optimization |
| 676 | 12. Media Archiving | ||
| 677 | 13. User Analytics | ||
| 678 | 14. Advanced Search | ||
| 679 | 15. Offline Access | ||
| 680 | 16. Personalization | ||
| 681 | 17. Community Discussion | ||
| 682 | |||
| |
1.4 | 683 | ---- |
| |
1.1 | 684 | |
| 685 | == 11. Key Strategic Questions == | ||
| 686 | |||
| 687 | **Question 1: Accessibility Investment** | ||
| 688 | How comprehensive at launch? | ||
| |
1.3 | 689 | |
| |
1.1 | 690 | * **Required:** WCAG 2.1 AA minimum, keyboard navigation, screen readers |
| 691 | * **Enhanced:** Voice navigation, haptic feedback (can add later) | ||
| 692 | |||
| 693 | **Question 2: Multilingual Priorities** | ||
| 694 | Which languages first? | ||
| |
1.3 | 695 | |
| |
1.1 | 696 | * **Recommend:** English, Spanish, French, German, Arabic (major markets + diversity) |
| 697 | * **Consider:** Chinese, Japanese, Portuguese, Hindi, Russian | ||
| 698 | |||
| 699 | **Question 3: Media Verification Approach** | ||
| 700 | Build vs. partner? | ||
| |
1.3 | 701 | |
| |
1.1 | 702 | * **Recommend:** Partner initially (InVID, TinEye, existing tools) |
| 703 | * **Build:** If demand proven and resources available | ||
| 704 | |||
| 705 | **Question 4: Community Model** | ||
| 706 | Evidence-focused vs. discussion-enabled? | ||
| |
1.3 | 707 | |
| |
1.1 | 708 | * **Option A:** No public discussion (maintain authority model) |
| 709 | * **Option B:** Limited discussion (Contributor+ only) | ||
| 710 | * **Option C:** Open discussion (requires moderation resources) | ||
| 711 | |||
| 712 | **Question 5: Mobile Strategy** | ||
| 713 | Native apps vs. PWA? | ||
| |
1.3 | 714 | |
| |
1.1 | 715 | * **Recommend:** PWA first (cross-platform, lower cost) |
| 716 | * **Consider:** Native apps if mobile usage dominant | ||
| 717 | |||
| |
1.4 | 718 | ---- |
| |
1.1 | 719 | |
| 720 | == 11. Research Sources == | ||
| 721 | |||
| 722 | **Academic Research (2024-2025):** | ||
| |
1.3 | 723 | |
| |
1.1 | 724 | * AI-Generated Misinformation (Cazzamatta & Sarısakaloğlu 2025) |
| 725 | * Show Me the Work: Fact-Checkers' Requirements for Explainable AI (CHI 2025) | ||
| 726 | * Multilingual Fact-Checking using LLMs (ACL 2024) | ||
| 727 | * Beyond Verification: Media Literacy Education (Mesquita et al. 2024) | ||
| 728 | |||
| 729 | **Industry Reports:** | ||
| |
1.3 | 730 | |
| |
1.1 | 731 | * Duke Reporters' Lab Census 2024-2025 (443 projects, 70+ languages) |
| 732 | * Poynter/IFCN State of Fact-Checkers Report | ||
| 733 | * Level Access: State of Digital Accessibility Report 2023-2024 | ||
| 734 | * Pew Research Center: News consumption patterns | ||
| 735 | |||
| 736 | **Standards & Compliance:** | ||
| |
1.3 | 737 | |
| |
1.1 | 738 | * WCAG 2.1 (W3C) |
| 739 | * European Accessibility Act (EAA) - June 28, 2025 | ||
| 740 | * Americans with Disabilities Act (ADA) | ||
| 741 | * Accessible Canada Act | ||
| 742 | * ClaimReview/MediaReview specifications (Schema.org) | ||
| 743 | |||
| |
1.4 | 744 | ---- |
| |
1.1 | 745 | |
| 746 | == 11. Related Pages == | ||
| 747 | |||
| |
1.6 | 748 | * [[User Needs>>Archive.FactHarbor 2026\.01\.20.Specification.Requirements.User Needs.WebHome]] |
| |
1.1 | 749 | * [[Requirements>>FactHarbor.Requirements.WebHome]] |
| 750 | * [[POC Requirements>>FactHarbor.POC.WebHome]] | ||
| |
1.5 | 751 | * [[Architecture>>Archive.FactHarbor 2026\.01\.20.Specification.Architecture.WebHome]] |
| |
1.1 | 752 | |
| |
1.4 | 753 | ---- |
| |
1.1 | 754 | |
| 755 | **Document Status:** ✅ Analysis Complete - Ready for Strategic Planning |