Challenges in a Web-Based Morse Code Translator Deployed on Microsoft Stack

Question

I’ve built a public Morse Code Translator website that converts text to Morse code and Morse code back to text, with support for visual output (dots/dashes), audio playback (beeps), and copy/share features. The application is currently hosted on a Microsoft-based stack (Azure App Service) and uses modern web technologies on the frontend with a lightweight backend for processing and logging. While the core functionality works, I’m facing several technical challenges related to performance, accessibility, and real-time behavior that I’d like guidance on from the Microsoft developer community.

The first issue is frontend performance and responsiveness when users enable real-time audio playback while typing. As users enter text rapidly, the app generates Morse signals on the fly, which can cause UI lag, especially on low-end devices. I’m currently using JavaScript timers for audio tone generation and debouncing input events, but I still see inconsistent behavior across browsers. I’d like to know best practices on the Microsoft stack (for example with Blazor WebAssembly or ASP.NET + SignalR) to handle real-time input without blocking the UI thread.

The second problem relates to accessibility and compliance. Since Morse code relies heavily on audio and visual cues, I want the site to be accessible for screen readers and users with disabilities. I’m struggling to balance ARIA labels, keyboard navigation, and live region updates without overwhelming assistive technologies. Are there recommended Microsoft accessibility guidelines or tooling (such as Accessibility Insights or specific ARIA patterns) that work well for dynamic, signal-based content like a Morse code translator?

Another challenge is scalability and cost optimization on Azure. Traffic is mostly bursty sometimes very low, sometimes spikes due to sharing or search traffic. I’m unsure whether Azure Functions, a minimal ASP.NET API, or static hosting with Azure CDN would be the most efficient approach. I’d appreciate advice on which Azure architecture is best suited for a utility-style website like this, where most logic can run client-side but still needs analytics, rate limiting, and basic API support. Very sorry for the long post

Answer 1

Dear @Emily Jack,

Thank you for reaching out to Microsoft Q&A forum.

I understand that you are navigating the transition from a standard web application to a high-performance, accessible utility. Based on your description and initial research, implementing real-time audio processing and a dynamic UI on the Microsoft stack often requires moving beyond basic JavaScript timers and leveraging native browser APIs along with scalable, serverless architectures.

Based on your description, your question appears to be more closely related to Azure architecture and advanced web application design. This forum primarily focuses on Office 365 products and their native features, and unfortunately, we have limited resources and expertise in Azure-specific scenarios.
To make sure you get the most accurate and helpful guidance, I sincerely recommend posting your query in the: Azure Community Support | Microsoft Azure. The members and experts there specialize in these scenarios and will be much better equipped to assist you.  

In addition, for issues of this complexity, it may be helpful for the Global Admin in your organization create a service request with Microsoft Support. A technical support engineer can perform a remote session to investigate the situation, verify the backend configurations, and run any necessary synchronization tools and provide targeted recommendations. If the issue requires further attention, they can escalate it to a specialized team for deeper analysis. Ask The Global Admin in your organization to create a service request with Microsoft support to get advanced technical assistance and diagnostics. For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin. If you don't know who your IT administrator is, please refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support 

For additional assistance, use this link to find the appropriate contact number from your region: Global Customer Service phone numbers - Microsoft Support 

I truly hope you get your issue resolved swiftly. Please know that even though I can't directly intervene, directing you to the correct, specialized support is the most effective help I can provide from my position. Thank you for your patience and understanding. Let me know if you need anything else.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

Answer 2

For your Morse Code Translator website hosted on the Microsoft stack, here are some best practices and recommendations to address your challenges:

1. Frontend Performance and Responsiveness

To improve performance and responsiveness, especially during real-time audio playback:

• Use Web Workers: Offload the Morse code generation to a Web Worker. This allows you to run scripts in background threads, freeing up the main UI thread and preventing UI lag.
• Optimize Audio Playback: Instead of using JavaScript timers, consider using the Web Audio API for more efficient audio generation. This can help reduce latency and improve responsiveness.
• Debouncing Input: Ensure that your debouncing logic is optimized. You might want to consider using a more sophisticated approach that can handle rapid input more gracefully, such as throttling the input events.
• Blazor WebAssembly: If you are considering Blazor, it can help manage state and UI updates more efficiently. Blazor's component model can help you build a more responsive UI without blocking the main thread.

2. Accessibility and Compliance

For accessibility, especially with audio and visual cues:

• Use ARIA Roles and Properties: Implement ARIA roles and properties effectively to ensure that screen readers can interpret the Morse code signals. For example, use aria-live regions to announce changes in real-time without overwhelming users.
• Keyboard Navigation: Ensure that all interactive elements are keyboard accessible. This includes providing clear focus states and allowing users to navigate using keyboard shortcuts.
• Accessibility Insights: Utilize tools like Accessibility Insights to evaluate your application and identify areas for improvement in accessibility compliance.

3. Scalability and Cost Optimization on Azure

For handling bursty traffic and optimizing costs:

• Azure Functions: Consider using Azure Functions for your backend logic. This serverless architecture can automatically scale based on demand and can be cost-effective for bursty traffic patterns.
• Static Hosting with Azure CDN: If most of your logic can run client-side, static hosting combined with Azure CDN can provide fast content delivery and reduce costs. This approach is particularly effective for utility-style websites.
• Minimal ASP.NET API: If you require server-side processing, a minimal ASP.NET API can be a good middle ground, allowing you to handle analytics and rate limiting while keeping costs manageable.

By implementing these strategies, you can enhance the performance, accessibility, and scalability of your Morse Code Translator application on the Microsoft stack.