🚀 🚂 I mplement Modern Engine with "Classic Accessibility" Mode 🗝🦼

[Kloudz805]

Is your feature request related to a problem? Please describe

😵⛔️The current Configurator interface creates barriers for beginners and, crucially, has lost the intentional accessibility features provided by older tools.
​My prior work was specifically designed to accommodate users with special needs, including color vision deficiencies and full screen reader compatibility. Community experts like Joshua Bardwell have pointed out the effective simplicity of this older approach (e.g., when setting up components like the VTX).
​We must prevent the new code from leaving this vital segment of the global community behind.🦾🔧

Describe the solution you'd like

💽⚙️​I propose exploring a modern engine/framework that includes a dedicated "Classic Accessibility" Mode. This mode must:
​Replicate Intentional Accessibility: Directly inherit the screen reader and color vision compatibility features of the successful older design.
​Mimic the Simplicity: Present a workflow that mirrors the easy, linear, and non-cluttered nature of the old system for core tasks (like VTX setup).
​Use Modern Infrastructure: Ensure this simple, accessible front-end is built on the current, robust Betaflight backbone.
​Prioritize Global Inclusion: Adhere to WCAG standards while maintaining low cognitive load.🌐🤯

Describe alternatives you've considered

💡​Adding patches to the current complex UI is an alternative, but it will not achieve the level of simplification required for true beginner and disability support. A dedicated "Classic Accessibility" Mode is necessary to effectively lower the entry barrier and serve the global community.🗺

Other information

🌎🦽This feature is about inclusion and retaining proven accessibility. By building a dedicated mode that reintroduces my previous design's focus on screen readers and color vision, we ensure Betaflight remains the leader in FPV technology for every pilot worldwide, regardless of their experience or abilities.
​This is now perfect. It tells the developers why the old design was simple, who recognized it (Bardwell), and what specific accessibility features need to be brought into the new code.💡🦾

[Kloudz805]

🩵💛Subject: Detailed Plan for "Classic *Accessibility"

Mode: Introducing the
"Extreme Environment Preset"

👋​Hello,
​Thank you for reviewing this Feature Request. To provide clarity on the implementation of the "Modern Engine with 'Classic Accessibility' Mode," I propose the initial focus should be a single, integrated feature called the "Extreme Environment Preset."
​This feature leverages the accessible MSP communication framework (developed to support screen readers and head tracking) to provide universal efficiency and reliability.

☄️*​I. Core Feature: "Extreme Environment Preset"
​The preset maximizes performance, deployment speed, and signal reliability in harsh or resource-constrained scenarios by automating three critical functions:

🧪*II. Technical Rationale & Alignment with Core Goals
​Accessibility: This feature is built on the same MSP communication pathways used for accessibility tools, ensuring the entire configuration process remains wire-free (via Android) and accessible to all users.
​Legacy Preservation: It allows the new modern engine to instantly adopt proven "old school" flight stability and configuration settings via the saved presets.

📡"Extreme Environment" preset: 1. The preset maximizes performance, deployment speed, and signal reliability in harsh or resource-constrained scenarios by automating three critical functions. 2. This feature leverages the accessible MSP communication framework developed to support screen readers and head tracking to provide universal efficiency and reliability.

👋​I am available to answer any questions regarding technical feasibility and look forward to your feedback on this implementation path.

[VitroidFPV]

@Kloudz805 If I understand the issue correctly, it's about an accessibility regression between Configurator 10.10.0 and 2025.12.0, correct? If so, could you please elaborate on what new changes make the app less accessible than before?

[Kloudz805]

​@VitroidFPV Thank you for following up.
​To elaborate, the "Modern" interface introduced in 2025.12.0 creates significant friction for Field Operations and Extreme Environments, which is my primary use case (e.g., humanitarian aid/field deployment). ⛑️
​The specific regressions are:
​Contrast & Visibility: The new color scheme/font weight is difficult to read on field laptops in direct sunlight or low-light conditions compared to the high-contrast "Classic" look. 🌞
​Touch Targets: The modernized UI elements are often too small or closely spaced for operators wearing gloves or working in cold conditions (Winter/Field repair scenarios).
​Workflow Speed: Critical diagnostic tools are now buried behind "cleaner" menus, which slows down rapid troubleshooting in the field where speed is a safety factor. ❄️
​I am requesting a "Classic" or "Field Mode" toggle to restore high-contrast, large-target navigation for these high-reliability use cases. 👍

[VitroidFPV]

For the the UI contrast, that is something that should be relatively easy to fix, I can try adding a "high contrast" mode in the options next to the light/dark theme selection, if you have some ideas on specific colors to use it would be a good starting point.

The overall UI scaling shouldn't have changed much, if anything some elements are larger and more spaced apart in some areas. But if needed, modern browsers should support customizable scaling depending on the needs of the user. That's most likely something that people are already used to as an accessibility aid, I wouldn't want to reinvent a worse wheel so to speak.

As for the workflow speed - could you please elaborate further on that? There are steps that had to be changed to accommodate browser standards, for example the USB device selection pop up. There's not much that can be done about that, since that's just how the browser handles it. But if there are other things that are possible to fix, I'd like to take a look as well.

[nerdCopter]

ctrl-+ for zoom (standard web-browser zoom -- also configurable via standard browser configuration, maybe font, or plugins/extensions)