FREEVIEW — NEEDS ASSESSMENT

Purpose

FreeView was created to address a gap in existing accessibility and AI interaction tools:
the lack of a universal, hands-free, low-distraction text-to-speech interface that works consistently across modern web environments.

---

Identified User Needs

1. Persistent, floating accessibility layer

• Must remain visible and usable across all webpages
  
• Must not require page reloads or site-specific integration
  
• Must not interfere with page layout or content
  

2. Hands-free operation

• Primary interaction via hover, keyboard, or minimal input
  
• No requirement for scrolling
  
• No dependency on complex UI navigation
  

3. Console-based text capture (not utterance-dependent)

• Capture text directly from the browser environment
  
• Avoid reliance on application-level “utterance” systems
  
• Work reliably in framed, protected, or sandboxed pages
  

4. Minimal distraction

• Calm visual presentation
  
• No forced animations
  
• No aggressive alerts or pop-ups
  
• User-controlled interaction only
  

5. Low system resource usage

• No large models running locally
  
• No constant polling
  
• Uses existing operating system TTS capabilities
  
• Idle when not in use
  

6. Stability and reliability

• Small code footprint
  
• Predictable behavior
  
• Resistant to browser updates
  
• Graceful failure instead of crashes
  

7. Easy maintenance

• Simple architecture
  
• Minimal dependencies
  
• Easy to debug and extend
  
• No fragile integrations
  

8. Solid foundation with future flexibility

• Core system remains stable
  
• “Roof” (UI, visuals, themes) can evolve
  
• Supports customization without breaking core logic
  

9. AI-assisted customization

• Visual themes, layouts, and content can be updated using AI tools
  
• Future automation without rewriting core code
  

10. Accessibility-first design

• Designed for users with ADHD, cognitive overload, visual fatigue, or motor limitations
  
• High-contrast targets
  
• Predictable layout
  
• Optional safe/quiet zone
  

---

Desired Outcomes

• A universal accessibility layer that works everywhere
  
• A tool that feels built into the system, not bolted on
  
• A foundation that others can extend without compromising stability
  
• A solution that remains free, lightweight, and protective of users