PROJECT: Voice Input Integration + TTS Narration Refinement This is a continuation of an existing project. The system is a King James Bible concordance engine that: * accepts user queries (currently via text) * retrieves scripture based on Cruden’s concordance logic * returns results in text and audio (TTS) --- OBJECTIVE Enhance the system by: 1. Adding voice input (speech-to-text) 2. Improving the quality of the voice output (TTS narration) --- 1. VOICE INPUT (PRIMARY FEATURE) Goal: Enable users to speak their query instead of typing. Requirements: * Add a microphone button next to the input field * When clicked, the system should: * activate browser-based speech recognition * capture the user’s speech * convert speech to text * populate the input field with the recognised text * User can then: * either manually submit * OR auto-submit after speech ends (optional) Example: User says: “What does the Bible say about trust?” System: * converts to text * runs existing search engine * displays results Important: * Use a simple, cost-effective browser-native solution (no heavy APIs required) * Keep it lightweight and responsive --- 2. TEXT-TO-SPEECH (TTS) REFINEMENT Goal: Improve narration quality to feel more like structured Bible reading. Adjustments required: * Slightly reduce speed (approx. 0.85–0.92 range) * Add small pauses between verses * Ensure consistent pacing across output * Maintain clarity and readability Output format example: “Genesis 2:24 — [pause] And they shall be one flesh. [pause]” Important: * Do NOT change core TTS provider unless necessary * Focus on tuning delivery rather than replacing system --- CONSTRAINTS * Do NOT change backend concordance logic * Do NOT introduce semantic/AI interpretation * This is purely input/output enhancement --- DELIVERABLES * Working microphone input in web interface * Speech converted to text and integrated into search flow * Improved TTS narration with better pacing * Clean, stable implementation --- TIME ESTIMATE Expected: * 1 day (or less for experienced developer) --- NOTES This system is intended to be voice-first, so usability and simplicity are key. Typing will remain as a secondary option.